Sprint 121 Progress Summary
Dec 2 - Dec 16, 2013
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 121:
- Partner and Community support
- Forum discussions
- Support community with Release 4.2 deployments and questions
- Continued support of the CMS 4.2 (Sprint 116) implementation
- Worked with SSA on infrastructure requirements for a future 4.2 or 4.3 implementation in their environment
- Brought the following two issues to the Spec Factory that came up when testing for both NIST MU2 and DIL
- It appears that the version of the IHE spec that our NHIN specs reference (specifically Document Submission, but I believe this will be true for all the underlying IHE specs), requires the WS addressing replyto element. Per our conversations with the folks at NIST, they informed us that IHE is voting on a CP during the next ballot to remove replyto as a requirement. This situation we are in is the NIST tool isn’t going to add this element because it’s being removed from required status, but the DIL will fail us if we don’t through a soap fault if the replyto is missing. We can work around this with a number of solutions, but guidance from the spec factory would help shape our solution.
- The authorization framework is unclear with regards to the nesting of attributes within one or multiple attribute statements. For what it’s worth, the attributestatement element in SAML is repeatable, as well as the attribute within the attributestatement. CONNECT currently creates a separate attributestatement with one attribute in each attributestatement, the DIL seems to like this format (but they use CONNECT, so maybe this is suspect). The non-normative example in the spec shows one attributestatement with a series of (6-8) attributes – the nist tool is expecting this.
- Continued testing of HIEOS with CONNECT codebase (CONN-722)
- Documentation has been updated - HIEOS Document Registry and Repository
- NIST tool testing with CONNECT (CONN-711/ CONN-713)
- Successfully exchanging(sending and receiving) Document Submission messages with http://transport-testing.nist.gov/t
- Supported and attended the CONNECT Open Source community open contribution meeting (CONN-714)
- Security scan analysis
- Address Unreleased Resource: Streams Fortify scan results (CONN-677)
- Address Often Misused: Authentication Fortify Scan results (CONN-680)
- Address Privilege Management: Overly Broad Grant Fortify scan results (CONN-681)
- Research CONN-678 and provide a POC; Address Password Management: Password in Configuration File Fortify scan results (CONN-724)
- Direct enhancements - This sprint was focused on the responding side of QoS
- Provide the ability to request delivery notification messages from Receiving STAs, so that I am informed of a successful or failed delivery (CONN-198)
- Provide the ability to provide Positive delivery notification message(MDN) to the Sending STA so that the sender may be informed of a successful delivery (CONN-199)
- Setup Connect With Latest Direct 3.x Jars (CONN-720)
- Create and send an MDN dispatched message after a message has been successfully sent to the edge client (CONN-723)
- Ongoing Custodial Agent Duties
JIRA Planning Board of Committed User Stories for Sprint 121
Sprint 121 Ticket Summary
View Sprint 121 in Issue Navigator
Closed Sprint 02/Dec/13 7:32 PM - 16/Dec/13 2:38 PM
Completed Issues | |||||
|---|---|---|---|---|---|
| Key | Summary | Issue Type | Priority | Status | Story Points (22) |
| CONN-198 | As a CONNECT adopter sending Direct messages I want to have the ability to request delivery notification messages from Receiving STAs, so that I am informed of a successful or failed delivery. |  User Story |  Minor |  Closed | 2 |
| CONN-199 | As a CONNECT adopter receiving Direct messages, I need the ability to provide Positive delivery notification message(MDN) to the Sending STA so that the sender may be informed of a successful delivery. | User Story | Minor | Closed | 3 |
| CONN-677 | Address Unreleased Resource: Streams Fortify scan results |  Task | Minor | Closed | 2 |
| CONN-680 | Address Often Misused: Authentication Fortify Scan results | Task | Minor | Closed | 1 |
| CONN-681 | Address Privilege Management: Overly Broad Grant Fortify scan results | Task | Minor | Closed | 1 |
| CONN-711 | TTT - Successfully validate messages with NIST-hosted TTT during sprint 121 | Task | Minor | Closed | 2 |
| CONN-713 | Support NIST with their CONNECT instance/install | Task | Minor | Closed | 1 |
| CONN-714 | Support discussion on open source community/contribution for CONNECT | Task | Minor | Closed | 1 |
| CONN-720 * | Setup Connect With Latest Direct 3.x Jars | Technical Story | Minor | Closed | 2 |
| CONN-722 * | Update HIEOS DocRepository Project to load Document into HIEOS Repository | Task | Minor | Closed | 2 |
| CONN-723 * | Create and send an MDN dispatched message after a message has been successfully sent to the edge client. | Task | Minor | Closed | 2 |
| CONN-724 * | Research CONN-678 and provide a Poc | Task | Minor | Closed | 3 |
| * Added after start of sprint. | |||||
Issues Not Completed | |||||
| Key | Summary | Issue Type | Priority | Status | Story Points (2) |
| 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 |  Resolved | 2 |
Issues Removed From Sprint | |||||
| Key | Summary | Issue Type | Priority | Status | Story Points (3) |
| CONN-678 * | Address Password Management: Password in Configuration File Fortify scan results | Task | Minor |  In Progress | 3 |