Sprint 151 Progress Summary

February 9th - February 23rd

Executive Summary

Overall Summary

Sprint status is excellent. The Product Team had prioritized the following themes and tasks for Sprint 151 comprising 23 points.  Themes for the sprint included - 

  • Partner and Community support
    –  Forum discussions
    –  Support for the Federal Agencies
    –  Community support
  • X12 Audit Research and Design
    –  Meet with CMS to finalize Auditing requirements
    –  Complete requirements and design
  • Gateway Properties Refinement and Demonstration
    –  Finish gateway properties research and wrap up design
    –  Complete proof-of-concept and demo readiness
  • Technical Stories
    –  Test Direct poller setup
    –  Testing improvements, automation and cleanup

The team completed 27 points this sprint. The team worked towards creating an automated Direct test suite to test sending outbound Direct messages and validate the Direct transport. POM files were cleaned up to solve conflicting dependencies and ensure that all build and testing is managed at a central location for the product POM via Maven. The team worked on a draft design for X12 auditing and also provided the requirements wiki to CMS for further review and feedback. The Healthcare Provider Directory specification was reviewed and some initial POC/client effort was initiated this sprint.

Burndown:

 

Sprint Themes and related tickets for Sprint 151:

Partner and Community Support

  • Team supported with VA on an related to time out exception when multiple QD requests were sent to a trading partner.

    • CONNECT Product Team worked with the VA implementation team and suggested options to consider like increasing JVM heap size, utilizing WebLogic Server performance and diagnostics tools to analyze the server state, and setting up performance testing to determine loads that can be handled by the VA implementation environment. 
    • The CONNECT team tried to recreate the same issue on the local test environment - Tried to send 10 DQ requests/sec using LoadUI and got successful responses for all requests. Tried the same(10 DQ requests/sec) after a minute and got all the responses without any issue. Tried the same set of requests 10 times with an interval of 1 minute and still were not able to recreate the issue reported by VA. 
  • Another support issue from VA was related to Document Retrieve where in the VA was unable to target one of their trading partners.
    • The root cause of that issue as determined by the CONNECT team was that the 2010 DR Entity Interface was  being used to send out a DR message to a partner who supports only 2011 specification. VA should use 2011 DR Entity Interface to send out this information to the partner.

CONNECT Development

  • The team reviewed the Health Care Provider Directory specification and also started working on an HPD client utilizing SITE code for better understanding the functionality. 
  • Project Object Model (POM) files were cleaned up so that dependencies were declared in a central location.
    • All dependency information is declared only in Product/pom.xml, unless a specific module needs to make an exception to the rule.
    • Duplicate configuration should be declared at the lowest common POM (e.g., SoapUI configuration would go under SoapUI_Test/pom.xml instead of Product/pom.xml).
    • Unnecessary plugins / code generation was removed.
    • Unused dependencies were removed (when directly declared) or excluded (when transitively included).
    • Typos were fixed.
  • Created wiki page for X12 requirements and design, the design effort will be completed next sprint
  • Completed the effort related to creating new instances of VMs with email servers to support Direct parallel testing. This enables us to more efficiently test Direct especially at release time.

    • Add the new domain cert to Bluebutton Trustbundle 

    • Successfully tested the new Direct instance

  • Developed an automated outbound Direct test to validate Direct functionality in an automated fashion. This is the first step in automating the Direct service and including it in our regression/build.
  • POC for displaying gateway.properties was completed, including view, update and comments display. 
    • Testing and documentation (test cases and manual will be completed next sprint) for this first iteration of this enhancement.
  • Updated the System Admin Module JBoss Deployment Descriptor to use the default context-root

    • Currently context-root for Admin GUI is not set for JBoss Application Server in the deployment descriptor. Because of this the application server uses the Application name(<application name>.war) as the context root and it is different for each release/version. This was fixed.

JIRA Planning Board of Committed User Stories for Sprint 151:

Related Files for Sprint 151:

Sprint 151 code tag

Common-Types source

CONNECT-Webservices source