David C. Meshel Senior Staff Systems Engineer NG-LAS 5115 Calvert Road College Park, MD 20740

1. Integrated Systems Engineering EnvironmentAn Interactive On-line Systems Engineering / Management Tool for use by Programs Managers and EngineersJanuary 7, 2002INCOSE - Northern Virginia Chapter David C. Meshel Senior Staff Systems Engineer NG-LAS 5115 Calvert Road College Park, MD 20740 (301) 454-9238 david_meshel@littonas.com

2. Mandate - Develop a Standard Systems Engineering Process • What are we doing now? • Adhoc processes on each program - Some good, some bad, all different • What do we need to do? • Come up with a consistent process • Not a mandated document exercise, some thing we can use • Add the items each program isn't doing now to complete the total process • Move to mapping effort to CMMI certification • Match to and incorporate existing SW SEI Level 3 certification and ISO Procedures • Roll out a process that can be used by everybody ( Big and Small) and for all new proposal activities • Process and associated documentation hosted on central server • Available on-line • Access by all company personnel • Interactive • Tailorable for specific program needs

3. Mandate -Develop a Systems Engineering Process - Goals • The process needs to be comprehensive • Incorporate functional organization processes and procedures • Customer • Design Engineering • Electrical • Mechanical • Logistics and Field Support • Manufacturing • Product Assurance • Program Management • Software Engineering • Specialty Engineering • Systems Engineering • Test Engineering • Needs to identify • Products of processes • Process Dependencies (goes into and out of) • Needs to define and provide guidance on executing the process Effort to be lead by a Systems Engineering Integrated Process Team (SEIPT)

4. Systems Engineering / Software Engineering Standards - Quagmire Chart

5. PROGRAM MANAGEMENT CUSTOMER SYSTEMS ENGINERING COMPANY ADMINISTRATION FUNCTIONAL ORGANIZATIONS Systems Engineering IPT as the Focal Point Public and Regulatory Agencies Politics External Influences PM Finance Contracts Marketing Test Engineering Procurement Manufacturing Product Assurance Security Facilities Human Resources Systems Engineering coordinates the activities between the major organizations

6. Keys to Success • Integrated Systems Engineering Environment Approach: • Must be totally integrated into the way of doing business • Must have Top Management approval • Must have Program approval • Must involve the domain experts (functional organizations) • Must involve the Customer(s)

7. Integrated Systems Engineering Environment - Major Elements • Technical Program Planning and Control • Guidelines on program acquisition phase • Defines acquisition phase transition milestones (design reviews) • Defines deliverables for each milestone • Guidelines on IPT charters, composition and responsibilities • Systems Engineering Process Cycle • Defines the systems engineering process for each phase of the product lifecycle • Defined inputs / outputs (products) for each process step • Systems Engineering Functions • Defines the people skills required for each systems engineering function Why What When How Where Who

8. Technical Program Planning And Control Pre-Systems Acquisition Concept & Technology Development System Development & Demonstration Production & Deployment Sustainment Operations and Support Concept Exploration Component Advanced Development System Integration System Demonstration Systems Integration & Control • Requirements Management • Risk Management • Effectiveness Analysis • Decision Management / Database • Technical Performance Measurement • Trade Study Management • Cost Analysis • Technologies Development • Program Planning / Integration • Specialty Engineering Integration Identify Customer(s) Needs Requirements Engineering Process Perform Systems Requirements Analysis and Functional Allocation Development / Analysis of Alternatives User feedback Develop System / Product Concept(s) SCR SRR System Design and Development Implement Product / Process Detail Design / Development SDR Manufacturing & Integration PDR Component / System Testing & System Integration Program Reviews Entry Criteria Exit Criteria CDR Verification and Implementation TRR SVR PRR Implementation / Operations and System Improvements Applying SE Processes to Acquisition Phases

9. Technical Program Planning And Control as Modeled • Model describes acquisition phases for • DOD Programs • NASA Program • Commercial Program (TBD) • Model has procedures and processes that are common across any type of program • Work Breakdown Structure • SEMP / IMP • SEMS / IMS • Program Reviews • IPT Structures • Others (TBD)

