1. Software Acquisition Management SAM-450 EXEC SAM Spiral Models and Paradigms SAM Executive Seminar George Prosnik DAU CDSC E&T Center

2. Software Acquisition Management SAM-450 EXEC SAM System and Software Engineering Process Linkages Systems Engineering, Hardware Design and Development Activities Software Engineering and Development Activities System Requirements Analysis Configuration Item Identification Long Lead SW Items Prototyping Needs Test Qualification Analysis T & E Results Review Support Allocated Baseline Information SI Delivery Rev 3.4

3. Software Acquisition Management SAM-450 EXEC SAM Rev 5.0 Grand Design P3I Evolutionary SoftwareDevelopmentParadigms Waterfall Paradigms Incremental Paradigms Spiral Models Acquisition Approach System Acquisition Strategy

4. Software Acquisition Management SAM-450 EXEC SAM Systems & Software Development System Sub Sys SI Software Units SI Software Units SI Software Units HIs System Design Software Requirements Analysis System Requirements Analysis Software Design Software Unit Coding SW Unit Integration and Testing Software Unit Testing Software Item Qualification Testing HI and SI Integration and Testing Subsystem Integration and Testing System Qualification Testing DT and OT&E Testing

5. Software Acquisition Management SAM-450 EXEC SAM Rev 4.4 Systems Acquisition Life Cycle Note: the linkage between a Waterfall paradigm and the underlying system acquisition life cycle can vary widely from this notional diagram. E.g., starting and stopping points may depend on acquisition/contract strategy. Multiple Waterfalls may be required over the total acquisition life cycle, etc. “Waterfall” Software Development Paradigm Implement & Unit Test Unit Integ & Testing SI Qual Testing SI/HI Testing Software Design System Require- ments Analysis System Design System Testing SW Require- ments Analysis KEY CHARACTERISTICS Do steps in a specified order Define ALL requirements up front Use comprehensive reviews as gates Complete program design before coding Emphasizes Functional & Allocated baselines Elaborate SW design via extensive documentation “Do the job twice if possible & involve the customer” Management Issues Excessive Documentation Acquisition Life cycle Linkage User Participation Late product visibility

6. Software Acquisition Management SAM-450 EXEC SAM How do you eat the software elephant?? (one of many variations!) Rev 5.1 One Byte at a time! Incremental Development KEY CHARACTERISTICS Define requirements before building Develop and code the system in a sequence of builds Each build incorporates part of the planned capabilities Development phases overlap Software design may begin before software requirements analysis complete Multiple configurations in development System Design System Qual Testing Testing and Integration Software Design Coding & Unit Testing Software Req’ts Analysis Testing and Integration Software Design Coding & Unit Testing Testing and Integration Software Design Coding & Unit Testing SI/HI Testing System Req’ts Analysis Management Issues: Baseline Control, Staff Loading, Phasing of Requirements, Definition of “Incremental”

7. Software Acquisition Management SAM-450 EXEC SAM Prototyping and Insight Prototype to: –Refine requirements –Assess affordability –Evaluate algorithms –Make cost/performance trades –Reduce risk on critical subsystems –Determine operational effectiveness –Assess User interfaces –Mitigate technology integration Unconstrained development Minimal/informal documentation Tie prototypes to risk mitigation “Think about” and document: –Prototype’s goals and purposes –Relationship of prototype to final product –Lessons to be learned or concepts proven –Completion or success criteria –Plans for monitoring the prototype effort Prototype #1Prototype #2Prototype #3 INSIGHTINSIGHT Rev 4.3 Level of Understanding Management Issues: Control of Prototypes; Scaling Issues; “Phantom Data”; Subversion of Disciplined Life Cycle; User Involvement & Ownership; Baseline Control

8. Software Acquisition Management SAM-450 EXEC SAM SPIRAL MODEL PARADIGMS KEY CHARACTERISTICS Concurrent determination of key artifacts done throughout lifecycle Level-of effort and degree of detail are risk driven Prototype feedback essential “Anchor points” should be used as intermediate milestones Emphasis should be on system- level lifecycle activities and artifacts Objectives, risk, alternatives, reviews and commitment to proceed done for each cycle Vers 2.0 Determine Objectives and Constraints ID & resolve RISKS Plan next Phase Develop & Verify Next Level Product Risk Analysis Prototyping Activities Management Issues: Floating Baselines, Process Visibility, Risk Management, Prototype Control, Funding, “Fielding” Decision, Many Look-Alike Variations of “Spiral Models” START

