Sprint 122 Progress Summary

Dec 16 - Jan 13, 2014

Executive Summary

Overall Status

Sprint status is excellent. The Product team initially pointed and prioritized the following themes and tasks for Sprint 121 comprising 13 points realizing there would be additional tickets pulled into the sprint once certain guidance was received.  After receiving this guidance and making great progress on certain originally scoped tickets an additional 7 tickets were pulled in to the sprint for an additional 17 points.  Two of these were not completed totaling 5 points.  Overall the team completed 22 points for this sprint.

Note - The velocity was higher this sprint due to the unexpected straightforward resolution of some of the Fortify scan tickets.

Sprint Themes and related tickets for Sprint 122:

• Partner and Community support
  • Forum discussions
  • Support community with Release 4.2 deployments and questions
    • Support of the CMS's 4.2.1 production release
    • Worked with SSA on testing 4.2.1 with WebSphere 8.5.5
      • Database installation
      • Necessary wars installed inside the ear
      • Configuring keystores  
    • Brought the following two issues to the Spec Factory that came up when testing for both NIST MU2 and DIL
      • Resolved ethnicity issue as a search parameter
      • xsi:type attribute required or not (PurposeOfUse)
    • Still pursuing the following two issues with the Spec Factory from testing with both NIST/ MU2 and Healtheway/ DIL
      • The version of the IHE spec that NwHIN specs reference, requires the WS addressing replyto element. IHE is voting on a CP during the next ballot to remove replyto as a required
      • The authorization framework is unclear with regards to the nesting of attributes within one or multiple attribute statements
    • Implemented a fix to support both RSA and x509 certificates (CONN-735) final testing is still pending
    • NIST tool testing with CONNECT (CONN-725)
      • Successfully exchanging (initiating and receiving) Document Submission messages with http://transport-testing.nist.gov/t
      • Resolved final few attribute discrepancies for initiating
      • Migrated and tested with NIST and the DIL in new GFE environments
    • Supported and attended the CONNECT Open Source community open contribution meeting (CONN-714)
• Continued testing automation and improvements
  • There were continued efforts this sprint with the testing infrastructure cleanup (CONN-734)
  • This clean up and consolidation will support more efficient release testing for 4.3
  • Investigate options to create a regression test to validate that we don't require a security header in the Nhin interface response messages (CONN-627)
    • Not able to configure SSL in SOAPUI and also no solution found to fix this issue in SOAPUI
• Security scan analysis
  • Received our license for Fortify
    • Downloaded and installed software
    • Verified accounts and infrastructure requirements
  • Fix assertion id in SAML attribute statement (CONN-732)
  • Review Fortify XML Validation tickets (CONN-730)
  • Scheduled meeting with DoD for Sprint 123 to discuss and compare Fortify scan reports

• Direct enhancements - This sprint was focused on the responding side of QoS
  • Negative delivery notification message to the Sending STA to inform of message delivery failure (CONN-200)
  • Using Direct I do not want to relay MDN notifications back to the edge client to avoid redundant notifications and be spec compliant (CONN-633)
  • Fork Direct 3.x and Upgrade Direct 3.x to use CXF 2.7.3 (CONN-726)
    • Updated POMs for config-ui and config-service to use cxf-bundle-2.7.3, and updated non-security Spring libraries to 3.0.7-RELEASE
  • Ticket still in progress at the end of the sprint
    • Create Config UI and Config Service as submodules which would be referenced by the Direct Core; update Direct Maven Scripts for RI Config Services (CONN-727)
  • Not started during the sprint
    • Update CONNECT direct implementation to use config services instead of config xml (CONN-728)
    • Test outbound messages using SMTP and SOAP to an organization using trust bundles and not using trust bundles (CONN-729)
• Additional Work Performed
  • CONNECT 4.x builds broken due to expired certificate in SoapUI ValidationSuite (CONN-733)
• Ongoing Custodial Agent Duties

JIRA Planning Board of Committed User Stories for Sprint 122

(https://issues.connectopensource.org/secure/RapidBoard.jspa?rapidView=1&view=planning&versions=visible)

View in Issue Navigator Completed Issues
Key	Summary	Issue Type	Priority	Status	Story Points (16)
CONN-200	As a CONNECT adopter receiving Direct messages, I need the ability to provide Negative delivery notification message to the Sending STA so that the sender may be informed of a failed delivery.	User Story	Minor	Closed	2
CONN-627	Investigate options to create a regression test to validate that we don't require a security header in the Nhin interface response messages.	Task	Minor	Closed	2
CONN-633	As a CONNECT adopter using Direct I do not want to relay MDN notifications back to the edge to avoid redundant notifications and inorder to be spec compliant	User Story	Minor	Closed	2
CONN-725	Support NIST testing in sprint 122.	Task	Minor	Closed	2
CONN-726	Fork Direct 3.x and Upgrade Direct 3.x to use CXF 2.7.3	Task	Minor	Closed	3
CONN-730	Review Fortify XML Validation tickets	Task	Minor	Closed	1
CONN-732 *	Fix assertion id in Saml attribute statement	Bug	Minor	Closed	1
CONN-733 *	CONNECT 4.x builds broken due to expired certificate in SoapUI ValidationSuite	Bug	Minor	Closed	1
CONN-734 *	Setup DIL/NIST Test environment in GFE	Task	Minor	Closed	2
View in Issue Navigator Issues Not Completed
Key	Summary	Issue Type	Priority	Status	Story Points (7)
CONN-184	As a Direct HISP implementer using CONNECT, I want CONNECT to support trust bundles to minimize configuration overhead for setting up multiple anchors and support the trust communities that use trust bundles	User Story	Minor	Open	0
CONN-194	As a Direct HISP implementer using CONNECT, I need a GUI for trust bundle configuration so that configuring anchors and trust bundles is made easy from an implementation perspective	User Story	Minor	Open	0
CONN-727	Update Direct Maven Scripts for RI Config Services	Task	Minor	In Progress	2
CONN-728	Update CONNECT direct implementation to use config services instead of config xml	Task	Minor	Open	2
CONN-729	Test direct after completing trust bundles	Task	Minor	Open	3