TOGAF Classroom Series - M18 architecture repository
1 like271 views
The Architecture Repository contains several key components: 1. The Architecture Metamodel which describes the architecture framework in use. 2. The Architecture Landscape shows the state of the enterprise at different points in time. 3. The Reference Library contains reusable architecture work products, standards, and best practices.
TOGAF Classroom Series - M18 architecture repository
- 3. Architecture Repository • The Architecture Repository is a logical information store for outputs of executing the ADM • The Architecture Metamodel describes the architecture framework in use • The Architecture Landscape shows the state of the operating enterprise at particular points in time • The Reference Library contains re-usable architecture work products
- 4. Architecture Repository • The Standards Information Base defines the compliance criteria for work governed by architecture • The Governance Log captures results of governance activity, such as compliance assessments • The Architecture Capability describes the organization, roles, skills and responsibilities of EA practice
- 5. 1. Architecture Metamodel •Architecture Method • a method to develop an architecture, ADM – Architecture Development Method •Content Metamodel • defines a formal structure for architectural work products
- 6. 2. Architecture Landscape •Strategic Architectures • show a long-term summary view of the enterprise, executive level •Segment Architectures • provide more detailed operating models for areas within an enterprise, program/portfolio level •Capability Architectures • show in a more detail how the enterprise can support a particular capability, project level
- 7. 3. Reference Library • A repository area to hold best practice or template materials that can be used to construct architectures within an enterprise • Reference materials held in the Reference Library are typically obtained from a variety of source, including • Standards, Vendors • Industry communities, Corporates • Best practices
- 8. 4. Standards Information Base • A repository area to hold a set of specifications, to which architectures must conform • Establishment of a Standards Information Base provides a clear basis for architectural governance since • Standards are easily accessible to projects Standards are stated in a clear manner
- 9. Standards Information Base • Types of Standard • Legal and Regulatory • Industry • Organizational • Standards Lifecycle • Trial • Active • Deprecated • Obsolete
- 10. Standards Classification • Business Standards • Standard shared business functions • Standard role and actor definitions • Security and governance standards for business activity • Data Standards • Standard coding and values • Standard structures and formats • Standards for origin and ownership • Restrictions on replication and access • Application Standards • Standard/shared applications supporting specific business functions • Standards for application communication and integration • Standards for access, presentation and style • Technology Standards • Standard hardware products • Standard software products • Standards for software development
- 11. 5. Governance Log • A repository area to hold shared information relating to the ongoing governance of projects • Maintaining a shared repository of governance information is important
- 12. 5. Architecture Capability • A repository area to hold the information with regards to the architecture capability of the enterprise • how the architecture is managed, the organization structure to run the EA, and needed skillset, roles and responsibilities.
Editor's Notes
- #3: The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content. The Architecture Capability 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.
- #12: Decision Log: A log of all architecturally significant decisions that have been made in the organization. This would typically include: Product selections Justification for major architectural features of projects Standards deviations Standards lifecycle changes Change request evaluations and approvals Re-use assessments Compliance Assessments: At key checkpoint milestones in the progress of a project, a formal architecture review will be carried out. This review will measure the compliance of the project to the defined architecture standards. For each project, this log should include: Project overview Progress overview (timeline, status, issues, risks, dependencies, etc.) Completed architecture checklists Standards compliance assessment Recommended actions Capability Assessments: Depending on their objectives, some projects will carry out assessments of business, IT, or Architecture Capability. These assessments should be periodically carried out and tracked to ensure that appropriate progress is being made. This log should include: Templates and reference models for executing Capability Assessments Business Capability Assessments IT capability, maturity, and impact assessments Architecture maturity assessments Calendar: The Calendar should show a schedule of in-flight projects and formal review sessions to be held against these projects. Project Portfolio: The Project Portfolio should hold summary information about all in-flight projects that fall under architectural governance, including: The name and description of the project Architectural scope of the project Architectural roles and responsibilities associated with the project Performance Measurement: Based on a charter for the architecture function, a number of performance criteria will typically be defined. The Performance Measurement log should capture metrics relating to project governance and any other performance metrics relating to the architecture charter so that performance can be measured and evaluated on an ongoing basis.
- #13: Decision Log: A log of all architecturally significant decisions that have been made in the organization. This would typically include: Product selections Justification for major architectural features of projects Standards deviations Standards lifecycle changes Change request evaluations and approvals Re-use assessments Compliance Assessments: At key checkpoint milestones in the progress of a project, a formal architecture review will be carried out. This review will measure the compliance of the project to the defined architecture standards. For each project, this log should include: Project overview Progress overview (timeline, status, issues, risks, dependencies, etc.) Completed architecture checklists Standards compliance assessment Recommended actions Capability Assessments: Depending on their objectives, some projects will carry out assessments of business, IT, or Architecture Capability. These assessments should be periodically carried out and tracked to ensure that appropriate progress is being made. This log should include: Templates and reference models for executing Capability Assessments Business Capability Assessments IT capability, maturity, and impact assessments Architecture maturity assessments Calendar: The Calendar should show a schedule of in-flight projects and formal review sessions to be held against these projects. Project Portfolio: The Project Portfolio should hold summary information about all in-flight projects that fall under architectural governance, including: The name and description of the project Architectural scope of the project Architectural roles and responsibilities associated with the project Performance Measurement: Based on a charter for the architecture function, a number of performance criteria will typically be defined. The Performance Measurement log should capture metrics relating to project governance and any other performance metrics relating to the architecture charter so that performance can be measured and evaluated on an ongoing basis.