Lecture 1.5: Systems Engineering Fundamentals (Ch 1)

1. Lecture 1.5: Systems Engineering Fundamentals (Ch 1) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

2. Agenda • The SEF defines DoD’s SE Process and is used by DOD’s Defense Systems Management College (DSMC) to train DOD personnel in SE. • Table of Contents of SEF Guide • Other SE Standards/References • Systems Engineering Overview (Chapter 1)

3. Part 1: Introduction Ch. 1 Introduction to SE Management (Today) Ch. 2 Systems Engineering Management in DoD Acquisition (Wk 2) Part 2: SE Process Ch. 3 Systems Engineering Process Overview (Wk 1 & 2) Ch. 4: Requirements Analysis (Wk 4) Ch. 5: Functional Analysis (Wk 5-10) Ch. 6: Design Synthesis (Wk 5-7, & 12) Ch. 7: Verification (Wk 12) Ch. 8: Systems Engineering Process Outputs (Wk 3-11) Part 3: System Analysis and Control Ch. 9: Work Breakdown Structure (Wk 3) Ch. 10: Configuration Management (Wk 10) Ch. 11: Technical Reviews and Audits (Today) Ch. 12: Trade Studies (Wk 11) Ch. 13: Modeling and Simulation (Wk 11) Ch. 14: Metrics (Wk 11) Ch. 15: Risk Management(Wk 11) Part 4: Planning, Organizing, & Managing Ch. 16: Systems Engineering Planning (Wk 3) Ch. 17: Product Improvement Strategies (Wk 2) Ch. 18: Organizing and Integrating System Development (Wk 3) Ch 19: Contractual Considerations (Today) Ch 20: Management Considerations and Summary The Scope of Systems Engineering Per DSMC SEF Guide

4. Other SE Standards and Guides • DSMC Systems Engineering Fundamentals (SEF) • INCOSE Systems Engineering Handbook (SEH) • NASA Systems Engineering Handbook • IEEE–1220-2005: Standard for Application and Management of the Systems Engineering Process • EIA/IS-632 • ISO/IEC 15288 • MIL-STD-499 • MIL-HDBK-881 • MIL-STD-1521B

5. Chapter 1 Topics: 1.1 Purpose (of SEF) 1.2 Definitions 1.3 Development Phasing 1.4 Systems Engineering Process 1.5 Guidance 1.6 Summary Points Definitions: “A System is an integrated composite of people, products, and processes that provide a capability to satisfy a stated need or objective.” Systems Engineering consists of the technical knowledge domain and the systems engineering management domain (the focus of the SEF Guide) Systems Engineering Definitions from Other References: MIL-STD-499A: “A logical sequence of activities and decisions that transforms an operational need into a description of system performance parameters and a preferred system configuration.” EIA Standard IS-632: “An interdisciplinary approach that encompasses the entire technical effort, and evolves into and verifies an integrated and life cycle balanced set of system people, products, and process solutions that satisfy customer needs.” IEEE P1220: “An interdisciplinary approach, collaborative approach that derives, evolves, and verifies a life-cycle balanced system solution which satisfies customer expectations and meets public acceptability.” Chapter 1: Introduction to SE Management Note: A very likely Final Exam Question is: “Provide YOUR definition of Systems Engineering.”

6. Systems Engineering Management Integrates: Development Phasing Systems Engineering Process Life Cycle Integration It includes: Life Cycle Planning Baseline Development & Management Integrated Teaming 1.2 Definitions

7. Levels/Stages of Development: Concept Development System Development Subsystem/Component Development Systems Engineering Process is applied to each level (one level at a time) DoD Progressive Baselines: Functional Baseline System Requirements Allocated Baseline Design Requirements Product Baseline Design Documentation 1.3 Development Phasing Note: These activities generally occur concurrently and with feedback. Generally, Concept starts before System and System before Subsystem/ Component. Baseline Reviews also occur in that order.

8. SE Process is: Top-Down Comprehensive Recursive It is a Problem Solving Process: Transforms needs and requirements into a set of product and process descriptions Generates information to support decision making Provides input to the next level of development Key Products: Architectures (Functional & Physical) Requirements Studies 1.4 Systems Engineering Process [1] Note: This will be discussed in more detail Next Week

9. Primary Life Cycle Functions: Development Verification Manufacturing Training Deployment/ Activation Operation Support Disposal 1.4 Systems Engineering Process [2]

10. Chapter 1.5: Guidance • DoDI 5000.2 provides overarching guidance for the DoD acquisition process including Systems Engineering • DoD 5000.2 Requires a Disciplined Systems Engineering Process to translate operational needs and/or requirements into a system solution • The DoD Acquisition Guidebook (DAG) provides additional more detailed guidance • This SEF provides specific DoD guidance on Systems Engineering • This guidance is based on 50+ years of DoD acquisition experience: • What works and what does not work • Things that projects neglect to do that get them into (cost and schedule) trouble • Tailoring of the SE Process is expected, but must be done carefully to avoid introducing risk. Note: SEF Reference is now dated, DoDI 5000.2R has been replaced by DoDI 5000 (see homework)

11. SE management integrates: Life Cycle Functions System Engineering Problem Solving Process Progressive Baselining The SE Process is (an iterative) problem solving process that drives the development of system products and processes IPTs should apply the SE Process to develop life-cycle-balanced design solutions Baseline Phasing provides an increasing level of descriptive detail of system products and processes with each application of the SE Process Fundamental SE Activities are: Requirements Analysis Functional Analysis/Allocation Design Synthesis Systems Analysis and Control Verification Baselining/Development Phasing may be summarized as: a concept description that leads to a system definition, that leads to component definitions, that lead to component design that leads to a product The output of each application of the SE Process is a major input to the next SE process application Chapter 1.6: Summary

12. Conclusion/Summary • No single “Right Way/Method” for doing systems engineering • There is a great deal of overlap between different SE models/methods • No program does it “All” and no program does it “Right” • Every program is different and has different constraints: • Customer • Contract/Work Scope • Management • Organizational Structure • Schedule/Budget/Resources • However, every program needs an “integrated structured technical approach” to achieving its objectives. • It is the job of the Systems Engineer to develop a Systems Engineering Process that is tailored to the needs/constraints of each program • We learn “a right way” that provides us a structured “tool kit” that we can make prioritized use of, given the needs/constraints of the program • This is the “Art of Systems Engineering”