1. SYSTEMS ENGINEERING COURSE BASICS OF SYSML Hervé Panetto, Professor University of Lorraine, TELECOM Nancy Research Centre for Automatic Control (CRAN UMR 7039 CNRS) Chair of IFAC CC 5 « Manufacturing and Logistics Systems » Herve.Panetto@univ-Lorraine.fr

2. Copyright This work is licensed under Creative Commons Attribution- NonCommercial-ShareAlike 3.0 available online at http://creativecommons.org/licenses/by-nc-sa/3.0/

3. 3 Agenda  What is SysML? Relationship between UML and SysML Examples of Extensions Industrial Control Concluding Remarks

4. 4 What is SysML? A graphical modeling language in response to the UML for Systems Engineering RFP developed by the OMG, INCOSE, and AP233  a UML Profile that represents a subset of UML 2 with extensions Supports the specification, analysis, design, verification and validation of systems that include hardware, software, data, personnel, procedures, and facilities Supports model and data interchange via XMI and the evolving AP233 standard (in-process) SysML is a Critical Enabler for Model Driven SE

5. 5 SysML Background UML for System Engineering RFP issued – 28 March 2003 SysML Partners Kickoff meeting – 6 May 2003  Chaired by S. Friedenthal and C. Kobryn v0.9 Submission to OMG – 10 Jan 2005  Addendum stereotypes chapter – 30 May 2005 SST and SP split – 30 August 2005 SST/SP revised submissions to OMG – 14 November 2005 INCOSE and OMG Evaluations – December 2005 thru January 2006 SysML Merge Team (SMT) submission v0.99 (ad/2006-02-01) – 13 February 2006 SMT formally announced - 15 February 2006 OMG Systems Modeling Language (OMG SysML) Specification - Final Adopted Specification ptc/06-05-04 – 6 July 2006 – Final public version planned in April 2007.

6. 6 SysML Partners Industry  American Systems, EADS Astrium, BAE SYSTEMS, Boeing, Deere & Company, Eurostep, Israel Aircraft Industries, Lockheed Martin, Motorola, Northrop Grumman, oose.de, Raytheon, THALES Government  DoD/OSD, NASA/JPL, NIST Vendors  Artisan, Ceira, Gentleware, IBM/Rational, I-Logix, PivotPoint Technology, Popkin, Project Technology, 3SL, Telelogic, Vitech Liaisons  AP-233, CCSDS, EAST, INCOSE, Rosetta

7. 7 DoDAF DoD Architectural Framework across multiple levels (Zachman And MoDAF are similar) UPDM Unified Modeling Language (UML) Profile for DoDAF and ModAF SOA Architecture based on services SysML UML Extension for Systems Engineering FEA-DEA-BEA Federal and Defense Enterprise Architectures SCA Component Interface Description SCBA FEA extension to Services and Components SDF Service Interface Descriptions Layers Enterprise Architects Software Architects Program Architects System Architects And Engineers MDA UML Models For software Architecture, Components and interfaces Developers Testbeds such as Federated Development and Certification Environment (FDCE) including Live Systems, Modules, Components,Services and Simulations SysML Context Services - Enterprise Systems - Operations

8. 8 SysML Specification Outline Preface Part I - Introduction Part II – Structural Constructs  Model Elements  Blocks  Ports and Flows  Constraint Blocks Part III – Behavioral Constructs  Activities  Interactions  State Machines  Use Cases Part IV – Crosscutting Constructs Allocations Requirements Profiles & Model Libraries Part V Appendices Diagrams Sample Problem Non-Normative Extensions Model Interchange * Requirements Traceability Terms and Definitions * BNF Diagram Syntax Definitions

9. 9 Harmony – a System Engineering Development Process

10. 10 Agenda What is SysML?  Relationship between UML and SysML Examples of Extensions Industrial Control Concluding Remarks

11. 11 Relationship Between SysML and UML UML4SysML SysML Profile

12. 12 SysML Diagram Taxonomy

13. 13 Major Extensions to UML 2 New Diagram Types  Requirement Diagram (visual modeling of requirements)  Parametric Diagram (showing relations between parameters) Structure Diagram  Block Definition Diagram (based on UML class diagram with blocks instead of classes)  Internal Block Diagram (based on UML composite structure diagram with restrictions and extensions) Activity Diagram  extensions for continuous flow modeling  extensions to support disabling control and control operators.  accommodate needs of Extended Functional Flow Block Diagrams (EFFBDs)

