Download presentation
Presentation is loading. Please wait.
Published byHillary Harrison Modified over 9 years ago
1
OMG Systems Modeling Language (OMG SysML™) Matthew Hause ARTiSAN Software Tools Some slides reused from the OMG SysML™ Tutorial with permission
2
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 2 Topics SysML Status SysML Language Architecture SysML Language Detail Requirements Structure Parametric Models Allocation Summary Questions
3
Copyright © 1998-2008 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
4
Copyright © 1998-2008 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
5
Copyright © 1998-2008 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
6
Copyright © 1998-2008 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
7
Copyright © 1998-2008 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
8
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 8 User Requirements Flow Down
9
Copyright © 1998-2008 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
10
Copyright © 1998-2008 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
11
Copyright © 1998-2008 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
12
Copyright © 1998-2008 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
13
Copyright © 1998-2008 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
14
Copyright © 1998-2008 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
15
Copyright © 1998-2008 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
16
Copyright © 1998-2008 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
17
Copyright © 1998-2008 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
18
Copyright © 1998-2008 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
19
Copyright © 1998-2008 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
20
Copyright © 1998-2008 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
21
Copyright © 1998-2008 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
22
Copyright © 1998-2008 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
23
Copyright © 1998-2008 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
24
Copyright © 1998-2008 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
25
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 25 Avionics - Topology of Processing Elements
26
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 26 Avionics - Internals of a Processing Element
27
Copyright © 1998-2008 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
28
Copyright © 1998-2008 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
29
Copyright © 1998-2008 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
30
Copyright © 1998-2008 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
31
Copyright © 1998-2008 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
32
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 32 Allocation to SW/HW
33
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 33 Cross Connecting Model Elements 1. Structure2. Behavior 3. Requirements4. Parametrics satisfy verify value binding allocate
34
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 34 Integration With MARTE
35
Copyright © 1998-2008 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
36
Copyright © 1998-2008 ARTiSAN Software Tools Ltd. All Rights Reserved 36 Questions?
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.