Why Use TOGAF TRM in Ardoq?
Using the TOGAF TRM in Ardoq provides organizations with a standardized foundation for technology architecture, enabling consistent service categorization, promoting application portability, and supporting enterprise-wide technology standardization. It helps architects assess current platforms, identify gaps, and plan technology roadmaps aligned with business requirements.
How Ardoq Adopts TOGAF TRM
The TOGAF TRM is implemented in Ardoq as a practical adaptation of the official framework, organized across multiple workspaces within three architectural layers: Application Layer, Motivation (Qualities), and Technology Layer. This implementation provides a starting foundation that organizations can extend and customize to meet their specific technology architecture needs. While not a literal 1:1 mapping of the official TOGAF TRM, this structure captures the essential concepts and taxonomy in a format optimized for enterprise architecture tooling. Organizations can use these pre-configured workspaces as-is or adapt them by adding industry-specific services, custom platform functions, or additional architectural layers relevant to their technology landscape.
Folder/Workspace Structure
Application Layer Workspaces
Workspace Name | Component Types | Purpose |
TRM - Applications | Application | Business and infrastructure applications that run on the platform |
TRM - Application Interfaces | Interface | Interfaces between applications and the platform (APIs) |
TRM - Data Objects | Data Object | Data structures and objects used by applications |
Motivation Layer Workspace
Workspace Name | Component Types | Purpose |
TRM - Service Qualities Taxonomy | Category, Constraint, Requirement | Cross-cutting service qualities (security, performance, manageability, etc.) |
Technology Layer Workspaces
Workspace Name | Component Types | Purpose |
TRM - Application Platform Taxonomy | Platform Service Category, Service | Complete taxonomy of 12 platform service categories (Security, Data Management, Network Services, etc.) |
TRM - Communication Network | Network, Path | Network infrastructure and communication pathways |
TRM - Devices | Device, Node | Physical and logical devices in the communications infrastructure |
TRM - Technology Interfaces | Technology Interface | Interfaces between platform and communications infrastructure |
Application Platform Service Categories:
The TRM organizes platform services into 12 major categories within the Application Platform Taxonomy. Each category is represented as a Category in Ardoq, with individual services listed as Service components:
Service Category | Description |
Data Interchange Services | Provide specialized support for the exchange of information between applications and the external environment. Handle data interchange between applications on the same platform and applications on different (heterogeneous) platforms. |
Data Management Services | Central to most systems is the management of data that can be defined independently of the processes that create or use it, maintained indefinitely, and shared among many processes. |
Graphics and Imaging Services | Provide functions required for creating, storing, retrieving, and manipulating images. Include defining multi-dimensional graphic objects in a form that is independent of output devices. |
International Operation Services | Provide a set of services and interfaces that allow a user to define, select, and change between different culturally-related application environments. Enable systems to operate in multi-national or multi-cultural environments. |
Location and Directory Services | Provide specialized support for locating required resources and for mediation between service consumers and service providers. Enable clients to establish where resources are and how they can be reached. |
Network Services | Support distributed applications requiring data access and applications interoperability in heterogeneous or homogeneous networked environments. Consist of both an interface and an underlying protocol. |
Operating System Services | Responsible for the management of platform resources, including the processor, memory, files, and input and output. Shield applications from the implementation details of the machine. |
Software Engineering Services | Provide the functional aspect of applications through programming languages and tools appropriate to the development and maintenance of applications. Support professional system developers. |
Transaction Processing Services | Provide support for the online processing of information in discrete units called "transactions", with assurance of the state of the information at the end of the transaction. |
User Interface Services | Define how users may interact with an application. Include graphical, character-based, and other interaction methods depending on capabilities required by users and applications. |
Security Services | Necessary to protect sensitive information in the information system. Must be designed into an architecture and applied across the whole system, whether stand-alone or distributed. |
System and Network Management Services | Manage diverse resources effectively to achieve open system environment goals. Apply basic concepts of operation, administration, and maintenance to the full suite of information system components. |
TRM Service Qualities:
Beyond the platform service categories, the TRM defines cross-cutting service qualities that affect all components of the information system. Service qualities describe pervasive behaviors such as security, performance, or manageability that require multiple functional service categories to cooperate in achieving the objective. These qualities sit on a "backplane" beneath all TRM components and must be designed into the architecture from the outset rather than added afterwards.
Category | Description | Requirements |
Availability | The degree to which something is available for use | • Manageability - Ability to gather information about state and control it • Serviceability - Ability to identify problems and take corrective action • Performance - Ability to perform tasks in appropriate time • Reliability - Resistance to failure • Recoverability - Ability to restore after interruption • Locatability - Ability to be found when needed |
Assurance | Protection and trust in the system | • Security - Protection from unauthorized access • Integrity - Assurance that data has not been corrupted • Credibility - Level of trust in system and data integrity |
Usability | Ease-of-operation by users | • International Operation - Multi-lingual and multi-cultural abilities |
Adaptability | Ability to change and evolve | • Interoperability - Integration within and outside the organization • Scalability - Ability to grow or shrink appropriately • Portability - Of data, people, applications, and components • Extensibility - Ability to accept new functionality |
TRM Metamodel Structure
The TRM metamodel connects applications, platform services, and communications infrastructure through standardized interfaces. Cross-cutting service qualities ensure requirements like security and performance are addressed across all layers, enabling organizations to assess their technology stack and plan evolution while maintaining portability.
Importing TOGAF TRM into Ardoq
Access the TOGAF TRM through Ardoq's Frameworks & Resources Importer. For step-by-step instructions, see How to use the Frameworks & Resources Importer.
Unlocking the TOGAF Framework
To access TOGAF content in Ardoq, you must provide proof of a valid TOGAF license as described by The Open Group. Contact your Ardoq representative to unlock this framework for your organization.