TOGAF
Architecture Repository
TOGAF states that a mature architecture
capability requires an Architecture Repository in order to structure all of the
information generated and managed by the architecture team. TOGAF provides a
structural framework for such Repository.
« At a high level, six classes of architectural information are expected to be held within an Architecture Repository : »
« At a high level, six classes of architectural information are expected to be held within an Architecture Repository : »
- The Architecture Metamodel
- The Architecture Capability
- The Architecture Landscape
- The Standards Information Base
- The Reference Library
- The Governance Log
The picture reproduced below illustrates TOGAF’s Framework for the Repository.
TOGAF ARCHITECTURE REPOSITORY |
The
Architecture Metamodel
Describes the architecture framework tailored
to the organization, including:
- The Architecture Content Metamodel (i.e. the set of 17 to 32 categories of building blocks, as defined for the organization)
- The set of artifacts (or viewpoints) as defined for the organization
- The set of deliverables
- The method for architecture development
The
Architecture Capability
Defines the processes and the organization
that support the governance of the architecture macro functions :
- The management and development of the enabling capabilities (including training and certification of the architects, management and development of the Enterprise Continuum, development of new processes, etc.)
- Demand management and monitorization of request for changes
- The development of new architectures
The
Architecture Landscape
Architectural views of the building blocks in
the organization (such as the application landscape, data landscape and
technology landscape).
The architecture landscape is divided in three
levels the granularity:
- Strategic architectures : show a long-term summary of the entire enterprise. This view is used at the executive level, for setting directions.
- Segment architectures : show operating models for areas within an enterprise (business functions, business services, process models). This view is used at the portfolio management level, fur supporting planning.
- Capability architectures : detailed models of building blocks, describing the units of capability (application component models, data element models, technology component models). This view is used for defining the work packages.
Standards
Information Base
The SIB provides a repository area to hold the
corporate standards to which architecture building blocks must conform.
Standards fall into three classes :
- Legal and regulatory obligations
- Industry's standards
- Organizational standards
The SIB is aimed at the teams developing new
architectures. The governance of these projects by the architecture team will
assess the compliance of their products to the standards in the SIB.
The
Reference Library
The Reference Library is intended to store
« best practice », template and reference materials that may be
used/reused for building the new
architectures (that is, part or all of the materials structured by the
Enterprise Continuum). This material includes :
- Foundation architectures
- Common systems architectures
- Industry architectures
- Organization specific architectures (developed in previous engagements and re-worked for later reuse)
The
Governance Log
The Governance Log holds information produced
during the architecture governance processes, that must be available for later
use and reference.
It should contain the following groups of
information:
- Decision log
- Compliance assessments
- Capability assessments
- Calendar
- Project portfolio
- Performance measurement
No comments:
Post a Comment