|Enterprise Architecture - TOGAF and ArchiMate|
... 90 % of solution is understanding the problem.
Enterprise Architecture - TOGAF and ArchiMate
TOGAF is an architecture framework - The Open Group Architecture Framework. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.
ArchiMate, an Open Group Standard, is an open and independent modelling language for enterprise architecture, supported by different tool vendors and consulting firms.
Architecture in the Context of TOGAF
ISO/IEC 42010:2007 defines "architecture" as:
Enterprise Architecture Scope and Techniquies
TOGAF embraces but does not strictly adhere to ISO/IEC 42010:2007 terminology. In TOGAF, "architecture" has two meanings depending upon the context:
In TOGAF we endeavor to strike a balance between promoting the concepts and terminology of ISO/IEC 42010:2007 - ensuring that our usage of terms defined by ISO/IEC 42010:2007 is consistent with the standard - and retaining other commonly accepted terminology that is familiar to the majority of the TOGAF readership. For more on terminology, refer to Definitions and Part IV, Architectural Artifacts .
What Kind of Architecture Does TOGAF Deal With?
There are four architecture domains that are commonly accepted as subsets of an overall enterprise architecture, all of which TOGAF is designed to support:
Architecture Development Method
The TOGAF Architecture Development Method (ADM) provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures.
All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities.
Phases within the ADM are as follows:
Deliverables, Artifacts, and Building Blocks
Architects executing the ADM will produce a number of outputs as a result of their efforts, such as process flows, architectural requirements, project plans, project compliance assessments, etc. The TOGAF Architecture Content Framework (see Part IV, Introduction) provides a structural model for architectural content that allows major work products to be consistently defined, structured, and presented.
The Architecture Content Framework uses the following three categories to describe the type of architectural work product within the context of use:
TOGAF includes the concept of the Enterprise Continuum, which sets the broader context for an architect and explains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organization. The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum.
Supporting the Enterprise Continuum is the concept of an Architecture Repository which can be used to store different classes of architectural output at different levels of abstraction, created by the ADM. In this way, TOGAF facilitates understanding and co-operation between stakeholders and practitioners at different levels.
By means of the Enterprise Continuum and Architecture Repository, architects are encouraged to leverage all other relevant architectural resources and assets in developing an Organization-Specific Architecture.
In this context, the TOGAF ADM can be regarded as describing a process lifecycle that operates at multiple levels within the organization, operating within a holistic governance framework and producing aligned outputs that reside in an Architecture Repository. The Enterprise Continuum provides a valuable context for understanding architectural models: it shows building blocks and their relationships to each other, and the constraints and requirements on a cycle of architecture development.
The major components within an Architecture Repository are as follows:
Establishing and Maintaining an Enterprise Architecture Capability
In order to carry out architectural activity effectively within an enterprise, it is necessary to put in place an appropriate business capability for architecture, through organization structures, roles, responsibilities, skills, and processes.
ArchiMate®, an Open Group Standard, is an open and independent modelling language for enterprise architecture that is supported by different tool vendors and consulting firms. ArchiMate provides instruments to enable enterprise architects to describe, analyze and visualize the relationships among business domains in an unambiguous way.
The ArchiMate language defines three main layers (depicted with different colors in the examples in the next chapters):
1. The Business Layer offers products and services to external customers, which are realized in the organization by business processes performed by business actors.
2. The Application Layer supports the business layer with application services which are realized by (software) applications.
3. The Technology Layer offers infrastructure services (e.g., processing, storage, and communication services) needed to run applications, realized by computer and communication hardware and system software.
Enterprise Architecture Management, IT Architecture, standards and tools
The area of analysis and modeling of functional architecture, Enterprise Architecture are applied these design standards:
• ArchiMate and TOGAF (ArchiMate, an Open Group Standard, is an open and independent modelling language for enterprise architecture, supported by different tool vendors and consulting firms).