Risk, Trade Space & Analytics in Acquisition                                  Unclassified     19-22 September 2011 | Sher...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified        19-22 September 2011 | S...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified       19-22 September 2011 | Sh...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified       19-22 September 2011 | Sh...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified         19-22 September 2011 | ...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified         19-22 September 2011 | ...
Risk, Trade Space & Analytics in Acquisition                                                           Unclassified       ...
Risk, Trade Space & Analytics in Acquisition                                                           Unclassified       ...
Risk, Trade Space & Analytics in Acquisition                                                            Unclassified      ...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified     19-22 September 2011 | Sher...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified        19-22 September 2011 | S...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified       19-22 September 2011 | Sh...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified       19-22 September 2011 | Sh...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified         19-22 September 2011 | ...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified        19-22 September 2011 | S...
Risk, Trade Space & Analytics in Acquisition                                  Unclassified             19-22 September 201...
Upcoming SlideShare
Loading in …5
×

MORS WG: Requirements Traceability and Adaptation

778 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
778
On SlideShare
0
From Embeds
0
Number of Embeds
42
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

MORS WG: Requirements Traceability and Adaptation

  1. 1. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VA Working Group 4Requirements Traceability and Adaptation David E. A. Johnson, Center for Advanced Defense Studies COL (Ret.) Tom Loper, USA AC, Ultra Electronics Mr. Chris Pernin, Rand Mr. Ervin “Chip” Mueller, AMSAA 19-22 Sep 2011 Unclassified 1
  2. 2. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 Participants David Johnson • Frank Swehosky Tom Loper • Alan Bohnwagner Chip Mueller • Brett Johnson Chris Pernin • Eric Harclerode Patrick Cantwell • Mike Nieman Jim Carr • T. W. Jackson Cindy Noble • Dr. Shlomo Argamon Willard Stratton • Tony Mckheen • Julia Sharkey Unclassified 2
  3. 3. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 BackgroundDefinition and Terms of ReferenceTraceability– linking attributes across a process or system– is necessary in order to ensure: what is built meets original intent as the world changes, 1st, 2nd, and higher-order effects can be captured and appropriate decisions made in a timely manner. Unclassified 3
  4. 4. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG 4 Objectives•Assess how well requirements traceability is integrated into acquisition lifecycle•Assess potential improvements, analytical methods and decision processesto enhance the use of bi-directional traceability•Discuss and record issues related to regulation and governance that mayimpinge on adaptation of requirements and use of traceability techniques•Develop recommendations for how to enhance traceability in currentrequirements processes Unclassified 4
  5. 5. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 Impact of Requirements TraceabilityIf Not Done / Not Done Well Reference points, direction and context are subject to varied opinions and interpretations. Leads to designs that don’t satisfy requirements. And don’t have military utility that was originally envisioned. Leads to disconnects & mis-matched activities & methods (design, dev., cost, T&E, …)  Difficult to revise direction/to integrate  Difficult to maintain schedule – admin  Result in increased costs to construct ∆s, fix the mess, etc. Limit trades available, increase risks and result in failed management Unclassified 5
  6. 6. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 Impact of Requirements TraceabilityWhen Done Right Provides a more complete initial set of purpose/objectives (starting point). Provides direction and context to System concept & development (common view for User, Developer, DM, Analysis, T&E) Provides structured framework for analyses (CBA, AoA, Cost, Trades, Risk) Captures internal & external incidents & the impact on requirements and system development.  Allows more structured approach to develop consensus changes  Communicates the measures (cost, performance, schedule, new trades, new risks) of interest Enables delivery of cost-effective systems that have positive military utility 6 Unclassified
  7. 7. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VA WG 4 Findings • There is currently no requirements traceability, in enough detail, from the CBA through the retirement of the system M D D A B C IOC FOCCapabilities Based Materiel Solution Technology Engineering & Production & OperationsAssessment Analysis Development Manufacturing Deployment & Support ICD AoA CDD CPD • CBAs and AoAs should be the primary analytic steps in the requirements traceability process • ICDs are often separated from the CBA • AoAs are not used as a “linking” process between ICDs and CDDs = Lack of detailed traceability Unclassified 7
  8. 8. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VA WG 4 Findings • Requirements traceability must begin with the required capabilities and end with the retirement of the system from the force • Requirements traceability needs analytic updates based on information changes with regard to: cost, schedule, performance, assumptions, environment, threat, risk, etc. M D D A B C IOC FOCCapabilities Based Materiel Solution Technology Engineering & Production & OperationsAssessment Analysis Development Manufacturing Deployment & Support ICD AoA CDD CPD Unclassified 8
  9. 9. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 FindingNumerous Requirements Management Software tools exist. WG4 identified problem areas that limit the effectiveness of requirements management. These areas are: o Requirements Collaboration “A cynical observation” o Requirements Identification Level of Involvement o Requirements Utilization Acquisition User Life Cycle Unclassified 9
  10. 10. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 FindingsCollaboration “Requirements Engineering is a Team Sport” Translators are needed between operators and developers Create and sustain Community of Practice Unclassified 10
  11. 11. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 FindingsIdentification Key Performance Parameters (KPPs) Must be re-examined throughout the life cycle  By User  By cost and OR analyst  By acquisition side Requirements are dynamic, explicit and implicit  Plan for Requirements Uncertainty and Risk  “Capability”/”Requirement” volatility can kill the program  Document Constraints and Assumptions early and evaluate iteratively  Capabilities, requirements, parameter, specifications require different attributes for completeness Unclassified 11
  12. 12. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 FindingsUtilization Process is not recursive enough and should be more flexible  AoA is early trade space discussion, and should be continuous throughout  Requirements volatility is an uncertainty/risk and impacts cost estimates  Requirements volatility can indicate changes to assumptions and constraints that should be documented and addressed  Linkage between requirements , acquisition and programming needs improved Unclassified 12
  13. 13. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG4 FindingsThe traceability matrix for each requirement should include: Requirements source Rationale (context for raw requirement(s)) Threat, environmental conditions, scenario Cost curve* Schedule Utility/performance curve Test needs Traceability should ‘work’ up, down, & horizontally * Capture point value, if possible capture curve – likely not available at MS A Unclassified 13
  14. 14. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VA WG4 FindingsCost estimation data, methods, values, and curves should be maintainedand updated within the traceability matrix. This will facilitate  Earlier and more frequent analyses of costs and consideration of cost drivers and their effects on program performance  Tighter linkage between program cost estimates throughout the acquisition process, including  Cost Analysis Requirements Documents  Independent Cost Estimates  Earned Value Management Unclassified 14
  15. 15. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VAWG 4 Summary Requirements are a team sport – operational community, acquisition community, budget community, test community, logistics community Analytic Rigor is needed – AoA should form the basis of periodic relook  Performance Utility Curve, Cost Curves  Recursive Analysis – Operational changes (threat, mission) to Acquisition community,  Recursive Analysis - Acquisition community changes (affordability, schedule) to operational community Realistic Performance Thresholds  Affordable, rapid acquisitions will require less aggressive technical solutions  Lower Performance Thresholds  More Performance Trade-space Unclassified 15
  16. 16. Risk, Trade Space & Analytics in Acquisition Unclassified 19-22 September 2011 | Sheraton Premiere at Tysons Corner, Vienna, VA Final Thoughts Requirements Analysis must support periodic assessment of Risk, Cost, and Trade-space analysis to permit the Department of Defense and the Services to achieve operationally effective and affordable systems delivered to the Warfighter in a reasonable time.Corruption . IO Unclassified 16

×