Configure ATS for Change Tracking
ATS Notifications		Configure Team Definition

Configure ATS for Change Tracking

Purpose

ATS is used to track any type of change throughout the lifecycle of a project. Below are the steps to configure ATS for tracking something new.

How to do it

• Review "ATS Overview" to understand ATS Concepts, Terms and Architecture. Pay special attention to ATS Terms.
• Determine what Actionable Items (AIs) need to be available to the user to select from. This can be anything from a single AI for tracking something like a tool or even an activity that needs to be done to a hierarchical decomposition of an entire software product or engineering program.
  • Considerations:
    • Item should be in the context of what the user would recognize. For example, OSEE ATS World View versus something unknown to the user such as AtsWorldView.java.
    • Decompose AI into children AI when it is desired to sort/filter/report by that decomposition.
  • Actionable Item attributes to be configured:
    • Name: Unique name that the user would identify with.
    • Active: yes (converted to "no" when AI is no longer actionable)
  • Actionable Item relations to be configured:
    • TeamActionableItem: relate to Team Definition that is responsible for performing the tasks associated with this AI. Note that if this relation is not set, ATS will walk up the Default Hierarchy to find the first AI with this relation.
• Determine the teams that are going to perform the tasks that are associated with the AIs selected by the user.
  • Considerations:
    • Use separate teams if certain changes are to be managed by different leads.
    • Use separate teams if one team's completion and releasing is independent of another's.
    • Use separate teams if team members are separate.
    • Use separate teams if different workflows are required for one set of AIs than another.
  • Team attributes to be configured:
    • Name: Unique team name that is distinguishable from other teams in a list.
    • Description: Full description of the team and it's scope.
    • Active: yes (converted to "no" when AI is no longer actionable)
    • Team Uses Versions: yes if team workflows are going to use the build management and release capabilities of ATS.
    • Full Name: Extended name for the team. Expansion of acronym if applicable.
  • Team relations to be configured:
    • TeamActionableItem: relation to all AIs that this team is responsible for.
    • Work Item.Child: WorkFlowDefinition artifact configures the state machine that this team works under. Note that if this relation is not set, ATS will walk up the Default Hierarchy to find the first AI with this relation.
    • TeamLead: User(s) that are leading this team. These users will be assigned to the Endorse state of the Team Workflow upon creation of an Action by a user. Providing multiple leads reduces bottlenecks. First lead to handle the Team Workflow wins.
    • TeamMember: User(s) that are members of the team. These users will be shown first as preferred assignees and have the ability to privileged edit a Team Workflow for the team they belong to.
• Choose existing WorkFlowDefinition or create new WorkFlowDefinition to be used by the team and relate it to Team Definition (as above). This can be done through File->New->Workflow Configuration. Enter a namespace and a default workflow will be created and can be edited.
• Create version artifacts necessary (if using versions) and relate them to Team Definition (as above)
  • If branching of artifacts is going to be used (see below), configure versions with their appropriate parent branch id.
• Determine if Branching within one of the states in the workflow is desired/required and configure as appropriate.
  • Considerations:
    • Branching is necessary if objects to change are stored in OSEE as artifacts. If so, OSEE ATS can create a working branch off the parent branch, allow user to modify artifacts and then commit these changes when complete, reviewed and authorized (as necessary). If objects are stored in outside OSEE (eg. code files in a Git repository), this option is not necessary.
  • Configure ATS workflow for branching:
    • Create AtsStateItem extension specifying which state the branching will occur. This is normally in the Implement state of a workflow.
    • Create root branch and import documents that will be managed through define and tracked through ATS.
    • Set all Version artifacts "Parent Branch Id" attribute to the branch id of the root branch (or child branches, if using multi-branching)
    • If only a single branch is to be used OR versioning is NOT configured to be used, the "Parent Branch Id" should be s

ATS Notifications		Configure Team Definition