SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - MODAF aliases > Elements > Mission use case (UPDM - MODAF aliases)
  
Mission use case (UPDM - MODAF aliases)
A Mission Use Case is a proprietary element that is required to model UPDM in Modeler.
Creation
To create a Mission Use Case:
• 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 Mission Use Case.
• From an OV-1d Mission Definition: click the Mission Use Case toolbar button, and then click in free space on the diagram.
Appearance
When shown on an OV-1d Mission Definition, a Mission Use Case appears as follows:
Relationships
The following relationships are of importance to a Mission Use Case:
• UML Generalization relationships define Mission Use Case inheritance.
• UML Interacts relationships link a Mission Use Case to Mission Actor elements.
• UML Extends and Includes relationships link a Mission Use Case to other Mission Use Case elements.
The following sections provide information about how a Mission Use Case is used in the model.
Create a Mission Use Case from
Architectural Description
OV-1d Mission Definition
Service Description
Create from a Mission Use Case
In addition to the UPDM elements that can be created from all UPDM elements ( Alias, Definition, Information, and Metadata):
Operational Constraint
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:
OV-1d Mission Definition
OV-6a Operational Rules Model (shows applied Operational Constraint elements)
UPDM writeable properties
The following writeable properties are available on the Mission Use Case tab of a Mission Use Case element's Property Pages:
• missionArea
• URI