Why Learning ArchiMate?

A picture is worth a thousand words. If you want to draw, then the right design tools are necessary to create great pictures.

In the software design discipline, our common design tool is "UML" diagram, including use case diagram, class diagram, object graph, state diagram, activity diagram, sequence diagram, collaboration diagram, component diagram, deployment diagram. But the "UML" diagram is a fine grained design, usually describing a system's internal design, not suitable for architectural design, which usually need to care about coarse-grained design, that is, the relationship between the system and the system, and not care about the relationship within the system.

ArchiMate is usually used to solve architecture design. Tt is good at describing the various relationships between systems and components.

What is ArchiMate?

The ArchiMate language provides a graphical representation of the description of the enterprise architecture. ArchiMate has the time dimension so that it can model the transformations and migrations involved in the evolution of the enterprise over time. As an enterprise architecture modeling language, the scope described by ArchiMate needs to cover all areas of the enterprise and can reflect the concerns of stakeholders, so the ArchiMate has the following characteristics compared with the specialized modeling language in various fields:

1. ArchiMate can span all areas of the enterprise, including at least the business, application, data, and technology infrastructure dimensions.
2. ArchiMate not only describes various areas of the enterprise, but also associates these areas, enabling stakeholders to obtain a complete and complete enterprise model, which is an important foundation for business and it alignment (business-it alignment).
3. Because it is an enterprise architecture Modeling Language, ArchiMate describes the level of abstraction and description granularity that should be global, so the description cannot be as detailed as a dedicated modeling language in each domain. However, in practice, ArchiMate can also extend the description granularity and abstraction of ArchiMate based on the extended rules, thus obtaining an enterprise architecture that provides multiple levels of abstraction and granularity for stakeholders.
4. While ArchiMate can be used to describe a complete and complete enterprise architecture, it is too complicated for a particular stakeholder to have such a large and all-encompassing enterprise model. Since each stakeholder has his or her own concerns and interests, it is often a matter of one aspect of the enterprise model, and in order for the stakeholders to gain the side of the enterprise model that reflects their concerns, ArchiMate the creation and use of enterprise models by customizing various typical perspectives and views.

ArchiMate can do the work

Architecture design to face different stakeholders, mainly the following stakeholders:

1. Customer
2. Demand Analyst
3. Detailed design staff
4. Developers
5. Implementation and operation of personnel
6. Leadership

ArchiMate uses different model domains to confront these stakeholders:

1. Business Domain Model
• This domain model is primarily for customers and requirements analysts.
• Includes models for three aspects of structural elements, behavior elements, and information elements.
2. Application domain Model
• This domain model is primarily intended for detailed designers and developers.
• Includes structure elements and behavior elements.
3. Physical Domain Model
• This domain model, mainly for the implementation and operation of the personnel.
• It is mainly used to describe the physical architecture, network architecture, operation architecture, etc.
4. Resource target domain model
• This area focuses on leadership.
• It is mainly used to describe the resources required by the project, the goals achieved, the plans formulated, etc.
• Through the design of these areas, ArchiMate will involve all aspects of architectural design. Like what
5. Conceptual framework and overall framework
6. logical architecture
7. Application architecture
8. Data architecture
9. Physical structure
10. Security architecture
11. Network architecture
12. Run the architecture
13. Development framework
14. Ha high-availability architecture
15. Expand the architecture
16. Performance architecture
17. Constraints