The Architecture Continuum illustrates how architectures are developed across a continuum ranging from Foundation Architectures such as TOGAF's, through common systems architectures, and industry-specific architectures, to an enterprise's own individual architectures.
Architecture Landscape
In a typical enterprise, many architectures will be described in the Architecture Landscape at any point in time. Some architectures will address very specific needs; others will be more general. Some will address detail; some will provide a big picture. To address this complexity, the TOGAF standard uses the concepts of levels and the Enterprise Continuum to provide a conceptual framework for organizing the Architecture Landscape.
Levels provide a framework for dividing the Architecture Landscape into three levels of granularity:
Strategic Architecture provides an organizing framework for operational and change activity and allows for direction setting at an executive level.
Segment Architecture provides an organizing framework for operational and change activity and allows for direction setting and the development of effective architecture roadmaps at a program or portfolio level.
Capability Architecture provides an organizing framework for change activity and the development of effective architecture roadmaps realizing capability increments.
TOGAF Library: A set of standard Reference Architectures that can be used within an enterprise architecture.
Value Stream Analysis: technique used in Phase B provides stakeholder context into why the organization needs business capabilities.
Architecture view is a representation of a system from the perspective of a related set of concerns.
Architecture viewpoint is a specification of the conventions for a particular kind of architecture view. It can also be called the definition or schema for that kind of architecture view.
Artifacts: a specific document, report, analysis, model, or other tangible asset that contributes to an architectural description. Classify as catalogs, matrices and diagrams.
Enterprise Continuum: TOGAF standard provide to guide architectural activity within the enterprise in terms of structures, roles, responsibilities, and processes.
Architecture principle: Define general rules and guidelines for the use of resources across the enterprise.
Understandability
Robustness
Completability- cover every situation perceived throughout the enterprise meet the recommended criteria
Consistency
Stability
Section of Architecture Principles: Name, Statement, Rationale and implication
Implementation and Migration Plan: Actions arising from the Business Transformation Readiness Assessment technique should be incorporated in this plan.
Architecture Board is typically made responsible, and accountable, for achieving some or all of the following goals:
■ Providing the basis for all decision-making with regard to the architectures
■ Consistency between sub-architectures
■ Establishing targets for re-use of components
Architecture Capability Framework: It does TOGAF provide as a set of reference materials for establishing an architecture function within an organization.
Architecture Capability: Processes to support governance of the Architecture Repository
Architecture Contract: An agreement between development partners and sponsors on the architecture deliverables.
Architecture Compliance Review: A review of an architecture project against established criteria and business objectives.
Gap Analysis technique: To highlight shortfalls between the baseline and target architectures.
Boundaryless Information Flow: Getting information to the right people at the right time in a secure, reliable and timely manner
The Architecture Content Framework Contains a detailed model of the architectural work products that includes deliverables(ABB), Artifacts
Reference Model provides models and taxonomies of generic platform services. This includes your existing architecture and industry reference models