1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
|
To Be Done:
- workbench lockup issue
- create screencast of User Use Case Scenario
- create why use ATS slide
- create configuration of ATS for Demo
- test workflow creation wizard
- should relate if workflow already exists
- not putting pages and flows in default hierarchy
- should create if workflow doesn't exist
---------------------------------------------------------
-- ATS User Use Case Scenario
---------------------------------------------------------
Why move all action, issue, problem tracking to ATS?
- Everyone has access to all data
- As issue/problem is analyzed, other teams can be added to Action
- Each team has it’s own independent workflow
- Workflows can be simple or complex
- One interface = Low cost of setup, deployment, training and admin
T. Rex decides to move to ATS - whew, that was tough ;>)
Show configuration of ATS for T. Rex - TBD
- Teams and Actionable Items
- Workflows
- Branch diagram
- Show diagram of what is being demo'd below
- Coder to Req to Coder to Test to Tools and Documentation and Facilities
- Show Action w/ workflows, reviews, tasks
Notes: You're welcome to follow along and perform the steps
- Limited time, so need to keep moving
- Will just explain some of the things going on versus showing due to time
- Will operate as more than one user, but will always say Joe Smith
- Will operate on single computer, this is multi-user/computer system with notifications
Use Case: Problem w/ requirement impacts code, test, tool and facilities
Coder Does Their Work:
- Coder Joe is looking at "Robot Object" requirement on SAW_Bld_2
- Set Default Branch to SAW_Bld_2 branch
- Search on "Robot Object"; Right-click, Open With, MS Word Preview
- Coder Joe finds a problem with requirement and creates Action against
- Switch to the ATS Perspective
- Select New Action icon in ATS Navigator
- Title: Robot Object requirements needs more detail
- AIs: expand SAW CSCI, select SAW Requirements
- Next, Desc: See title, Change Type: Problem, Pri: 3, User Community: Program 1
- NOTE: Action created, assigned to Joe Smith (configured Lead for SAW Req Team)
Requirements Developer Does Their Work:
- [Requirements Team Lead Joe] (Team Lead) Endorses Action
- Target Version: SAW Build 2 - Next Version
- Changes Priority: 2
- Transitions to Analyze
- NOTE: This is where you would assign another user, but can't for demo
- [Requirements Developer Joe] Analyzes Action
- Proposed Resolution: Fix It
- Notices that change will impact Code and Test; Add code and test workflows
- Select Actionable Items hyperlink in top left
- Add SAW Code and SAW Test Actionable Itesm
- NOTE: Action View shows new workflows kicked off; Email notification sent
- Estimated Hours: 2.5
- Transition to Authorize - NOTE: Can be reassigned or configured to be auto-assign
- [Requirements Team Lead Joe] Authorizes Action
- Work Package: A324324A
- Joe needs concurrence from Kay - Add Decision Review
- Select Add Decision Review, Title: Any Problems with Authorizing this? State:Auth
- Prepare Review-> Blocking: Transition, Est Hours: 3, Assign Kay, Transition
- Kay Runs "My World" - Select "Users World", Select Kay Jones, Select review
- Kay decides Yes and transitions; Review Completed
- Transition to Implement - NOTE: Can be reassigned
- [Requirements Developer Joe] Implements Change
- Select "Create Working Branch"
- Select "Show Working Branch" shows branch manager and branch associated
- Select "Set As Default Branch" (from Workflow Editor or Branch View
- Select "Artifact Explorer" view in top left
- Expand Software Requirements, Robot collaboration, Robot Object
- NOTE: If don't have MS Word, just watch
- Right-click, Open With, MS Word Edit
- Insert: Need more information here., Save and Close
- Change Qualification Method: Inspection
- Switch back to Workflow Editor:
- Select "Run Change Report" - Shows Changes
- Select "Commit Working Branch"
- Transition to Complete
Coder Does Their Work:
- [Code Lead Joe] Endorses the Team Workflow
- Work Package: A234532
- Transition to Analyze
- [Coder Joe] Analyzes the Team Workflow
- Runs Change Report
- Estimated Hours: 10
- Analysis Requires Tasks
- Switch to Task Tab
- Add Task: "Do the first thing"
- Add Task: "Do the second thing" - Assign different user
- Add Task: "Do the third thing" - Assign different user
Tester Does Their Work:
- [Test Lead Joe] Estimates the work
- Kay Jones not in today and estimates due...
- Joe is Priviledged Editor - Yes
- Transition To Analyze
- Estimated Hours: 25
Manager Intervention
- [Manager Joe] Wants status
- Select World; Redisplay as workflows
- Metrics Tab
- Estimated Completion Date - 2 Days
- Kay won't make it; Joe will
Coder Does Their Work:
- [Coder Joe] Realizes needs peer to peer review for Analysis
- Add PeerToPeer Review
- Add Roles - Author, and 2 Reviewers
- Location: That.java; This.java
- Estimated Hours: 2
- Blocking: Transition
- Transition to Review
- [Coder Joe] Realizes this change will affect Tools and Facilities-Computers
- On SAW Code Workflow: Select Action Actionable Items
- Select Tools - Website
- Select Facilities - Computers
- Workflows are created for IT Team and Website Team
And the work continues...
---------------------------------------------------------
-- ATS Configuration
---------------------------------------------------------
- Show diagram of each team's workflow
- Diagram of Action, Workflows, Reviews, Tasks
- Diagram of Team Definitions and Actionable Items
- Work Flows, Pages, Widgets, Rules
- Versions
- Groups
- Users / User Groups
- Configuration of ATS
- ATS Configuration
- New -> Other -> OSEE ATS -> ATS Configuration
- Configuration Namespace: org.myCompany.labs
- Team Definition Name: Labs Team
- Actionable Item(s): Lab 1, Lab 2, Lab Door, Lab Computer
- Versions:
- Workflow Id: osee.ats.defaultTeamWorkflow
|
