sprint 103 review / sprint 104 planning march 25, 2013
TRANSCRIPT
Sprint 103 Review / Sprint 104 PlanningMarch 25, 2013
Sprint Resource Pages
• For this sprint, visit: https://developer.connectopensource.org/display/NHINProgress/Sprint+103
• For next sprint, visit:https://developer.connectopensource.org/display/NHINProgress/Sprint+104
• For information on the CONNECT 4.0 release, visit:https://developer.connectopensource.org/display/CONNECT40/CONNECT+4.0
• For information on the CONNECT 4.1 release visit: (Currently Under Construction) https://developer.connectopensource.org/display/CONNECT40/4.1+%28Draft%29
2
Sprint 103 - Community Contributions
• Open forum for community members to shareo Their work of the last two weeks
o Their needs from CONNECT
o Ideas and suggestions
• Community contributionso UPMC - CONNECT 4.0 Alpha 1 / WebSphere
o SSA - CONNECT 4.0 WebSphere
3
Sprint 103 Summary - Cumulative Flow
4
To Do
In Progress
QA
Done
Sprint 103 Summary - Burndown Chart
5
Sprint 103 Summary –Sprint Stats
• Points committed = 24
• Pulled out 1 point of effort, totaling 23 points for sprint
• Points remaining (unclosed) at end of sprint = 4
• Points completed in sprint (velocity) = 19
6
Sprint 103 – Themes & Tasks
• 4.0 Partner and Community Support– SSA 4.0 install on WAS
– CMS-CCSQ 4.0 install on WL 11g or 12c
– CMS-OFM 4.0 install on WAS 7 JDK 1.7
– Respond to IHS re the Direct ticket (CONN-279)
– Community support through forum responses and guidance
• 4.1 Enhancements– Multi Spec QD/ RD End point enhancement for DoD/SSA (pending DE&I approval)
– Installation improvements through community engagement
– Continued development of a robust CI and automated test environment
– JBoss - (CONN-25) in the Ordered features list
• Product Backloghttps://issues.connectopensource.org/secure/VersionBoard.jspa?
selectedProjectId=10140
7
Sprint 103 - What We are Showing Today4.0 Community and Partner Support
• Work Completed to Support the CONNECT Community and Federal Partners– CONN-310 Standardize recommended java options (heap sizes, perm sizes)
across installation instructions
– CONN-288 Provide support for SSA and their efforts to download and install CONNECT 4.0 into their development environment
– CONN-279 As a CONNECT adopter, I want CONNECT 4.0 to be tested on WebSphere 7.x to validate whether CONNECT will work in my
preferred environment
– CONN-278 As a CONNECT adopter, I would like assistance installing and configuring "Direct only" for CONNECT 4.
– CONN-183 Missing DIRECT_ERROR event in use case (Direct-A-Thon)
– CONN-74As a CONNECT adopter/developer I want a clean property file (gateway.properties) so that there is no confusion with regards to
the unused properties or default values.
8
Sprint 103 - What We are Showing TodayCONNECT 4.1
• CONNECT 4.1 JBoss Support– Another strategic application server the community wanted CONNECT 4.0 tested with
was JBoss
– JBoss provides an open source app server that supports FIPS requirements
– CONN-303 - As a CONNECT adopter, I want CONNECT to be deployable in JBOSS, so that I can use my preferred application server for health data exchange
– CONN-314 - Add JBoss 7 profile
– CONN-315 - Create JBoss 7 configuration info
CI and Build Improvements– A key goal for 4.1 was to increase the JUnit code coverage and reduce FindBugs
errors for the Connect Core Library
– The initial target was to remove all possible bugs from the library using the FindBugs tool and increase both our line and branch coverage by 20%
– https://developer.connectopensource.org/display/CONNECT40/4.1+Code+Coverage
9
Sprint 103 - What We are Showing TodayCONNECT 4.1
• CONNECT 4.1
Resolved Support Tickets– CONN-319 Fix testMpi resource so it doesn't always get updated
– CONN-307 Interop testing for 4.1
– CONN-305 Reverification testing for 4.1
– CONN-304 Regression testing for 4.1
– CONN-301 As a CONNECT user, I want the Direct feature to work out of the box on binary installations, so I can set up Direct more easily.
– CONN-299 4.1 patch release test plan
– CONN-298 release 4.0 as 4.1
– CONN-297 merge all fixes in CONNECT_integration into branch 4.0-integration in order to prepare to release 4.1
– CONN-295 Interop: Update harness for repeatable Ldev11 tests
– CONN-292 CONNECTSamlAssertionValidator Logic needs review
10
Sprint 103 - What We are Showing TodayCONNECT 4.1
• CONNECT 4.1
Resolved Support Tickets– CONN-280 PatientDB implementation does not work
– CONN-244 Create QA Mail Server
– CONN-92Remove NHINC_PROPERTIES_DIR environment variable
– CONN-61GUIs deployed in the EAR (GF) cause the admin console to misbehave after restart
– CONN-40Audit Log Transforms (PD) throws exception in server log
– CONN-37NPI SAML attribute is not supported in CONNECT
11
Sprint 103 - What We are Showing TodayCONNECT 4.0 Implementation Support
• CONNECT 4.0 Implementation Support– Forums + Community Support
• http://www.connectopensource.org/developer-resources/forums
12
Sprint 104 - Proposed Themes
• 4.1 Release Preparation– Complete functional and regression testing
– Continue with installation testing
– Complete and finalize supporting documentation
• 4.0 Partner and Community Support– CMS-OFM 4.0 install on WAS 7 JDK 1.6
– Support CMS with their planned Direct Pilot
– Provide support for SSA testing of 4.0
– Community support through forum responses and guidance
• Incorporate CI Testing Improvements to Additional App Servers
• Start Work on Design for Enhancements to Auditing
• Product Backloghttps://issues.connectopensource.org/secure/VersionBoard.jspa?selectedProjectId=10140
13
CONNECT 4.0Community Announcements
• CONNECT Awareness
– Open sprint review and planning meetings
Next sprint meeting will be April 8th
– CONNECT 4.0 Blogs and Forum posts
– CONNECT 4.0 user group meeting being planned for mid to late May at George Washington University
14
Questions and Discussion
15