Conformance Statement

Product Standard: TOGAF 8 TOOL SUPPORT

Version 1.02

This form contains a series of questions that need to be answered. Use an HTML editor or simple text editor to edit the form to provide the answers. DO NOT EDIT ANY OF THE QUESTIONS. Note that the completed Conformance Statement will be made publicly accessible.

As you go about answering the questions, please keep in mind the following:

Enter the name, and organization of the author of this completed Conformance Statement (the "Applicant").

Name Organization
Scott Darlington IBM

1. Mandatory Requirements

1.1 Organization / Product Information

Enter the Tool name and version number for which TOGAF 8 TOOL SUPPORT certification is being sought and the name of the providing Organization (Enterprise, Division, etc.).

Enterprise Name Division / Organization Tool Name Version
IBM IBM Rational System Architect V11

1.2 Mandatory TOGAF Support

 

1.2.1 TOGAF Architecture Development Method (ADM) - Process

Question 1: Does the Tool provide support for modeling the process of the TOGAF 8 ADM? If so, indicate how that support is achieved.

Enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference.

Response:
Function Response: Tool Documentation Reference:(s)
The tool provides a usable model of the TOGAF 8 ADM "out-of-the-box". Yes See the help, wherein TOGAF Enterprise (V8) and TOGAF 7 are main books in the table of contents. See also the product's configuration dialog (select Tools, Customize Method Support), wherein you can turn on TOGAF Enterprise (V8) or TOGAF 7 support.
The tool provides a general capability to model the TOGAF 8 ADM, which the user must customize. Yes TOGAF 8 is fully supported, as described in the help. Users may customize this support by customizing the tools metamodel to add new diagram, definition, and property set types. They may also build VBA macros to customize tool behavior and add utilities.
The tool provides the capability to work with another tool that can model the TOGAF 8 ADM (the net effect of the tool combination being to meet the mandatory criteria for modeling the process of the TOGAF 8 ADM). Yes IBM Rational System Architect also has a tight integration with the IBM Rational DOORS tool for requirements. System Architect can also integrate with IBM Rational Requirements Composer for requirements, as well as many other IBM tools.

Question 2: Does the tool support the export of graphical and textual artefacts for use in the ADM documents that require them? If so, declare the mechanism(s) used.

Enter "Yes" or "No" as appropriate; for "yes", provide the appropriate tool documentation reference(s).

Response:
Response: Tool Documentation Reference:(s)
Yes Users may export graphical information from System Architect in a variety of ways.
  • They may use SA/Publisher add-on to publish complete websites of the architecture, including SVG images of diagrams. See that product's help.
  • They may use SA/XT to gain live read/write access to the repository, run reports, and add information or view information in the repository. See that product's help.
  • Users may generate Word reports that contain architecture information. Users may use SA's native reporting system to output information of the architecture. Users may export all information in the repository to XML or CSV format. Users may copy/paste diagrams to Powerpoint or other Office products, etc, etc. See SA's help.
  • Users may generate Cognos Business Intelligence reports using the built-in integration with Cognos BI and the bundled copy of Cognos BI (for use with SA data only).
Rationale:

In order to participate in the TOGAF 8 TOOL SUPPORT certification program, the Tool must support the modeling of the sequence and content of the Phases, Steps, and Activities comprising the TOGAF 8 Architecture Development Method. The tool must also support the export of graphical and textual artefacts for use in the ADM documents that require them.

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

 

1.2.2 TOGAF Architecture Development Method (ADM) - Deliverables

Question 3: Does the Tool provide support for storing and reusing the graphical and textual artefacts of the deliverables of the ADM?

Response:

Enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s).

Function Response: Tool Documentation Reference:(s)
Business Architecture
Yes		 See Enterprise Architecture and Business Modeling section of SA's help for descriptions of the myraid diagram types support business architecture, including BPMN, BPMN 2, Functional Hierarchy diagrams, Business Motivation Model (BMM), Explorer diagram, Org Charts, Balanced Scorecards and Strategy Maps, etc, etc and so on.
Data Architecture
Yes		 See Data Modeling section of SA's help for descriptions. System Architect supports logical data model and Physical data model, and schema generation/reversal/synchonization to all major DBMS's.
Applications Architecture
Yes		 System Architect supports UML 1.4 in System Architect. See Help. System Architect also supports the exchange of UML models with Rational Software Architect, a UML 2 modeling tool for further elaboration of applications architecture. In addition, System Architect supports linking using the Open Services for Lifecycle Collaboration integration protocols described on Jazz.net. These allow linking to and from Rational System Architect models and Rational Software Architect models for cases where referencing is important or copied data is to be avoided.
Technical Architecture Yes
 SA supports Network diagrams, UML 1.4, and numerous other diagram types to support Technical Architecture. SA also supports DoDAF Systems Views and Technical Views (as well as Operational Views). See Help.
Architecture Views Yes
 Full support added specifically for TOGAF architecture views (see TOGAF sections of help in product), as well as other diagram types such as Explorer diagram which provides overview of architecture. See TOGAF section of Help.
Architecture Building Blocks Yes
 Architecture Building Block definitions and supporting diagrams have been added to tool specifically to support TOGAF. See TOGAF section of Help.

Question 4: Does the Tool provide support for defining and maintaining the relationships between these artefacts? If so, declare the mechanism(s) used.

Enter "Yes" or "No" as appropriate; for "yes", provide the appropriate tool documentation reference(s).

Response:
Response: Tool Documentation Reference:(s)
Yes Relationships between artifacts are prescribed in the underlying metamodel of the tool (which can be customized by the user). Users can use a myraid of other matrices to view relationships or specify relationships between artifacts. So for example, user can use a CRUD matrix to specify what business processes use what entities, and so forth. Relationships can also be specified in the definitions of artifacts themselves. So for example, a user can open the definition of a business process and specify related entities. This is one example; there are myraid relationships between artifacts of different types in the tool. See the help.
Rationale:

In order to participate in the TOGAF 8 TOOL SUPPORT certification program, the Tool must support the development of the above deliverables of the ADM. 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. The tool must also support the ability to define required relationships between artefacts.

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

 

1.2.3 TOGAF Foundation Architecture

Question 5: Does the Tool provide support for modeling the TOGAF Technical Reference: Model (including the detailed taxonomy) as defined in the TOGAF 8 Core Definition, including support for updating this model to generate an organization-specific TRM?

Enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s).

Response:
Function Response: Tool Documentation Reference:(s)
The tool provides a usable model of the TOGAF 8 TRM "out-of-the-box" Yes TOGAF TRM is provided as a Framework Graphic that can be clicked on to open browsers to various relevant artifact types for the particular portion of the TRM. See the help, TOGAF section.
The tool provides a general capability to model the TOGAF 8 TRM, which the user must customize. Yes TRM can be modeled in the tool, and elaborated upon. See the help, TOGAF section.

Question 6: Does the Tool provide support for referencing (hence re-using) the information held in a Standards Information Base?If so, declare the mechanisms used.

Enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s).

Response:
Function Response: Tool Documentation Reference:(s)
Support via creating a Standards Information Base within the tool Yes Users may create a Standards Information Base within the SA repository, using pre-built Architecture Building Block and Solution Building Block definition types to capture information. Users may use other definition types available in the standard metamodel, or create new ones by extending that metamodel. See the help.
Support via importing a Standards Information Base Yes User may import Standards Information Base via CSV import or use SA's open API with VBA to build interface. See the help.
Support via dynamic linkages to a Standards Information Base Yes User may use Reference Property capability in any definition type in System Architect to reference an external document of file. See the help.
Rationale:

In order to participate in the TOGAF 8 TOOL SUPPORT certification program, the Tool must provide support for modeling the TOGAF Technical Reference: Model (including the detailed taxonomy), either "out-of-the-box", or via a general capability, which the user must customize. The tool  must also provide support for updating this model to generate an organization-specific TRM.

