Versions Compared

Version Old Version 4 New Version Current
Changes made by

Greg Turner (Unlicensed)

Greg Turner (Unlicensed)

Saved on

Key

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

Feb 10 - Feb 24, 2014

...

Sprint status is excellent. The Product team initially pointed and prioritized the following themes and tasks for Sprint 125 comprising 40 points. The team completed 38 points for this sprint. The team completed all the tickets related to the primary themes for this sprint, there were several important themes including final partner support, CORE lib clean up HIMSS preparation, infrastructure cleanup and to begin release readiness including testing and documentation. There were several additional tickets pulled into the sprint with only one ticket for 2 points not being completed.  This ticket was for creating the 4.3 release test plan which was started but not completed it , this ticket was moved into Sprint 126.  

 

Burndown

Sprint Themes and related tickets for Sprint

...

125:

  • Partner and Community support
    NIST to fix
    • Continued work with the NIST team
    • (CONN-768)
  • A new CONNECT system was set up for NIST testing to separate it from the machine used for DIL testing, thereby providing the team with greater flexibility as we continue to support both efforts.(CONN-799)
    • Had a follow-up discussion with NIST. Pending issues see CONN-805
      • Support and testing efforts continued with NIST, discussed several topics and compared interpretations of specifications
        • Held web-conference meeting with NIST team on 2/18/14
      • Validated the new NIST environment setup in GFE (CONN-804) 
      • Tested the following NIST updates to validate required changes in their deployment
    • nesting. Open question with spec factory. CONNECT has not made any changes yet, we do have a backlog to allow for a single nested attribute statement. At this point it seems that NIST would need to fix to accept both flavors -
        • .  Both through nesting multiple attributes in a single statement and for a single statement for each attribute statement. Originally NIST would accept only the single attribute statement with
    • all attributes nested as well as support each attribute within its own attribute statement
    • Community Implementation support
        • Release
          • Worked with the VA team in their deployment of 4.2.1
        • rebranding.(CONN-798, CONN-783, CONN-772)
      • Sprint 116 rebranded to be Sprint 4.2.1. 
      • See wiki page for details and binaries - https://developer.connectopensource.org/x/YABWCg
        • eHealth Exchange Participant test cases were executed successfully
          • in a test environment 
            • Supported several meetings and email exchanges
            • Conducted research on a deployment issue with WebLogic 12c and windows (CONN-857) 
          • Reviewed delta in functionality between CONNECT and Aurion in support of Open Source community planning (CONN-852)
          • Researched and tested a persistent eHealth Exchange certificate issue affecting multiple organizations  
            • Conducted industry and exchange related research to isolate the issue
            • Tested with the VA, Conemaugh and MiHIN
            • Discussed and presented findings with Healtheway and Spec Factory
        • Confluence update/upgrade (CONN-706)
            • Prepared for migrating COnfluence
              • Completed the migration of Confluence to Atlassian On Demand
            • . .
          • Updated plugins and pages to remove the unsupported markups and macros/plugins.
            • Attachments moved to ftp site to facilitate migration
              • Verified the migration
              • Resolved any issues found with plugins or links. .
          • Security scan analysis and resolution
            • Awaiting confirmation and feedback from the DoD security team on the Fortify scan and security report responses supplied by the CONNECT Product team
          • HIMSS Demo and Conference preparation (CONN-

          ...

          • 759)
              • This was the primary focus in Sprint 124. The team addressed all the Critical and HIgh findings from Fortify. 
              • Some of the issues identified by the Fortify scan were fixed in code and some were addressed with documentation. See wiki page with details -  Fortify Install notes
            • HIEM was removed from the codebase (CONN-771)
              • HIEM was not refactored in 4.X and also included many security vulnerabilities in code that were discovered as part of Fortify. Since there is no partner in the Exchange using HIEM this service has been removed.
            • Testing Improvements
                • <jvm-options>-Dorg.connectopensource.enablejmx=true</jvm-options> has been permanently added to domain.xml template(CONN-775)
            • Infrastructure improvements
              • Ability to tag and generate binaries from any branch specified (CONN-786) which helps simplify the release process for binaries generation. Created the necessary environments to support the HIMSS demo and work (CONN-823) 
              • Rebranded the HIE portal with the CONNECT theme to support the HIMSS demo (CONN-824)
              • Ensured all supporting applications, test data  and the CONNECT universal client were installed and ready to support the HIMSS demo 
              • Performed internal dry runs and received sign-off with ONC for conference readiness (CONN-825) 
            • Testing Improvements
              • Pulled integration tests our of the build and replaced them with JUnit tests where necessary to contribute to a more stable build (CONN-808)
                • Added JUnit tests for the mail classes for Direct/ Address Parsing package (CONN-811)
                • Added JUnit tests for mail classes for XDR package (CONN-820)
                • Added JUnit tests for mail classes for Mail package (CONN-821)
            • Infrastructure improvements
              • Infrastructure migration for Terremark (CONN-778813)
                • Migration of the Direct RI and Mail servers
                • GFE cleanup of configurations and servers 
                • Inventory management and documentation
            • Direct functional enhancementsVerify Direct requirements and current approach. Notes from the discussion can be found at - https://developer.connectopensource.org/x/BQB2Cg
            • Moved mail package out of ConnectCore lib and into DirectCore. All direct greenmail tests were then moved out of DirectCore and into a new project, DirectCoreTest (CONN-810)
            • Unit tests for Remaining DirectCore Classes for Target Coverage, added more JUnits and the coverage reached to 80%.(CONN-853)
            • QA Task to build DirectCore, found total line coverage of 82.2% (CONN-854)
          • Preparation and begin 4.3 Release testing
            • Re-tested new features and bug fixes to ensure the new functionality is validated prior to the release (CONN-816)
            • Setup interop test environment on Linux with JBoss/ CONNECT 4.2.1 (CONN-826)
            • Start documenting the Release 4.3 test plan (CONN-815) Started but not completed by Sprint close
          • Bugs that were fixed
            • Extract slots always gets one last value from the slots list (Adapter) (CONN-484)
            • SAML Assertion AuthzDecisionStatement resource is passed from the adapters to the external parties 'as is', failing the DIL test MA-1092_AuthzDecisionStatement_Resource(CONN-612)Resource will always be updated to include the URI.Default SAML Issuer value being used in all SOAP Header Security sections even though a valid X509SubjectName is defined in the private SSL certificate (CONN-691)
            • Resolve known "statefulness" in unit tests, update JUnit tests so that all of the reported test cases can be run by themselves (CONN-800)
            • SAML Attribute PurposeOfUse missing namespace for the @type attribute(CONN-740)

          ...

          • CONNECT 4 Blogs and Forum posts

          JIRA Planning Board of Committed User Stories for Sprint 125

          * Issue Issues added to sprint after start time
          View in Issue Navigator

          Completed Issues

          KeySummaryIssue TypePriorityStatusStory Points (35)
          CONN-691Default SAML Issuer value being used in all SOAP Header Security sections even though a valid X509SubjectName is defined in the private SSL certificateBugMinorCLOSED3
          CONN-759As an adopter interested in interoperabilty and health data exchange, I want to see a CONNECT demo so that I understand how CONNECT is used to exchange health data and how it interacts with other supporting MPI and repository systemsUser StoryMinorCLOSED0
          CONN-800Resolve known "statefulness" in unit testsBugMinorCLOSED1
          CONN-804Validate the new NIST Test environment in GFE (GFE-ONC-WDEV12.connect.org -192.168.34.3)TaskMinorCLOSED2
          CONN-808As a CONNECT developer, I want integration tests moved out of the build (and replaced with JUnit tests when necessary) so that tests are scoped appropriately.User StoryMinorCLOSED0
          CONN-810Regression suite tests for GreenmailTaskMinorCLOSED2
          CONN-811Add JUnit tests for mail classes for Direct/ Address Parsing packageTaskMinorCLOSED3
          CONN-813Support for GFE/TERREMARK infrastructure activities for CONNECTTaskMinorCLOSED3
          CONN-816As a CONNECT adopter, I want new features and bug fixes are re-tested so that new functionality is validated prior to releaseUser StoryMinorCLOSED5
          CONN-820Add JUnit tests for mail classes for XDR packageTaskMinorCLOSED3
          CONN-821Add JUnit tests for mail classes for Mail packageTaskMinorCLOSED3
          CONN-823As a CONNECT developer, I want to set up an environment for a HIMSS 2014 demo.Technical StoryMinorCLOSED2
          CONN-824As a CONNECT developer I want to rebrand the portal with CONNECT theme to demo at HIMSS 2014Technical StoryMinorCLOSED1
          CONN-825As a CONNECT developer I want to do a dry run of the HIMSS 2014 demo with good data.Technical StoryMinorCLOSED2
          CONN-826Setup Interop test environment on Linux with JBoss/CONNECT 4.2.1TaskMinorCLOSED3
          CONN-852 *Review of Bug Fixes Made to AurionTaskMinorCLOSED2
          CONN-853 *Unit tests for Remaining DirectCore Classes for Target CoverageTaskMinorCLOSED2
          CONN-854 *QA Task for DirectCore Unit testsTaskMinorCLOSED0
          CONN-857 *Research VA deploy issue in WLS 12c WindowsTaskMinorCLOSED1
           
          View in Issue Navigator

          Issues Not Completed

          KeySummaryIssue TypePriorityStatusStory Points (2)
          CONN-815As a CONNECT adopter, I want a Release test plan for 4.3 so that the community understands how 4.3 has been tested prior to making it availableUser StoryMinorIN PROGRESS2
           
          View in Issue Navigator

          Issues Removed From Sprint

          KeySummaryIssue TypePriorityStatusStory Points (0)
          CONN-779As a CONNECT adopter, I want 4.3 to be install tested so that the installation is successfully validated in the supported environmentsUser StoryMinorOPEN