ArchiMate 3 Tool Certification Checklist - The Open Group · Web viewThe assessor will use the...

The Open Group® Architecture Tool Certification

ArchiMate® 3 Tool Certification Checklist

February 2017Version 1.01

© Copyright 2017, The Open Group. All rights reserved

1 IntroductionThis document is completed by the applicant who is submitting a tool supporting the ArchiMate® 3 Specification for certification.

This document is used in conjunction with the ArchiMate 3 Conformance Requirements for The Open Group Architecture Tool Certification program. This document provides a mapping between the supporting evidence supplied with a certification submission and the conformance requirements. The assessor will use the completed checklist to perform the assessment phase of the certification process in order to determine whether the Architecture Tool meets the Conformance Requirements.

The applicant is required to submit a full set of evidence that collectively illustrates that each of the requirements listed in the Checklist has been implemented, and that the tool supports the applicable conformance requirements.

The applicant has some latitude as to how to meet the documentation submission requirements as the exact form and number of documents will vary between applicants. However, the format of this document should not be changed and all mandatory parts must be completed.

Regardless of the application used to populate it, this document must be submitted in a format that can be edited by the assessor. Microsoft Word, iWork Pages, and Open Office are acceptable formats. Alternate formats may be used only with approval from the assessor.

1.1 Tool InformationProvide information on the tool supplier and the architecture tool to be accredited.

Organization Name

Architecture Tool Name

1.2 Applicant Document SubmissionFor each document submitted for the assessment, enter the name of the document in the “Document Title” column. The “Document Reference” is a short, unique identifier you assign to the document to enable shorthand references to the document in the tables that follow. Where possible this identifier should relate easily to filenames uploaded. You may optionally enter any relevant comment concerning the document in the “Comment” column.

Completed by

Date

Document Title Document Reference Comment

The Open Group® Architecture Tool Certification: ArchiMate® 3 Tool Certification Checklist 2

1.3 Checklist InstructionsWhen you complete an entry in the table, use the value in “Document Reference” column from Section 1.1 above in the “Document in which evidence is found” column in the checklist. Enter the section number, elapsed time in the video evidence or location within the document in the “Reference within document” column so the assessor may easily identify where and how the conformance requirement is supported in the architecture tool. Failure to do so may result in this checklist being rejected and thus having to be revised and re-submitted.

1.4 Key to the Conformance Requirements Mapping ReferencesThe Conformance Requirements document upon which this checklist is based is The Open Group® Architecture Tool Certification: ArchiMate® 3 Conformance Requirements, Version 1.0 (Document X1701), published February 2017.

1.5 Key to the ChecklistItem DescriptionReference The name of the reference within the Conformance Requirements

document and a section number. This also contains an assigned reference number for the checklist, e.g. M1 is the first mandatory set of requirements, and a section reference (in parentheses) back to the conformance requirements.

Conformance Requirement The detailed conformance requirementDocument in which evidence is found

Insert the short-form document name (e.g., “Document Reference” from Section 1.2) as a reference to where the conformance requirement is covered in your submitted evidence.

Reference within document Insert the section number in the document that addresses the requirement. You could also reference slide numbers, section numbers, or elapsed time in a video. Do not use page numbers as these may not stay the same when the assessor is viewing your document.

Other pertinent information Additional information that will demonstrate that the conformance requirement is covered by your tool. You could insert verbatim text here if it is brief. The use of this column is optional.

Applicant Comment Anything else you would like the assessor to know, and that might move forward the assessment process. The use of the column is optional.

Assessor Comment As stated, for official use only and not for completion by the applicant.


2 Summary of Evidence SubmittedThis section summarizes the evidence submitted. Sections 2 and 3 document the evidence for the detailed conformance requirements.

Reference Conformance Requirement

Submitted (Yes/No)

Document in which evidence is found

Reference within document

Other pertinent information(e.g., text extract) Applicant Comment

Assessor Comment (Leave blank - for official use only)

Evidence of Compliance (3.1)

The evidence that shall be provided is: A set of reference views

according to the requirements defined in Sections 2.1.1, 2.1.2, and 2.1.3 of The Open Group Architecture Tool Certification: ArchiMate® 3 Conformance Requirements. The set of reference views should be the ones detailed as reference information in Appendix C (Example Viewpoints) of the ArchiMate 3.0 Specification.

Evidence of compliance with Section 2.1.4 of the Conformance Requirements document regarding the viewpoint mechanism.

• Evidence of compliance with Section 2.1.5 of the Conformance Requirement document regarding Exchange File Format support.

Evidence for Additional Options (3.2)

The evidence that shall be provided is: Evidence of compliance with

Section 2.2.1 of the Conformance Requirements document regarding language and relationship customization.



Submitted (Yes/No)





• Evidence of compliance with Section 2.2.2 of the Conformance Requirements document regarding viewpoint support.