The Tool must provide support for referencing (hence re-using) the information held in a Standards Information Base (but not necessarily holding the information in the tool itself); and supporting the definition of relationships between SIB and TRM components.

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

 

1.2.4 TOGAF Enterprise Continuum

Question 7:  Does the Tool provide support for:

Enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s).

Response:
Function Response: Tool Documentation Reference:(s)
The tool provides a usable model of the TOGAF Enterprise Continuum "out-of-the-box" Yes System Architect's base metamodel and diagram suite natively supports the TOGAF Enterprise Continuum concepts. See the help, TOGAF section.
The tool provides a general capability to model the TOGAF Enterprise Continuum, which the user must customize. Yes SA provides Architecture Building Block and Solution Building Block definition types to capture information, and build upon. See the help, TOGAF section.
Rationale:

In order to participate in the TOGAF 8 TOOL SUPPORT certification program, 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. The Tool must also provide support for defining and maintaining the relationships between the different artefacts in the Enterprise Continuum, and for navigating in both directions between the architecture types within the Continuum.

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

 

2. Optional Requirements

2.1 Optional TOGAF Support

2.1.1 TOGAF Architecture Development Method (ADM) - Process

Question 8: Does the Tool provide a mechanism for navigating between the ADM phases and deliverables? If so, declare how this is done.

Enter "Yes" or "No" as appropriate; for "yes", provide the appropriate tool documentation reference(s).

Response:
Response: Tool Documentation Reference:(s) to Navigation Mechanism(s)
Yes Users have multiple ways of navigating the repository information -- through the Explorer Browser, through the Views Explorer, by running reports, by using "referenced by" utilities, by navigating relationships in the definitions themselves, and so forth. See the help.

Question 9: Does the tool enable the business, data, appliactions, and technology architectures to be validated against requirements? If so, declare how this is done.

Enter "Yes" or "No" as appropriate; for "yes", provide the appropriate tool documentation reference(s).

Response:
Response: Tool Documentation Reference:(s) to Navigation Mechanism(s)
Yes Users may add requirement definitions into the SA tool as definitions, and specify what TOGAF artifacts are addressed by those requirements. See Requirements topic in the help.

User may also optionally address TOGAF artifacts with requirements in DOORS or Rational Requirements Composer, through a tight integration with these other IBM Rational products. User may run reports to show what requirements are satisfied by what definitions and diagrams and symbols on diagrams. Also, user may use Explorer diagram to get a visual cause-effect analysis birds' eye view of relationships between requirements and TOGAF artifacts. See the help for the SA/DOORS integration and SA/RRC integration.

Question 10: Does the Tool provide support for use of Business Scenarios?

Response:

Indicate which Business Scenario elements the tool allows to be modeled, stored and reused, by entering "Yes" or "No" as appropriate under "Response"; for each "Yes", provide the appropriate tool documentation reference(s).

Business Scenario Elements Response: Tool Documentation Reference:(s)
Problem Description Yes Can be entered as a separate definition type or as a property in a definition type. Users can customize according to where they want to capture this information. User can also reference an external document, or a document that they import into the Files table of the repository (SQL Server or Oracle repository). See the help.
Objectives Yes Yes, as a separate definition type. See the help.
Environment Models Yes Yes, via Technology and Network diagrams. See the help.
Process Models Yes Yes -- supports BPMN, BPMN 2, IDEF3, UML Activity, and Process Chart diagram types. See the help.
Information Flow Yes Yes -- supports Data Flow diagramming (Gane and Sarson, Yourdon DeMarco), IDEF0, Network diagrams, etc. See the help.
Human Actors, their Roles and Responsibilities Yes Yes -- supports UML Use Cases, Roles as a definition type, Responsibilities as a property on Actor and Role, and so forth. Business Process diagrams can be simulated -- you can specify manpower placed against processes and the competencies of that manpower. See the help.
Computer Actors, their Roles Yes Yes -- support UML Use Cases, Roles, etc as stated above. See the help.
Requirements Yes Yes -- as separate definition type, natively supported in tool, that can be used to address models (diagrams, symbols, and definitions) that each requirement pertains to. User can also use tight integration to DOORS. See the help.
Technology Architecture Model Yes Yes -- support Technology Architecture Model diagram natively. See the help.
Constraints Yes Yes -- through property sets in definitions, and also intersecting cell definitions of cross-reference matrices (you can specify the constraint of a relationship). See the help.
IT Principles Yes Yes -- through property set of relevant definitions or link to external documents (which can be done in every definition type). See the help.
Requirements Mapped to Technology Architecture Yes Yes -- again using requirements natively or optionally via added power of DOORS integration or Requirements Composer integration. See the help.
Rationale:

A Tool participating in the TOGAF 8 TOOL SUPPORT certification program may optionally provide support for the above functions, in support of use of the ADM process. 

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

 

2.1.2 TOGAF Architecture Development Method (ADM) - Deliverables

Question 11: Does the Tool provide support for developing the following deliverables of the ADM?

Response:

(For each major category, enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s).)

Deliverable Response Tool Documentation Reference:(s)
Framework Definition Yes TOGAF Framework supported in tool - users can click on parts of the TOGAF graphic and open browser that provides pertinent diagram and definition types for that part of the TOGAF Framework. See the help.
Architecture Principles Yes Via a property set; can also link to external docs. See the help.
Business Principles, Goals, and Drivers Yes Via definition types and property sets. See the help.
IT Governance Strategy Yes Via property set; can also link to external docs. See the help.
Request for Architecture Work Yes Via a specific property set added for TOGAF; can also link to external docs. See the help.
Statement of Architecture Work Yes Via a specific property set added for TOGAF; can also link to external docs. See the help.
Architecture Vision Yes Via a specific property set added for TOGAF; can also link to external docs. See the help.
Business Architecture Yes Via diagram set and reports. See the help.
Business Architecture Report Yes Via a specific report added for TOGAF. See the help.
Business Requirements Yes Via a definition type and also via integration to DOORS or Requirements Composer. See the help.
Technical Requirements Yes Via a definition type and also via integration to DOORS or Requirements Composer. See the help.
Gap analysis Yes Via reporting and the Explorer diagram for visual interpretation of gap analysis reports. See the help.
Data Architecture Yes Via diagram set (logical and physical data models). See the help.
Data Architecture Report Yes Via reports. See the help.
Applications Architecture Yes Via UML support (and ancillary diagram support; for example, System Architecture diagram, which shows high level of applications and their interrelationships). Also supports portfolio management via the included SOA add-on solution. See the help.
Applications Architecture Report Yes Via reports. See the help.
Technical Architecture Yes Via diagram set.
Technical Architecture Report Yes Via reports. See the help.
Architecture Viewpoints Yes Via diagram set. See the help.
Architecture Views Yes Via Views Explorer browser, which can be used to show different views of architecture. See the help.
Re-usable Architecture Building Blocks Yes Via specific definition type added for TOGAF (Architecture Building Block definition type). See the help.
Re-usable Solution Building Blocks Yes Via specific definition type added for TOGAF (Solution Building Block definition type). See the help.
Impact Analysis - Project list Yes Via reports and also via Explorer diagram. See the help.
Impact Analysis - Migration Plan Yes Via reports and also via Explorer diagram. See the help.
Impact Analysis - Implementation recommendations Yes Via reports and also via Explorer diagram. See the help.
Architecture Contracts Yes Via property set and also ability to reference to external documents and files. Can also push this out to website generated from architecture. See the help.
Product Information Yes Via definition type. See the help.
Request for Architecture Change Yes Via property set. See the help.
New Technology Report Yes Via reports. See the help.
Requirements Impact Statement Yes Via property set. See the help.
Rationale:

A Tool participating in the TOGAF 8 TOOL SUPPORT certification program may optionally provide support for any or all of the above ADM deliverables. 

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

 

2.1.3 TOGAF Enterprise Continuum

Question 12: Does the Tool support the import and/or export of architecture artefacts to/from the Enterprise Continuum? If so, declare the mechanism(s) used.

Enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s).

Response:
Function Response: Tool Documentation Reference:(s)
Import of architecture artefacts Yes Via CSV import, XML import, or via interface built using open API and VBA. See the help.
Export of architecture artefacts Yes Via CSV export, XML export, publishing of reports to HTML or XML or Word format, publishing of websites, or via interface built using open API and VBA. See the help.
Rationale:

To enable re-use of existing architecture artefacts, a tool participating in the TOGAF 8 TOOL SUPPORT certification program may optionally provide support for their import and export.

2.2 Other Support for Architecture Modeling

Question 13: Does the Tool support other Architecture Frameworks, Modeling Standards and Methods? If so, declare below.

(For each major category, enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s). Then answer any subsidiary questions.)

Topic Response Tool Documentation Reference:(s)
Model Types

Indicate which model types are supported in the Tool, by entering "Yes" or "No" as appropriate under "Response"; for each "Yes", provide the appropriate tool documentation reference(s).

 Data models Yes Logical and Physical models -- see help.
Business Process models Yes BPMN, BPMN 2, Functional Hierarchy diagrams, Enterprise Direction diagram (Business Motivation Model), Process Hierarchy diagrams, Org Charts, Use Cases, and so forth -- see help.
Application models Yes UML 1.x
System models Yes System Application diagram, DoDAF SV diagrams,UML, etc -- see help
Organisation models Yes Org Charts, BPMN/BPMN 2with swimlanes, Business Concept diagram, etc. See the help.
Technology models Yes Network diagram, UML Deployment diagram, DoDAF TV views, etc. See the help.
Support for Other Architecture Frameworks

Indicate which other Architecture Frameworks are supported in the Tool, by entering "Yes" or "No" as appropriate under "Response"; for each "Yes", provide the appropriate tool documentation reference(s).

 C4ISR / DoDAF Yes All DoDAF (including DoDAF 2) workproducts supported. See the help.
EAP Yes Support via the SA/ERP add-on tool. See the help.
Zachman Yes Zachman Framework fully supported. Zachman Framework is also provided as a "Framework Editor", so users can click on various parts of it and open browsers that provide relevant artifact types. See the help.
Other (specify):  
MODAF Yes Ministry of Defense Architecture Framework supported. See the help.
NAF Yes NATO Architecture Framework supported. See the help.
Support for Modelling Methods and Standards

Indicate which modelling methods (for example, Business Process Modelling, Entity / Relation Modelling) and standards (for example, ANSI / IEEE 1471-2000, IDEF, UML, XML) are supported in the Tool, by entering "Yes" or "No" as appropriate under "Response"; for each "Yes", provide the appropriate tool documentation reference(s).

 Business Process Modelling Yes BPMN, BPMN 2, IDEF3, UML Activity diagram, and Process Charts (generic technique). See the help.
Entity / Relation Modelling Yes ER diagram and IDEF1X diagram. Also Physical model separate from logical (and mapping to/from). Also provide schema generation/reverse engineering/synchronization for major DBMS's. See the help.
ANSI / IEEE 1471-2000 Yes Users can follow this recommended practice with numerous diagram and definition types and reports available to them in SA. See the help.
IDEF Yes IDEF1X, IDEF0, and IDEF3. See the help.
UML Yes UML 1.x and interchange with, or linking between UML 2 models in Rational Software Architect and Rational Design Manager-- see help.
XML Yes XML design of DTDs and Instance Documents (via XML Design diagram), and also of XML Schemas via UML Class diagram. Support reverse engineering of XML schemas, and generation thereof. See the help.
Other modelling methods and standards (specify): FEA Reference Model Support. See the help.
     
     
Rationale:

