Sei sulla pagina 1di 4

System Context Diagram

Use Case Diagram

bdd System Context

uc

SYSMOD
SYSMOD

SYSMOD

SYSMOD
SYSMOD

continuous use case


Continuous
Use Case

External System
Environmental
Effect

system process
System Process

include

SYSMOD

Sensor

system
System

Use Case

SYSMOD

user
User
include

SYSMOD

Information Flow

SYSMOD

Specialized
Use Case

SYSMOD

user
User

Actuator

Block Definition Diagram

Ports

Value
distribution

name8:Type

val1:Type
uniform {mean=2, stdDeviation=0.1} val2:Type

nameA:Type
nameB:Type

block
Block
flow properties
in p1:Type
out p2:Type
inout p3:Type

bdd
Simple association

1..*
role3

1..*
role2
1..*
role4

block
Block 2

block
Whole

block
Dependent
Block
block
Specialized
Block

operation(params):Type

Provided and
requested features

properties
prov name:Type
block
Block 2

Navigable
Association

block
Whole

Aggregation

block
Part

Composition

block
Part of Composite

SYSMOD

SYSMOD

domain block
Domain
Block

system context
SystemContext
Element
FAS

FAS

functional group
Functional group

functional block
Functional block

SYSMOD

Dependency

block
Independent
Block

Generalization

block
General
Block

quantityKind
Length

document block
Block

unit
Meter

block
Abstract block
{abstract}

unit
quantityKind=LEngth
symbol=m

Item Flow

properties
name:Type
valueType
unit=aUnit

0..*
role1
0..1
role2

valueType
ValueType
operations
name(param:Type):Type

name6:DocumentType

interfaceBlock
Block

operations
prov op1(params):Type
reqd op1(params):Type

block
Association
Block

name4:Type
name5:Type

name7:Type

Nested Port

parts
p1:Block
name:SystemBlock [Multiplizitt]
references
r1:Block

block
Block 1

name3:Type
block
System Block

constraints

{val1 > 0}

Ports with
Flow properties

proxy name9:Type

values

1..*
role1

Conjugated Port

full name1:Type name2:~Type

operations
op1(param1:Type, param2:Type):Type

block
Block 1

Full Port

Proxy Port

block
{encapsulated}
Block

block
Block

enumeration
EnumerationType
Literal1
Literal2

block
Block

structure
t1:Part 1

c:Association

namespace
t2:Part 2

OMG Systems Modeling Language (OMG SysML) 1.3 (http://www.omgsysml.org)


incl. SYSMOD (http://www.sysmod.de) and FAS stereotypes (http://www.fas-method.org)
MBSE Blog: http://www.model-based-systems-engineering.com

block
Block 1

block
Block 2

Version 2.2.1

Mechanical
System

secondary use case


Secondary
Use Case

Reference card, page 1/4


2013 Tim Weilkiens, www.oose.de
Support by T. Netter

Internal Block Diagram


Reference

ibd [block] Block

ibd [block] Association Block

Item Flow
Participant property
role1:Type

role2:Type
name:Type

port

p:PortType

Multiplicity
port
role3:Type [2]
roleA:Type

Nested
Connector

participant
{end=role}
inLink1:Type

participant
{end=role}
inLink2:Type

connector:Association

p:~PortType

roleB:Type

role:Type

role4:Type
Type

Requirements

ibd [block] Block

requirement
Requirement X

requirement
Requirement Y

Master
requirement Requirement X

copy
requirement
id="4712"
text="The System..."

Copies relationship

requirement
id="4711"
text="The System..."

requirement
Requirement

requirement
Sub-Requirement

deriveReqt

requirement
Requirement X

trace

Derived
requirement Requirement X

Model View
view
{viewpoint=name}
View
conform

Refines
requirement Requirement X

viewpoint
Viewpoint

Use Case

Refines requirement

satisfy

block
Block

Satisfies requirement

verify

requirement
Requirement X

Unidirectional
Connector

requirement
Requirement Y

refine

requirement
Requirement X

initialValues
val1=42
t="text"

:values
val1:Type=42

TracedTo
requirement Requirement X

Traceability

requirement
Requirement X

role2:[Type]

role1

requirement
Requirement Y

Infers requirement

requirement
Requirement X

Property-specific
type

testCase
TestCase

Verifies requirement

DerivedFrom
requirement Requirement Y

TracedFrom
requirement Requirement Y

SatisfiedBy
block SystemBlock

VerifiedBy
testcase TestCase

Satisfies
requirement Requirement X

Verifies
requirement Requirement X

viewpoint
stakeholder="Who has an interest in the model view?"
concerns="Which requirements satisfy the model view?"
purpose="What objectives/purposes fulfil the model view?"
methods="What methods/processes build the model view?"
languages="What languages constitute the model view?"

Packages

RefinedBy
usecase UseCase

Package

Subpackage

Subpackage
table Requirements Table

Name

4711 Requirement
...

...

Text

Subpackage

The System...
...

OMG Systems Modeling Language (OMG SysML) 1.3 (http://www.omgsysml.org)


incl. SYSMOD (http://www.sysmod.de) and FAS stereotypes (http://www.fas-method.org)
MBSE Blog: http://www.model-based-systems-engineering.com

block
Block

Version 2.2.1

ID

Reference card, page 2/4


2013 Tim Weilkiens, www.oose.de
Support by T. Netter

Sequence Diagram
sd SeqABC
sd
role1:Type

role2:Type
ref SeqABC

role1:Type

Combined fragement
(alternatives)

asynchronous message

[a<b]

alt

Lifeline Decomposition

ref

synchronous message

Focus of control

role2:Type

SeqABC

[else]

reply

ref

SeqXYZ

message to self
Elaborated sequence
diagram of referenced
interaction SeqXYZ

Destroy Instance

sd SeqXYZ
role1:Type

Create Instance

role3:Type

role2:Type
message

Activity Diagram
act
Accept
Event

Start Node
ObjectA

overwrite
Time Event

Action
ObjectB

{stream}

optional
[else]

[x > 0]

Activity
Final Node

Interruptible
Activity Region

discrete
{rate=1/minute}

FAS
IO
Input/Output-Partition

Receive
Event
Time Event

nobuffer

Action

SYSMOD

continuous activity
Continuous
Step

Action

Flow Final Node

Object
[State]

Action

SYSMOD

essential activity
Essential
Step

controlOperator
Action

{control}
Pin

Action name :
Behavior name

localPostcondition
Condition

localPrecondition
Condition

{probabiliy=0.25}
[y < 0]

Action
name:Type
[State]

Send
Signal

continuous

Action

[else]
{probability=0.75}

name:Type
Object

Activity Parameter
Node

Activity Parameter
Node

Comments & Constraint

bdd Activity Tree


activity
Activity

Name of
Object Node
block
Block

rationale
Rationale of modeling

Constraint

Name of
Action
activity
Activity

Comment

{x > y}

OMG Systems Modeling Language (OMG SysML) 1.3 (http://www.omgsysml.org)


incl. SYSMOD (http://www.sysmod.de) and FAS stereotypes (http://www.fas-method.org)
MBSE Blog: http://www.model-based-systems-engineering.com

problem
Problem description
Version 2.2.1

Activity Parameter
Node

Reference card, page 3/4


2013 Tim Weilkiens, www.oose.de
Support by T. Netter

State Machines
stm StateMachineName
Entry point

History
Initial state

Orthogonal State
State
event[guard]/behavior

State

Junction

at(time)

State

entry/behavior
do/behavior
exit/behavior
event[condition]/behavior

after(time)/behavior

State

State

event[guard]

Entry point
Composite
State

Terminate

[x<-5]

[x>0]

Final state

Receive
Signal

Send
Signal

Behavior

stm1:StateMachine
[else]
Exit point
State
Exit point

Allocations

block
Logical Block

allocate

allocate
Physical Block 1

block
Physical Block 1

allocate
Physical Block 2
Allocation
Activity Partition

allocatedFrom
action Action 1
AcTion 1

AcTion 2

act
Action

Object

Parametric Diagram

allocatedTo
elementType Element name

par [package] Package


ActivityName
allocatedTo
elementType Element name
Object

Object
Action

valueA

PartB.valueC

constraints
{x > y}
z1:ConstraintBlock
parameters
x:Real
y:Real

x:

y:

b:ConstraintBlock

Version 2.2.1

allocatedTo
connector Connector

constraint
Constraint block

OMG Systems Modeling Language (OMG SysML) 1.3 (http://www.omgsysml.org)


incl. SYSMOD (http://www.sysmod.de) and FAS stereotypes (http://www.fas-method.org)
MBSE Blog: http://www.model-based-systems-engineering.com

Reference card, page 4/4


2013 Tim Weilkiens, www.oose.de
Support by T. Netter

Potrebbero piacerti anche