INCOSE IW 2012 MBSE Workshop Systems Modeling John

INCOSE IW 2012 MBSE Workshop Systems Modeling John C. Watson Principal Member of Engineering Staff Lockheed Martin, MS 2 Moorestown john. watson@lmco. com 1

Topics • Systems Engineering Modeling Approaches • Key Practices • Integration Challenges Copyright ©

INCOSE - Integrated Systems Engineering Vision Copyright © 2012 by Lockheed Martin Corporation 3

The MBSE Integration Across Domains Program Management Product Support System Architectural Model Analytical Models ò Test Plan G(s) Analysis Spec U(s) Verification Models MBSE Performance, RMA, SWa. P, Cost, etc. Manufacturing Mechanical & Electrical Models S SET Software Models Q R CLR Q Copyright © 2012 by Lockheed Martin Corporation 4

System Architectural Model Value Added • Improve communications across all domains – engineering, manufacturing, management and support • Uniform and Consistent Repository of the “Truth” integrated across all engineering domains • Improve ability to Measure Change Impact – A more thorough and complete assessment – Reduce time to access the change • Reduce the number of defects and detect them earlier Copyright © 2012 by Lockheed Martin Corporation 5

A Model Tree So. S Level System of Systems Model - System Specification Spec S 1 System Level System Model - Subsystem Specification Subsystem Level Subsystem A Model Subsystem B Model . . . Subsystem C Model …. Spec n Spec 1 S/W …. Spec n … Spec 1 S/W Spec 6 Component Domain Model 1 Spec 5 Spec 4 - Implementation Spec 2 Spec 3 - Design Spec 2 Component Level Spec 1 - Component Specification Spec 1 Component Domain Model 2 S/W … S/W H/W Copyright © 2012 by Lockheed Martin Corporation 6

SAM Goal - Derive Component Requirements • The Requirement Flow Down – Analyze Customer Needs – Define System Requirements – Refine Logical Architecture – Synthesize Allocated Architecture – Results • A derived Set of Component Specifications • Used to Buy, Modify or Build Components Copyright © 2012 by Lockheed Martin Corporation 7

System Architecture Model Content System Architecture Model – A structured representation that focuses on the overall system requirements, behavior, structure, properties, & interrelationships • Requirements – What are the stakeholder goals, purposes, and success conditions for the system – Specification of black box behavior and characteristics for each component • Behavior – – What the system has to do to meet the requirements Transformations of inputs to outputs (functional/activity models) State/Mode-based behavioral differences (state models) Responses to incoming requests for services (message models) • Structure – The parts that exhibit the behavior – The component hierarchy, elements, interfaces and stores • Properties – The performance, physical characteristics and governing rules that constrain the structure and behavior • Interrelationships – Including all UML/Sys. ML relationships between model elements. How do we leverage the SAM foundation to Integrate other domains? Copyright © 2012 by Lockheed Martin Corporation 8

Integration of SE Domains within SAM • Allocate & Manage System Budgets • Size • Weight • Power • System Cost • Development Costs • System Readiness Levels • Reliability, Maintainability and Availability (RMA) Copyright © 2012 by Lockheed Martin Corporation 9

Allocate &Manage System Budgets System X Max Power = 100 W Actual = 87. 3 System 18. 8 Subsystems 38 20 SS 1 9. 6 Components 10 4. 9 C 1 -1 5 C 1 -2 40 30 SS 2 5 4. 3 C 1 -3 Copyright © 2012 by Lockheed Martin Corporation 30. 5 SS 3 16. 5 15 9. 5 C 3 -1 10 C 3 -2 5 4. 5 C 3 -3 10

Integration to Program Change Control Process Assess Change Requests Implement Changes Review Change Merge Change into Current Baseline 1. 2. 3. 4. Evaluate change requests Assess change impact Path to all domains Estimate cost of change 1. Isolate information involved in the change 2. Evaluate alternatives 3. Implement change 1. Prepare Review Package 2. Conduct review 3. Adjudicate issues 1. Resolve conflicts 1. Take snapshot of the CM environment (entire or partial) 2. Name and manage Baselines Copyright © 2012 by Lockheed Martin Corporation 11

Integration of SE Domains within SAM • Behavior Execution Animation – Component collaboration – Validate desired behavior • Manage Requirements – Manage Domain Specific Requirement Attributes – Requirement Traceability and Coverage • Derived, Verify, Refine, Satisfy • Manage System Hazards and Safety Requirements • Manage Product Line Variations • Generate External Documents – With Report Generators – Or By Modeling Document Content and Format Copyright © 2012 by Lockheed Martin Corporation 12

System Architecture Models vs. Analytical Models U(s) G(s) ò Used to reduce risks thru analysis, validation and optimization Analysi s Spec Analytical Models Used to capture the system’s behavior, structure, constraints, interfaces and requirements Mathematically-based to support computation or simulation Repository-based to define product entities and their interrelationships A vehicle to solve or verify a solution defined by constraints and assumptions consistent with SAM A vehicle to define the needed analysis task including the task’s goals, imposed constraints, and assumptions Copyright © 2012 by Lockheed Martin Corporation 13

Analysis and Simulation Tool Integration Analytical Models G(s) ò Analysi s Spec U(s) • How have we used them? – Early Conceptual Design • Increase the number of early Architectural iterations • Improves quality and reduces risk of proposal – Behavior Performance Analysis • Validate latency requirements and software deployment – Mechanical Analysis – Thermal Analysis – Calculate allocated budgeted values – Trade Studies – Cost Analysis Copyright © 2012 by Lockheed Martin Corporation 14

