OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group. 4 Motivation & Background SE Practices for Describing Systems Future Past • Specifications • Interface requirements • System design • Analysis & Trade-off • Test plans Moving from Document centric to Model centric 7/26/2007 Copyright © 2006,2007 by Object Management Group. 6 System Modeling Requirements Start Shift Accelerate Brake Control Power Vehicle Input Equations Dynamics Mass Properties ModelStructural Model Safety Model Cost Engine Transmission Transaxle Model Integrated System Model Must Address Multiple Aspects of a System 7/26/2007 Copyright © 2006,2007 by Object Management Group. 7 Model Based Systems Engineering Benefits • Shared understanding of system requirements and design – Validation of requirements – Common basis for analysis and design – Facilitates identification of risks • Assists in managing complex system development – Separation of concerns via multiple views of integrated model – Supports traceability through hierarchical system models – Facilitates impact analysis of requirements and design changes – Supports incremental development & evolutionary acquisition • Improved design quality – Reduced errors and ambiguity – More complete representation • Supports early and on-going verification & validation to reduce risk • Provides value through life cycle (e.g., training) • Enhances knowledge capture 7/26/2007 Copyright © 2006,2007 by Object Management Group. 8 System-of-Systems Interactions Boundaries Modeling Needed to Manage System Complexity 7/26/2007 Copyright © 2006,2007 by Object Management Group. 9 Modeling at Multiple Levels of the System MCE (CRC) MCE (CRC) AWACS MCE (CRC) LINK 16 LINK 16 AMDPCS FAAD C3I LINK 16 LINK 16 Patriot ICC E-2C AWACS F/A-18 RIVET JOINT MCE F-15C ABMOC Subsystem Voice Comm Operator Interface Power Hardware Power Generation Hardware includes MSE SIAP ACDS (CVN) and Distribution Power Data Processing Power Terminal Power TCIM JTIDS Hardware Operational Models Terminal DDG-51 AEGIS Destroyer Software Power CG EPLRS or SINGARS Force Level Terminal Control System TAOM Power Voice & TADIL-B Data PLGR (GPS) Patriot ICC Power A2C2 Subsystem Power Operator Interface Voice Comm Power Hardware Power Generation Hardware includes and Distribution MSE Power CEC Information Exchange Requirements - Classified SECRET when filled in Data Processing 12 34567891011 Terminal TCIM Sending Receiving Latency: SA/Eng Message FAAD C3I Voice & TADIL-B Data Rationale/UJTL Number Event/Action Information Characterization Critical Format Class Rem ar k s Hardware Power No de No de Support Error Rate Radar measurements to REF: CEC A-spec JTIDS Provide SA/Support OP 5.1.1 Com m Op Info support data fusion composite Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3 and AMDPCS Terminal Engagements Software track ing Hos t r e qm ts IFF measurements to support Provide SA/Support OP 5.1.1 Com m Op Info data fusion and composite Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements EPLRS or SINGARS track ing IFF interrogation requests to Terminal Provide SA/Support Respond when Power OP 5.1.1 Com m Op Info support data fusion and Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements requested Force Level Power com posite tracking Provide SA/Support ID Changes to support data Control System OP 5.1.1 Com m Op Info Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % PLGR Engagements fusion and composite tracking (GPS) Provide SA/Support Navigation data to support data REF:CEC SRS and Power OP 5.1.1 Com m Op Info Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements fusion and composite tracking Host Nav. spec Engagement Support Requests Provide SA/Support OP 5.1.1 Com m Op Info to support data fusion and Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % AEGIS only Engagements com posite tracking Track number management to Provide SA/Support Changes sent OP 5.1.1 Com m Op Info support data fusion and Host-CEP CEP-Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements immediately com posite tracking Composite Track State Update Provide SA/Support REF: CEC IDDs for OP 5.1.1 Com m Op Info to support data fusion and CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements e ach host com posite tracking Associated Measurement REF: CEC A-spec Provide SA/Support OP 5.1.1 Com m Op Info Reports to support data fusion CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3. SPY Engagements and com posite track ing only IFF As signments to support Provide SA/Support When assigned OP 5.1.1 Com m Op Info data fusion and composite CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements or changed track ing ID recommendations to Network Plan Provide SA/Support When assigned OP 5.1.1 Com m Op Info support data fusion and CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements or changed CID Criteria com posite tracking REF: CEC A-spec Provide SA/Support Sensor cues to support data OP 5.1.1 Com m Op Info CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3. SPY Engagements fusion and composite tracking Network only Network Track Data Receive Network Track Data Track File 11 Correlate Track Correlated Track Files 12 Manage BMDS Track File Data BMDS Track JDN Correlation S/W Network Interface Track Management Module Correlation Module Track File HIC Module Module 13 Request Attempt to Track Data Correlate with Track Data Possible BMDS Track Network BMDS Track File Matches Interface S/W Network Track MSG Track File Request Track Data Send Track System Models Track Mangement S/W Module HIC File Data BMDS Track Data Correlate Tracks BMDS Track Data Correlation Results Session Activated Verify CID, Correlation, and Assoicated Track yes Update Track File Data Data Correlation no / initialize Possible CreateCorrelation New Complete ( Correlation BMDSResults Track ) [ set not null ] / Send Results Idle Network Track File Received ( File Data ) [ number tracks > 0 ] / Input Network Track Correlating TracksMonitor BMDS Track Display Correlation Receiving Network Track File On entry / match state vectorsProcess Data BMDS Track Data Do / corr state vectors Do / corr LPE On entry / receive file data Do / corr PIP Do / store track data Track MSG Data Send BMDS Do / corr RCS On exit / request matching data Track Data to Do / corr CID JDN <TITLE>System Design<TITLE> On exit / corr BMDS Track # Prepared Track MSG corr fail / is new BMDS Track corr success / is corr BMDS Track <META http-equiv="REFRESH" BMDS Track File Request Sent ( Request ) / Pull BMDS Track Files BMDS Track File Data Received ( File Data ) / <!--CSSDATA:966533483--> Correlate Tracks Receiving BMDS Track File Data <SCRIPT src="/virtual/2000/code On entry / receive file data Do / store track data <LINK rel="stylesheet" href="/ <SCRIPT language="javascript" Track Mangement Module HIC /current tracks /associated track data manages 1..* /CID data uses 1..* assign CID () 1..* JDN recommend CID () 1..* retrieve track file data () display track file data () communicates with ABMOC Subsystem 1 Voice Comm Operator Interface Power 0..* Hardware Hardware includes interface for Power Generation <<entity>> MSE 1 1 1 and Distribution Track File Power <<interface>> Correlation Module Track Number Network Interface Module Data Processing Power CID 0..* algorithm Terminal Power TCIM /State Vector buffer capacity /tracks to be correlated JTIDS /Date-Time correlation data Hardware /msg data Terminal received from decorrelation data send track data () receive msg () parse msg () correlate tracks () Power route msg data () decorrelate tracks () Software build msg () retrieve track data () send msg () send track data () EPLRS or SINGARS Force Level Terminal Control System