14. 14 Agenda What is SysML? Relationship between UML and SysML  Examples of Extensions Industrial Control Concluding Remarks

15. 15 SysML Diagram Frames

16. 16 Blocks are Basic Structural Elements

17. 17 Block Definition Diagram

18. 18 Internal Block Diagram

19. 19 Internal Block Diagram Example Control signals

20. 20 Requirements Diagram (NEW)

21. 21 Parametric Diagram (NEW) Used to express constraints (equations) between value properties  Provides support for engineering analysis (e.g., performance, reliability) Constraint block captures equations  Expression language can be formal (e.g., MathML, OCL) or informal  Computational engine is defined by applicable analysis tool and not by SysML Parametric diagram represents the usage of the constraints in an analysis context  Binding of constraint usage to value properties of blocks (e.g., vehicle mass bound to F= m × a) Parametrics Enable Integration of Engineering Analysis with Design Models

22. 22 Example: Defining Vehicle Dynamics

23. 23 Example: Vehicle Dynamics Analysis – Parametric Diagram

24. 24 Parametric Example - Usage Parametric Diagram

25. 25 Activity Diagram Notation Flows can be discrete, streaming or control

26. 26 SysML EFFBD Profile

27. 27 Allocations Provides general relationship to map one model element to another Includes specific subclasses of allocation with constraints on their usage  Behavioral  Structural  Flow Explicit allocation of activities to swim lanes (e.g. activity partitions) Graphical and/or tabular representations

28. 28 Different Allocation Representations Explicit Allocation of Activity to Swim Lane Allocate Relationship Callout Notation Compartment Notation

29. 29 Example - SysML Allocation to SW and HW

30. 30 definition use 4 Pillars of SysML ABS Example 1. Structure2. Behavior 3. Requirements 4. Parametrics interactionstate machine activity/ function

31. 31 Cross Connecting Model Elements 1. Structure 2. Behavior 3. Requirements4. Parametrics allocate value binding satisfy verify

32. 32 Agenda What is SysML? Relationship between UML and SysML Examples of Extensions  Industrial Control Concluding Remarks

33. 33 System Modeling

34. 34 Combining Model-Driven and Model Based Design in Industrial Machine Control MDD: Model Driven Development in Rhapsody (Telelogic) MBD: Model Based Design in Simulink (Mathworks)

35. 35 MDD versus MBD Feature Comparison Table 1. MDD versus MBD feature comparison

36. 36 Complementary Tool Solution The Rhapsody MDD environment covers standard UML 2.0 / SysML based software and systems design Simulink is the de-facto standard for dynamic systems modeling  allowing block diagrams of complex dynamic (mathematical) algorithms to be captured and analyzed Simulink connection to Rhapsody

37. 37 Rhapsody – Simulink Integration (1)

38. 38 Rhapsody – Simulink Integration (2) Simulink Model and Code Imported into Rhapsody

39. 39 Agenda What is SysML? Relationship between UML and SysML Examples of Extensions Industrial Control  Concluding Remarks

40. 40 Concluding Remarks SysML contains many interesting extensions of UML It will be good to get a more common language between different disciplines Question is what kind of validation can be made with these different models  What about common semantics?  What about time connectivity between discrete event an continuous simulators?

41. W HERE WE ’ VE COME FROM … A H ISTORICAL P ERSPECTIVEXMIXMI yrs ’70 yrs ’80 yrs ’90 yrs ’60 yrs2000 OO Programming : ADAEiffelSmalltalkSimulaC++ ADAEiffelSmalltalkSimulaC++ Shlaer/MellorShlaer/Mellor BoochBooch Coad/YourdonCoad/Yourdon Wirfs-BrockWirfs-Brock Jacobson: OOSE Martin/OdellMartin/Odell Rumbaugh: OMT Bell Labs XEROX PARC US D.O.D ecc. ecc..... Structured Method: SA&SD Entity Modelling Event Modellingi Structured Method: SA&SD Entity Modelling Event Modellingi SysMLSysML MDAMDA UMLUML INCOSEINCOSE SPEMSPEM DDSDDS BPMNBPMN MOFMOF 41

