Typical Project Life Cycle D. KANIPE 1/29/2015
Contract Initiation VISION REQUEST FOR INFORMATION REQUEST FOR PROPOSAL SOURCE EVALUATION BOARD RFI RFP Proposals Evaluated Companies Respond Companies Submit Proposals SOW IS WRITTEN PRIOR TO CONTRACT AWARD Statement of Work Winner Selected Develop Requirements, Etc. 2
Project Life Cycle NASA Life-Cycle Phases Formulation Approval Implementation Project Life- Cycle Phases Pre-Phase A/Phase A Concept Studies & Technology Development First Semester Phase B Phase C Phase D Phase E Phase F Preliminary System Operations Final Design & Assembly, & End Design & Technology Integration, Sustaining of Fabrication Completion Test/LaunchEngineering Life Second Semester Robotic Mission Reviews MCR SRR SDR PDR CDR SIR ORR FRR PLAR Supporting Reviews Peer Reviews, Subsystem Reviews, and System Reviews Figure 2 Student Project Life Cycle 3
Key Definitions Formulation: System requirements are baselined Feasible concepts are developed System architecture definition is baselined for the selected concept(s) Implementation: Detailed design of system products is completed Products to be deployed are fabricated, assembled, integrated and tested Products are delivered to their customers or users Baseline: Design solution that meets the stakeholder s expectations Everyone focuses on this one design Baseline is documented Begin configuration management of the design 4
Developing a Baseline Stakeholder Expectations Trade Studies & Iterative Design Loop Start Mission Objectives & Constraints Operational Objectives High Level Requirements Functional And Logical Decomposition Product Breakdown Structure ConOps Requirements Mission Success Criteria No Functional & Performance Analysis Sufficient Level? Yes No Yes Re-baseline Requirements? No Works Safe & Reliable Affordable? Yes Select Baseline 5
Life Cycle Relationships Organizations & People Concept Studies Phase A Phase B Phase C Phase D Phase E Concept & Technology Development Preliminary Design Completion Final Design & Fabrication System Assembly, Int/Test, Launch Operations & Sustainment Artifacts Problems CONOPS Prelim. Design Design-to Specs As-built Asdeployed Concepts System Reqmts. Subsystem Reqmts. Build-to Specs As-verified Asoperated Expectations Validation Plan Verificat n Plan Verificat n Procedures Anomalies
Project Phase Definitions (1/2) Pre-Phase A (Concept Studies) Purpose: To produce a broad spectrum of ideas and alternatives for missions from which new projects can be selected. Phase A (Concept and Technology Development) Purpose: To determine the feasibility of a suggested new system in preparation for seeking funding. Phase B (Preliminary Design and Technology Competition) Purpose: To define the project in enough detail to establish an initial baseline capable of meeting mission needs. Phase C (Final Design and Fabrication) Purpose: To design a system (and its associated subsystems, including its operations systems) so that it will be able to meet its requirements. 7
Project Phase Definitions (2/2) Phase D (System Assembly, Integration and Test, and Launch)) Purpose: To build the subsystems (including operations systems) and integrate them to create the system, while developing confidence that it will be able to meet the systems requirements. Phase E (Operations and Sustainment) Purpose: To ensure that the certified system is ready for operations. Implement the Mission Operations Plan developed in earlier phases. Collect and archive mission and science data. Phase F (Closeout) Purpose: To dispose of the system in a responsible manner. 8
Project Manager Technical Integration Classical Systems Engineering Design and Analytical Integration Hardware & Software Integration Operations Requirements Mgt Functional Analysis System Analysis & Trades Software Management Technology Dev. Req ts WBS Risk Management Verification Plan Configuration/Data Mgt Cost Effective Design Design/Discipline Eng. Software Development Cost Estimates Performance Estimates Verification Requirements Testing Analysis and Simulation Manufacturing/Assembly Interface Management Verification Validation Assembly Ground Mission Logistics Figure 1 Technical Integration Model 9
Alternatives to the Linear Project Life Cycle The development life cycle is dependent upon the technical nature of what s being developed => the project life cycle may need to be tailored accordingly. Spiral development The development and construction activities proceed in parallel Follows the doctrine of successive refinement. Rapid prototyping Produce partially operational mock-ups/prototypes early in the design Allow for learning prior to production of expensive flight unit. Skunkworks (Lockheed trademark) A small team charged to achieve unusual results Work outside the usual rules Minimal management constraints Product design thereafter may be developed more conventionally 10