The Requirements Management Process is used throughout the entire Architecture Development Methodology life-cycle in all phases.
It’s key objective is to address the requirements of the enterprise or organisation, store the requirements and then pass the requirements to and from each ADM phase when required.
The Requirements Management Process is what drives the ADM and this is why the Requirements Management Process is at the center of the ADM life-cycle as shown below.
It is imperative that an architecture is able to handle changes in requirements as by its very nature an architecture is subject to changes such as:
- Stakeholder uncertainty regarding requirements and solutions
- What was proposed and what can actually be delivered (e.g. Constraints may force a change in deliverables)
- Drivers and constraints outside of the control of the ADM or enterprise, such as changes in technology, new legislation for example