Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

OpenNCP Weekly Sprint Meeting

26th August 11:00 to 12:00  CET

Work RoadMap - epSOS 2 Services

1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > Completed
4º Sprint: 11Mar > 22Mar (2 weeks) Completed

...

  • Release OpenNCP 2.0.1 > 31 July, 2013 (Wednesday) 6th August

 

Agenda

a) Dissemination documentation progress

...

d) RoadMap consolidation (dates and features included)

 

 

Location

Skype (sirLicman) + Jira Board + MeetingWords (http://meetingwords.com/csPSTM2Iwm)

Participants:

Aarne Roosi <Aarne.Roosi@affecto.com>, 

...

Fredrik Dahlman <fredrik.dahlman@cag.se>,
[yes] Gareth Woodham <Gareth.Woodham@apotekensservice.se>, 

...

Ivo Pinheiro <ivo.pinheiro@iuz.pt>, 
[yes] Konstantin Hypponen <konstantin.hypponen@kela.fi>, 
Kostas Karkaletsis <k.karkaletsis@gnomon.com.gr>, 
[yes] Licinio Mano <licinio.mano@iuz.pt>,
[yes] Marcello Melgara <Marcello.Melgara@cnt.lispa.it>,

...

Mindaugas Ajauskas <mindaugas.ajauskas@lispa.it>, 
[yes] Norbert Repas <norbert.repas@elga.gv.at>,

...

[yes] Stéphane Spahni <stephane.spahni@hcuge.ch>,

 

 

 

MEETING NOTES

1. OpenNCP Documetation

 Request for content about epSOS OpenNCP for website & presentations (Kathrin - 19Ago)

        - Are there any documents with text I can reuse? any suggestions? any volunteers for initial drafting the text or review it?
        -- D3.B.2_App_A1_OSS_NCPDesign_V0.9_AR.docx >  - Open Source NCP Design (D3-4.B.2_App_A1_OSS_NCPDesign_V0.9-RC5.docx)
        -- NCP OS implementation v0.9-mustafa-wp3.b.docx
        -- Installation Manual 
        -- epSOS-OpenNCP-IWEEE_20130125.pptx
        
        ToDo:
        - Installation Manual (transform in Overview) > Gareth (review by Norbert)
        - OpenNCP Community and Artefacts > Inicial draft > LKM (reviewers Per and Konstantin)
        
        30-8 / 8 working days;
        epSOS Glossary
             OpenNCP (official definition) - epSOS NCP software publicly available under Open Source licensing; 
             OpenNCP Community (official definition) - Open group of people orchestrated by an agile software development methodology conducting effort on designing, coding, testing and delivering OpenNCP software;
             
            ToDo: LKM share this definitions with Kathrin

2. OpenNCP RoadMap

        TPM Shared RoadMap and resource effort allocation >> https://service.projectplace.com/pp/pp.cgi/r908758673
  • UPDATED with today meeting information (Release Dates + HR Availability)
        
         THERE IS NO AGREEMENT ON THE MANDATORY RECOMMENDATION ABOUT go under a  new PPT slot if you do a bum between V1 to V2 from the OpenNCP;
        - Inform the TPM that there are countries that informed they don't have availability for participating in another PPT;
        - Those countries also state that changes are not so significant, namely in the eP/eD scenario.
        
        2.0.2 Will there be one? What will Include? When can be released? For what purpose?
         - Transformation Manager UPDATE
         - Bug Fix
            - https://openncp.atlassian.net/browse/OP-10 - most likely fixed by the end of the week
            - Others BLOCKER, CRITICAL and MAJOR issues;
        - Release date 2013-09-11
        
        2.1.0 What can be included? When can be released?
            - MRO (Medication Related Overview)
            - TSAM-sync adaptation for CTS2 compliance
                - Testing strategy: how can we test this component without a server or a validation service on that?
            - Bug Fix  BLOCKER, CRITICAL and MAJOR issues;
        - Release date 2013-10-30

3. OpenNCP Support Issues

        Open ISSUES on the Support board > https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2

a) Dissemination documentation progress

- LKM: shared the terms for the glossary;
-- Kathrin: witing feedback;
-- Marcello: for the website, it is enough to provide 1 line: "an Open Source version is publicly made available.
in addition the flyer: http://www.epsos.eu/fileadmin/content/pdf/epSOS_Technical_Aspects_2012.pdf has to be revised. it is just two pages in total 
-- [ACTION] LKM: epSOS Technical Aspects > 
-- [ACTION] Norbert Review available 30 August!!!
---- [NR] Short Note: On Tuesday (27/08/2013) and Friday (30/08/2013) I am out of office, so in the worst case the review will be completed on Monday. thx.

b) Bug Fixing progress

https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2

c) TransformationManager update progress

- (Gareth available today and tomorrow): - dificult to understand what has changed since last version

d) RoadMap consolidation (dates and features included)

- PPT need for PNs that adopt 2.0.2?
-- [LKM] OpenNCP Recommendation to TPM
-- [OpenNCP Comm] believes that there is no need for doing that;
-- [MM] Relaxation may be accepted by TPM, but each PN is responsible for there implementation;
-- [MM] which are the minimal test to do, having in mind jump from V1 to V2 (Simplification PPT)???
---- [KTT] all PPT tests could be skipped, except documents validation and e2e testing;
---- [NR] A test has meaning and purpose only when it is performed as detailed as possible. I´v tried it in the past with ClosedSourceOpenNCP incl. Scrutiny tests and so on. Only in this case is it possible to detect errors. But we have reached such a stage in the project where the requirements to fulfill and to behave consistently becomes more difficult. This role should be adopted and monitored by the regression automation, where possible.
---- [GW] We totally agree that a suite of regression tests should be performed when changing version, minor or major doesn't really matter.  Both maj/min releases can potentiallyt introduce new bugs
---- [GW]  we feel that regression tests hsould be a subset of the ppt test suite.  countries upgrading a version and doing ppt should do regression tests only, not full ppt
---- [GW]  full ppt requires large effort from country.  this will deter countries from upgrading, many may choose to stay on old version.,  this creates maintenance problems
---- [LKM] the V1 to v2 jump also had big improvments and bug fixes. What tests should be done regarding those changes? Post this uqestion to Kostas and Marcelo fonseca
---- Probably the solution may be NOT REGRESSION TEST but a simplified QA stage before entering operation with new version.
- RoadMap
          OSS NCP V2.0.2                      2013-09-10   Transformation Manager + Emergency Scenario + Bug Fixing       
          OSS NCP V2.0.3 (after PPT)   2013-10-02   OPERATION   Ready for: PAC + HCER epSOS 2 Services   
          
          OSS NCP V2.1.0                      2013-10-30   PPT Ready for: MRO + TSAM-sync (adaptation for CTS2 compliance)       
          OSS NCP V2.1.1 (after PPT)   2013-12-05   OPERATION   Ready for: ?? 


NEXT Steps


  •      Next meeting - 2nd - August 12hCETSeptember 15h00 CET