OMG Systems Modeling Language (OMG SysML™) Matthew Hause ARTiSAN Software Tools Some slides reused from the OMG SysML™ Tutorial with permission.

Slides:



Advertisements
Similar presentations
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Advertisements

® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
1 Model Driven Development. 2 DoDAF/ModAF/ SysML and AP233 Architecture –DODAF MODAF Modelling –UML –SysML Interchange –AP 233AP 233 –XMI.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
Component and Deployment Diagrams
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.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
SysML: A Modeling Language for Systems of Systems
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
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
Free Mini Course: Applying SysML with MagicDraw
Systems Modeling Language ™ Overview Cris Kobryn and Sandy Friedenthal SysML Partners ( October 2003.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Unified Modeling Language, Version 2.0
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Conceptual Modelling – Behaviour
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
An Introduction to the Unified Modeling Language
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
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,
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
An Introduction to SysML
SYSE 802 John D. McGregor Module 1 Session 2 Requirements Modeling in SysML.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
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.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
XASTRO-2 Presentation CCSDS SAWG th November 2004.
Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.
Object-Oriented Systems. Goals Object-Oriented Methodologies – The Rumbaugh et al. OMT – The Booch methodology – Jacobson's methodologies.
SYSTEMS ENGINEERING COURSE BASICS OF SYSML Hervé Panetto, Professor University of Lorraine, TELECOM Nancy Research Centre for Automatic Control (CRAN UMR.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Basic Characteristics of Object-Oriented Systems
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.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
UML (Unified Modeling Language)
SysML and Modelica Integration Working Group Meeting 3/11/09 Peter Fritzson Wladimir Schamai.
© Copyright 2010 Rockwell Collins, Inc. All rights reserved. Practical SysML Applications: A Method to Describe the Problem Space Ray Jorgensen David Lempia.
Systems Modeling Language (SysML). 2 What is SysML? A graphical modeling language in response to UML for Systems Engineering developed by the OMG, INCOSE,
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Introduction to UML.
Analysis Classes Unit 5.
Object-Oriented Analysis and Design
Systems Analysis and Design With UML 2
SysML v2 Usability Working Session
Systems Analysis and Design With UML 2
University of Central Florida COP 3330 Object Oriented Programming
The Process of Object Modeling
Unified Modeling Language
Introduction to UML.
UML profiles.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Software Design Methodologies and Testing
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Presentation transcript:

OMG Systems Modeling Language (OMG SysML™) Matthew Hause ARTiSAN Software Tools Some slides reused from the OMG SysML™ Tutorial with permission

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 2 Topics SysML Status SysML Language Architecture SysML Language Detail Requirements Structure Parametric Models Allocation Summary Questions

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 3 * Where we’ve come from… A Historical PerspectiveXMIXMI 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

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 4 A Unifying Systems LanguageSysML A Language to document the properties from different disciplines to describe the whole solution

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 5 SysML Contents Summary Structure e.g., system hierarchy, interconnection Behaviour e.g., function-based behaviour, state-based behaviour Properties e.g., parametric models, time property Requirements e.g., requirements hierarchy, traceability Verification e.g., test cases, verification results Cross-Cutting e.g., allocation of entities for workflow

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 6 use interaction The Four Pillars of SysML (ABS Example) 1. Structure 4. Parametrics 2. Behavior 3. Requirements definition state machine activity/function

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 7 Requirements Requirements represents a text based requirement Includes id and text properties Can add user defined properties such as verification method Can add user defined requirements categories (e.g. functional, interface, performance,...) Requirements hierarchy describes requirements contained in a specification Requirements relationships include DeriveReqt, Satisfy, Verify, Refine, Trace, Copy Graphical, tabular and tree notation specified

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 8 User Requirements Flow Down

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 9 Activities Activity used to specify the flow of inputs/outputs and control, including sequence and conditions for coordinating activities Secondary constructs show responsibilities for the activities using swim lanes SysML extensions to Activities Support for continuous flow modeling Support probabilistic choice Alignment of activities with Enhanced Functional Flow Block Diagram

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 10 Analysis Model of Vehicle SysML additions on this chart «streaming» activities consume inputs after initialization «continuous» flows

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 11 Analysis Model of Vehicle SysML additions on this chart «streaming» activities consume inputs after initialization «continuous» flows

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 12 Analysis Model of Vehicle SysML additions on this chart «streaming» activities consume inputs after initialization «continuous» flows

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 13 Analysis Model of Vehicle SysML additions on this chart «streaming» activities consume inputs after initialization «continuous» flows

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 14 SysML Blocks Provides a unifying concept to describe the structure of an element or system Hardware Software Data Procedure Facility Person Block is Basic Structural Element

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 15 Block Definition Diagram for Vehicle Structural Components Parts shown by black-diamond notation, or by Parts Compartment Values compartment shows properties of the block Flowports compartment shows block interface

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 16 Block Definition Diagram for Vehicle Structural Components Parts shown by black-diamond notation, or by Parts Compartment Values compartment shows properties of the block Flowports compartment shows block interface

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 17 Block Definition Diagram for Vehicle Structural Components Parts shown by black-diamond notation, or by Parts Compartment Values compartment shows properties of the block Flowports compartment shows block interface

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 18 Block Definition Diagram for Vehicle Structural Components Parts shown by black-diamond notation, or by Parts Compartment Values compartment shows properties of the block Flowports compartment shows block interface

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 19 Unit and Item Types Unit types normally based on Real SI Units and Dimensions defined in SysML appendix

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 20 Item Flows Distinct from what can flow via the port specification Supports top down description of flows without imposing behavioural method (e.g. activities, state, interactions) Behaviour is not driven from itemFlows but needs to be consistent with it Is aligned with behaviour thru refinement and allocation Can be allocated from an object node, message, or signal from a behavioural diagram Properties of item flow can be specified and constrained in parametric diagram

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 21 IBD for Vehicle Non-Atomic Ports I/O is specified using FlowSpecification FlowSpecification consists of properties stereotyped «FlowProperty» isConjugate promotes reuse of flowSpecifications Atomic FlowPorts In this case the port is directly typed by the item type (Block or ValueType) Direction property specify the direction of flow

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 22 IBD for Vehicle Non-Atomic Ports I/O is specified using FlowSpecification FlowSpecification consists of properties stereotyped «FlowProperty» isConjugate promotes reuse of flowSpecifications Atomic FlowPorts In this case the port is directly typed by the item type (Block or ValueType) Direction property specify the direction of flow

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 23 IBD for Vehicle Non-Atomic Ports I/O is specified using FlowSpecification FlowSpecification consists of properties stereotyped «FlowProperty» isConjugate promotes reuse of flowSpecifications Atomic FlowPorts In this case the port is directly typed by the item type (Block or ValueType) Direction property specify the direction of flow

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 24 Internal Block Diagram for CC Shows parts (structural children) … … and ports (interaction points on blocks and parts) Supports integration of behavior and structure Port types Standard Ports Specify a set of operations and/or signals Typed by a UML interface Flow Ports Specify what can flow in or out of block/part Typed by a flow specification

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 25 Avionics - Topology of Processing Elements

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 26 Avionics - Internals of a Processing Element

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 27 Parametrics Used to express constraints (equations) between value properties Provides support to engineering analysis (e.g. performance, reliability, etc) 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

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 28 Vehicle Parametrics BDD BDDs can show parametric definitions Parameter compartment shows the constraint parameters Constraint compartment for the applied constraint

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 29 Parametric Diagram Small boxes represent parameters and bound properties Boxes on left represent item flows Constraint can be in compartment or in attached note

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 30 Parametric Diagram Small boxes represent parameters and bound properties Boxes on left represent item flows Constraint can be in compartment or in attached note

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 31 Allocations Provides general relationship to map one model element to another Different types of allocation may include: Behavioural (i.e. function to component) Structural (i.e. logical to physical) Hardware to Software …. Explicit allocation of activities to swim lanes (e.g. activity partitions) Use of graphical and/or tabular representations

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 32 Allocation to SW/HW

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 33 Cross Connecting Model Elements 1. Structure2. Behavior 3. Requirements4. Parametrics satisfy verify value binding allocate

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 34 Integration With MARTE

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 35 Summary SysML sponsored by INCOSE/OMG with broad industry and vendor participation SysML provides a general purpose modelling language to support specification, analysis, design and verification of complex systems Subset of UML 2 with extensions 4 Pillars of SysML include modelling of requirements, behaviour, structure, and parametrics OMG SysML Adopted in May 2006 Multiple vendor implementations announced Standards based modelling approach for SE expected to improve communications, tool interoperability, and design quality

Copyright © ARTiSAN Software Tools Ltd. All Rights Reserved 36 Questions?