©January 2004, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.

Product Standard

NAME

TOGAF 8 TOOL SUPPORT

LABEL FOR LOGO

TOGAF 8 TOOL SUPPORT

When this logo is used on, or in relation to, a product registered as conformant to this Product Standard, it must be accompanied by an attribution, in the form defined in the TOGAF Certification Agreement, which includes the TOGAF 8 TOOL SUPPORT Product Standard name.

DESCRIPTION

The TOGAF 8 TOOL SUPPORT Product Standard defines core requirements for tools that support the development of Enterprise Architectures using The Open Group Architecture Framework (TOGAF), Version 8.¹

MANDATORY CONFORMANCE REQUIREMENTS

In order for an applicant to submit a product for certification to the TOGAF 8 TOOL SUPPORT Product Standard, the applicant must be a current commercial licensee of TOGAF Version 8.1.

A product conforming to this Product Standard (hereafter simply referred to as the "product") may be a single tool, or a defined configuration of tools from a single product family.

A conforming product shall:

• Support the modeling of the TOGAF Architecture Development Method (ADM) process, as defined below

• Support the development of the key deliverables of the TOGAF Architecture Development Method (ADM), as defined below

• Support the modeling of the TOGAF Foundation Architecture (Technical Reference Model and Standards Information Base), as defined below

• Support the import, storage, use, and reuse of models in accordance with the concepts of the Enterprise Continuum, as defined below

ADM Process Conformance

1. The tool must support the modeling of the sequence and content of the Phases, Steps, and Activities comprising the TOGAF Architecture Development Method,² in one of the following ways:

   • Provide a usable model of the TOGAF Version 8.1 ADM "out-of-the-box" (that is, after normal documented installation)

   • Provide a general capability to model the TOGAF Version 8.1 ADM, which the user must customize

   • Provide the capability to work with another tool that can model the TOGAF Version 8.1 ADM

2. The tool must support the export of graphical and textual artefacts for use in ADM documents that require them. The Conformance Statement must declare how this is achieved.

ADM Deliverables Conformance

1. The tool must support the development of the following deliverables of the ADM:³

   • Business Architecture

   • Data Architecture

   • Applications Architecture

   • Technical Architecture

   • Views of all architectures

   • The Architecture Building Blocks used in constructing all architectures

   To achieve this, the tool must be capable of storing the definitive source of both the graphical and textual artefacts of those products, and enabling their maintenance and use through the ADM by architecture practitioners.

2. The tool must support the ability to define and instance relationships between artefacts, and between artefacts and entries in the Standards Information Base.⁴

Foundation Architecture Conformance

• Technical Reference Model (TRM)

  The tool must provide support for modeling the TOGAF 8 Technical Reference Model⁵ (including the detailed taxonomy), in one of the following ways:

  • Provide a usable model of the TOGAF 8 Technical Reference Model "out-of-the-box"

  • Provide a general capability to model the TOGAF 8 Technical Reference Model, which the user must customize

  The tool must also provide support for updating this model to generate an organization-specific TRM.

• Standards Information Base (SIB)

  The tool must provide support for referencing (hence reusing) the information held in a Standards Information Base (but not necessarily holding the information in the tool itself); and for defining relationships between SIB and TRM components, in one of the following ways:

  • Creating a Standards Information Base within the tool

  • Importing a Standards Information Base

  • Dynamic linkages to a Standards Information Base

Enterprise Continuum Conformance

1. The tool must provide support for modeling the TOGAF Enterprise Continuum⁶ (including the distinction between Architecture Building Blocks and Solutions Building Blocks, and the four architecture types), and including support for updating this model to generate an organization-specific Enterprise Continuum.

2. The tool must provide support for defining and maintaining the relationships between the different artefacts in the Enterprise Continuum, and for navigating in both directions (from generic to specific and vice versa) between the architecture types within the Continuum.

OPTIONAL CONFORMANCE REQUIREMENTS

A conforming product may support any or all of the following optional features. The Conformance Statement must state which of these optional features the product supports.

