ACE3 Working Group Session, March 2, 2005

Similar documents
Concurrent Increment Sequencing and Synchronization with Design Structure Matrices in Software- Intensive System Development

Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - ISPA-SCEA 2007

Object-oriented Analysis and Design

Typical Project Life Cycle

Object-Oriented Design

SERC Technical Overview: First-Year Results and Future Directions. Barry Boehm, USC Rich Turner, Stevens. 15 October 2009

An introduction to software development. Dr. C. Constantinides, P.Eng. Computer Science and Software Engineering Concordia University

UNIT-III LIFE-CYCLE PHASES

Software Life Cycle Models

Requirements Gathering using Object- Oriented Models

A FRAMEWORK FOR PERFORMING V&V WITHIN REUSE-BASED SOFTWARE ENGINEERING

Evolving Enterprise Architecture

Model Based Systems Engineering (MBSE) Business Case Considerations An Enabler of Risk Reduction

A Case Study of Changing the Tires on the Bus While Moving

SYSTEMS ENGINEERING MANAGEMENT IN DOD ACQUISITION

Unit 5: Unified Software Development Process. 3C05: Unified Software Development Process USDP. USDP for your project. Iteration Workflows.

About Software Engineering.

THR%%A%P COM 1?4w XFROX. Agenda

Our Acquisition Challenges Moving Forward

Michael Gaydar Deputy Director Air Platforms, Systems Engineering

UNIT IV SOFTWARE PROCESSES & TESTING SOFTWARE PROCESS - DEFINITION AND IMPLEMENTATION

Spiral Acquisition and the Integrated Command and Control System

Stevens Institute of Technology & Systems Engineering Research Center (SERC)

Software Project Management 4th Edition. Chapter 3. Project evaluation & estimation

ESA Iris Programme Analysis & definition of the Satellite System Operations. Briefing 28 July

Manufacturing Readiness Levels (MRLs) and Manufacturing Readiness Assessments (MRAs)

Refinement and Evolution Issues in Bridging Requirements and Architectures

Software Maintenance Cycles with the RUP

IS 525 Chapter 2. Methodology Dr. Nesrine Zemirli

Are Rapid Fielding and Good Systems Engineering Mutually Exclusive?

Human System Integration: Challenges and Opportunities

The Drive for Innovation in Systems Engineering

DEFENSE ACQUISITION UNIVERSITY EMPLOYEE SELF-ASSESSMENT. Outcomes and Enablers

Critical Role of Software Engineering in Development Planning and Sustainment

Test and Evaluation of Autonomous Systems & The Role of the T&E Community in the Requirements Process

The Impact of Conducting ATAM Evaluations on Army Programs

Model-Based Systems Engineering Methodologies. J. Bermejo Autonomous Systems Laboratory (ASLab)

CS Division of EECS Dept. KAIST

DoDI and WSARA* Impacts on Early Systems Engineering

A New Way to Start Acquisition Programs

NASA Space Exploration 1 st Year Report

ULS Systems Research Roadmap

Jerome Tzau TARDEC System Engineering Group. UNCLASSIFIED: Distribution Statement A. Approved for public release. 14 th Annual NDIA SE Conf Oct 2011

Architecture Standards for Software Technology Readiness Assessments

Introduction to Software Engineering

Tutorial - Track 8: The Effective Use of System and Software Architecture Standards for Software Technology Readiness Assessments

UNIT VIII SYSTEM METHODOLOGY 2014

Fundamentals of Systems Engineering

OCEAN OBSERVATORIES INITIATIVE. Release 2 Schedule. OOI CI Release 2 Kickoff M a y 2,

A System Maturity Index for Decision Support in Life Cycle Acquisition

Introduction to Systems Engineering

CC532 Collaborative System Design

Course Introduction and Overview of Software Engineering. Richard N. Taylor Informatics 211 Fall 2007

CHAPTER 1: INTRODUCTION TO SOFTWARE ENGINEERING DESIGN

Assessing the Value Proposition for Operationally Responsive Space

Using Data Analytics and Machine Learning to Assess NATO s Information Environment

An Architecture-Centric Approach for Acquiring Software-Reliant Systems

Manufacturing Readiness Assessment (MRA) Deskbook

