SYSTEMS ENGINEERING COURSE BASICS OF SYSML Hervé Panetto, Professor University of Lorraine, TELECOM Nancy Research Centre for Automatic Control (CRAN UMR.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

January, 2012 UPDM – Unified Profile for DoDAF/MODAF 88Solutions Adaptive Atego ASMG Axway Software BAE Systems DoD DND Everware-CBDI Generic General Dynamics.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
OMG Systems Modeling Language (OMG SysML™) Matthew Hause ARTiSAN Software Tools Some slides reused from the OMG SysML™ Tutorial with permission.
1 Model Driven Development. 2 DoDAF/ModAF/ SysML and AP233 Architecture –DODAF MODAF Modelling –UML –SysML Interchange –AP 233AP 233 –XMI.
Object-Oriented Analysis and Design
November 2010 UPDM – Unified Profile for DoDAF/MODAF Adaptive Artisan Software ASMG BAE Systems DoD DND embeddedPlus Generic General Dynamics IBM Lockheed.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
© Copyright Eliyahu Brutman Programming Techniques Course.
DoDAF DoD Architectural Framework across multiple levels (Zachman And MoDAF are similar) UPDM Unified Modeling Language (UML) Profile for DoDAF and ModAF.
Andrew SuttonKent State University1 Software Modeling Andrew Sutton Department of Computer Science Kent State University.
A Combat Support Agency Defense Information Systems Agency Model Based Systems Engineering and Systems Modeling Language Chris Gedo Chief, Architecture.
Using UML Models for the Performance Analysis of Network Systems Nico de Wet and Pieter Kritzinger Department of Computer Science University of Cape Town.
3106 Use of UML 2.0 Diagrams for Systems Architecture Modeling Gundars Osvalds Systems of Systems Architect The Boeing Company.
SysML: A Modeling Language for Systems of Systems
OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM) Dwayne Hardy American Systems Jan 30, 2007.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Deployment of SysML in Tools and Architectures: an Industry Perspective Rick Steiner Raytheon IDS, San Diego
Model Based Systems Engineering (MBSE) using SysML GSFC Systems Engineering Seminar June 8, 2010 Sanford Friedenthal Lockheed Martin
Leveraging Model Driven Architecture ® for Model Driven Systems Engineering MARC 2004 Richard Mark Soley, Ph.D. Chairman and CEO.
Model-Driven User Requirements Specification using SysML Authors: Michel dos Santos Soares, Jos Vrancken Source: Journal of Software(JSW), Vol. 3, No.
Free Mini Course: Applying SysML with MagicDraw
Systems Modeling Language ™ Overview Cris Kobryn and Sandy Friedenthal SysML Partners ( October 2003.
Introduction to UML 1 Quick Tour Why do we model? What is the UML? Foundation elements Unifying concepts Language architecture Relation to other OMG technologies.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Introduction to MDA (Model Driven Architecture) CYT.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e UPDM Review Session Col. Jack Jibilian Enterprise Architecting & Warfighting Decision Support SAF/XCPA.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Model Driven Development An introduction. Overview Using Models Using Models in Software Feasibility of MDA MDA Technologies The Unified Modeling Language.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
SysML Awareness John Davies BSc, PhD, CEng, FIET.
ARCH-2: UML From Design to Implementation using UML Frank Beusenberg Senior Technical Consultant.
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Systems Modeling Language (SysML) v0.9 Submission Update DRAFT SysML Partners June 2005.
An Introduction to SysML
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Interoperability. Designing how to move from requirements to code Handling complexity – Platforms, libraries, technology evolution, languages, testing,
Enterprise Engineering Directorate (EE)
XASTRO-2 Presentation CCSDS SAWG th November 2004.
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
Object-Oriented Systems. Goals Object-Oriented Methodologies – The Rumbaugh et al. OMT – The Booch methodology – Jacobson's methodologies.
Session 1 What Is the UML? Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 5, 2011 Presented by Kang-Pyo Lee.
Emerging Standards for SOA Seminar Robert Marcus
Model Based Systems Engineering Visualization Steven Corns Missouri University of Science & Technology.
SysML-Modelica Transformation Specification (SE DSIG Meeting, Jacksonville, 3/22/2010) Chris Paredis Georgia Tech On behalf of the SysML-Modelica Working.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
UML (Unified Modeling Language)
Systems Modeling Language (SysML). 2 What is SysML? A graphical modeling language in response to UML for Systems Engineering developed by the OMG, INCOSE,
Ron Williamson, Ph.D. Raytheon Jan 30-31, 2011
Introduction to UML.
Ron Williamson, Ph.D. Raytheon Jan 30-31, 2011
Evolution of UML.
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
SysML v2 Formalism: Requirements & Benefits
Systems Analysis and Design With UML 2
Report to OMG by MDSD on A Review of SysML Submissions to OMG Sponsored by INCOSE MDSD- WG David Oliver, editor 2/8/06.
SysML v2 Usability Working Session
Systems Analysis and Design With UML 2
Systems Modeling Language (SysML) Overview
Introduction to UML.
UML profiles.
SysML Overview October 19, 2004 Sanford Friedenthal
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Software Design Methodologies and Testing
Presentation transcript:

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 »

Copyright This work is licensed under Creative Commons Attribution- NonCommercial-ShareAlike 3.0 available online at

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

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 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/ ) – 13 February 2006 SMT formally announced - 15 February 2006 OMG Systems Modeling Language (OMG SysML) Specification - Final Adopted Specification ptc/ – 6 July 2006 – Final public version planned in April 2007.

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 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 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 Harmony – a System Engineering Development Process

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

11 Relationship Between SysML and UML UML4SysML SysML Profile

12 SysML Diagram Taxonomy

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 Agenda What is SysML? Relationship between UML and SysML  Examples of Extensions Industrial Control Concluding Remarks

15 SysML Diagram Frames

16 Blocks are Basic Structural Elements

17 Block Definition Diagram

18 Internal Block Diagram

19 Internal Block Diagram Example Control signals

20 Requirements Diagram (NEW)

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 Example: Defining Vehicle Dynamics

23 Example: Vehicle Dynamics Analysis – Parametric Diagram

24 Parametric Example - Usage Parametric Diagram

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

26 SysML EFFBD Profile

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 Different Allocation Representations Explicit Allocation of Activity to Swim Lane Allocate Relationship Callout Notation Compartment Notation

29 Example - SysML Allocation to SW and HW

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

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

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

33 System Modeling

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 MDD versus MBD Feature Comparison Table 1. MDD versus MBD feature comparison

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 Rhapsody – Simulink Integration (1)

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

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

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?

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

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 A U NIFYING S YSTEMS L ANGUAGESysML A Language to document the properties from different disciplines to describe the whole solution

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

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

S YS ML D IAGRAM T AXONOMY

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

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

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

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

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

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

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

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

Cross Connecting Model Elements 1. Structure2. Behavior (Source: Friedenthal, 4. Requirements3. Parametrics

Cross Connecting Model Elements 1. Structure2. Behavior allocate (Source: Friedenthal, 4. Requirements3. Parametrics

Cross Connecting Model Elements 1. Structure2. Behavior 4. Requirements3. Parametrics allocate (Source: Friedenthal,

Cross Connecting Model Elements 1. Structure2. Behavior 4. Requirements3. Parametrics allocate satisfy (Source: Friedenthal,

Cross Connecting Model Elements 1. Structure2. Behavior allocate (Source: Friedenthal, satisfy 4. Requirements3. Parametrics

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

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

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

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 »