Part 1: Instructions

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

First, enter the name, and organization of the author of this completed Conformance Statement (the "Applicant"), along with the name and version of the tool to which this statement refers.  Please submit a separate conformance statement for each major tool version.

Identifying Information
Applicant Name Organization Tool Name and Major Version
 Martin Owen
Corso
Agile Enterprise Architecture (EA)

Then, review and complete Part 2: Conformance Requirements and Part 3: Recommended Capabilities below.

The second row under the heading is labeled "Explanation" In the right-hand column of each of these rows, please describe concisely:


Part 2: Conformance Requirements

For certification, a tool must fulfill all of the requirements as specified in the tables below.

2.1 Concept Coverage

2.1.1
A conforming product shall support all of the concepts defined in the ArchiMate specification Chapters 3, 4, and 5 (Core), Section 10.2 (Motivation extension), and section 11.2 (Implementation & Migration extension).
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  All concepts as per the requirement are full supported.
 All concepts in the core, motivation and implementation and migration extension are supported and provided.

2.2 Relationship Coverage

2.2.1 A conforming product shall allow the ArchiMate concepts to be connected by means of the relationships defined in the ArchiMate Specification Chapter 7 and section 10.3, according to the constraints in Appendix B.
Applicant Responses
Tool Conformance (Full, Partial, None)  Full
Explanation All associations as defined in chapter 7 and section 10.3 have been full implemented. 
All associations in the ArchiMate specification are supported and can be connected between ArchiMate concepts.

2.2.2 For each supported ArchiMate relationship as defined in requirement 2.2.1 above,  if the relationship applies to multiple combinations of ArchiMate concepts, the user of a conforming product shall be able to reuse the same relationship symbol and method to connect  each supported combination of concepts as denoted by their concept symbols.  For example, ArchiMate defines the association relationship for nearly all pairs of ArchiMate concepts.  However, the user of a conforming product shall be able to use a single line symbol to connect all pairs of concepts for which ArchiMate defines the association relationship.
Applicant Responses
Tool Conformance (Full, Partial, None)  Full 
Explanation Each association type can be used for multiple combinations of concepts.
A single line symbol can depict an association. It can be used wherever that association appears between two concepts of permitted types for that association.

2.3 Language Notation

2.3.1 A conforming product shall implement the vocabulary, notation, syntax and semantics of the visual modeling language described in Chapters 3-7, Chapters 10-11, and Appendix A of the ArchiMate Specification.
Applicant Responses
Tool Conformance (Full, Partial, None)  Full
Explanation Full vocabulary, notation, syntax and semantics of the ArchiMate Visual modeling language are implemented and used throughout the platform.

2.3.2 A conforming product shall support nesting as an alternative representation of relationship types as described in sections 7.1.1, 7.1.2 and 7.1.3 of the ArchiMate 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.
Applicant Responses
Tool Conformance (Full, Partial, None)  Full 
Explanation Any asssociation can be represented alternatively as a nested representation.
 Full nesting of any association type is supported.

2.3.3 A conforming product shall ensure that the graphical notation used for ArchiMate concepts and relationships remains unambiguously compliant with the ArchiMate Specification even after changes to the size, proportion, or color of modeling symbols.
Applicant Responses
Tool Conformance (Full, Partial, None)  Full 
Explanation The graphical notation is unambiguously consistent and compliant with the ArchiMate specification.
The graphical notation is fully supported and is kept throughout the platform whenever a concept is used. 

2.4 Viewpoint Support

2.4.1 A conforming product shall support all the viewpoints specified in sections 8.4, 10.5 and 11.5 of the ArchiMate Specification by predefining them or by enabling ordinary or specially privileged users to define them.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  All viewpoints are supported out of the box.   Users may construct their own viewpoints in addition to those specified in the ArchiMate specification.

2.4.2 A conforming product shall support design viewpoints both within and across ArchiMate layers and extensions, including a comprehensive viewpoint, in which all of the ArchiMate concepts and relationships are available.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  All viewpoints are supported including the Layered view. Users may create their own diagram types (Viewpoints) for any valid concept and association.

2.4.3 A conforming product shall reuse objects from a single underlying model in multiple views. Specifically, 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.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  Full reuse via a single repository is supported. The platform has a single concept (object) that is reused in multiple views. Making a change in the one concept will reflect in the other views.  Concepts may be viewed in multiple views. All concepts are consistently represented when changed.

2.4.4 A conforming product shall allow for different graphical notations for an object in different views.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  A concept can be represented in different notations in different views.  Different views may represent objects in different notations.

2.4.5 A conforming product shall track the occurrences of objects in different views
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation   An object can be seen in multiple diagrams (views). From a concept, you can track the views it appears in.    The platform allows the user to see the occurrences of concepts on viewpoints from within the concept.

2.5 Language Extension Mechanisms

2.5.1 A conforming product shall permit the users to add attributes to ArchiMate concepts and relationships  as described in section 9.1 of the ArchiMate Specification.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  All concepts can have attributes added to them by users.  In addition, users may create complex attributes that represent scorecards, associations and other data types.

2.5.2 A conforming product shall permit users to define specializations of ArchiMate concepts as described in section 9.2 of the ArchiMate Specification.
Applicant Responses
Tool Conformance (Full, Partial, None)  Full 
Explanation  The user can add additional meta types (concept types) to further extend the meta-model.    Users may create specializations and any other type of association for new meta types (concept types).

Part 3: Recommended Capabilities

3.1 Concept Coverage

3.1.1 A conforming product may optionally provide predefined specializations of the ArchiMate concepts according to section 9.2 of the ArchiMate Specification
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation   All specializations referred to in the ArchiMate specification are included out of the box.

3.1.2 A conforming product may optionally support concepts that are neither defined within ArchiMate nor are specializations of the ArchiMate concepts as long as they do not obstruct the use of ArchiMate.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  Users may create further meta types and associations that can be used in conjunction with ArchiMate meta types and associations.

3.2 Relationship Coverage

3.2.1 A conforming product may optionally provide predefined specializations of ArchiMate relationships according to section 9.2 of the ArchiMate Specification.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation Pre-defined specializations are provided of ArchiMate relationships as specified in section 9.2 of the ArchiMate specificaiton.

3.2.2 A conforming product may optionally support relationships that are not defined within the ArchiMate Specification as long as the product does not require the use of such relationships to develop an ArchiMate model.  
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation   Users may add in their own associations. However, full ArchiMate support is already provided.

3.3 Language Notation

3.3.1 A conforming product may optionally support alternative notations for the concepts and relationships described in the ArchiMate Specification.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation   Alternative notations/methods are also provided such as BPMN and Capability modeling.

3.4 Other Capabilities

3.4.1 If a conforming product supports modeling frameworks and languages other than ArchiMate, it may optionally provide the same capabilities for ArchiMate as it does for the other supported modeling frameworks and languages.
Applicant Responses
Tool Conformance (Full, Partial, None)   Full
Explanation  TOGAF 9 attributes are provided as described in the TOGAF/ArchiMate harmonization work from the Open Group.  Other capabilities such as BPMN hiearchy capability can be used within the ArchiMate language.

 

4 Revision History

Revision Date of Completion Reason for Revision
1.0 January 2012 Initial version of the  ArchiMate 2 Tool CSQ