This document list all the AM use case scenarios that we consider as being of interest to this topic. This page just contains links to a more detailed description. The ordering (and even existence or non-existence) does not imply any priority or level of importance. One of the first goals of this team is to capture all the interesting use cases, and then after discussion and consensus identify key and significant scenarios to work on.
Essential scenarios to support in OSLC AM specification
Basic linking - Analyst links a requirement document to a discovered UML model element that supports/implements/satisfies it. This indicates that the requirement is being addressed in the design. It can be found if given the model element. The model element can be found if given the requirement.
Link type variance and query - A UML model describes a specification for some desired functionality. It is based on some open standard. A developer creates an implementation for a particular platform (i.e. JEE). The QA team is tasked (via a work item) to test the implementation. This team references the project specific requirements and the open standards. The QA team reviews the design and develops an appropriate plan and test cases. Each scenario, expressed as a UML sequence diagram tagged with some predefined UML stereotype must be associated with at least one test case to ensure coverage. Missing test cases show up in a report or in project viewlet for QA team.
Detailed scenario examples
The following detailed examples show how the OSLC AM service interface may be used by clients wishing to:
