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 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. 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 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. 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.

4 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

5 Verification & validation to reduce risk Provides value through life cycle ( , training). 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.

6 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. 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.

7 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 %.

8 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 %.

9 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. 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 %.

10 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.