Agenda

• Scenarios- Actions to review
  • RmRequirementElaboration (compare with RmRequirementElaborated)
  • Commit to scenarios for V2.0
• OSLC Core progress
  • Familiarization / Feedback
  • What needs to be done to adopt OSLC Core?
• Spec. progress - Actions to move these forward
  • Feedback from 1.0 implementation efforts (RmImplementationExperiences)
  • Specification needs (RmSpecificationNeedsV2)
• AOB

Apologies: NickKruk? , SimonWills

Attendees: IanGreen, DominicTulley, JeremyDick, ScottBosworth, DaveJohnston? , PaulMcMahan, TorgeKummerow

Minutes:

PaulM? : is the responsibility of the RM provider to maintain n-step downstream links rather than the 1-step links. Scott: both valid. Role OSLC plays here is debateable. OSLC can define the links that are involved (and also extensible relationship types). Jeremy: Link from requirement to build different from links between requirements/test cases. Any linking capability should be without prejudice to link type.

Torge: All requirements are "chaptered" .

Scott What assumptions do we make about the definition of a collection? Paul: does a collection allow us to avoid adding formal properties to requirements because it is ad hoc. Eg inm the AM scenario should a collection be "all things allocated to a sprint".

Scott: is collection-collection asserted or derived? Paul: does collection deal with hierarchy