• Evidence of compliance with the other features detailed in Sections 2.2.3 to 2.2.6 of the Conformance Requirements document.

Mechanisms to Provide the Compliance Evidence (3.3)

Applicants shall provide evidence as follows:

• The set of reference views (evidence of compliance with Section 3.1 and 3.2 of the Conformance Requirements document) exported in the ArchiMate 3.0 Model Exchange File Format (when available)

• Evidence of successful import from a set of ArchiMate 3.0 Model Exchange File Format reference models (when available)

• Evidence of successful import from and export to two other tools in the ArchiMate 3.0 Model Exchange File Format (when available)

In addition, one of the following:• A recorded live demo

demonstrating how the tool complies (mp4 format or similar)

• • A printed version of the models (pdf format)


3 ArchiMate® 3 Tool Checklist: Mandatory Requirements Complete the checklist below to assert where each Conformance Requirement is addressed in your submitted supporting evidence.






M1. Concept Coverage (2.1.1)

1. A conforming product shall support all of the concepts defined in Chapter 2 of

the ArchiMate 3.0 Specification.























10. A conforming product shall support all of the concepts defined in Chapter 11

of the ArchiMate 3.0 Specification.





13. A conforming product shall support all of the concepts defined in Chapter14


M2. Language Element Support – Language Element Coverage (2.1.2)

1. A conforming product shall support all ArchiMate language elements as defined generically in Chapter 4 (Generic Metamodel) of the ArchiMate 3.0 Specification







2. A conforming product shall support all language elements as defined in Chapter 6 (Motivation Elements) of the ArchiMate 3.0 Specification.

3. A conforming product shall support all language elements as defined in Chapter 7 (Strategy Elements) of the ArchiMate 3.0 Specification.

4. A conforming product shall support all language elements as defined in Chapter 8 (Business Layer) of the ArchiMate 3.0 Specification.

5. A conforming product shall support all language elements as defined in Chapter 9 (Application Layer) of the ArchiMate 3.0 Specification.

6. A conforming product shall support all language elements as defined in Chapter 10 (Technology Layer) of the ArchiMate 3.0 Specification.

7. A conforming product shall support all language elements as defined in Chapter 11 (Physical Elements) of the ArchiMate 3.0 Specification.

8. A conforming product shall support all language elements as defined in Chapter 13 (Implementation and Migration Elements) of the ArchiMate 3.0 Specification.







M3. Language Element Support – Language Element Notation (2.1.2)

1. A conforming product shall implement the vocabulary, notation, syntax, and semantics of the visual modeling language for all ArchiMate language elements using the symbols defined in Section A.1 (Core Elements) and Section A.2 (Motivation, Strategy, Implementation and Migration Elements) of the ArchiMate 3.0 Specification.

2. A conforming product shall support nesting as an alternative representation of relationship types as described in Section 3.8 (Use of Nesting) of the ArchiMate 3.0 Specification. The conforming product shall clearly indicate which relationships are defined by each nesting instance and, in updatable views, shall enable user control of relationships to be created, modified, or deleted.

3. A conforming product shall ensure that the graphical notation used for ArchiMate concepts and relationships remains unambiguously compliant with the ArchiMate 3.0 Specification even after changes to the size, proportion, or color of modeling symbols.

M4. Relationship Support – Relationship Coverage (2.1.3)

1. A conforming product shall support all ArchiMate language relationships, as defined in Chapter 5 (Relationships) and Appendix B (Relationship Tables) of the ArchiMate 3.0 Specification.

2. A conforming product shall support relationships between two language elements, and in some cases relationships to other relationships







M5. Relationship Support – Relationship Notation (2.1.3)

1. A conforming product shall enable notation of all ArchiMate relationships using the symbols defined in Chapter 5 (Relationships) of the ArchiMate 3.0 Specification.

2. A conforming product shall enable notation of all ArchiMate structural relationships via nesting as defined in Section 5.1 (Structural Relationships) of the ArchiMate 3.0 Specification.

M6. Relationship Support – Relationship Symbol Reuse (2.1.3)

1. For each supported ArchiMate relationship, if the relationship applies to multiple combinations of ArchiMate language elements, the user of each conforming product shall be able to reuse the same relationship symbol to connect each supported combination of concepts as denoted by their concept symbols. For example, the ArchiMate language allows the association relationship between all pairs of elements. However, the user of each conforming product shall be able to use a single symbol, in this case a plain line, to connect all pairs of ArchiMate language elements that share an association relationship.

M7. Viewpoint Support (2.1.4)

1. Each conforming product shall support the mechanism described in Section 14.4 (Viewpoint Mechanism) of the ArchiMate 3.0 Specification.

2.Each conforming product shall enable users to create model views using any combination of new elements and relationships and those that may already exist within the model.







3. Each conforming product shall provide a comprehensive viewpoint with all standard language elements and relationship types.

4. Each view shall be based on a particular viewpoint that serves as a template for the view.

