Please enable JavaScript.

Coggle requires JavaScript to display documents.

Multi Release Tagging (Usability (Easy to use, Efficient, Reliable,…

- - - - The change can be applied on the same item:
        A) The item has only one TR assigned
        B) Change is valid for all assigned TRs
    - - Item is assigned to two and more releases
      - MRT Copy Tool is used
    - - Item assigned to only one TR
        
        If the item is assigned to only one TR it can be Deprecated / Rejected directly
        (State change & TR is removed)
        
        All traces shall be removed
      - Item assigned to two or more TRs
        
        A) Copy item and deprecate the child
        or B) Remove selected TR and make formatted comment: Deprecated from TR - HP ALM WFL
        
        Needs to be elaborated!!
        
        All irrelevant traces must be removed
        Traced items assigned to selected TR
    - - Item assigned to only one TR
        
        Item can be set as Deferred
        
        TR removed and substitute with Deferred TR
      - Item assigned to two or more TRs
        
        Copy item and defer the child
        
        Remove from Parent selected TR
        
        Remove from parent irrelevant traces
        
        Assign child to Deferred TR
  - - - Define a new TR name
        (in Scope Release Tracker)
      - Assign all valid items to a new release
        (all at that time valid items)
        (Mass update)
      - Each new item needs to be assessed
        if it belongs to all open releases or to only specific
        (Appropriate release(s) must be assigned)
      - Each modified item needs to be assessed
        to what release the change needs to be applied
        A) If to all, no copy is needed
        or B) If only to specific release then copy needs to be created and change applied only for impacted release
      - Each Deprecated / Rejected item needs to be assessed to what release the change applies
        A) If to all, the item can be Deprecated
        or B) If only to specific release then the impacted TR needs to be removed from this item.
        
        Option B needs to be elaborated!!
    - - Define a Patch TR name
        (in Scope Release Tracker)
      - A) Assign patch TR only to imparted items
        or B) Assign Patch TR to all valid items
        (only to valid items of the release what is patched)
- - - - Copies Exists attribute set to Yes
      - TR of the copy is removed from the TR of the origin
      - Trace removal
        Traced items having no match on at least one TR
      - Traces preservation
        A) Traced items having no TR assigned
        and B) Traced items assigned to Deferred TR
    - - Copies Exists attribute set to No
      - Parent ID attribute set the ID of the origin
        The ID of the Parent - first family member)
      - TR selected for copy is assigned to Child
      - Traces copy
        A) Traced items having selected TR assigned
        and B) Traced items having no RT assigned
        and C) Traced items assigned to Deferred TR
- - - - Protection
      - Multi-Run
      - Inheritance
      - Determine Scope
      - Multi-Tagging
      - MRT data integrity
    - - Assignment to a release
      - Family membership
      - Versioning