Systems Engineering Overview. Axel Claudio Alex Gonzalez

Customising Foresight

An Element of Digital Engineering Practice in Systems Acquisition

Agile Non-Agile. Previously on Software Engineering

Engineering Autonomy

When Failure Means Success: Accepting Risk in Aerospace Projects NASA Project Management Challenge 2009

Systems Engineering. An Introduction. What is a system? Definition: Systems Engineering is an interdisciplinary. deploying successful systems.

Lesson 17: Science and Technology in the Acquisition Process

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

Future Concepts for Galileo SAR & Ground Segment. Executive summary

Fundamentals of Systems Engineering

Spiral Development: Experience, Principles, and Refinements

Prototype to product the difficult transition

UML and Patterns.book Page 52 Thursday, September 16, :48 PM

A New Approach to the Design and Verification of Complex Systems

Test & Evaluation Strategy for Technology Development Phase

Technology & Manufacturing Readiness RMS

Developing and Distributing a CubeSat Model-Based Systems Engineering (MBSE) Reference Model Interim Status

MODEL AND SIMULATION BASED SATELLITE ENGINEERING

ENGAGE MSU STUDENTS IN RESEARCH OF MODEL-BASED SYSTEMS ENGINEERING WITH APPLICATION TO NASA SOUNDING ROCKET MISSION

THE APPLICATION OF SYSTEMS ENGINEERING ON THE BUILDING DESIGN PROCESS

Spiral Development: Experience, Principles, and Refinements

Computer Science: Disciplines. What is Software Engineering and why does it matter? Software Disasters

A Knowledge-Centric Approach for Complex Systems. Chris R. Powell 1/29/2015

Presentation of the Xatcobeo project XAT PRE-012-UVIGO.INTA

Synopsis and Impact of DoDI

OSRA Overarching Strategic Research Agenda and CapTech SRAs Harmonisation. Connecting R&T and Capability Development

The New DoD Systems Acquisition Process

EGS-CC. System Engineering Team. Commonality of Ground Systems. Executive Summary

Evaluating Evolutionary Prototyping for Customizable Generic Products in Industry (TAT AB)

Requirements Analysis aka Requirements Engineering. Requirements Elicitation Process

Introduction to Software Requirements and Design

Finding Discipline in an

BEYOND SHALL STATEMENTS: MODERNIZING REQUIREMENTS ENGINEERING

Advancing the Use of the Digital System Model Taxonomy

Domain Understanding and Requirements Elicitation

A MODEL-DRIVEN REQUIREMENTS ENGINEERING APPROACH TO CONCEPTUAL SATELLITE DESIGN

Manufacturing Readiness Level Deskbook

GALILEO Research and Development Activities. Second Call. Area 1A. Statement of Work

Rapid FPGA Modem Design Techniques For SDRs Using Altera DSP Builder

The Role of CREATE TM -AV in Realization of the Digital Thread

UNCLASSIFIED. R-1 Program Element (Number/Name) PE F / NAVSTAR Global Positioning System (User Equipment) (SPACE) Prior Years FY 2013 FY 2014

Transcription:

ACE3 Working Group Session, March 2, 2005 Intensive s The Synergy of Architecture, Life Cycle Models, and Reviews Dr. Peter Hantos The Aerospace Corporation 2003-2005. The Aerospace Corporation. All Rights Reserved.

Acknowledgements This work would not have been possible without the following: Feedback Richard J. Adams, Acquisition and Process Office Dr. Joe Betser, Engineering Subdivision Suellen Eslinger, Acquisition and Process Office Dr. Leslie J. Holloway, Engineering Subdivision Sponsor Michael Zambrana, USAF Space and Missile s Center, Directorate of s Engineering Funding source Mission-Oriented Investigation and Experimentation (MOIE) Research Program ( Acquisition Task) Inspiration Dr. Barry W. Boehm, University of Southern California GSAW/ACE3 2005 Peter Hantos Slide 1-2