10. EIA/IS-632 Systems Engineering Process - Dec 94 Systems Analysis & Control • Requirements Analysis • Analyze Missions & Environment • Identify Functional Requirements • Define / Refine Performance & Design Constraint Requirements • Select Preferred Alternatives • Trade-off Studies • Effectiveness Analysis • Risk Management • Configuration Management • Interface Management • Data Management • Performance-Based Progress Measurement • SEMS • TPMs • Technical Reviews • Process Input • Customer Needs / Objectives / Requirements • Mission / Operations • Measures of Effectiveness • Environments • Constraints • Technology Base • Prior Output Data • Program Decision Requirements • Requirements from Tailored Standards & Specifications Requirements Loop • Functional Analysis / Allocation • Decomposition to Lower-Level Functions • Allocate Performance & Other limiting Requirements to Lower-Level Functions • Define / Refine Functional Interfaces (internal / External) • Define / Refine / Integrate Functional Architecture Design Loop • Synthesis • Transform Architectures (Functional to Physical) • Define Alternate Product Concepts • Define / refine Functional Interfaces (Internal / External) • Define Alternative Product & Process Solutions Verification • Integrated Decision Database • Decision Support Data • System Functional & Physical Architectures • Specifications & Baselines • Balanced System Solution Process Output

11. Technical Management Planning Process Assessment Process Control Process Acquisition & Supply Supply Process Acquisition Process System Design Requirements Definition Process Solution Definition Process Product Realization Implementation Process Transition to Use Process Technical Evaluation Systems Analysis Process Requirements Validation Process System Verification Process End Product Validation Process ANSI/EIA-632-1998 Relationship of Process for Engineering a System Outcomes and Feedback Requirements System Products Acquisition Request Designs Products Plans, Directives & Status

12. Requirements Engineering Process FUNCTIONAL BASELINE 5. CONDUCT SYSTEM RQMTS. REVIEW CONDUCT LCC AND CAIV TRADE-OFFS TOP LEVEL PERFORMANCE REQUIREMENTS ID KEY COST ATTRIBUTES AND RELATIONSHIPS 4. ESTABLISH FUNCTIONAL BASELINE SYSTEM DESCRIPTION INTERFACES SYSTEM ANALYSIS AFFORDABILITY BOUNDRIES 3. IDENTIFY ATTRIBUTES TO SUPPORT OBJECTIVES DESIGN REFERENCE MISSION 2. DEFINE SYSTEM BOUNDRIES GEO-ECOMONIC ALTERNATIVES 1. DEFINE ENVIRONMENT OPERATIONAL NEEDS AND REQUIREMENTS Development and Analysis of Alternatives Verification and Implementation Models & Simulations Selected Alternatives Reviews Plans Specifications Screened Alternatives Verification Matrix Identified Alternatives Test Reports Manufacturing & Integration System Design & Development Development of Baselines HW - SW Allocation Product Baseline Rqmts Fnct’s Archtr. Allocated Baseline Systems Engineering Process Cycle Customer/ User Needs Process Inputs Process Inputs External Influences Technologies Existing Designs Politics & Market Existing Facilities Integration, Test and Verification Loop Requirements Loop Systems Integration & Controls Process Output Design Loop • Product • Process • System • Facility Build and Test Loop

13. Modeling the SE Process using the CASE Tool • SE Process is defined as a series of functions with linked inputs and outputs • Each function is described in detail in the CASE Tool: • Owner • Definition • Inputs • Outputs • Requirements • Clarifications / Rationale • Metrics (for CMMI Compliance) • CASE Tool can display: • Functional Flow Diagram • Hierarchical Process Diagram • Create formatted text output as a SE Process / Procedure