5. Each view may contain only the language element and relationship types specified in the definition of its viewpoint.

6. Each conforming product shall enable users to present ArchiMate elements and relationships from a single underlying model in multiple views, or in multiple instances in the same view. Therefore, any changes to the content of one view shall be reflected throughout all views of the same model that share any added, changed, or deleted ArchiMate elements and relationships. This means that any changes to objects, object properties, or relationships in one view shall be reflected in all views that present the changed objects, object properties, or relationships.

7. Each conforming product shall enable users to use different scaling or coloration for multiple representations of any single element or relationship in a single view or in multiple views.

8. A conforming product shall track the occurrences of objects in different views.

9. A conforming product shall allow for different graphical notations for an object in different views.







M8. Exchange File Format Support (2.1.5)

1. Each conforming product shall support the ArchiMate 3.0 Model Exchange File Format, an Open Group Standard, when available, and be able to export and import models.

NA NA NA NA


4 ArchiMate® 3 Tool Checklist: Optional Requirements Complete the checklist below to assert where each Conformance Requirement is addressed in your submitted supporting evidence.


Supported (Yes/No)





O1. Language Element Customization (2.2.1.1)

1. A conforming product may support customization of ArchiMate language element symbols with arbitrary scaling and coloration of all standard symbols without distortion. In other words, each conforming product shall ensure that the graphical notation used for ArchiMate concepts remains clearly recognizable to individuals familiar with the language even after changes to the size, proportion, or color of modeling symbols.

2. If a tool supports language element customization, it should support customization of language elements as defined in Chapter 15 (Language Customization Mechanisms) of the ArchiMate 3.0 Specification, including the definition of specialized elements that inherit the characteristics of standard elements



Supported (Yes/No)





3. If a tool supports language element customization, it may support:

• Custom names, as defined in the Specialized Content column of the tables in Section 15.2.1 (Examples of Specializations of Business Layer Elements (Informative)) through Section 15.2.8 (Examples of Specializations of Composite Elements (Informative)) of the ArchiMate 3.0 Specification


• Custom stereotypes, as defined in Section 15.2 (Specialization of Elements and Relationships) of the ArchiMate 3.0 Specification


• Custom attribute profiles


• Custom symbols


• Custom default coloration



Supported (Yes/No)





O2. Relationship Customization (2.2.1.2)

1. A conforming product may support arbitrary scaling and coloration of all ArchiMate language relationship symbols without distortion. In other words, each conforming product shall ensure that the graphical notation used for ArchiMate relationships remains clearly recognizable to individuals familiar with the language even after changes to the size, proportion, or color of modeling symbols.

2. If a tool supports relationship customization, it should support customization of relationship elements as defined in Chapter 15 (Language Customization Mechanisms) of the ArchiMate 3.0 Specification, including the definition of specialized relationships that inherit the characteristics of standard relationships

3. If a tool supports relationship customization, it may support:

• Custom names, as defined in the Specialized Content column of the table in Section 15.2.9 (Examples of Specializations of Relationships (Informative)) of the ArchiMate 3.0 Specification


• Custom attribute profiles


• Custom symbols



Supported (Yes/No)






• Custom default coloration

O3. Viewpoint Support (2.2.2)

1. If a tool supports language element and relationship customization, it may enable users to define and name custom viewpoints consisting of any combination of standard elements and relationships along with any combination of custom elements and relationships developed using the mechanisms described in Sections 2.2.1.1 and 2.2.1.2 of the conformance requirements.

O4. Concept Coverage (2.2.3)

1. A conforming product may provide predefined specializations of the ArchiMate concepts according to Chapter 15 (Language Customization Mechanisms) of the ArchiMate 3.0 Specification.

2. A conforming product may support concepts that are neither defined within the ArchiMate language nor are specializations of the ArchiMate concepts, as long as they do not obstruct use of the ArchiMate language.

O5. Relationship Coverage (2.2.4)

1. A conforming product may provide predefined specializations of ArchiMate relationships according to Section 15.2 (Specialization of Elements and Relationships) of the ArchiMate 3.0 Specification.



Supported (Yes/No)





2. A conforming product may optionally support relationships that are not defined within the ArchiMate language, as long as the product does not require the use of such relationships to develop an ArchiMate model.

O6. Language Notation (2.2.5)

1. A conforming product may support alternative notations for ArchiMate concepts and relationships other than those described by the ArchiMate 3.0 Specification.

O7. Other Capabilities (2.2.6)

1. If a conforming product supports modeling frameworks and languages other than the ArchiMate language, it may optionally provide the same capabilities for the ArchiMate language as it does for the other supported modeling frameworks and languages.


ArchiMate 3 Tool Certification Checklist - The Open Group · Web viewThe assessor will use the...

Documents

Transcript of ArchiMate 3 Tool Certification Checklist - The Open Group · Web viewThe assessor will use the...