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 by | ARCH.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 | ||||||||||||||||||||||||||||||
Viewpoint | The record of system capabilities and missions shall contain the following information:
The format of the record can be in table format as shown in the following example: System Capability:
System Mission:
| ||||||||||||||||||||||||||||||
Diagram modelling rules | After the content has been transferred to the model this viewpoint can be Automatic generation by script. | ||||||||||||||||||||||||||||||
Element modelling rules | 2. 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. |