Enterprise Architecture Repository
- Satwinder Singh
Enterprise Architecture Repository Structure
1. Architecture Repository
At a high level, six classes of architectural information are expected to be held within an Architecture Repository: The Architecture Framework describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content. It also defines the parameters, structures, and processes that support governance of the Architecture Repository. The Architecture Landscape presents an architectural representation of assets in use, or planned, by the enterprise at particular points in time. The Standards Information Base captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization. The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise. The Governance Log provides a record of governance activity across the enterprise.
2. Requirements Repository
The Requirements Repository is used by the Requirements Management Phase of the Architecture Development Method (ADM) to record and manage all information relevant to the architecture requirements. The requirements address the many types of architecture requirements; i.e., strategic, segment and capability requirements which are the major drivers for the enterprise architecture. Requirements can be gathered at every stage of the architecture development lifecycle and need to be approved through the various phases and governance processes.
3. Solution Repository
The Solutions Repository holds the Solution Building Blocks (SBBs).