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


Description

The clarification for the fields in the template is given in the Interaction template (Actant Dictionary).

Name Architecture development
Domain
Target Outcome Predictable costs, efforts and impacts of the intervention/implementation part of Regulative Interactions.
Social actors and roles Architects
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 architecture models to support understanding by stakeholders of the architecture decisions (and their implications on the life cycle of work system (providing services).
Inputs and outputs input: non-architectural inputs, pre-existing models or descriptions
Stores and tools Drawing board, architecture description tools, repositories
Other characteristics
Part of The design/action plan part of Regulative Interactions
Parts Iinteractions 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 of the architecture work.
Further reading ref: Source (for enterprise architecture): TOGAF 9.1, Part II Architecture Development Method; See also TOGAF 8, Chapter 3.

Add a New Comment

Position of Architecture development among the interactions: