SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - MODAF aliases > Elements > Standard operational activity (UPDM - MODAF aliases)
  
Standard operational activity (UPDM - MODAF aliases)
Creation
To create a Standard Operational Activity:
• From an Architectural Description or Service Description: right-click the Architectural Description or Service Description, point to New, point to MODAF, point to Operational, and then click Standard Operational Activity.
• From a Node, Operational Activity or Standard Operational Activity: right-click the element, point to New, point to MODAF, and then click Standard Operational Activity.
• From an OV-5 Operational Activity Hierarchy, StV-6 Operational Activity to Capability Mapping or SV-5 Function to Operational Activity/Service Function Definition: click the Standard Operational Activity toolbar button, and then click in free space on the diagram.
You can convert a Standard Operational Activity to an Operational Activity: right click the Standard Operational Activity, point to Convert To, and then click Operational Activity.
Appearance
When shown on an OV-5 Operational Activity Hierarchy, StV-6 Operational Activity to Capability Mapping or SV-5 Function to Operational Activity/Service Function Definition, a Standard Operational Activity appears as follows:
When shown on an OV-6b Operational State Transition Description, a Standard Operational Activity appears as a Do Standard Operational Activity call:
Relationships
The following relationships are of importance to a Standard Operational Activity:
• Implements relationships link a Standard Operational Activity to the Service Function elements it implements.
• Is Capable Of Performing relationships link a Standard Operational Activity to Node and Security Domain elements that perform the Standard Operational Activity.
• Operational Activity Action elements link a Standard Operational Activity to other Standard Operational Activity and Operational Activity elements that are invoked by the Standard Operational Activity.
• Maps To Capability relationships link a Standard Operational Activity to Capability elements that are mapped to.
• A Node Operation message represents a Standard Operational Activity on an OV-6c Operational Event-Trace Description.
The following sections provide information about how a Standard Operational Activity is used in the model.
Create a Standard Operational Activity from
Architectural Description
Node
Operational Activity
OV-5 Operational Activity Hierarchy
Service Description
StV-6 Operational Activity to Capability Mapping
SV-5 Function to Operational Activity/Service Function Definition
Create from a Standard Operational Activity
In addition to the UPDM elements that can be created from all UPDM elements ( Alias, Definition, Informationand Metadata):
Desired Effect
Node Operation Action
Operational Activity
Operational Activity Action
Operational Activity Structured Node
Operational Constraint
Operational Input Pin
Operational Output Pin
Operational Parameter
Operational Partition
OV-5 Operational Activity Model
Service Operation Action
Standard Operational Activity
Shown on these diagrams, tables and matrices
In addition to the AV-2 Integrated Dictionary and TV-1 Standards Profile, which can show all UPDM elements:
AV-5 Capable Performer Matrix
OV-3 Operational Information Exchange Matrix
OV-5 Operational Activity Model
OV-5 Operational Activity Hierarchy
OV-6a Operational Rules Model- shows applied Operational Constraint elements
OV-6b Operational State Transition Description
OV-6c Operational Event-Trace Description- Node Operation messages represents Standard Operational Activity elements
SV-5 Function to Operational Activity/Service Function Traceability Matrix
StV-6 Operational Activity to Capability Mapping
SV-5 Function to Operational Activity/Service Function Definition
UPDM writeable properties
The following writeable properties are available on the Standard Operational Activity tab of a Standard Operational Activity element's Property Pages:
• URI