History   View   Links to this page Revision from: 2012 September 7 | 10:48 am
This is the revision from 2012 September 7 at 10:48 am   View the current live version of the article.

Goal:

Support the ability to associate/link change requests to change sets instead of directly to resources.

Prerequisites:

  • AM repository with history enabled (change tracking)
  • AM system with a connection to a CM system
  • Multiple change requests created in the CM system that will require modification of the same resource(s) in the AM repository
  • Each change request assigned to a user, could be the same user or different users, the scenario uses different users

Outcomes:

  • Change request 1 linked to a change set in the AM repository
  • Change request 2 linked to a change set in the AM repository
  • Given a change request find the change set(s) and all Resource(s) affected in the AM repository
  • Given a resource find all change request(s) that affect the resource in the AM repository

Scenario

  • User1 establishes a context in the AM tool
    1. User 1 opens existing AM repository - Proj1/Wksp1
    2. User 1 selects an existing change request - CR1 from a list of assigned requests retrieved from the CM system
    3. All changes made will now be tracked and related to the active change request CR1
  • User1 assesses the scope of the change request
    1. Locate AM resource(s) Res1 impacted by the request - CR1
  • User1 Applies required changes
    1. Open AM resource - Res1 and make required changes (Res1 is locked while being modified)
    2. Save AM resource - Res1
    3. Change set created and association with the active change request - CR1 is established
    4. Resource Res1 is unlocked
  • User2 establishes a context in the AM tool
    1. User 2 opens existing AM repository - Proj1/Wksp1
    2. User 2 selects an existing change request - CR2 from a list of assigned requests retrieved from the CM system
    3. All changes made will now be tracked and related to the active change request CR2
  • User2 Assesses scope of Change Request
    1. Locate AM resource(s) impacted by the request- Res1
  • User2 Applies required changes
    1. Open AM resource - Res1 and make required changes (Res1 is locked while being modified)
    2. Save AM resource - Res1
    3. Change set created and association with the active change request - CR2 is established
    4. Resource Res1 is unlocked
  • User3 reviews the changes for each change request
    1. Opens existing AM repository - Proj1/Wksp1
    2. Selects CR1 and is able to view a list of the changes made to Res1 on behalf of CR1
    3. Selects CR2 and is able to view a list of the changes made to Res1 on behalf of CR2

Goal:

In architecture artifacts (object x) an architect (role) would create a link from a high-level design object (object y), such as a data controller component, to a high-level testing artifact (object z), such as a test plan.