For a detailed description of architecture development in the context of enterprise architecture, see TOGAF 9.1, Part II Architecture Development Method.


Name1 Requirements debate
Target Outcome Predictable costs, efforts and impacts of the intervention/implementation part of Regulative Interactions.
Social actors and roles Requirements engineers
Trigger or preceding interaction Requirements statement or gap analysis (gap between the actual and desired state); diagnosis part of of Regulative Interactions
Interfaces and services The rendering of requirements to support understanding by stakeholders of the requirements decisions (and their implications on the life cycle of work system (providing services).
Inputs and outputs input: stakeholder ideas and expectations, pre-existing products and services, innovations
Stores and tools templates, repositories, methods
Other characteristics
Part of The requirements specification for a service solution.
Parts Interactions that are part of any of the phases (and their steps) included in TOGAF 9.1: A. Architecture Vision, B. Business Architecture, C. Information Systems Architecture, etc.
Succeeding Interactions Detailed analysis and design; intervention/implementation part of Regulative Interactions.
Alternatives Architecture development may be skipped for incremental changes.
Action Realm Change
Risks Poor determination of the scope and the goals of the requirements debate.
Further reading Source (for service solutions): Requirements-led and Commons-enabled Service Initiatives.

Add a New Comment