TOGAF is a high-level approach to design. The four architectural domains of TOGAF The way that TOGAF achieves its intended goal is to divide Enterprise Architecture into four Architectural Domains: Business, Application, Data, and Technical. The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content. To open the Architecture Repository, select ITSM > Architecture Repository from the application toolbar. The Architecture Content Framework (also known as the “TOGAF Content Framework”) is defined as “The TOGAF content framework provides a detailed model of architectural work products, including deliverables, artifacts within deliverables, and the architectural building blocks that artifacts represent. It is the most prominent and reliable Enterprise Architecture standard, ensuring consistent standards, methods, and communication among Enterprise Architecture professionals. The TOGAF® Standard, a standard of The Open Group, is a proven Enterprise Architecture methodology and framework used by the world’s leading organizations to improve business efficiency. Application Architecture: Application & User Location Diagram, Application Communication Diagram, System Use-Case Diagram Architecture Vision: Solution Concept Diagram, Value Chain Diagram Business Architecture: Business Footprint Diagram, Business Services and Information Diagram, Functional Decomposition Diagram, Product Lifecycle Diagram Remember, TOGAF is intended to be used to design and implement an Enterprise Architecture; the software is but a component of the greater whole. The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture today that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. The figure below shows how the Architecture Repository looks like. When all the activities associated with a TOGAF ADM deliverable are done, a deliverable (document) will be automatically generated and archived in the drawer named Organization-Specific Architectures . The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository.