COSMOS SDD Minutes 25MAR08

Logistics

• Date: 25MAR08
• Time: 9AM EST
• Attendees: Julia McCarthy, Chris Mildebrandt, Charlie Halloran, Mark McCraw, Merri Jensen, Josh Hester, Jeff Hamm, Jason Losh, Robert DeMason

Agenda

1. Review minutes from last week
2. Cover using SDD to install COSMOS possibilities
   • Create an SDD for installing COSMOS
   • Marry change analyzer code to SAS extraction code and UI
   • Create an SML profile of the COSMOS install
3. Deployment runtime use case review -- need these moved to COSMOS use case section
4. Follow-up on action items
   • Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
   • Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements. (Jason)
   • Look into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08. (Jeff - ongoing)
   • Mark W. to move forward with vote for Eric as code committer with COSMOS. Jason has already been approved. (Jason to nominate Eric)
   • Charlie to ask Mark W. about whether package name changes will be needed for Change Analyzer code.
   • Mark M. or Jeff to send Merri the link to the P2 findings wiki.
   • Charlie needs to submit COO for Change Analyzer.
   • Runtime use cases need to be rewritten.

Minutes

1. We had a separate call with some folks last week to discuss what would be a good set of functionality to get into COSMOS for i11 release.
2. Jason also had a call with Mark W. yesterday to have more discussion b/c he couldn't attend the earlier meeting.
   • There are three items that we would like to accomplish
     1. Capture the COSMOS installation with the SAS MIT tooling (including Tomcat checking)
        • Mark M and Jeff working on
     2. Connect the Change Analyzer code with the SAS Extracter code
        • Julia - The Change Analyzer doesn't resolve the plan, this code would have to be added
        • Jason - create CL1 SDD for COSMOS and run it through Change Analyzer, and could come up with basic resolution algorithm for it (do everything in baby steps rather than trying to tackle a comprehensive resolution algorithm)
        • Julia, Mark M, and Jeff to create CL1 SDD, Julia and Chris to run through Change Analyzer (if ready before code is submitted)
     3. SML Profile for COSMOS
        • Merri and Jason to work with COSMOS SML experts
3. Deployment Use Cases have been updated to be more like the COSMOS use cases, the implementation/design details that we included initially will be added as "Details" or included in the associated Enhancement Requests.
   • Everyone needs to review the updated use cases (at the very bottom of COSMOS Use Cases for SDD) and submit comments by tomorrow.
   • Revisions will be made and the use cases will be moved over to the COSMOS Use Case page by the end of the week.
   • From last week it was suggested that we need to include "inputs to the use case", which are the different inputs to the use case to help determine what the runtime does, there are infinite possible types, so for example an SDD with no requirements, a CL1 SDD with an RPM, etc. Would include these inputs with ER.
4. Action Item updates
   • Charlie updated the use cases and is doing the COO today and everything should be submitted to IBM legal this week.
   • Chris has done the Change Analyzer code scan and Julia submitted all the appropriate documentation that is needed to send to IBM legal. Will probably take a week or so to get back.
   • Jason has started the decision matrix and is including weights for the potential technologies. Right now java looks like it will be the best technology. (I'll get the URL from Jason.)
   • Jason is going to submit Eric for committer status while he is on vacation.
   • P2 has been pretty quiet since EclipseCon flurry of activity.
     • Jeff and Mark are keeping an eye on it, and are making updates to their P2 Analysis page: COSMOS SDD Runtime P2 Review

Action Items

1. Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
2. Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements.
3. Look into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08.
4. Jason to move forward with vote for Eric as code committer with COSMOS.
5. Charlie to ask Mark W. about whether package name changes will be needed for Change Analyzer code.
6. Everyone review the new deployment use cases by tomorrow, then move use cases and "details" into COSMOS Use Cases by end of week.
7. Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
8. Julia to work with Jeff and Mark M. to create CL1 SDD for COSMOS and work with Chris to run it through the Change Analyzer.
9. Mark M. and Jeff to continue working on code for COSMOS install.