Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.004 Analyse trade space factors
Goal | Identify and characterise the factors that will dominate tradeoff decisions on operational and system architecture. |
---|---|
Requirements met by this process step | EN 50126-1 7.2.2 b) |
Inputs | Consultation with a small set of key stakeholders Existing strategic documentation Knowledge of the person doing the work |
Outputs | |
Methodology | This task is mostly a case of the person responsible using their own knowledge and some research or stakeholder consultation to explore a standard range of factors to determine which of them is particularly dominant in this current project. Mnemonics such as TEPIDOIL or PESTEL are used in defence systems engineering to prompt the engineer to consider relevant factors. Tutorial material on these mnemonics can be found by searching them on the Internet or consulting a systems engineering textbook. For each heading in the mnemonic, find out
Then attempt to rank the factors according to their relative dominance in architectural decision-making for the organisation/system of interest. Document the findings of the analysis in plain English. |
Tools and non-human resources | Systems Engineering literature Confluence (note: an area for this, and a ticket
|
Cardinality | One-off, with possibility for later revisions. |
Completion criteria | The analysis results are judged to be reasonable, accurate and relevant to the organisation. All review feedback has been addressed. |
Design review | |
Step done by (Responsible) | Operational concept architect |
Provides input to/assists (Contributes) | Product Owner |
Uses outputs (Informed) | None directly |