Sep 09 - Sep 23, 2013

Executive Summary

Overall Status

The team completed 13 out of 17.5 points for this sprint.

Burndown

Cumulative Flow

Sprint Themes:

Complete final automation steps for nightly run of Regression test suite
- Enable a nightly automated run of the enhanced Regression suite with the ability to switch between Standard and Passthru operating modes
- CONN-594 Some of the Bimodal regression suites fail when running automatically in Linux environment (Windows works)
- CONN-579 Create a new regression suite to validate that UDDI is correctly looked up for all services
- Still Open
  - CONN-583 Some of the Bimodal regression suites fail when running automatically – passthru mode
  - CONN-593 Embedded glassfish does not start a JMX listener, required for regression tests to set passthru mode
Meaningful Use certification testing support
- Work with the NIST team to ensure they have support they need to develop the MU2 test tool utilizing CONNECT as the test gateway
- CONN-592 In person meeting with NIST team to discuss issues found with MU certification testing and the CONNECT gateway
- Addressed a couple of issues to support MU testing
  - CONN-588 WS-Addressing Header “MustUnderstand”
  - CONN-560 Accepting an empty URI reference ("") for the Resource attribute of the the Authorization Decision Statement
Requirements and design for database-less transaction logging and Wiki page
- Meet the needs of adopters with multi-tier architectures where the gateway and databases reside on different tiers
- CONN-590 Create wiki page for requirements and design related to database-less transaction logging - Link
- CONN-335 & CONN-587 As a Federal Partner, I want a database-less implementation of transaction logging, so that I can deploy CONNECT 4.x without a database at the gateway
- This effort also identified needed work with the Regression suite CONN-599 & CONN-601

Support community with Release 4.2 deployments
- Working with NIST testing 4.2 against MU2 use cases
- Assisted SSA installing 4.2 into their dev environment
- Actively supporting CMS and DoD with 4.2 testing
- Working with several community members testing and working with 4.2
- A couple are moving closer to entering eHealth Exchange participant testing
- Supporting other vendors via the CONNECT forums about leveraging 4.2
Start review of DoD Fortify scan results
- DoD has been performing security scans on each CONNECT release with the Fortify application. They supplied the Product team with the most recent report for Release 4.2
- CONN-594 Research Fortify scan issues/results so that we can come up with plan to address issues --Wrote up an initial finding and plan for pursuing deeper analysis of the potential issues

Prioritized JIRA Planning Board of Committed User Stories for Sprint 116

(https://issues.connectopensource.org/secure/VersionBoard.jspa?selectedProjectId=10140)

Related Files

Sprint 116 review notes - Notes about the work completed in s116. (Also includes work planned for s117)
Sprint 116 planning notes- Notes about the work planned in s116. (Also includes work completed for s115)
JIRA. See Sprint 116
Sprint 116 code tag

Browser not supported