The Open Group Architecture Framework
The The Open Group Architecture Framework ( TOGAF ) provides an approach for the design, planning, implementation and maintenance of enterprise architectures. As an Operational Framework of Group Government and Agency Framework, the TOGAF Architecture Development Method with the (ADM) provides a procedure model for the development of technical architectures.
TOGAF is developed by the Open Group. Published in December 1995 first version of TOGAF based on the developed by the Department of Defense of the United States TAFIM ( Technical Architecture Framework for Information Management). On this basis, the Open Group TOGAF developed further, the current status will be posted on the website of the Open Group. On 2 February 2009 was published in the TOGAF Version 9.
The Open Group TOGAF provides for internal use to develop an enterprise architecture for free at.
Structure to describe the enterprise architecture
When using TOGAF enterprise architecture is usually in the three domains of business architecture, information systems architecture (consisting of application architecture and data architecture) modeling and technology architecture.
- Business architecture: the business architecture considers the strategy, organizational structure, business processes and business skills ( business capabilities ) of the company. The business process architecture is the result of business process modeling.
- Information system architecture:
- Data Architecture: The data architecture, the data are with their relationships, which are needed for the implementation of business processes, identified and described. This is done in a model and a form of representation that is stable, complete, consistent and understandable for all stakeholders ( cf. data model). The information architecture represents information, information groups and their information needs. Under information groups different roles are summarized, which have the same information needs ( ie, controllers).
- Application Architecture: within the application architecture, the applications are managed, which are necessary for the execution of business processes. In addition to the inventory management of all applications, the relations and interfaces between the applications in the application architecture are considered. The applications are categorized based on their technical functionality and the data processed by them information. These categories are relatively stable. The specific applications that come within the categories used are replaced more frequently. This change results from the technical advancement and changing requirements.
- Technology Architecture: The technology architecture describes the elements of architecture for the construction and operation of the IT infrastructure. It defines the base, raised on the applications that can be integrated and operated.
This base architectures, depending on the perspective, to be complemented other architectures, such as the security architecture (description of security processes, security systems and the tasks of the organizational units involved with the suitable one for the organization of information security is achieved ) and the operating architecture (operation and management of the software, hardware and communication infrastructure).
TOGAF defines a process for the development of the architecture: the Architecture Development Method (ADM). By the cyclic execution of this process, the architecture is updated.
The process consists of eight phases: In Phase A ( Architecture Vision) will set out the aims and stakeholders in updating the enterprise architecture. In the BD phases are described for the business, application, and technology architecture Informations-/Daten- the current and the desired state. The key differences are worked out. In Phase I the project approved, which perform the transformation from the current situation to the target state. Phase F is used to describe the cross-border cooperation of the individual projects, these arrangements are monitored in Phase G. In Phase H requirements and external influences are collected, they are then used as the basis for the next iteration of the ADM.