Analyst links a requirement document to a UML model element that supports/implements/satisfies it. This indicates that the requirement is being addressed in the design. It can be queried for given the model element. The model element can be queried for given the requirement.
A BMPN model is published as an asset. A developer uses this asset, and extends it for a particular project. An analyst references this model as a specification for a requirement. A detailed UML model is created as an implementation of it. The UML developers want easy access to the original specification model, and to the information associated with the asset (i.e. reviews, comments).
A commission for the design of a component in an application is defined by a change request. The change request references the requirements, and other information relevant to the task. A designer starts a new model, associating the resource directly to the requirements (not just via the work item). The work item association can be derived from the change set delivered in the name of the work item
A UML model described a specification for some desired functionality. It is based on some open standards. 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.
A development organization uses AM resources in many ways and has special needs to associate custom meta data to AM resources (i.e. client billing id, due date, …)
