Systems Modeling Language (SysML) Tutorial

1 OMG Systems Modeling Language (OMG SysML ). Tutorial September, 2009. Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end). Copyright 2006-2009 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. OMG SysML Specification Specification status Adopted by OMG in May '06. Available Specification in Sept '07. Available Specification in Nov 08. Revision task force for in process Multiple vendor implementations available This Tutorial is based on the OMG SysML available specification (formal/2007-09-01). This Tutorial , the specifications, papers, and vendor info can be found on the OMG SysML Website at Refer to A Practical Guide to SysML by Friedenthal, Moore, and Steiner for Language details and reference 4/15/2008 Copyright 2006-2008 by Object Management Group. 2. Objectives & Intended Audience At the end of this Tutorial , you should have an awareness of: Motivation of model-based Systems engineering approach SysML diagrams and Language concepts How to apply SysML as part of a model based SE process Basic considerations for transitioning to SysML.

2 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 4/15/2008 Copyright 2006-2008 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 Class Exercise 4/15/2008 Copyright 2006-2008 by Object Management Group. 4. Motivation & Background SE Practices for Describing Systems Past Specifications Future Interface requirements System design Analysis & Trade-off Test plans Moving from Document centric to Model centric 4/15/2008 Copyright 2006-2008 by Object Management Group.

3 6. System Modeling Requirements Start Shift Accelerate Brake Control Power Vehicle Input Equations Dynamics Mass Properties Model Structural Model Safety Model Cost Engine Transmission Transaxle Model Integrated System Model Must Address Multiple Aspects of a System 4/15/2008 Copyright 2006-2008 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 ( , training).

4 Enhances knowledge capture 4/15/2008 Copyright 2006-2008 by Object Management Group. 8. System-of- Systems Interactions Boundaries Modeling Needed to Manage System Complexity 4/15/2008 Copyright 2006-2008 by Object Management Group. 9. Modeling at Multiple Levels of the System MCE (CRC). MCE (CRC). MCE (CRC). AWACS. 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 Operator Interface Voice Comm SIAP. Power Hardware Hardware includes Operational Models Power Generation and Distribution MSE. ACDS (CVN). Power Data Processing Power Terminal Power TCIM. JTIDS. Hardware 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 Operator Interface Power Voice Comm Hardware Power Power Generation Hardware includes and Distribution MSE. CEC Information Exchange Requirements - Classified SECRET when filled in Power Data Processing 1 2 3 4 5 6 7 8 9 10 11.

5 FAAD C3I Terminal TCIM Sending Receiving Latency: SA/Eng Message Voice & TADIL-B Data Rationale/UJTL Number Event/Action Information Characterization Critical Format Class Remarks Hardware Power Node Node Support Error Rate JTIDS Provide SA/Support Radar measurements to REF: CEC A-spec AMDPCS Terminal OP Comm Op Info Engagements support data fusion composite Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3 and Software tracking Host reqmts IFF measurements to support Provide SA/Support OP Comm Op Info data fusion and composite Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %. Engagements EPLRS or SINGARS tracking Terminal Provide SA/Support IFF interrogation requests to Respond w hen Power OP Comm Op Info support data fusion and Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %. Engagements requested Force Level Power composite tracking Provide SA/Support ID Changes to support data Control System PLGR OP Comm Op Info Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %.

6 Engagements fusion and composite tracking (GPS). Provide SA/Support Navigation data to support data REF:CEC SRS and Power OP Comm 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 Comm Op Info to support data fusion and Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % AEGIS only Engagements composite tracking Track number management to Provide SA/Support Changes sent OP Comm Op Info support data fusion and Host-CEP CEP-Host Yes Binary IAW IDD Secret xx secs/xx secs xx %. Engagements immediately composite tracking Composite Track State Update Provide SA/Support REF: CEC IDDs for OP Comm Op Info to support data fusion and CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %. Engagements each host composite tracking Associated Measurement REF: CEC A-spec Provide SA/Support OP Comm Op Info Reports to support data fusion CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3.

