This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Elaboration of business/stakeholder requirements

This is a variant on the elaboration scenario (RmRequirementElaboration) in which the collaborator is another RM system. The business requirements are in the first RM application (here called RM1) and the lower-level requirements (here called "user requirements") will be elaborated in a second RM application (here called RM2).

Preconditions

  1. RM1 and RM2 systems are configured so as to enable integration.
  2. RM1 and RM2 users have a means of communication (for example, email, tasking system etc.)
  3. A collection of requirements has been defined in the RM1 application.

Scenario

  1. The RM1 user defines a requirement collection (b) which contains input business requirements that are to be elaborated as user requirements in the RM2 system.
  2. RM2 user discovers the collection of requirements
    1. Alternative: the RM2 user uses OSLC delegated selection UI.
    2. Alternative: the RM2 user is informed of the collection by some other means.
  3. OPTIONAL: RM2 user creates a collection of user requirements and links this to the collection of business requirements with an elaborates.
  4. For each business requirement in the requirement collection, the RM2 user creates a user requirement and an elaborates relationship.
    1. Alternative: in general the correspondence will not be 1-to-1.
  5. RM2 user extends the user requirements during the process of elaboration until the required level of detail has been achieved.

Alternative

  1. The RM1 user elaborates the business requirements by creating user requirements in the RM2 application, and linking them with an elaboratedBy link.


Postconditions

  1. Each business requirement in the RM1 collection has a linked RM2 requirement

Discussion This is simpler then then the elaboration of requirements with model elements since there is no creation of "derived" business requirements in the RM1 application.

There is a symmetry between the RM1 and RM2 systems, which suggests some symmetry in the vocabulary, for example, elaborates and elaboratedBy. (This symmetry is further explored in RmToRmScenarios? .)

RM 2.0 does not have a "elaborates" predicate in its vocabulary.

See also RmToRmScenarios? .

Topic revision: r1 - 22 Aug 2011 - 09:36:22 - IanGreen
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback