Model Based Systems Engineering MBSE using Sys ML

Model Based Systems Engineering (MBSE) using Sys. ML GSFC Systems Engineering Seminar June 8, 2010 Sanford Friedenthal Lockheed Martin sanford. friedenthal@lmco. com

Topics § Model-based Systems Engineering (MBSE) Motivation and Scope § System Modeling Using Sys. ML § System Model as an Integration Framework § Deploying MBSD into your Organization § Sys. ML Status and INCOSE MBSE Roadmap § MBSE Observations § Summary

MBSE Motivation and Scope

SE Practices for Describing Systems Future Past § Specifications § Interface requirements § System design § Analysis & Trade-off § Test plans Moving from Document centric to Model centric

Model-based Systems Engineering (MBSE) § Formalizes the practice of systems development through use of models § Broad in scope – Integrates with multiple modeling domains across life cycle from system of systems to component § Results in quality/productivity improvements & lower risk – Rigor and precision – Communications among system/project stakeholders – Management of complexity Vertical Integration Life Cycle Support © Copyright Lockheed Martin Corporation All Rights Reserved

System Description • Document-Based System Engineering: Where is truth? Document 1 A<B Document 2 A=B Document 3 A>B Inconsistencies within and among documents • Model-Based System Engineering: Model Repository Model enforces consistency © Copyright Lockheed Martin Corporation All Rights Reserved

System Modeling Using Sys. ML

System Modeling Requirements Integrated System Model Must Address Multiple Aspects of a System

What is Sys. ML? § A graphical modeling language in response to the UML for Systems Engineering RFP developed by the OMG, INCOSE, and AP 233 – a UML Profile that represents a subset of UML 2 with extensions § Supports the specification, analysis, design, verification, and validation of systems that include hardware, software, data, personnel, procedures, and facilities § Supports model and data interchange via XML Metadata Interchange (XMI®) and the evolving AP 233 standard (in-process) Sys. ML is Critical Enabler for MBSE

4 Pillars of Sys. ML

4 Pillars of Sys. ML – ABS Example 1. Structure 2. Behavior interaction state machine activity/ function definition use 3. Requirements 4. Parametrics

Sys. ML Model Used to Elaborate System and Component Requirements

System Model as an Integration Framework

MBSE Must Integrate across Modeling Domains Ops/Mission Analysis Logistics Support Manufacturing System Design Integration & Test Modeling Domains Algorithm Development Performance Simulation Software Design Engineering Analysis Hardware Design Human System Integration © Copyright Lockheed Martin Corporation All Rights Reserved

Using System Architecture Model as an Integration Framework System Architecture Model Analysis Models U(s) G(s) Verification Models ò Req’ts Allocation & Design Integration Hardware Models S R SET CLR Software Models Q Q © Copyright Lockheed Martin Corporation All Rights Reserved

Using the System Architecture Model to Flowdown Requirements System-of-System Level Mission Concept of Operations Trade Studies, Simulation, Specification Reviews, etc. UC • 1 st Level Of Decompositions • How Our System Contributes to the Overall Mission System 1 Spec . . . System 2 Spec Behavior, Structure & Requirements System Level • Derives Subsystems • Allocates Requirements to Subsystems A-Spec Sub. System 1 Spec . . . Sub System 2 Spec Behavior, Structure & Requirements Element Level • • Trade Studies, Simulation, Specification Reviews, etc. UC Derives Hardware and Software Components Allocates Requirements to Components B-Spec UC SW Comp 1 Spec . . . SW Comp X Spec Component Design & Implementation Level Trade Studies, Simulation, Specification Reviews, etc. Behavior, Structure & Requirements UC (from John Watson/LMC Sys. ML Info Days presentation) Comp 1 Software . . . Comp X Software © Copyright Lockheed Martin Corporation All Rights Reserved