14. Requirements Engineering Process FUNCTIONAL BASELINE 5. CONDUCT SYSTEM RQMTS. REVIEW CONDUCT LCC AND CAIV TRADE-OFFS TOP LEVEL PERFORMANCE REQUIREMENTS ID KEY COST ATTRIBUTES AND RELATIONSHIPS 4. ESTABLISH FUNCTIONAL BASELINE SYSTEM DESCRIPTION INTERFACES SYSTEM ANALYSIS AFFORDABILITY BOUNDRIES 3. IDENTIFY ATTRIBUTES TO SUPPORT OBJECTIVES DESIGN REFERENCE MISSION 2. DEFINE SYSTEM BOUNDRIES GEO-ECOMONIC ALTERNATIVES 1. DEFINE ENVIRONMENT OPERATIONAL NEEDS AND REQUIREMENTS Requirements Engineering Process Program Requirements Rules, Orders, Regulations, Standards Outputs Politics & Market Place • Top Level System Requirements • Requirements Traceability Matrix • System Concept of Operations • Functional Architecture • System Functional Block Diagram • System External Interfaces • Life Cycle Cost Objectives • Verification Methodology • Programmatic Risks • Technical Performance Measures • Logistics • Program Systems Engineering Master Schedule • Preliminary Models / Simulations Inputs Perform Systems Requirements Analysis and Functional Allocation • Customer / User Needs • Performance Requirements • System External Interfaces • Environmental Requirements • External Influences • Federal Regulations • Navy Orders • Standards • Available Funding • Define customer needs • Identify requirements • Decompose requirements to appropriate working level • Identify top-level functions • Decompose functions to appropriate working level • Integrate functional interfaces • Define performance measures of effectiveness • Identify Systematic Risks

15. Requirements Engineering Process - as Modeled

16. Development and Analysis of Alternatives Models & Simulations Selected Alternatives Screened Alternatives Identified Alternatives Development and Analysis of Alternatives Inputs Outputs • Top Level System Requirements • System Concept of Operations • Functional Architecture • System Functional Block Diagram • System External Interfaces • Life Cycle Cost Objectives • Verification Methodology • Programmatic Risks • Technical Performance Measures • Logistics • Program Systems Engineering Master Schedule • Existing Designs • Available Technologies • Available Facilities • System Designs and Concepts • Internal / External Interface Designs / Requirements • Identified Technical, Schedule and Cost Risks • Detail Cost and Schedules Estimates • Identified Critical Technologies and Processes • Prime Item Performance Spec(s) • System Test Plan • Identify and develop alternatives (designs / concepts) • Verify compatibility of program interfaces • Ensure traceability between program requirements and functions • Identify, quantify, mitigate and track risks • Reconcile cost, schedule, and scope issues

17. Development and Analysis of Alternatives - As Modeled • Model includes functions for • Design Engineering • Logistics and Support • Manufacturing • Program Management • Systems Engineering • Specialty Engineering • Software Engineering • Test Engineering • Each function depicts • Inputs and outputs • Dependencies • Deliverable Products (CDRLs) • Similar models for the other Systems Engineering processes • Manufacturing and Integration • System Design and Development • Systems Integration and Control • Verification and Implementation

18. Typical Systems Engineering Functions Life Cycle Cost Analysis Systems Analysis Systems Architecture Modeling and Simulation • Affordability • Design - to - Cost • Life Cycle Cost • Cost as Independent Variable • Concept of Operations • Mission Utility Studies and Trades • BMC4I • Communications Architecture • Command & Control Architecture • Data Processing Architecture • Functional Allocations • Functional Architecture • Hardware - In - Loop • 6 Degrees of Freedom • Computer - In - loop • System End - to - End Simulation Risk Management Operational Site Integration Training and Tool Development System Test and Verification • Risk Assessment • Risk Mitigation • Risk Tracking • Risk Monitoring • Shipboard Systems • Aircraft Systems • Spacecraft Systems • Tactical Systems • CASE Tool Implementation • SE Training • Requirement Verification Matrix • System Test Planning • System Test Methods & Procedures Requirements Development and Analysis System Design and Integration Software Development Specialty Engineering • Analysis • Database • Identification • Interfaces • Specifications • Configuration Control • Integration • P4I • Performance • Synthesis • TPMs • Trade Studies • Software Engineering Environment Tools • Software Development Plan • Software Specifications (CSCIs) • Dependability / Durability / Reliability • EMI/EMC • Fault Tolerance • Human Factors • Logistics / Supportability • Maintainability • Parts, Materials & Processes • Producibility • Safety • Security • Survivability / Vulnerability • Testability

