23.05.2015 Views

Space Link Extension - Service Management - CCSDS

Space Link Extension - Service Management - CCSDS

Space Link Extension - Service Management - CCSDS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT<br />

D2.2 ACTIVITY DIAGRAM EXAMPLES<br />

The following diagrams demonstrate the UML conventions used in the activity diagrams.<br />

Activity Diagram 1 is illustrated in figure E-2. It shows the notion of ‘swim lanes’ and the<br />

lower-level graphical constructs used throughout the activity diagrams in the specification.<br />

Activity Initial<br />

node - this is the<br />

starting point of<br />

the complete<br />

activity<br />

Fork - activity<br />

splits in<br />

concurrent<br />

outgoing flows<br />

Swimlane/<br />

Partition -<br />

indicates who is<br />

executing the<br />

contained actions<br />

Join - activity<br />

must wait for all<br />

incoming flows to<br />

continue<br />

Guard - a<br />

condition for<br />

allowing the flow<br />

to continue along<br />

this edge<br />

Token -<br />

represents output<br />

that travels along<br />

an edge as input<br />

for the next action<br />

Vending machine Customer<br />

Select drink<br />

[coffee<br />

selected]<br />

Brew coffee<br />

coffee<br />

Fill cup<br />

Pay for drink<br />

[tea selected]<br />

Brew tea<br />

tea<br />

Activity edge/flow -<br />

specifies the flow from<br />

one action to the next.<br />

Tokens, ie. output,<br />

from an action may<br />

also be carried along<br />

the edge<br />

Action -<br />

represents a<br />

function being<br />

executed<br />

Decision - flow<br />

will follow only<br />

one outgoing<br />

edge depending<br />

on the guard of<br />

each edge<br />

Merge - activity<br />

may flow from<br />

any input at any<br />

time and continue<br />

to the next action<br />

(without waiting<br />

for the rest of the<br />

inputs)<br />

Activity Final<br />

node - if the flow<br />

should reach this<br />

node, then all<br />

activity is stopped<br />

and completed<br />

Figure E-2: Activity Diagram 1<br />

Activity Diagram 2 is illustrated in figure E-3. It is an example of an activity diagram that<br />

‘calls’ or utilizes another of the detailed activities stated in another activity diagram. This<br />

technique is used to factor-out commonly recurring activities in the specification such that<br />

they do not have to be repeated in detail in addressing higher-level activity flows.<br />

<strong>CCSDS</strong> 910.11-R-2 Page E-3 March 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!