Analysis and Simulation Tool Integration • Integrate SAM with multiple analysis tools Weight U(s) • Optimization Across multiple individual analyses – e. g. Optimize across cost, performance, weight G (s) Cost U(s) G (s) Performance U(s) Copyright © 2012 by Lockheed Martin Corporation G (s) 15

Software Domain Integration • Derive Software Architecture Spe c • Deliver Specifications – Software Requirement Specification (SRS) Software Models – Interface Requirement Specs (IRS) – Interface Definition Documents (IDD) – Interface Description Language (IDL) code file • Approach – Direct - Sys. ML to UML Model – Indirect– Extract documents from SAM Copyright © 2012 by Lockheed Martin Corporation 16

Mechanical and Electrical Integration • Deliver Firmware Component Specifications – Direct approach • Interface to Firmware Design Tools SAM (Sys. ML) → System. C → VHDL → Hardware Mechanical & Electrical Models – Indirect approach • Extract specification document from SAM • S SET Q R Q CLR • Cable Specification Documents – Derived Cable Requirements – Identified cable numbers, cable interconnects and internal cable connections – Deliver Interface Control Document (ICD) Copyright © 2012 by Lockheed Martin Corporation 17

Integration and Test Integration Verification Models • SAM Provides – Requirements, behavior, structure, etc. • Using Sys. ML and UTP to: – Define the Test System Architecture – Derive an Integration and Test Plan • Define Test Contexts, Test Cases, and Test Components – Requirement Traceability Matrix – Manage Test Component Inventory Copyright © 2012 by Lockheed Martin Corporation 18

Program Management • Exchange Development Status Metrics – Schedules – Development Costs – Product Costs – Development Progress – Technical Performance • Support Change Control Process – Assess Change Request – Estimate cost of change Copyright © 2012 by Lockheed Martin Corporation Program Management 19

Manufacturing and Support • Provide Product Line Management Data – Product Line Variants – Component Revision Compatibility Product Support Manufacturing • Synchronize BOM to SAM • Second Source or Component Replacement – Component Specification – Rationale – Help evaluate alternatives Copyright © 2012 by Lockheed Martin Corporation 20

INCOSE Vision - What are the Challenges? Copyright © 2012 by Lockheed Martin Corporation

INCOSE Vision - What are the Challenges? • Tool Environment Integration – We use many analysis/design and test tools • • • Today they are difficult to set-up, configure and upgrade We need to be able to easily and quickly integrate them Establish more Standard Transformations – e. g. Sys. ML-Modelica Transformation Specification – Sys. ML Modeling tool compatibility • • • We need to share models with our customers, contractors and within LM We will not all use the same modeling tool Complete Sys. ML Model Tool Interchange is needed – XMI and Diagram Interchange – Spend too much time setting up and maintaining tool environment • • • Today we need tool experts for each tool Transition to new updates and inter-tool compatibility Need “Plug and Play” Copyright © 2012 by Lockheed Martin Corporation 22

INCOSE Vision - What are the Challenges? • Maintaining Information integrity – Need better and quicker ways to validate information • Leverage Re-use – Standardized Domain Profile definitions • Profile, Library, Viewpoints, Use Case, Validation constraints, icons, etc. – Domain Libraries – Reference Architecture • Standardized Viewpoints – Need ability to quickly switch to one or combination of selected domain viewpoints – Filter out what is not needed • Marking and Isolating Classified or Proprietary Information Copyright © 2012 by Lockheed Martin Corporation 23

INCOSE Vision - What are the Challenges? • Barrier to change – Understand Risk and Benefits of change – Understand Cost to change and ROI • Tool Vendors – What is SE? – Most of the UML based SE modeling tools originated from software domain communities • SW development community, e. g. UML experts not SE experts – Understand the SE workflow use cases • Not just within a single tool but across the entire SE domain workflow use case – Without that understanding it has been difficult to; • Deliver the most productive product by automating Task • Non-homogeneous MBSE environment – Some Departments/companies are document based Copyright © 2012 by Lockheed Martin Corporation 24

INCOSE IW 2012 MBSE Workshop Requirements Flowdown Breakout Session John C. Watson Principal Member of Engineering Staff Lockheed Martin, MS 2 Moorestown john. watson@lmco. com 26

The MBSE Integration Across Domains Program Management Product Support System Architectural Model Analytical Models ò Test Plan G(s) Analysi s Spec U(s) Verification Models MBSE Performance, RMA, SWa. P, Cost, etc. Manufacturing Mechanical & Electrical Models S SET Software Models Q R CLR Q Copyright © 2012 by Lockheed Martin Corporation 27

A Model Tree So. S Level System of Systems Model - System Specification Spec S 1 System Level System Model - Subsystem Specification Subsystem Level Subsystem A Model Subsystem B Model . . . Subsystem C Model …. Spec n Spec 1 S/W …. Spec n … Spec 1 S/W Spec 6 Component Domain Model 1 Spec 5 Spec 4 - Implementation Spec 2 Spec 3 - Design Spec 2 Component Level Spec 1 - Component Specification Spec 1 Component Domain Model 2 S/W … S/W H/W Copyright © 2012 by Lockheed Martin Corporation 28

SAM Goal - Derive Component Requirements • The Requirement Flow Down – Analyze Customer Needs – Define System Requirements – Refine Logical Architecture – Synthesize Allocated Architecture – Results • A derived Set of Component Specifications • Used to Buy, Modify or Build Components Copyright © 2012 by Lockheed Martin Corporation 29

Questions to Explore • What is the content of these exchanges between domains? • What are the challenges to do these exchanges? • How would we like to exchange data? Copyright © 2012 by Lockheed Martin Corporation 30