19. Tools Provides Guidance for each Function / Process • Each function / process provides guidance and/or specific instructions • Description • CMMI compliance criteria • Inputs to process • Outputs from process • Requirements and/or guidance criteria • Verification Metrics • Process document can be extracted from the tool using a “script”

20. Functional Organization Processes • Design Engineering • Logistics and Field Support • Manufacturing • Product Assurance • Program Controls • Software Engineering • Systems Engineering • Test Engineering Integrated Systems Engineering Environment - Results Program Management • Deliverables • Schedules • Requirements CMMI Compliant Process ISEE Server Application & Database • Standard Processes and Procedures • Common (Tailorable) Program Plan • CMMI / ISO Process Metrics Company Administration Policies and Procedures • Facilities • Procurement • Safety • Security

21. Back-up Charts

22. Systems Engineering Benefits 1. Decomposing top-level requirements into workable lower-level specifications and guidelines provides a framework for integrated product development. 2. Reporting programmatic changes to the program team, and assessing and integrating the impact of those changes back into established baselines ensures that there are no surprises in the development of products and services. 3. Integrating various engineering resources ensures products and services will perform as intended and meet customer requirements. 4. Eliminating repetitive efforts reduces program costs and expedites schedules.

23. Systems Engineering Benefits (cont’d) 5. Establishing a basis for informed decision making results in defensible decisions and increased customer acceptance of products and services. 6. Delegating many of the product analyses and integration activities to Systems Engineering allows program managers to more effectively focus on key issues and customer interfaces.

24. Systems Engineering References • Electronics Industry Association: EIA/IS 632 Systems Engineering - Version Dec 94 • IEEE Standard for Application and Management of the Systems Engineering Process - P1220-1998 • Program Executive Office - Theater Air Defense (PEO(TAD)) - Systems Engineering Plan: Volume I - Systems Requirements Engineering • MIL-STD-1521B Technical Program Reviews • DoD instruction 5000.2-R3 Mandatory Procedures for Major Defense Acquisition Programs • Defense Systems Management College: Systems Engineering Fundamentals • Lockheed Martin Missiles and Space Company, Code 66 Systems Engineering Manual • International Council On Systems Engineering (INCOSE) publications and technical papers • Johns Hopkins University, Applied Physics Laboratory - System Engineering Principles and Practice - A Guide to the Engineering of Complex Systems • Carnegie Mellon University Software Engineering Institute (SEI) publications

25. Development and Analysis of Alternatives Models & Simulations Selected Alternatives Screened Alternatives Identified Alternatives System Design and Development • Collect parametric data • Establish technical and cost baseline • Perform sensitivity and trade analyses • Provide documentation that allows informed customer and management decision-making • Establish formal configuration control of technical data package • Optimize alternatives • Perform decision analyses • Optimize solution • Prototyping Outputs Inputs • Detail Designs • Internal / External Interface Designs • Refined Models / Simulations • Performance Assessment • Risk Mitigation Plans • Detail Cost and Schedules • Selected Technologies and Processes • Product Specs (B, C and D) • Subsystem Test Plans • System Designs and Concepts • Internal / External Interface Designs / Requirements • Identified Technical, Schedule and Cost Risks • Detail Cost and Schedules Estimates • Identified Critical Technologies and Processes • Prime Item Performance Spec(s) • System Test Plan