Agenda Problem Statement The National Security Space Acquisition Policy (NSSAP 03-01) Acquisition Life Cycle Model Waterfall vs. Iterative/Incremental Development Anchor Points in The IBM/Rational Unified Process (RUP ) Risk-based Life Cycle Model (LCM) Selection Opportunities and Risks of Various LCMs Simplified Hierarchy of and LCMs Different WBS Levels Different LCM Choices Reviews Technical Reviews Technical Reviews and Anchor Point Reviews Architecture-Centric Synergy of Elaboration, Evolution and Evaluation Conclusions RUP is registered in the U.S. Patent and Trademark Office by IBM/Rational Corporation GSAW/ACE3 2005 Peter Hantos Slide 1-3

Problem Statement Fundamental Lack of Understanding and Appreciation of LCMs Current National Security Space Acquisition Policy (NSSAP 03-01) Acquisition phase-names imply a waterfall structure of development Prescribes technical reviews that in their names and their positioning also imply waterfall development Although, with respect to review details, no specifics are given Current Life Cycle Standard (J-STD-016-1995) While does not explicitly exclude iterative development, it does not really supports it either Index does not even has an Iteration -related entry It is not properly harmonized with systems engineering standards Technical Review Standard (MIL-STD-1521B) Although it is under revision, most likely the updated version will still Maintain the obsolete, waterfall-oriented review-names Lack of a solid, overarching, life cycle modeling foundation GSAW/ACE3 2005 Peter Hantos Slide 1-4

NSSAP 03-01 Acquisition Life Cycle Model Small Quantity Model NSS Space Acquisition Policy 03-01 (December 24, 2004) Pre-s Acquisition s Acquisition Sustainment Key 1 A B C st Launch Decision Approval Approval Approval Build Upgrade Points: Approval Decision JROC A B C IOC ICD Pre KDP-A Concept Studies A Concept Development SRR SDR B Preliminary Design PDR C Complete Design CDR Reviews: SRR Requirements Review SDR Design Review PDR Preliminary Design Review CDR Critical Design Review D Build & Operations GSAW/ACE3 2005 Peter Hantos Slide 1-5

Waterfall vs. Iterative/Incremental Development RUP Phases Waterfall INCEPTION ELABORATION CONS TRUCTION TRANS ITION Requirements Disciplines 1 1 1 2 3 1 2 Iterations High-level Design (Architecture) Business Modeling Requirements Detailed Design Implementation (Coding) Unit ing S/W Integration S/W Qualification ing Analysis and Design Implementation Deployment One Increment Legend: Approximate Effort (Notio nal) Flow of Executio n (Mini-Waterfalls ) GSAW/ACE3 2005 Peter Hantos Slide 1-6

Anchor Points in RUP LCO LCA IOC PRR Inception Elaboration Construction Transition Increment Definition: Anchor points are a set of project planning milestones with specific objectives LCO (Life Cycle Objectives) LCA (Life Cycle Architecture) IOC (Initial Operational Capability) PRR (Product Release Review) Anchor Points bring architecture focus into the life cycle Explicitly address architecture option-exploration and evolution GSAW/ACE3 2005 Peter Hantos Slide 1-7

Opportunities and Risks of Various Life Cycle Models Risk Factor Basic Life Cycle Models Category Item Once-Through Incremental Evolutionary Iterative O R O R O R O R Requirements High Requirements Volatility is expected due to user feedback X X X X is not precedented X X X X Requirements are not well understood X X X X User needs some capabilities delivered early X X X X Technology New technology is being incorporated X X X X Rapid changes of critical technologies are anticipated X X X X Complexity Size (SLOC, function points, etc.) is a concern X X X X High level of inter-dependencies amongst different disciplines X X X X The system naturally breaks into increments X X X X Personnel Concerns about responsiveness to funding/staffing needs X X X X Politics Concerns about securing funding for a large project X X X X Difficult stakeholder conflicts are expected X X X X Rigid Simple Adaptive Difficult GSAW/ACE3 2005 Peter Hantos Slide 1-8

Different WBS Levels Different LCM Choices WBS Hierarchy LCM Hierarchy Segments Elements Program management and systems engineering areas - HW/SW discipline-independent considerations Subsystems HW/SW Items HW/SW Units GSAW/ACE3 2005 Peter Hantos Slide 1-9 Project management area - HW/SW discipline and design/development methodology-dependent considerations

