Master ArchiMate 3.2 Specification - Ontology and Modeling

Description

This course intends to bring step-by-step explanation and demo on the ArchiMate 3.2 specification and building up the ontology knowledgebase for meta-model in detail. Also, provide hands-on Archi modeling practice on every ArchiMate layers and aspects. Now matter your role is enterprise architect or any other types of architects, or non-architects, you'll learn from this course a holistic view on Enterprise Architecture modeling, after all, remember - the scope of Enterprise Architecture is the Enterprise!

The ArchiMate® Specification, a standard of The Open Group, defines an open and independent modeling language for Enterprise Architecture that is supported by different tool vendors and consulting firms. The ArchiMate language enables Enterprise Architects to describe, analyze, and visualize the relationships among business domains in an unambiguous way.

This is the official specification of the ArchiMate 3.2 modeling language from The Open Group.

You can find the source ontology and ArchiMate model in github repository: yasenstar/ArchiMate_Ontology .

Throughout the course, you're learning from the demo and able to practice multiple tools - Protege (Opensource Ontology Editor), Archi (Opensource ArchiMate Modeling Tool) and FreePlane (Opensource Mindmap Tool) - be prepare to do those from your hands at the same time.

Enjoy!

The main changes between Version 3.1 and Version 3.2 of the ArchiMate Specification are listed below. In addition to these changes, various other minor improvements in definitions, explanations, and examples have been made.

• Improved the definitions of several concepts, most notably outcome, constraint, business function, and product

• Made the Physical elements part of the Technology Layer chapter instead of a separate chapter

• Changed the Technology Layer metamodel, making device, system software, facility, and equipment no longer subtypes of node but of technology internal active structure element, and adding composition and aggregation relationships with node

• Added composition and aggregation relationships from plateau to outcome

• Added realization from material to equipment

• Improved the restrictions on derivation rules described in Section B.3.5

• Added a derivation rule for grouping

• Changed the icon notation of the meaning and communication network elements, added an icon notation for work package, and added new box notations for meaning, value, business object, contract, representation, work package, and deliverable

• Changed the default color of the plateau and gap elements to the same pink as the other Implementation and Migration elements

Course Info