ADM Process Conformance

A conforming product may support any or all of the following optional features:

1. Provide a mechanism for navigating between the ADM phases and deliverables

2. Enable the business, data, applications, and technical architectures to be validated against requirements

3. Support the development and use of Business Scenarios⁷ by architecture practitioners

ADM Deliverables Conformance

1. The tool may support the development of the following deliverables of the ADM:

   • Architecture Principles

   • Request for Architecture Work

   • Statement of Architecture Work

   • Product Information

   • New Technology Reports

   • Impact Analysis (architecture planning and implementation)

   • Architecture Contract

Enterprise Continuum Conformance

1. The tool may support the import and/or export of architecture artefacts to/from the Enterprise Continuum.

2. The tool may be capable of supporting relationships between components in the Architecture and Solutions Continuums.

Other Architecture Modeling Support

• Support for Other Architecture Frameworks

  The tool may declare support for any other Architecture Frameworks, either referenced in TOGAF⁸ (for example, C4ISR, Enterprise Architecture Planning, Zachman Framework, and so on), or not, that are supported in the tool.

• Support for Other Modeling Standards and Methods

  The tool may declare support for any modeling methods (for example, Business Process Modeling, Entity/Relation Modeling) and standards (for example, ANSI/IEEE 1471:2000, IDEF, UML, XML) that are supported in the tool.

Additional TOGAF Support Functionality

The tool may declare support for any of the following additional functionality, and/or declare support for other additional functionality not listed, relevant to TOGAF support:

• Shared Repository Support

• Support for multiple concurrent users

• Single definition/multiple use of model artefacts

• Configuration management and version control at the model level

• Capability for access to models based on the role or area of interest of the individual modeler

• Scalability to support the modeling needs of the whole enterprise

• Publication of models in both electronic and paper form

• Output in standard formats (for example, HTML, XML, and so on)

• Tool Customization capabilities:

  • Customize information content and presentation of model artefacts

  • Add new model artefacts (definition types, symbol types, diagram types)

  • Extend the tool; for example, by scripts (such as VBA macros, and so on)

  • Configure the repository to support an organization's chosen methods and languages for modeling

• Non-English Language Support

OPERATIONAL ENVIRONMENT

Not applicable.

PORTABILITY ENVIRONMENT

Not applicable.

OVERRIDING STANDARDS

There are no overriding standards for this Product Standard.

INDICATORS OF COMPLIANCE

There are no Indicators of Compliance for this Product Standard.

MIGRATION

As this is the first version of this Product Standard, there are no migration issues.

Footnotes

1.

The Open Group Architecture Framework (TOGAF), Version 8.1, January 2004, available at: www.opengroup.org/architecture/togaf8/index8.htm.

2.

TOGAF Documentation, January 2004, TOGAF 8 Core Definition (I917), published by The Open Group, Section 1: TOGAF Architecture Development Method (ADM) - Process.

3.

Refer to the TOGAF 8 Core Definition, Section 2: TOGAF Architecture Development Method (ADM) - Information Sets.

4.

Refer to the TOGAF 8 Core Definition, Section 3: TOGAF Foundation Architecture.

5.

Refer to the TOGAF 8 Core Definition, Section 3: TOGAF Foundation Architecture.

6.

Refer to the TOGAF 8 Core Definition, Section 4: The Enterprise Continuum.

7.

Refer to the TOGAF 8 Core Definition, Section IV: Resource Base, Business Scenarios.

8.

Refer to the TOGAF 8 Core Definition, Section 5: The Relationship of TOGAF to Other Architectures and Architecture Frameworks.

Boundaryless Information Flow is a trademark and UNIX and The Open Group are registered trademarks of The Open Group in the United States and other countries.

All other trademarks are the property of their respective owners.

Any comments relating to the material contained in this document may be submitted to The Open Group at:

The Open Group
Apex Plaza
Forbury Road
Reading
Berkshire, RG1 1AX
United Kingdom

OGSpecs@opengroup.org