OMG Systems Modeling Language OMG Sys ML Matthew

  • Slides: 36
Download presentation
OMG Systems Modeling Language (OMG Sys. ML™) Matthew Hause ARTi. SAN Software Tools Some

OMG Systems Modeling Language (OMG Sys. ML™) Matthew Hause ARTi. SAN Software Tools Some slides reused from the OMG Sys. ML™ Tutorial with permission

Topics n n n Sys. ML Status Sys. ML Language Architecture Sys. ML Language

Topics n n n Sys. ML Status Sys. ML Language Architecture Sys. ML Language Detail n n n Requirements Structure Parametric Models Allocation Summary Questions Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 2

Where we’ve come from… A Historical Perspective INCOSE US D. O. D OO Programming

Where we’ve come from… A Historical Perspective INCOSE US D. O. D OO Programming : ADA Eiffel Smalltalk Simula C++ Bell Labs XEROX PARC Booch Sys. ML Wirfs-Brock Jacobson: OOSE ecc. . . UML Shlaer/Mellor Structured Method: SA&SD Entity Modelling Event Modellingi yrs ’ 60 yrs ’ 70 SPEM MOF BPMN XMI DDS Coad/Yourdon Rumbaugh: OMT Martin/Odell yrs ’ 80 yrs ’ 90 Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved MDA yrs 2000 3 *

A Unifying Systems Language Sys. ML A Language to document the properties from different

A Unifying Systems Language Sys. ML A Language to document the properties from different disciplines to describe the whole solution Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 4

Sys. ML Contents Summary n Structure n n Behaviour n n e. g. ,

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

The Four Pillars of Sys. ML (ABS Example) 2. Behavior 1. Structure interaction definition

The Four Pillars of Sys. ML (ABS Example) 2. Behavior 1. Structure interaction definition state machine activity/function use 4. Parametrics 3. Requirements Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 6

Requirements n Requirements represents a text based requirement n n n Includes id and

Requirements n Requirements represents a text based requirement n n n 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 Derive. Reqt, Satisfy, Verify, Refine, Trace, Copy Graphical, tabular and tree notation specified Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 7

User Requirements Flow Down Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All

User Requirements Flow Down Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 8

Activities n n n Activity used to specify the flow of inputs/outputs and control,

Activities n n n 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 Sys. ML extensions to Activities n n n Support for continuous flow modeling Support probabilistic choice Alignment of activities with Enhanced Functional Flow Block Diagram Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 9

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming»

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming» activities consume inputs after initialization «continuous» flows Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 10

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming»

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming» activities consume inputs after initialization «continuous» flows Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 11

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming»

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming» activities consume inputs after initialization «continuous» flows Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 12

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming»

Analysis Model of Vehicle n Sys. ML additions on this chart n n «streaming» activities consume inputs after initialization «continuous» flows Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 13

Sys. ML Blocks n Provides a unifying concept to describe the structure of an

Sys. ML Blocks n Provides a unifying concept to describe the structure of an element or system n Hardware n Software n Data n Procedure n Facility n Person Block is Basic Structural Element Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 14

Block Definition Diagram for Vehicle Structural Components n n n Parts shown by black-diamond

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

Block Definition Diagram for Vehicle Structural Components n n n Parts shown by black-diamond

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

Block Definition Diagram for Vehicle Structural Components n n n Parts shown by black-diamond

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

Block Definition Diagram for Vehicle Structural Components n n n Parts shown by black-diamond

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

Unit and Item Types n n Unit types normally based on Real SI Units

Unit and Item Types n n Unit types normally based on Real SI Units and Dimensions defined in Sys. ML appendix Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 19

Item Flows n n Distinct from what can flow via the port specification Supports

Item Flows n n Distinct from what can flow via the port specification Supports top down description of flows without imposing behavioural method (e. g. activities, state, interactions) n n Behaviour is not driven from item. Flows 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 © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 20

IBD for Vehicle n Non-Atomic Ports n n n I/O is specified using Flow.

IBD for Vehicle n Non-Atomic Ports n n n I/O is specified using Flow. Specification consists of properties stereotyped «Flow. Property» is. Conjugate promotes reuse of flow. Specifications n Atomic Flow. Ports n n In this case the port is directly typed by the item type (Block or Value. Type) Direction property specify the direction of flow Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 21

IBD for Vehicle n Non-Atomic Ports n n n I/O is specified using Flow.

IBD for Vehicle n Non-Atomic Ports n n n I/O is specified using Flow. Specification consists of properties stereotyped «Flow. Property» is. Conjugate promotes reuse of flow. Specifications n Atomic Flow. Ports n n In this case the port is directly typed by the item type (Block or Value. Type) Direction property specify the direction of flow Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 22

IBD for Vehicle n Non-Atomic Ports n n n I/O is specified using Flow.

IBD for Vehicle n Non-Atomic Ports n n n I/O is specified using Flow. Specification consists of properties stereotyped «Flow. Property» is. Conjugate promotes reuse of flow. Specifications n Atomic Flow. Ports n n In this case the port is directly typed by the item type (Block or Value. Type) Direction property specify the direction of flow Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 23

Internal Block Diagram for CC n n Shows parts (structural children) … … and

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

Avionics - Topology of Processing Elements Copyright © 1998 -2008 ARTi. SAN Software Tools

Avionics - Topology of Processing Elements Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 25

Avionics - Internals of a Processing Element Copyright © 1998 -2008 ARTi. SAN Software

Avionics - Internals of a Processing Element Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 26

Parametrics n Used to express constraints (equations) between value properties n n Constraint block

Parametrics n Used to express constraints (equations) between value properties n n Constraint block captures equations n n n Provides support to engineering analysis (e. g. performance, reliability, etc) Expression language can be formal (e. g. Math. ML, OCL …) or informal Computational engine is defined by applicable analysis tool and not by Sys. ML Parametric diagram represents the usage of the constraints in an analysis context n 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. Software Design Copyright © 1998 -2008 ARTi. SAN Tools Ltd. All. Models Rights Reserved 27

Vehicle Parametrics BDD n n n BDDs can show parametric definitions Parameter compartment shows

Vehicle Parametrics BDD n n n BDDs can show parametric definitions Parameter compartment shows the constraint parameters Constraint compartment for the applied constraint Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 28

Parametric Diagram n n n Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd.

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

Parametric Diagram n n n Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd.

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

Allocations n n Provides general relationship to map one model element to another Different

Allocations n n Provides general relationship to map one model element to another Different types of allocation may include: n n n 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 © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 31

Allocation to SW/HW Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights

Allocation to SW/HW Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 32

Cross Connecting Model Elements 1. Structure 2. Behavior c allo ate value binding satisfy

Cross Connecting Model Elements 1. Structure 2. Behavior c allo ate value binding satisfy verify. Software Tools Ltd. Copyright © 1998 -2008 ARTi. SAN 3. Requirements 4. Parametrics All Rights Reserved 33

Integration With MARTE Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights

Integration With MARTE Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 34

Summary n n Sys. ML sponsored by INCOSE/OMG with broad industry and vendor participation

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

Questions? Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 36

Questions? Copyright © 1998 -2008 ARTi. SAN Software Tools Ltd. All Rights Reserved 36