ATLAS Shrugged ATLAS Shrugged Pat O Toole Toole Pat O (with - PowerPoint PPT Presentation

ATLAS Shrugged ATLAS Shrugged Pat O’ ’Toole Toole Pat O (with apologies to Ayn Rand and John Galt) (with apologies to Ayn Rand and John Galt)

ATLAS ATLAS � “ “A Ask sk T The he L Lead ead A Appraiser ppraiserS S” ” � � A scenario A scenario- -based email forum used to elicit based email forum used to elicit � opinions on “ “interesting interesting” ” topics topics opinions on � Distributed to all 400+ LAs and 1500+ non Distributed to all 400+ LAs and 1500+ non- -LAs LAs � � Limited to one page Limited to one page � � Multiple choice format Multiple choice format - - ample room for comments ample room for comments � � Results are compiled and published by PACT with Results are compiled and published by PACT with � no intellectual property rights retained no intellectual property rights retained � SEI is just another recipient of the data SEI is just another recipient of the data – – they do they do � not sponsor or influence ATLAS in any way. not sponsor or influence ATLAS in any way. 2 2

ATLAS Scenarios ATLAS Scenarios Scenario number (# LA’ ’s / # non s / # non- -LA LA’ ’s) s) Scenario number (# LA #1 – – Bidirectional traceability (46/45) Bidirectional traceability (46/45) #1 #2 – – Process descriptions/measures (40/17) Process descriptions/measures (40/17) #2 #3 – – Applicability of SAM (66/75) Applicability of SAM (66/75) #3 #4 – – Interpretational issues (79) Interpretational issues (79) #4 3 3

ATLAS Scenarios ATLAS Scenarios #1 – – Bidirectional traceability (46/45) Bidirectional traceability (46/45) #1 #2 – Process descriptions/measures (40/17) Manage Requirements #3 – Applicability of SAM (66/75) Obtain Manage Obtain an Commitment Requirements #4 – Interpretational issues (79) Understanding to Changes of Requirements Maintain Requirements Bidirectional Traceability of Requirements Requirements Identify Inconsistencies Between Project Work and Traceability Matrix Requirements 4 4

ATLAS #1 – – Bidirectional Traceability Bidirectional Traceability ATLAS #1 � A project in a SCAMPI A appraisal is: A project in a SCAMPI A appraisal is: � � estimated to be 30,000 person hours estimated to be 30,000 person hours � � 14 months into its 18 month schedule 14 months into its 18 month schedule � � preparing to initiate system testing preparing to initiate system testing � � No alternative practices for this project. No alternative practices for this project. � 5 5

Question 1 Question 1 1. For this project, which selection best For this project, which selection best 1. represents your view of model expectations represents your view of model expectations with respect to REQM SP1.4? with respect to REQM SP1.4? A. Vertical and horizontal traceability Vertical and horizontal traceability A. B. Either vertical or horizontal traceability Either vertical or horizontal traceability B. C. Only vertical traceability Only vertical traceability C. D. Only horizontal traceability Only horizontal traceability D. E. Other Other E. 6 6

Answer 1: Model Expectations Answer 1: Model Expectations Selected choice: Leads Non-Leads A: Vertical and horizontal 70% 84% B: Vertical or horizontal 13% 0% C: Vertical only 13% 11% D: Horizontal only 0% 4% E: Other/None 4% 0% 7 7

Question 2 Question 2 2. What characterization (FI, LI, PI, NI) 2. What characterization (FI, LI, PI, NI) is most appropriate if there is: is most appropriate if there is: A. ___ ___ Ample evidence of vertical traceability Ample evidence of vertical traceability A. but no no evidence of horizontal traceability? evidence of horizontal traceability? but B. ___ ___ Ample evidence of horizontal traceability Ample evidence of horizontal traceability B. but no no evidence of vertical traceability? evidence of vertical traceability? but 8 8

Answer 2a - - Characterizations Characterizations Answer 2a Ample evidence of vertical traceability Ample evidence of vertical traceability but no no evidence of horizontal traceability evidence of horizontal traceability but Selected choice: Leads Non-Leads A. FI 20% 15% B. LI 39% 32% C. PI 36% 47% D. NI 5% 6% 9 9

Answer 2b - - Characterizations Characterizations Answer 2b Ample evidence of horizontal traceability Ample evidence of horizontal traceability but no no evidence of vertical traceability evidence of vertical traceability but Selected choice: Leads Non-Leads A. FI 7% 2% B. LI 11% 9% C. PI 66% 66% D. NI 16% 23% 10 10

Question 3 Question 3 3. For each of the following, please 3. For each of the following, please indicate if you consider it to be: indicate if you consider it to be: A. Vertical Traceability A. Vertical Traceability B. Horizontal Traceability B. Horizontal Traceability C. Neither C. Neither D. Both D. Both E. I don’ ’t have a clue! (Don t have a clue! (Don’ ’t know) t know) E. I don 11 11

Answer 3a – – Traceability Type Traceability Type Answer 3a High- -level business requirements level business requirements High are traceable to feature requirements are traceable to feature requirements Selected choice: Leads Non-Leads A: Vertical 95% 86% B: Horizontal 5% 2% C: Neither 0% 0% D: Both 0% 12% E. Don't Know 0% 0% 12 12

Answer 3b – – Traceability Type Traceability Type Answer 3b Traceability is maintained among Traceability is maintained among interdependent functional requirements interdependent functional requirements Selected choice: Leads Non-Leads A: Vertical 4% 9% B: Horizontal 82% 74% C: Neither 2% 2% D: Both 9% 16% E. Don't Know 2% 0% 13 13

Answer 3c – – Traceability Type Traceability Type Answer 3c Each of the 500+ system test cases lists Each of the 500+ system test cases lists the specific requirement(s) being tested the specific requirement(s) being tested Selected choice: Leads Non-Leads A: Vertical 78% 67% B: Horizontal 16% 21% C: Neither 2% 4% D: Both 4% 9% E. Don't Know 0% 0% Note: Traceability ACROSS ACROSS the life cycle is the life cycle is “ “vertical; vertical;” ” Note: Traceability And we wonder why there are interpretational issues! And we wonder why there are interpretational issues! 14 14

Answer 3d – – Traceability Type Traceability Type Answer 3d System requirements are traceable to System requirements are traceable to the group(s) to which they are allocated the group(s) to which they are allocated Selected choice: Leads Non-Leads A: Vertical 51% 32% B: Horizontal 29% 39% C: Neither 16% 14% D: Both 0% 16% E. Don't Know 4% 0% 15 15

Answer 3e – – Traceability Type Traceability Type Answer 3e Technical requirements are traceable Technical requirements are traceable to specific elements in the WBS to specific elements in the WBS Selected choice: Leads Non-Leads A: Vertical 51% 40% B: Horizontal 29% 35% C: Neither 16% 16% D: Both 4% 7% E. Don't Know 0% 2% 16 16

ATLAS #1 Note ATLAS #1 Note � The SEI The SEI’ ’s website contains answers to s website contains answers to � “Frequently Asked Questions Frequently Asked Questions” ” (FAQ) (FAQ) “ � Bidirectional traceability is covered: Bidirectional traceability is covered: � � http://www.sei.cmu.edu/cmmi/faq/new http://www.sei.cmu.edu/cmmi/faq/new- -faq.html#Q318 faq.html#Q318 � � See partial text on next slide See partial text on next slide � � Only 1 of nearly 100 respondents (a lead Only 1 of nearly 100 respondents (a lead � appraiser) mentioned the SEI FAQ! appraiser) mentioned the SEI FAQ! 17 17

SEI FAQ regarding Traceability SEI FAQ regarding Traceability Vertical traceability identifies the origin of items (e.g., Vertical traceability identifies the origin of items (e.g., customer needs) and follows these same items as they travel customer needs) and follows these same items as they travel through the hierarchy of the WBS to the project teams and through the hierarchy of the WBS to the project teams and eventually to the customer. When the requirements are eventually to the customer. When the requirements are managed well, traceability can be established from the source managed well, traceability can be established from the source requirement to its lower level requirements and from the lower requirement to its lower level requirements and from the lower level requirements back to their source. level requirements back to their source. Horizontal traceability is also important, but it is not Horizontal traceability is also important, but it is not required to satisfy bidirectional traceability. Horizontal Horizontal required to satisfy bidirectional traceability. traceability identifies the relationships among related items traceability identifies the relationships among related items across work groups or product components for the purpose of across work groups or product components for the purpose of avoiding potential conflicts. For example, horizontal avoiding potential conflicts. For example, horizontal traceability would follow related requirements across two work traceability would follow related requirements across two work groups working on two associated components of a product. groups working on two associated components of a product. 18 18