1. National Cancer Institute caCORE Software Developers Meeting Agenda and meeting notes July 26, 2007

2. National Cancer Institute 2 2 Agenda Administrative Announcements/Reminders caCORE ‘4.0’ Scope Update caCORE Cross-product Feature Update caCORE Documentation Discussion Q&A

3. National Cancer Institute 3 3 Announcements New caDSR Team Members –Ekagra JJ Maurer, Charles Griffiin, Tejas Dave, Denis Avdic –ScenPro: Anupama Chickerur –QA resource : Jyothsna Chilukuri Others? –EVS QA resources, new developer Summer Conferences: –CDC PHIN – August 26-28 Atlanta Vocabulary Standards and Interoperability Knowledge management –Arch/VCDE FTF August 6-8 Georgetown Other than Annual meeting, most relevant to caCORE developers

4. National Cancer Institute 4 4 caDSR Team Secondary Responsibility Primary Responsibilit y AnuPrernaSumanaChristopheTejasSteveLarryTBD Anupama Chickerur Prerna Aggarwal ODI Metadata Loader (new) Database Design, PL/SQL API, Concepts, User Accounts Admin Tool, caBIO Views, Excel Loader Sumana Hegde Form Builder, eDCIeDCI Christophe Ludet GME ODI GME Semantic Tools Tejas Dave UML Model Browser CDE Browser Steve Alred Concepts ODI User Reviews (PM) Larry Hebel Curation Tool User ReviewsODI Sentinel, Freestyle, Gforge, Build Scripts J-J Maurer (PM) caMDR Charles Griffin (PM) caMDR Denis Avdic caMDR

5. National Cancer Institute 5 5 caCORE 4.0 Scope update caCORE into the Future –Individual services – caDSR, EVS, Common, caBIO (move to ICR Product Line) –Version numbering SDK version used to build the service? Major release for the product? E.g. major release but used SDK 3.2.1

6. National Cancer Institute 6 6 5/1/07 5/15/07 6/1/07 6/15/07 7/1/07 7/1507 8/1/070 8/15/07 9/1/07 9/1507 9/24/07 9/24/2007 caCORE 4.0 GO LIVE caCore 4.0 Release Timeline 6/1 Cross- Product Scope Complete 6/25 Cross- Product Design Reviews Complete 7/1 LexBIG and caCORE API Iteration 2 Complete 7/15 Cross- product Design Feature Freeze Last 3.2.x.x Unit Test complete 8/1 Last 3.2.x.x Product Increments In Production 8/24 Dependent Products Regression Testing and QA Complete UAT, Documentati on, Staging 5/1 caCORE caBIO LexBIG Iteration 1 Complete 6/8 caCORE LexBIG API 3.2.+1 “sniff” test Complete 6/11 Domain Model Changes Approved 7/24 SDK 4.0 Beta Unit Test caCORE 4.0 Tech Stack Regression Complete 8/10 Dependen t Products New Features Unit Test Complete 8/3 caCORE 4.0 API Dependent Regression Unit Test Complete QA

7. National Cancer Institute 7 7 caCORE Cross-Team Tech Review candidates GME Namespaces –GME Namespace name Domain Model – August 6 caAdapter, SDK, SIW/UML Loader, UML Model Browser teams, caGrid 2.0 ArgoUML –SDK 4.0 – in QA –SIW/UML Loader, caAdapter to follow Inherited Attributes –SIW/UML Loader 3.2.1.1 – August –SDK, caAdapter impact

8. National Cancer Institute 8 8 caCORE Documentation Update Splitting the APIs/Services provides opportunity to develop standalone documentation –1) End User documentation: one document per product. We should think of each of the unbundled caCORE services as “Product” (caDSR Services, EVS Services, Provenance Services). –2) Technical Documentation: architecture documentation, server architecture schemas, installation instructions, etc – still create one “caCORE” document, one section per product, again so they can be updated independently. –3) Software Developers Guide: “A roadmap for developing interoperable services using caCORE products”: (or something like that) One for the product line that includes only those products needed to support the overall process. This guide would describe the process and steps, e.g. the tags that need to be created, etc… and link to point to the individual users guides rather than duplicating material.

9. National Cancer Institute 9 9 caCORE Documentation Update WIKIs? Current process –writing and editing in Word and transferring edits to Adobe FrameMaker and reviewing and publishing in pdf is cumbersome. Future –In light of the new documentation proposed, opportunity to look into use of wiki SemanticMediaWikis MediaWiki –Advantages are real-time writing and editing vs current processes. –Issues Timing for 4.0? –Each team will establish appropriate timing to move to Wiki –caDSR team will look into this for next release (caDSR 4.0) which will be late 2007 or early 2008 Document Roadmap –Taking existing Content, transitioning to a wiki, and creating a look and feel on a set of wiki pages Server for MediaWiki? –Update from Frank on plan for EVS semantic media wiki, can we piggyback? –Probably, semantic media wiki adds features that would allow us to leverage links to other content and to EVS concepts from within our documentation Training? –If widescale adoption, caCORE developer training/workshop would be needed Conversion of existing content –Existing tools are available that convert from.doc to wiki –Custom converters could be developed if needed

10. National Cancer Institute 10 Notes caCORE Futures: –Teams should think about most appropriate versioning strategy and if not sure, bring to caCORE developers for feedback ArgoUML support –SDK team will post the test ArgoUML file in XMI Handler project DOCs page: –http://gforge.nci.nih.gov/projects/xmihandler/http://gforge.nci.nih.gov/projects/xmihandler/ –Suggestion to change references to the model files from “the XMI” file to “UML Model File” because ArgoUML exports a.xml file, while in EA we have exported.xmi Inherited Attributes –SIW team will post a sample test file to Semantic Integration Tools project for other teams to test to ensure that new tagged values don’t break SDK or caAdapter: –http://gforge.nci.nih.gov/projects/siw/http://gforge.nci.nih.gov/projects/siw/ Documentation –All teams will begin creating 3 types of documentation for 4.0 releases –Each team will determine when/whether to implement documentation on Wikis in future –caDSR team will look into wiki for 4.0 documentation –caGrid wiki : http://www.cagrid.org/mwiki/index.php?title=CaGrid http://www.cagrid.org/mwiki/index.php?title=CaGrid