A Tool participating in the TOGAF 8 TOOL SUPPORT certification program may optionally declare support for any architecture frameworks, modeling standards and methods. 

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

Question 14: Does the Tool have the following additional functionality? If so, declare below.

Response:

(For each major category, enter "Yes" or "No" as appropriate; for each "yes", provide the appropriate tool documentation reference(s). Then answer any subsidiary questions.)

Topic Response: Tool Documentation Reference:(s)
Shared Repository Support

Enter "Yes" or "No" as appropriate under "Response"; if "Yes", provide the appropriate tool documentation reference(s).

 Does the tool include a shared repository to store and manage all definitions and model artefacts? Yes
SQL Server 2005, SQL Server 2008, SQL Server 2008R2, Oracle 10g or Oracle 11g. See Help.
Other Functional Support

Indicate which features and functionality the Tool supports, if any, by entering "Yes" or "No" as appropriate under "Response"; for each "Yes", provide the appropriate tool documentation reference(s).

 Support for multiple concurrent users Yes See the help.
Single definition / multiple use of model artefacts Yes
 See the help.
Configuration management and version control at the model level Yes Via History function in the tool (see help) and external Config Mgt tools (see whitepapers on the IBM Rational Support Center). System Architect's Workspaces feature, which allows descendent sandboxes for play before pushing back to the main stream, can also server this function.
Capability for access to models based on the role or area of interest of the individual modeller Yes Role-based access control via SA/Catalog Manager. See help.
Scalability to support the modelling needs of the whole enterprise
Yes		 See installation instructions and whitepapers on IBM Rational Support Center for how to deploy on networks, and on Terminal Server environments. See also the developerWorks white paper: http://www.ibm.com/developerworks/rational/library/scalability-of-rational-system-architect-11-4/
Publication of models in both electronic and paper form Yes Most info is in the help, which can be printed out. Also provide set of manuals. Models can be published in both electronic and paper forms using a variety of tools such as System Architect Publisher, Rational Publishing Engine, and Cognos Business Intelligence software.
Output in standard formats (for example, HTML, XML, etc.) - please specify Yes Generate websites in HTML and XML via native reporting system, HTML generator, and via add-on tools SA/Publisher and SA/XT. See the help.
Tool Customization - Is the tool customizable and extensible, in order to meet specific requirements?

Indicate which capabilities the Tool supports, by entering "Yes" or "No" as appropriate under "Response"; for each "Yes", provide the appropriate tool documentation reference(s).

 Customize information content and presentation of model artefacts Yes
 Customize metamodel (via usrprops) and customize images used. See help.
Add new model artefacts (definition types, symbol types, diagram types) Yes Customize metamodel textually via USRPROPS and/or graphically via the graphical metamodel editing capability. See help.
Extend the tool, for example by scripts (such as VBA macros, etc.)
Yes		 Support VBA and open API. See help.
Configure the repository to support an organisation's chosen methods and languages for modelling yes Customize Framework for portal view of architecture. Customize Guidebook for how-to methods. Insert custom help.
Other (please specify):


Non-English Language Support Does the tool have implementations in Languages other than English?

If so, enter the answer(s) under the "Response" column and give the appropriate Tool Documentation reference
Yes.		 SA is fully localized and supports, listed alphabetically, Chinese (Simplified), Chinese (Traditional), English, French, German, Japanese, Korean, Russian, and Spanish.




Rationale:

It is an advantage for a tool to include a shared repository to store and manage architecture artefacts, and
to enable their productive use throughout an organisation.

A tool participating in the TOGAF 8 TOOL SUPPORT certification program may optionally provide support for some or all of the functionality listed above. 

Reference:

Product Standard: TOGAF 8 TOOL SUPPORT

Copyright © 2003-2004 The Open Group. All Rights Reserved.