Simplified Hierarchy of and LCMs 1st Acquisition Increment 1 st Launch Acquisition A B C D EVOLUTIONARY Requirements 1 st Increment Incr 1 Design Integration 2 nd Increment Incr 2 Integration Qualification INCREMENTAL Ground Ground SPIRAL Spiral 1 Spiral 2 Build 1 Build 1 Build 2 Build 1 Spiral 1 Build 2 Spacecraft WATERFALL Payload 1 st SW Increment SW High- Detail Reqs. Level Design Design 2 nd SW Increment Impl. & Unit Integr. & SW Qual. WATERFALL GSAW/ACE3 2005 Peter Hantos Slide 1-10

Technical Reviews 1st Acquisition Increment 1 st Launch Acquisition A B C D EVOLUTIONARY Requirements 1 st Increment Design 2 nd Increment Incr 1 Integration Incr 2 Integration Qualification INCREMENTAL SRR SDR PDR CDR Ground Spiral 1 Spiral 2 Build 1 Build 1 Build 1 Spiral 1 SPIRAL Build 2 Build 2 Spacecraft WATERFALL Payload WATERFALL 1 st SW Increment SW High- Detail Reqs. Level Design Design 2 nd SW Increment Impl. & Unit In-Process Review Integr. & SW Qual. GSAW/ACE3 2005 Peter Hantos Slide 1-11

Technical Reviews and Anchor Point Reviews 1st Acquisition Increment 1 st Launch Acquisition A B C D EVOLUTIONARY Requirements 1 st Increment Incr 1 Design Integration 2 nd Increment Incr 2 Integration Qualification INCREMENTAL SRR SDR PDR CDR Ground Ground RUP INCEPTION ELABORATION CONSTRUCTION 3 1 1 1 1 2 2 TRANS ITION INCEPTION ELABORATION CONSTRUCTION 3 1 1 1 1 2 2 TRANS ITION Spacecraft WATERFALL Payload 1 st SW Increment SW High- Detail Reqs. Level Design Design 2 nd SW Increment Impl. & Unit Integr. & SW Qual. Anchor Point Reviews WATERFALL GSAW/ACE3 2005 Peter Hantos Slide 1-12

Architecture-Centric Synergy of Elaboration, Evolution and Evaluation Objective Process Domain Product Domain Elaboration Understanding Internals (Refining Implementation) LCM Hierarchy and Synchronization Architectural Views (UML Diagrams) Evolution Understanding and Refining Changing Requirements LCM Choices Use Case Hierarchy Evaluation (Reviews) Progress Against Objectives Integrity of Artifacts Validation of LCM Choices LCM-based Determination of Review Content Verification of Artifacts Verification of Consistency with LCMs GSAW/ACE3 2005 Peter Hantos Slide 1-13

Conclusions Life Cycle Models are key in ensuring the synergy across Evolution, Elaboration, and Evaluation Paraphrasing P. Kruchten, this is a high-level, 3+1 View Model of -Intensive development Due to the dynamic nature of system development, state-of-theart review standards would have to be structured around more meta-level definitions, e.g., Architectural views are consistent with the appropriate LCMs design has been defined to the level of completeness that is based on the selected LCM. Using such standards requires a higher level of sophistication from both the Contractor and the SPO Unfortunately, we don t have a choice here The sophistication of Evaluation must match the rapidly evolving sophistication of system Evolution and Elaboration GSAW/ACE3 2005 Peter Hantos Slide 1-14

Acronyms ACE3 CDR HW IOC J KDP LCA LCM LCO MIL MOIE NSSAP O PDR PRR R RUP SLOC S/W SDR SPO STD SW USAF WBS Architecture-Centric Evolution, Evaluation, and Elaboration Critical Design Review Hardware Initial Operational Capability Joint Key Decision Point Life Cycle Architecture Life Cycle Model Life Cycle Objectives Military Mission-Oriented Investigation and Experimentation National Security Space Acquisition Policy Opportunity Preliminary Design Review Product Release Review Risk IBM/Rational Unified Process Source Lines Of Code Design Review Program Office Standard United States Air Force Work Breakdown Structure GSAW/ACE3 2005 Peter Hantos Slide 1-15