Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
AMOD-075 Subsystem implementation constraints
RCAMT-533
-
Define a process step to take the tension from comp/com under consideration that may the subsystem boundary/subsystem constraint
Finished
Created by | ARCH.118 Identify implementation constraints on the subsystem solution | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Concerns | Collect in one place the constraints on the subsystem solution that are relevant to define the best possible architecture | |||||||||||||||
Modified by | None | |||||||||||||||
Used by | ARCH.097 Evaluate subsystem boundary options against the architectural tradeoff criteria | |||||||||||||||
Viewpoint | The first version of this viewpoint should consist of a list of identified constraints. If needed, these constraints can afterwards be included in the model or used as rationales for architectural decisions.
| |||||||||||||||
Diagram modelling rules | Not applicable | |||||||||||||||
Element modelling rules | Non-functional property modelling rules under development as of - rules will be added in a later version. | |||||||||||||||
Viewpoint modelling rules | Not applicable |