Legal information

Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)

AMOD-120 Record of system capabilities and missions

RCAMT-485 - Populate Confluence page for view specification: AMOD-120,121,122 Finished

Created byARCH.049 Define set of potential system capabilities/missions
Concerns

Explain the rationale behind the decisions to transfer operational capabilities down to system level.

OR

Explain the rationale behind the inclusion of a system capability/mission in the list of potential system capabilities/missions.

Modified by

ARCH.119 Define consolidated set of system capabilities/missions

ARCH.051 Align the system context with collaboration projects

Used by

ARCH.036 Identify all alternative system boundaries

ARCH.041 Transfer or trace upper level model elements to system level

ARCH.082 Trade off system requirements and constraints

ARCH.062 Produce the concept of use (CONUSE)

Viewpoint

The record of system capabilities and missions shall contain the following information:

  • Unique Number: For each capability to allow unambiguous identification
  • Name: To provide a short conclusive indication of the topic of a capability/mission
  • Traceability: To indicate the name of the related model elements on the higher level. This gives a hint what was to be realized by the system capability/mission under development
  • Type: To distinguish between system capability and system mission
  • Rationale: Textual description about the reason why a system capability/mission is generated instead of a system function to realize the higher level model element
  • Description: Textual description about the topic of the system capability or system mission
  • Precondition: Textual description of the conditions that are given prior to the execution of the system capability/mission under development
  • Postcondition: Textual description of the conditions that shall be achieved after the completion of the system capability/mission under development


The format of the record can be in table format as shown in the following example:

System Capability:

Unique number: NameTraceabilityDescriptionRationalePreconditionPostcondition
...Operational Activity OAXYZ............
...Operational Capability OCXYZ............

System Mission:

Unique number: NameTraceabilityDescriptionRationale








Diagram modelling rulesAfter the content has been transferred to the model this viewpoint can be Automatic generation by script.
Element modelling rules2. Modelling Rules for System Analysis#ModRules_VE_SysCapability
2. Modelling Rules for System Analysis#ModRules_VE_Mission
Viewpoint modelling rules

After the content has been transferred to the model this viewpoint can be Automatic generation by script.