OMG Systems Modeling Language (OMG SysML™) Tutorial
11 July 2006
Sanford Friedenthal Alan Moore Rick Steiner
Copyright © 2006 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Caveat
• This material is based on version 1.0 of the SysML specification (ad-06-03-01) – Adopted by OMG in May ’06 – Going through finalization process
• OMG SysML Website – http://www.omgsysml.org/
11 July 2006 Copyright © 2006 by Object Management Group. 2 Objectives & Intended Audience
At the end of this tutorial, you should understand the: • Benefits of model driven approaches to systems engineering • Types of SysML diagrams and their basic constructs • Cross-cutting principles for relating elements across diagrams • Relationship between SysML and other Standards • High-level process 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 – Already familiar with system modeling & tools, or – Want to learn about systems modeling • Software Engineers who want to express systems concepts • Familiarity with UML is not required, but it will help
11 July 2006 Copyright © 2006 by Object Management Group. 3 Topics
• Motivation & Background (30) • Diagram Overview (135) • SysML Modeling as Part of SE Process (120) – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework (20) • Transitioning to SysML (10) • Summary (15)
11 July 2006 Copyright © 2006 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
11 July 2006 Copyright © 2006 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 11 July 2006 Copyright © 2006 by Object Management Group. 7 Model Based Systems Engineering Benefits • Improved communications • Assists in managing complex system development – Separation of concerns – Hierarchical modeling – Facilitates impact analysis of requirements and design changes – Supports incremental development & evolutionary acquisition • Improved design quality – Reduced errors and ambiguity – More complete representation • Early and on-going verification & validation to reduce risk • Other life cycle support (e.g., training) • Enhanced knowledge capture
11 July 2006 Copyright © 2006 by Object Management Group. 8 System-of-Systems
Interactions
Boundaries
Modeling Needed to Manage System Complexity
11 July 2006 Copyright © 2006 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 Sending Receiving Latency: SA/Eng Message Terminal Rationale/UJTLTCIM Number Event/Action Information Characterization Critical Format Class Rem ar k s FAAD C3I Voice & TADIL-B Data No de No de Support Error Rate Hardware Radar measurements to REF: CEC A-spec Power 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 JTIDS Engagements track ing Hos t r e qm ts AMDPCS Terminal IFF measurements to support Software 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 track ing IFF interrogation requests to Provide SA/Support Respond when 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 EPLRS or SINGARS com posite tracking Provide SA/Support ID Changes to support data Terminal OP 5.1.1 Com m Op Info Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Power Engagements fusion and composite tracking
Provide SA/Support Navigation data to support data REF:CEC SRS and Force Level OP 5.1.1 ComPower m Op Info Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Engagements fusion and composite tracking Host Nav. spec Control System PLGR Engagement Support Requests Provide SA/Support (GPS) 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 Power 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 si Provide SA/Support OP 5.1.1 Com m Op Info Engagements
gnments to support When assigned data fusion and composite CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % track in or changed g Provide SA/Support ID recommendationst o OP 5.1.1 Com m Op Info Network Plan Engagements support data fusion and When assigned CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % com or changed CID Criteria 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
corr fail / is new BMDS Track corr success / is corr BMDS Track Correlate Tracks Receiving BMDS Track File Data