Creating a Relationship from a Requirement

  1. Click (Define).
  2. Choose a Requirement from the Requirements list.
  3. Click the Relationships tab.
  4. Choose a Project from the Project list. By default, the current Project is listed.
  5. Click New Relationship.
  6. In Add Relationships, click the tab for the item type. The list of items appear.
  7. Optional: Type the name of the Requirement, Story, or Concept in the Find field.
  8. Select the item from the list and click Add.
    The Relationship Type & Direction dialog appears.
  9. Click the arrow to create a to or from relationship between the item you are currently in and the item you selected.
  10. Click the Relationship tab . The Relationship pane appears.
  11. Scroll through the Existing Relationships. Each Relationship shows the status or details.
    Note: Select the status from the Relationship Status list to filter the list based on status or select Project, Relationship Type, Artifact Type, or Direction from the Group By list to group relationships.
  12. Click ... and choose to Update or Defer suspect relationships.
  13. Select the type of relationship from the Relationship Type list.

    The options vary depending upon the items to which you create a relationship.

    Type Description Available Status Values
    Basic Relationship Creates an association between two items, without status. None.
    Copy Creates a copy relationship. Future versions of Atlas will utilize Copy relationships to further support variant and re-use scenarios.

    With the current version, Copy relationships behave identical to Dependent relationships and they can be used to denote items that have been derived by Copy and Paste, for example items copied from template structures.

    Up-to-date, Deferred, Suspect.
    Dependent This type of relationship is designed to formally model a relationship of dependent items that need to be considered together. Up-to-date, Deferred, Suspect.
    Break down Items related with a Break Down relationship receive special handling in tracking views. Downstream items will appear in both the Tracking tab and the Tracking Gantt as if they were hierarchically children of the upstream related items. All statuses will also roll up. There is some logical overlap between Dependent and Break down relationships but in general Dependent relationships influence items while Break down items represent the same thing as the From item(s) but on lower, more detailed level. Up-to-date, Deferred, Suspect.
    Requirement Stream This type of relationship is used to track the relationship between Requirements and the Stories that delivery them. Requirements manually related to Stories with a Requirement Stream relationship will fully participate in all delivery status tracking. Up-to-date, Deferred, Suspect.
  14. Click OK.