7 SPY. Engagements and composite tracking only IFF Assignments to support Provide SA/Support When assigned OP Comm Op Info data fusion and composite CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %. Engagements or changed tracking ID recommendations to Network Plan OP Comm Op Info Provide SA/Support support data fusion and CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %. When assigned Engagements or changed CID Criteria composite tracking REF: CEC A-spec Provide SA/Support Sensor cues to support data OP Comm Op Info CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3. SPY. Network Engagements fusion and composite tracking only Network Track Data Receive Network Track Data Track File 11. Correlate Track Correlated Track Files 12. Manage BMDS. BMDS Track JDN Track File Data Correlation S/W Network Interface Track Management Module Correlation Module Track File HIC. Module Module 13. Request Attempt to System Models Track Data Correlate with Track Data Possible Network BMDS Track BMDS Track File Matches Interface S/W Network Track MSG Track File Request Track Data Send Track 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 Results BMDS 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 Process Data On entry / match state vectors BMDS Track Data Do / corr state vectors Do / corr LPE On entry / receive file data <TITLE>System Design<TITLE>.

8 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 On exit / corr BMDS Track #. Prepared Track MSG. corr fail / is new BMDS Track corr success / is corr BMDS Track <META http-equiv="REFRESH". <!--CSSDATA:966533483-->. BMDS Track File Request Sent ( Request ) / Pull BMDS Track Files BMDS Track File Data Received ( File Data ) /. Correlate Tracks <SCRIPT src="/virtual/2000/code Receiving BMDS Track File Data On entry / receive file data <LINK rel="stylesheet" href="/. Do / store track data <SCRIPT Language ="javascript". Track Mangement Module HIC. /current tracks * /associated track data manages /CID data uses *. assign CID () *. JDN recommend CID (). * retrieve track file data (). display track file data (). communicates with ABMOC Subsystem 1. Operator Interface Voice Comm Power * Hardware Power Generation Hardware includes interface for 1 <<entity>> and Distribution MSE.

9 1 1. Track File Correlation Module Power <<interface>>. Track Number Network Interface Module Data Processing Power CID * algorithm Terminal Power TCIM. /State Vector buffer capacity /tracks to be correlated JTIDS. /Date-Time /msg data correlation data Hardware decorrelation data Terminal received from send track data () receive msg (). parse msg () correlate tracks (). route msg data () decorrelate tracks () Software Power build msg () retrieve track data (). send msg () send track data () EPLRS or SINGARS Force Level Terminal Control System 1. * Voice & TADIL-B Data Power Component Models correlates PLGR (GPS). <<entity>>. Network Track <<entity>>. Customer BMDS Track Power Software License owning element Primary Key Client Call <<derived>> /associated data Primary Key is subject to A2C2 Subsystem owns /history Customer_ID [PK1] Power Received Date-Time local track number traces to Serial_Number [PK1] Primary Key Operator Interface Voice Comm Non-Key Attributes Hardware Serial_Number [PK1] [FK] Power create () Customer_Name Non-Key Attributes Power Generation Hardware includes receive ().

10 Store () update () Technical_Contact and Distribution MSE. destroy () Purchase_Contact update (). retrieve () Customer_Address send () Power createsData Processing consists of Terminal TCIM. Voice & TADIL-B Data Hardware Power JTIDS. Software Release Terminal Software Tech Support System Entry Primary Key Version_Number [PK1] Primary Key TSS_Entry_Number [PK1]. Non-Key Attributes EPLRS or SINGARS. Windows_Version Terminal Power TSS_Description Force Level Power Control System PLGR. (GPS). Power Status Location is a currently has Primary Key Primary Key Status [PK1]. Status [PK1] [FK]. 4/15/2008 Copyright 2006-2008 by Object Management Group. 10. Stakeholders Involved in System Acquisition Developers/. Customers Integrators Project Managers Vendors Regulators Testers Modeling Needed to Improve Communications 4/15/2008 Copyright 2006-2008 by Object Management Group. 11. What is SysML? A graphical modelling Language in response to the UML for Systems Engineering RFP developed by the OMG, INCOSE, and AP233.