COSMOS 1.1 Iteration1 Features

COSMOS v1.1 iteration 1 plan

Cross component work items (Jimmy Mohsin, David Whiteman, Jason Losh)

externalization/internationalization

• SDD to complete

logging

• SDD will do due diligence to ensure that it is consistent with the way that the rest of COSMOS logs

clean API

• SDD to decide which method signatures should be API
• SML to decide which method signatures should be API
• CMDBf to add any method signatures to its API list?

Design doc every enhancement

• if the enhancement is really small, put in at least a paragraph and a link to the use case for QA and documentation.
• if the enhancement is not small, the design doc needs to explain the change, anyone other than the assignee who is affected, how much work it is, any ramifications, and in general please avoid any changes to 3rd party open source other than removing a dependency on it. We have no guarantee that the change will be approved for COSMOS v1.1.

Mandatory for releasing V1.1 (Ruth Lee)

Review itself

• arrange for COSMOS to be added to the Eclipse Board docket 5 weeks in advance of the intended release of V1.1
• create the review slides
• clean up the inactive committer list

Legal

• about.html for third party OSS in COSMOS: Ruth to arrange for these specialized about.html to be written and then delivered to the build team for inclusion in COSMOS
• IP log written and submitted for approval 3 weeks prior to the release review
• get ipzillas approved by Eclipse Legal: list of IPZillas awaiting approval

Bugzillas for this iteration (Jimmy, David, Jason, Saurabh, QA, Doc)

Sizing legend:

• Low - takes 1-3 days
• Medium - takes a week
• High - takes more than a week

Status to be filled in by:

• Data Collection bugzilla status (Jimmy Mohsin)
• Data Visualization bugzilla status (Jimmy Mohsin)
• Resource Modeling bugzilla status (David Whiteman)
• Management Enablement bugzilla status (Jason Losh)
• RE/Build bugzilla status (Saurabh Dravid)
• QA bugzilla status (No owner)
• Doc bugzilla status (No owner)

The Status column can have one of these values:

• COMPLETE
• On track
• At risk
• Not containable
• Defer (no longer a priority for i13)
• Not started

Note: there are no known features in plan for iteration 1 for the Resource Modeling, Data Collection, or Data Visualization components. Resource Modeling will have several small defect fixes in the iteration.

Priority	Status	Project or subteam	Enhancement	Severity	Description	Blocked by (if applicable)	Owner	Sizing	Design Doc	Use Case
Medium	On track	ME	257992	Enhancement	Rule to merge AlternativeRequirementType from two or more SDDs		Josh Hester	Low	[1]	[2]
Medium	On track	ME	257993	Enhancement	Rule to merge AlternativeRequiredBaseConstraints from two or more SDDs		Josh Hester	Low	[3]	[4]
Medium	On track	ME	257994	Enhancement	Rule to merge PropertyValueLists from two or more SDDs		Josh Hester	Low	[5]	[6]
Medium	On track	ME	257995	Enhancement	Rule to merge RequiredBases from two or more SDDs		Josh Hester	Low	[7]	[8]
Medium	On track	ME	257996	Enhancement	Rule to merge RequiredBaseConstraints from two or more SDDs		Josh Hester	Low	[9]	[10]
Medium	On track	ME	257997	Enhancement	Rule to merge CompletionTypes from two or more SDDs		Josh Hester	Low	[11]	[12]
Medium	On track	ME	257998	Enhancement	Rule to merge AdditionalContents from two or more SDDs		Josh Hester	Low	[13]	[14]

Use cases

• Use cases: SDD related function
• SDD Deployment Use Cases (PDF file)
• COSMOS 1.0 use case page
• COSMOS 1.1 use case page