26. Manufacturing & Integration HW - SW Fabrication & Integration Inputs • Establish Bill of Materials • Procurement of parts, materials and Processes • Fabrication of parts and components • Build, Code and Unit Test Software • Assemble components, subsystems and system elements • Update technical data package • Integrate hardware and software Outputs • Detail Designs • Internal / External Interface Designs • Refined Models / Simulations • Performance Assessment • Risk Mitigation Plans • Detail Cost and Schedules • Selected Technologies and Processes • Product Specs (B, C and D) • Test Plans • Comprehensive technical data package • System, Subsystem, and component test plans and procedures • As-built configuration list • Risk Mitigation Reports

27. Verification and Implementation Reviews Plans Specifications Verification Matrix Test Reports Verification and Implementation • Define verification and test criteria and requirements • Reconcile verification and testing with baseline requirements • Execute test plans and procedures • Ensure verification and testing is completed • Perform test and design reviews • Support implementation of product Inputs Outputs • Top Level System Requirements • Prime Item Performance Spec(s) • Subsystem and Component Spec(s) • System Concept of Operations • Functional Architecture • System Functional Block Diagram • Verification Methodology • Test Requirements • Test Procedures • Test Equipment Requirements • Packaging, Handling, Shipping & Transportation Equipment • Facility Requirements • Test Reports • GFE Requirements

28. System Integration and Control Systems Integration & Controls • Integrate technical system interfaces • Integrate technical and administrative interfaces • Develop and maintain SEMP, SEMS & SEDS (program planning) • Support configuration management • Conduct Risk Management • Coordinate and conduct technical reviews • Provide system data for effective decision making • Cost as Independent Variable Analysis • Technical Performance Measurement • Specialty Engineering Integration Inputs Outputs • System and Subsystem Designs • External System Interface Designs / Requirements • Customer Schedule Requirements • System & Subsystem Requirements • Contract, Funding & SOW Requirements • Deliverables (CDRLs) • Design / Requirements Change Requests • Requests for Action Items • SEMP, SEMS & SEDS • EVMS Performance Measurement Baseline • CCB Record of Decisions • Conflict Resolution • Risk Assessments & Mitigation Plans • Performance Assessment Reports

29. Systems Engineering Management Plan and Schedules • Systems Engineering Management Plan (SEMP) • Defines Systems Engineering methodologies: “how to” processes • Defines the products of the processes • Defines the pass / fail criteria for each process / product • Systems Engineering Master Schedule (SEMS) • Identifies the top level milestones • Identifies the “significant accomplishments” that determine the milestones • Assigns each significant accomplishment to a WBS element • Identifies interdependencies (predecessors and successors) for each significant milestone • Compatible with Earned Value Management Systems (EVMS) process (Work packages and activity data sheets) • Systems Engineering Detail Schedule (SEDS) • Identifies the criteria that determine the significant accomplishment • Identifies the specific tasks that accomplish the criteria • Assigns each criteria and task to a WBS element • Compatible with EVMS process • Identifies the critical path

30. Costs Allocated to Costs WBS Cost Physical Architecture Verification Methodology Functional Behavior Requirements Specifies Verifies Processes CAIV Analysis Cost Analysis System Description Test Methods Test Procedures Data CONOPS Behavioral Model Specifications Traceability Matrix Products Program Implementation of ISEE • ISEE also is used to capture program specific engineering data • ISEE provides the capability to • capture all the system requirements and associated rationale • capture system architecture • capture top to mid level design data (physical architecture) • capture verification methodologies and plans • capture cost • provides traceability of information throughout the system. • ISEE documents the results of the Systems Engineering Processes

31. ISEE Database Schema - Baseline documented verified by by specifies Statement of Work Customer Requirements Test Report System Functions Test Events Document allocated to incorporates Verification Event Function configuration for specifies System Components Annexes Attachments Clauses & Schedules tested by defines Customer Clarifications clarifies Component Test Methods & Procedures costs Clarifications traces to costs Cost Test Procedures implemented by documented by Item Specs Contractor Derived Requirements WBS Document Test Resources & Equipment Test Requirements verifies Verification Requirement Requirements Test Configuration categorizes generated by caused by Risks Issues Categories Categories, Risks and Issues can be attributes linked to any database element Category Risk Issue The Systems Engineering Process defines the baseline schema and its implementation