42. DoDAF DoD Architectural Framework across multiple levels (Zachman And MoDAF are similar) UPDM Unified Modeling Language (UML) Profile for DoDAF and ModAF SOA Architecture based on services SysML UML Extension for Systems Engineering FEA-DEA-BEA Federal and Defense Enterprise Architectures SCA Component Interface Description SCBA FEA extension to Services and Components SDF Service Interface Descriptions Layers Enterprise Architects Software Architects Program Architects System Architects And Engineers MDA UML Models For software Architecture, Components and interfaces Developers Testbeds such as Federated Development and Certification Environment (FDCE) including Live Systems, Modules, Components,Services and Simulations S YS ML C ONTEXT Services - Enterprise Systems - Operations

43. 43 A U NIFYING S YSTEMS L ANGUAGESysML A Language to document the properties from different disciplines to describe the whole solution

44. R ELATIONSHIP B ETWEEN S YS ML AND UML UML4SysML SysML Profile

45. 45 use interaction T HE F OUR P ILLARS OF S YS ML (ABS E XAMPLE ) 1. Structure 4. Parametrics 2. Behavior 3. Requirements definition state machine activity/function

46. S YS ML D IAGRAM T AXONOMY

47. SysML: A Key Enabler for MBSE What Can be Expressed in SysML?  All the information and knowledge needed for the application of a systems development methodology u Specification u Analysis u Design u Verification u Validation u Hardware u Software u Data u Personnel u Procedures u Facilities The Systems Modeling Language (OMG SysML TM ) is a visual, general purpose modeling language

48. Pillars of SysML — 4 Main Diagram Types definition 1. Structure2. Behavior 4. Requirements3. Parametrics (Source: Friedenthal, www.omgsysml.org)

49. Pillars of SysML — 4 Main Diagram Types definition use 1. Structure2. Behavior 4. Requirements3. Parametrics (Source: Friedenthal, www.omgsysml.org)

50. Pillars of SysML — 4 Main Diagram Types (Source: Friedenthal, www.omgsysml.org) definition use 1. Structure2. Behavior 4. Requirements3. Parametrics interaction

51. Pillars of SysML — 4 Main Diagram Types (Source: Friedenthal, www.omgsysml.org) definition use 1. Structure2. Behavior 4. Requirements3. Parametrics interaction state machine

52. Pillars of SysML — 4 Main Diagram Types (Source: Friedenthal, www.omgsysml.org) definition use 1. Structure2. Behavior 4. Requirements3. Parametrics interaction state machine activity/ function

53. Pillars of SysML — 4 Main Diagram Types (Source: Friedenthal, www.omgsysml.org) definition use 1. Structure2. Behavior 4. Requirements3. Parametrics interaction state machine activity/ function

54. Pillars of SysML — 4 Main Diagram Types (Source: Friedenthal, www.omgsysml.org) definition use 1. Structure2. Behavior 4. Requirements3. Parametrics interaction state machine activity/ function

55. Cross Connecting Model Elements 1. Structure2. Behavior (Source: Friedenthal, www.omgsysml.org) 4. Requirements3. Parametrics

56. Cross Connecting Model Elements 1. Structure2. Behavior allocate (Source: Friedenthal, www.omgsysml.org) 4. Requirements3. Parametrics

57. Cross Connecting Model Elements 1. Structure2. Behavior 4. Requirements3. Parametrics allocate (Source: Friedenthal, www.omgsysml.org)

58. Cross Connecting Model Elements 1. Structure2. Behavior 4. Requirements3. Parametrics allocate satisfy (Source: Friedenthal, www.omgsysml.org)

59. Cross Connecting Model Elements 1. Structure2. Behavior allocate (Source: Friedenthal, www.omgsysml.org) satisfy 4. Requirements3. Parametrics

60. Cross Connecting Model Elements 1. Structure2. Behavior allocate value binding (Source: Friedenthal, www.omgsysml.org) satisfy 4. Requirements3. Parametrics

61. Cross Connecting Model Elements 1. Structure2. Behavior allocate value binding (Source: Friedenthal, www.omgsysml.org) satisfy 4. Requirements3. Parametrics

62. Cross Connecting Model Elements 1. Structure2. Behavior allocate (Source: Friedenthal, www.omgsysml.org) 4. Requirements3. Parametrics satisfy verify value binding

63. SYSTEMS ENGINEERING COURSE BASICS OF SYSML Hervé Panetto, Professor University of Lorraine, TELECOM Nancy Research Centre for Automatic Control (CRAN UMR 7039 CNRS) Chair of IFAC CC 5 « Manufacturing and Logistics Systems » Herve.Panetto@univ-Lorraine.fr