9. Software Acquisition Management SAM-450 EXEC SAM Systems and Software Development “Here are all the pieces. Tailor out what you don’t need” “Here are all the pieces. Put them together in the best way that makes sense for your particular program!” Hardware Reqts Analysis Preliminary Design Detail Design Hardware Fabrication HWCI Testing System Integrate & Testing Software Reqts Analysis Prelim Design Detailed Design CSCI Testing PDR CDR T&E FCA PCA System Reqts System Design S Y S T E M E N G I N E E R I N G CDR Coding & CSU Test CSC Integ & Testing PCA PDR SDR SRR SSR PDR CDR TRR Project Planning Software Dev Environment System Req’ts Analysis System Design SW Req’ts Analysis SW Design SW Implementation and Unit Testing Unit Integration and Testing Software Item Qualification Testing Software & Hardware Integration & Test System Qual Test Prepare SW for Use Prepare for SW Transition Software CM Software Product Evals Software QA Corrective Process Joint Tech & Mgt Reviews MIL-STD-1521B MIL-STD-499A DOD-STD-2167A MIL-STD-973 DOD-STD-7935A Old DoD MILSPEC approach to DoD System and Software Development 1.1 J-STD-016-1995 ISO 12207 IEEE/EIA 12207

10. Software Acquisition Management SAM-450 EXEC SAM Legend Mil-Std- 498 Systems Engineering Standards EIA / IS 632 ISO 15288 ISO/IEC 12207 IEEE 1498 /EIA 640 Software Standards Mil-Std- 499B Mil-Std- 499A DoD-Std- 7935A 1994 Jan 1999 1995 1996 1994 1988 1974 (Not Released) DoD-Std- 2167A 1988 DoD-Std- 1703 1987 Mil-Std- 499 1969 (Trial Use) IEEE 1220 (Full Standard) (Drafts) J-Std-016 1997 Supersedes Source for EIA 632 EIA/ANSI 632 Others... (Updates) IEEE 1220 (Updates) EIA/IS 731 SE CMM IEEE 1220 ISO/IEC 12207 (Updates) (Interim) IEEE/EIA 12207.x 1998 *Based on SMI INCOSE Nov 97 presentation (Full Standard) Systems & Software Standards Systems & Software Standards* Jan 1999 Rev 1.1

11. Software Acquisition Management SAM-450 EXEC SAM *Derived from Annex B J-STD-016 and Annex B.4 ISO 12207.0 Before any standard can be successfully use by a developer, these types of questions must have been considered by the acquirer! Some Key Tailoring Preconditions* What organizational policies (languages, safety, security, reserve margins, etc.) apply? What Acquisition Strategy is being used? What software builds are envisioned? What activities are required in each build? What is the role of IV&V agents? What is the software support concept? What lifecycle model is relevant and applicable? Which system lifecycle activities are applicable? How are Software Items (SI) selected? What types of software products (new, NDI, firmware, embedded, COTS, etc.) are envisioned? What management controls (testing, reviews,etc.) are needed? What deliverables are needed and why? Format? Who will tailor deliverable content? Rev 1.1

12. Software Acquisition Management SAM-450 EXEC SAM Universal Truth # 6: Shortcuts in software configuration management lead to chaos when the “rubber hits the road” Management Emphasis Use review boards to enforce CM Allow no exceptions to CM rules Anything that is shared by two or more people should come under configuration control Elephant Bungee Jumping # 6: Help…I’ve Fallen and I Can’t Get Up Elephant Bungee Wisdom

13. Software Acquisition Management SAM-450 EXEC SAM Universal Truth # 10: Cutting- edge software development tools lead to bleeding edge projects Management Emphasis Use only established technologies Reduce requirements if necessary to avoid cutting-edge technologies Add reserve margins to the project to account for these technologies If cutting edge technologies must be used for software development, make them your no. 1 risk item Elephant Bungee Jumping # 10: Cutting Edges and Bloody Mistakes Elephant Bungee Wisdom

14. Software Acquisition Management SAM-450 EXEC SAM Universal Truth # 15: Avoid ping pong developments like the plague Management Emphasis Control deliverables via interfaces Make deliverables testable in a stand- alone mode prior to integration Keep the skill base to correct code on contract until until final transition Don’t allow modules to be shuttled between different developers Make subcontractor management a key contractual clause Dispersed contractors increase risk Elephant Bungee Jumping # 15: Self-Eating Watermelons Elephant Bungee Wisdom