Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.118 Identify implementation constraints on the subsystem solution
RCAMT-533
-
Define a process step to take the tension from comp/com under consideration that may the subsystem boundary/subsystem constraint
Finished
Goal | Identify constraints from the implementation strategy and implementation technology on the subsystem architecture characteristics, subsystem design characteristics, or subsystem implementation techniques. |
---|---|
Requirements met by this process step | ISO 15288 6.4.7.3 a 2) |
Inputs | |
Outputs | AMOD-075 Subsystem implementation constraints |
Methodology | To avoid selecting a subsystem architecture that can never be implemented in reality, it is necessary to determine limitations beforehand and to take them into account in the subsystem boundary definition. E.g. the platform physical limits/boundaries/constraints... (threshold values that are impossible to go beyond due to physics and/or technology state of the art). The system level implementation constraints AMOD-116 System implementation constraints should be consistent with the subsystem implementation constraints. At system level, some of the physical constraints described above may already be known. Note: This includes current or anticipated limitations of the chosen implementation technology, acquirer furnished materials or system elements for adaptation and limitations resulting from the use of required implementation enabling systems. |
Tools and non-human resources | General brainstorming materials Research materials |
Cardinality | One-off, with possible revisions. |
Completion criteria | The set of identified subsystem implementation constraints is safe enough to try. |
Design review | ARCH.R.8 Subsystem review - consolidated |
Step done by (Responsible) | COM/COP architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None. |