TOGAF: Architectural Artifacts

From Glitchdata
Jump to navigation Jump to search
Architecture Artifacts

Architectural artifacts are created in order to describe a system, solution, or state of the enterprise. The concepts discussed in this section have been adapted from more formal definitions contained in ISO/IEC 42010:2007.

  • A "system" is a collection of components organized to accomplish a specific function or set of functions.
  • The "architecture" of a system is the system's fundamental organization, embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution.
  • An "architecture description" is a collection of artifacts that document an architecture. In TOGAF, architecture views are the key artifacts in an architecture description.
  • "Stakeholders" are people who have key roles in, or concerns about, the system; for example, as users, developers, or managers. Different stakeholders with different roles in the system will have different concerns. Stakeholders can be individuals, teams, or organizations (or classes thereof).
  • "Concerns" are the key interests that are crucially important to the stakeholders in the system, and determine the acceptability of the system. Concerns may pertain to any aspect of the system's functioning, development, or operation, including considerations such as performance, reliability, security, distribution, and evolvability.
  • A "view" is a representation of a whole system from the perspective of a related set of concerns. In capturing or representing the design of a system architecture, the architect will typically create one or more architecture models, possibly using different tools. A view will comprise selected parts of one or more models, chosen so as to demonstrate to a particular stakeholder or group of stakeholders that their concerns are being adequately addressed in the design of the system architecture.
  • A "viewpoint" defines the perspective from which a view is taken. More specifically, a viewpoint defines: how to construct and use a view (by means of an appropriate schema or template); the information that should appear in the view; the modeling techniques for expressing and analyzing the information; and a rationale for these choices (e.g., by describing the purpose and intended audience of the view).


Artifacts are components of architecture work that make up TOGAF: Architectural Deliverables. Artifacts have continuity by being placed in the TOGAF: Architecture Repository and eventually being viewed in the TOGAF: Enterprise Continuum.

# Artifacts PR AV - Phase A BA - Phase B IS - Phase C DA - Phase C AA - Phase C TA - Phase D OS - Phase E MP - Phase F IG - Phase G CM - Phase H RM
1 TOGAF: Architecture Contract C U U U U U U U U
1 TOGAF: Architecture Vision C U U U U U U U U

1 TOGAF: Principles Catalog C
2 TOGAF: Stakeholder Map Matrix C
3 TOGAF: Value Chain Diagram C
4 TOGAF: Solution Concept Diagram C
5 TOGAF: Organisation/Actor Catalog C
6 TOGAF: Driver/Goal/Objective Catalog C
7 TOGAF: Role Catalog C
8 TOGAF: Business Service/Function Catalog C
9 TOGAF: Location Catalog C
10 TOGAF: Process/Event/Control/Product Catalog C
11 TOGAF: Contract/Measure Catalog C
12 TOGAF: Business Interaction Matrix C
13 TOGAF: Actor/Role Matrix C
14 TOGAF: Business Footprint Diagram C
15 TOGAF: Business Service/Information Diagram C
16 TOGAF: Functional Decomposition Diagram C
17 TOGAF: Product Lifecycle Diagram C
18 TOGAF: Goal/Objective/Sevice Diagram C
19 TOGAF: Business Use-Case Diagram C
20 TOGAF: Organisation Decomposition Diagram C
21 TOGAF: Process Flow Diagram C
22 TOGAF: Event Diagram C
23 TOGAF: Data Entity/Data Component Catalog C
24 TOGAF: Data Entity/Business Function Matrix C
25 TOGAF: Application/Data Matrix C
26 TOGAF: Conceptual Data Diagram C
27 TOGAF: Logical Data Diagram C
28 TOGAF: Data Dissemination Diagram C
29 TOGAF: Data Security Diagram C
30 TOGAF: Data Migration Diagram C
31 TOGAF: Data Lifecycle Diagram C
32 TOGAF: Application Portfolio Catalog C
33 TOGAF: Interface Catalog C
34 TOGAF: Application/Organisation Matrix C
35 TOGAF: Role/Application Matrix C
36 TOGAF: Application/Function Matrix C
37 TOGAF: Application Interaction Matrix C
38 TOGAF: Application Communication Diagram C
39 TOGAF: Application and User Location Diagram C
40 TOGAF: Application Use-Case Diagram C
41 TOGAF: Enterprise Manageability Diagram C
42 TOGAF: Process/Application Realisation Diagram C
43 TOGAF: Software Engineering Diagram C
44 TOGAF: Application Migration Diagram C
45 TOGAF: Software Distribution Diagram C
46 TOGAF: Technology Standards Catalog C
47 TOGAF: Technology Portfolio Catalog C
48 TOGAF: Application/Technology Matrix C
49 TOGAF: Environments and Locations Diagram C
50 TOGAF: Platform Decomposition Diagram C
51 TOGAF: Processing Diagram C
52 TOGAF: Networked Computing/Hardware Diagram C
53 TOGAF: Communications Engineering Diagram C
54 TOGAF: Project Context Diagram C
55 TOGAF: Benefits Diagram C
56 TOGAF: Requirements Catalog C

Related ACF Topics