Workgroup Needs and Activities for RM 3.0

Requirement Organization

During 1.0 and 2.0 we ignored the problems associated with large numbers of requirements in a requirement collection. For example, when a requirement is added to a collection, it is typically important where in that collection it is added. The current resource model treats a collection as a set, not an ordered tree.

Action: (all) Consider this and decide if we want to take this forward during 2010.

Baselining

There is a number of scenarios for baselining of requirements, both within an RM system, and also across applications. (Eg Test, Requirements, Models.) Workgroup needs to articulate scenarios for baseling, and ensure that the RM specification is compatible with the OSLC Core baselining specification.

Action: (all) Review output of the OSLC Core workgroup on the topic of baselining

• BaselinesInOslc

Change log

Motivate the need for change log (Ian & Dave) resource. How will this bring value to the integration landscape?

Action: (Ian and Dave) to bring this to the RM workgroup.