Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
A Data Set
(known as a class
in the UML
specification)
Multiplicity - e.g. a
TireShopInvoice data set is
composed of 1 or more (with no
limit) LineItems. Each LineItem
is composed of zero or more
Tire ‘s.
Constraint - constrains the
relationship between data
sets or composition of a
data set. In this case, it’s a
constraint levied on Tire.
Constraints can appear in
notes or situated with other
UML notations
This is another means of
defining an association.
In this example, Tire
“references” either (see
Constraint Example #2)
TireModelAInformation
or
TireModelBInformation
TireShopInvoice
1
1..*
LineItem
itemNumber
quantity
{must not exceed 4 of the same 0..*
model and make}
Tire
name
description
model
make
rating
references
TireModelA
Information
1
{xor}
references
TireModelB
Information
name
description
Applied Stereotype - specifies
that this data set is an extension
of the specified stereotype. In
this case, TireShopInvoice uses
the stereotype and
can be expanded into its
associated data sets
Part
partNumber
price
warehouseLocation
Generalization -
specifies
inheritance of the
contents of an
abstract data set
Composition - defined by the filled diamond
and the line. Given the placement of the
diamond, this can be read as:
TireShopInvoice is composed of LineItem
Navigability - defined by the open arrowhead.
This implies visibility and direction. In
combination with composition, this notation
helps indicate direction of the composition and
implies reference of the LineItem in
TireShopInvoice.
Parameters (known as
class attributes in the UML
specification) of a data set.
The data type of a
parameter may also follow
the name (separated by a
colon)
Abstract Data Set (known
as an abstract class in
the UML specification) -
this is a data set that
cannot exist on its own.
It is inherited by other
data sets. This is
typically combined with
the Generalization
association/arrow
Constraint example #2- this example
applies an exclusive OR operation on
each association (line) it touches,e.g.
Tire can “reference” TireModelA
Information or TireModelB
Information but never both at the
same time
Figure E-1: Class Diagram Example
D2
ACTIVITY DIAGRAM
D2.1 GENERAL
A UML activity diagram describes the possible actions that can take place given the flow of
an invocation message of an operation procedure document exchange pattern. Activity
diagram conventions include partitions to show whether UM or CM is responsible for the
action, forks/joins to show parallel activity, guards and decisions/merges to guide flow, and
pins to show parameterization of an action. The parameter pins are used in the definition of a
stereotype or an activity group.
CCSDS 910.11-R-2 Page E-2 March 2008