Architecture development
For a detailed description of architecture development in the context of enterprise architecture, see TOGAF 9.1, Part II Architecture Development Method.
Description
| Name1 | 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 |
|
||||||||||||
| Further reading | ref: Source (for enterprise architecture): TOGAF 9.1, Part II Architecture Development Method; See also TOGAF 8, Chapter 3. |
- Questions, answers, comments
- "Architecture development" among the interactions
- All interactions
- All events
- On the template
Add a New Comment