1 UML Basic Training

UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML extensions

UML Basic training3 Definitions  Requirement  A description of the behavior of the system or part of the system (sub-system, component) or a property of it  Design  A representation (model) that describes how something is going to be built “All models are wrong. Some are useful” George Box

UML Basic training4 Types of R&D Engineering Activities SW modeling UML HW modeling VHDL, CAD, … System modeling SysML Requirements definition & management SysML extends UML in order to support all system engineering methodology

UML Basic training5 The Basic Development Process  Requirements  High level (system view)  Review  Detailed (per feature)Use case models  Review  Design  High level (system view)Design models  Detailed (per unit/class/interface)  Code

UML Basic training6 Object Oriented Analysis and Design OOA Model of requirements (user view) OOD Model of design (developer view)

UML Basic training7 UML - Unified Modeling Language  A graphical language for visualizing the structure and behavior of systems and systems parts  Not a methodology. A language  Provides notation (symbols) and meaning (semantics)  Developed by Object Management Group (OMG)  Supported by many tools

UML Basic training8 Diagram Types in UML 1.x  Class, Object, Component  Package  Deployment  Use case  Sequence  Activity  Collaboration  State chart

UML Basic training9 Static and Dynamic Models  Static (structure):  Class, Object, Component  Package  Deployment  Dynamic (behavior):  Use case  Activity  Sequence  Collaboration  State chart

UML Basic training10 Use Case Diagram

UML Basic training11 Use cases (UC)  External view of the system  Expressed in user terms  Use case is used by an actor  Actor is not necessarily human. Can be other systems  Use case can:  > other use case  Each UC is described using an activity diagram or sequence diagram

UML Basic training12 Use Case Documentation  Title (goal)  Short description  Actors  Trigger  Pre-condition  Post-condition  Normal flow (steps)  Using text and/or activity diagrams  Exceptional/alternate flows

UML Basic training13 Activity diagram  Describes logic of flow/process, sequence of actions * (see later SysML extensions for activity diagrams)

UML Basic training14 Class Diagram Generalization Association

UML Basic training15 Class Diagram Terms  Class  Name  Attributes  Operations  Visibility: public (+), Private (-), Protected (#)

UML Basic training16 Class Diagram Terms  Relationships  Dependency  Change to one may cause change to other  Association  Connection exists between classes/objects  Generalization  Abstract classes, inheritance  Aggregation  Model of Whole/Part. Lifetime of whole & part not linked  Composition  Model of Whole/Part. Lifetime of whole & part linked  Multiplicity: m..n, 1, 0..1, *  Indicates how many objects may fill the relation

UML Basic training17 Interfaces  Distinguish between interface and the implementation  Abstract class has one or more operations that are abstract  Interface is a class with only abstract operations *(In SysML “port” is used)

UML Basic training18 Object Diagram  Model specific instances derived from class diagram

UML Basic training19 Package Diagram  Groups UML elements:  By diagram types (other packages, diagrams, classes, etc.)  By system hierarchy (structure): system, sub- systems, etc.  In software: model namespaces in C++ and.NET

UML Basic training20 Sequence Diagram  Describes a set of objects that take part in a flow/sequence  Shows data and behavior in one place  Time line is from top to bottom  Sequence diagrams can refer (ref) to other seq. diagrams, can include alternative (alt) paths, loops and more (not shown in the example).

UML Basic training21 Sequence Diagram

UML Basic training22 Collaboration Diagram  Describes a set of objects that take part in a flow/sequence  Shows data and behavior in one place  Time is expressed by numbers on the association lines

UML Basic training23 Collaboration Diagram

UML Basic training24 State Chart Diagram  Model dynamic aspect of an object, component or a system  Terms:  Initial state  States  Events  Transition activity  Final state

UML Basic training25 Component Diagram  Component is a replaceable SW part of the system that implements a set of interfaces  Components can be used to define also sub- systems *(In SysML “block” is used)

UML Basic training26 Deployment Diagram  Model physical aspect of the system  SysML uses different notation (block diagrams with >)

UML Basic training27 SysML System engineering Modeling Language

UML Basic training28 UML & SysML  UML 2.0 contains many enhancements to support systems engineering (SE)  BUT, It doesn’t satisfy all SE needs  SysML extends UML 2.0  Adopted by Object Management Group in Feb  Not very popular yet

UML Basic training29 UML & SysML UML 2 SysML Not required by SysUML UML reused by SysUML SysUML extensions SysML Extensions: - Blocks - Item flows - Allocations - Requirements - Parametrics - Continuous flows …

UML Basic training30 SysML Diagrams

UML Basic training31 Example of Block Diagrams in SysML  A block element extends the UML Class element  A block can contain properties, ports, operations, etc

UML Basic training32 Example of Block Diagrams in SysML

UML Basic training33 Activity in SysML

UML Basic training34 Activity Diagram in SysML

UML Basic training35 For more info  2_tutorial 2_tutorial  SysML-Tutorial.pdf SysML-Tutorial.pdf

UML Basic training36