System Decomposition Process using Sys. ML Analyze System Level Requirements Input UC . . . Analyze System Services Identify the Subsystem Analyze Subsystem Collaboration to Satisfy the System Services Trade Studies, R&D, Simulation, Specification Reviews, etc. Incorporate Additional Analysis as Needed Derive and Allocate Requirements to Subsystem Yes UC . . . The Subsystem shall. . Derived Requirements Continue? No Complete Subsystem Specs (from John Watson/LMC Sys. ML Info Days presentation) © Copyright Lockheed Martin Corporation All Rights Reserved

System Architecture Model to Support Tradeoff Analysis Alt 2 Alt 3 System Architecture Model Analysis Results Cost Reliability Performance Subsystem Alternative 1 Alternative 2 Alternative 3 Sensor 1 Sensor 2 Sensor 3 Processor 1 Processor 2 Processor 3 Control 1 Control 2 Control 3 Criteria Weight Performance 0. 5 7 5 5 Reliability 0. 2 4 6 5 Cost 0. 3 3 5 8 5. 2 4. 2 5. 9 Effectiveness Alt 1 Alt 2 U(s) Alt 3 © Copyright Lockheed Martin Corporation All Rights Reserved G(s) ò Optimization

Integrating Sys. ML with Simulation GIT* Project Modelica Lexical Representation (auto-generated from Sys. ML) [Johnson, 2008 - Masters Thesis] * Georgia Institute of Technology

Deploying MBSD into Your Organization

Deploying MBSD as part of Improvement Process ASSESS Assess the state of your practice DEPLOY Incrementally integrate changes into the current workflow PLAN Plan the improvement Infrastructure & Support Practices Tools Training PILOT Pilot the practice and tailor the approach CODIFY Codify the practice © Copyright Lockheed Martin Corporation All Rights Reserved

Sys. ML Status and INCOSE MBSE Roadmap

OMG Sys. ML™ Status § Specification – OMG Beta Specification in May ’ 06 – Available Specification v 1. 0 in Sept ’ 07 – Available Specification v 1. 1 in Nov ‘ 08 – Revision task force for v 1. 2 in Dec ‘ 09 – Revision task force for v 1. 3 in process § Adoption – – – Multiple vendor implementations available Increasing number of early adopters across industry Being introduced into academia Books available (4) Sys. ML Certification being developed DISR Emerging Standard (March 26, 2009) § Information can be found on the OMG Sys. ML Website at http: //www. omgsysml. org/

INCOSE MBSE Roadmap MBSE Capability Reduced cycle times System of systems interoperability Design optimization across broad trade space Cross domain effects based analysis Extending Maturity and Capability Institutionalized MBSE across Academia/Industry Distributed & secure model repositories crossing multiple domains Well Defined MBSE Maturity Defined MBSE theory, ontology, and formalisms Architecture model integrated with Simulation, Analysis, and Visualization Matured MBSE methods and metrics, Integrated System/HW/SW models Ad Hoc MBSE Document Centric Emerging MBSE standards 2010 Refer to activities in the following areas: • Planning & Support • Research • Standards Development • Processes, Practices, & Methods • Tools & Technology Enhancements • Outreach, Training & Education 2020 2025

MBSE Observations § Transition from document-centric to model-centric is a cultural change § Well defined MBSE method is essential § Multiple tool vendors provide a range of price point, capability, and standards conformance § MBSE training should include language, method, and tools § Employ pilots to validate your MBSE approach § Need buy-in from program and customer on MBSE benefits, approach and deliverables § Scope model to support program objectives and within program constraints § A lot has been learned, but much more remains © Copyright Lockheed Martin Corporation All Rights Reserved

Summary § MBSD is a key practice to advance complex systems development § Standards such as Sys. ML and UML are critical enablers of MBSD § Multiple tool vendors implementing Sys. ML § System architecture model and standards based approach facilitate integration across modeling domains § Growing interest and application of MBSD

Acronyms § § MBSE – Model-based Systems Engineering OMG – Object Management Group Sys. ML – Systems Modeling Language UML – Unified Modeling Language

Sys. ML Diagram Taxonomy