Technology Modeling 1
The Technology Layer of the Essential Meta Model is concerned with the Technology that provides and supports the systems that are in use in the organization – both software and hardware technology.
As with the other layers of the core meta-model, the Technology Layer is split into the following views:
- Conceptual – The conceptual area is where we define the ‘what’. In technology terms, this means ‘what’ technology capabilities are required to provide the appropriate technology infrastructure for the enterprise. For example, Data Integration Services is a technology capability that describes ‘what’ is needed – but does not stipulate how – this capability is to be realized.
- Logical – The logical area is where we define the ‘how’. In technology terms this is the next level of abstraction of ‘how’ the ‘what’ will be achieved. These deals in terms of the classes of technology and the technology products that are available to realise the Technology Capabilities.
- Physical – The physical captures the implementation and deployments of technology in the enterprise. In the technology layer this means the lowest level of abstraction and captures the instances of the technology products and where they are physically deployed.
The Technology Architecture according to TOGAF follows B-DAT sequence. The Technology architecture is right at the lowest level of architecture because it is the layer that realizes architecture. The level of detail addressed in Phase D will depend on the scope and goals of the overall architecture effort. New technology building blocks being introduced as part of this effort will need to be defined in detail during Phase D. Existing technology building blocks to be supported in the target environment may need to be redefined in Phase D to ensure interoperability and fit-for-purpose within this specific Technology Architecture.
The order of the steps in Phase D, as well as the time at which they are formally started and completed should be adapted to the situation at hand in accordance with the established architecture governance. In particular, determine whether in this situation it is appropriate to conduct Baseline Description or Target Architecture development first.
Technology Standards 3
The Tech standards are more for architectural hygiene and discipline. It is the layer at where standards from all layers are revealed or realized, also the most ignored layer for standards adherence. A key element that is missing is the link between architecture and business benefits. In particular, enterprise architecture must be driven from the business strategy. This link provides the appropriate context for the architecture and lets trade-offs be made between the benefits of architecture standards and the granting of standards waivers to projects. However, architecture still has many hurdles to negotiate to make this connection effective. These include:
- Finding the business strategy
- Analyzing the business strategy
- Getting business support for the architecture
- Instituting appropriate governance arrangements
This is particularly common in enterprises in which businesspeople have little or no engagement with architecture. As a result, architecture focuses on technology: a domain with which architects are likely to be familiar and over which they think they have control.
- Technology Modeling, Essential Project avaiable at : http://www.enterprise-architecture.org/techology-architecture-tutorials/58-techology-architecture-overview
- The Open Group Architecture Framework, Phase D : Technology Architecture at : http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap12.html
- James, G. , Making Technology Standards Work, 2008, Gartner, G00137199