Analytical model

The analytical model is used to describe the services, systems and technologies that are used to provide the services. The model can be built in multiple layers as needed. It is used both for internal documentation and – especially in conjunction with requirements – to create specifications during development and change.

The analytical model corresponds in its object structure and internal logic to the ArchiMate analytical language. To work with the analytical model, we recommend that you familiarize yourself with the language at least briefly (there are many free materials on web).

Why model in ArchiMate?

The ArchiMate language was invented so that even complex products, systems, services can be described clearly. It defines a few basic objects that are needed for this and thus divides the analysis into parts that are understandable not only to forged analysts, but basically to everyone.

The analytical model in AyMINE allows you to describe in detail the purpose, behaviour, features and functions of departments and systems and thus maintain the information for internal improvements, organizational changes, audits and specifying modification requirements.

Why model in ArchiMate?

The ArchiMate language was invented so that even complex products, systems, services can be described clearly. It defines a few basic objects that are needed to do this and thus divides the analysis into parts that are understandable not only to forged analysts, but basically to everyone.

The analytical model in AyMINE allows you to describe in detail the purpose, behaviour, features and functions of departments and systems and thus maintain the information for internal improvements, organizational changes, audits and specifying modification requirements.

What are language objects?

The basic objects are:

• Product describes exactly what you envision-something that a company or organization provides to others. A product might be a bank account, but it might also be a welfare benefit, roof insulation, a car, etc.
• Service is something that someone provides to someone else. A system provides a service to users, a school to students, an office to citizens. Products are made up of a set of services, so services describe in more detail what the product actually is,
• Module is a unit that internally can perform functions and externally provides services. At the business level, a module is, for example, a human resources department that internally provides employee care services.
• Role is closer to the role of an employee. In practice, we need many more so-called process roles – e.g. invoice approver
• Location expresses where other objects are. A location is e.g. a company's website
• Rule describes how work is done and in particular what decisions are made. A typical rule is how the price of a contract is calculated
  A * Scenario describes how the implementation of a product or provision of a service is carried out. It is closer to a process, but is more general, and may describe disparate (i.e., not just process steps) procedures.
• Object contains the information that is being worked with. Examples are an order, a product in stock, etc.
• Actor is a person who does or wants something.
• Interface the place where information is passed and services are provided. A typical interface is a website.
• Function is the internal functionality of modules, i.e. what they actually do. They can describe not only system functions but also the work of people.
• Output is typically the information that is transmitted – e.g. an email order. But the output can also be physical (an insulated roof).
• Object is a slightly different object. Its purpose is to describe why the objects in question are and do what they do. For example, the purpose of an order taking module on a website is to contact customers and get orders.

Note:
ArchiMate was defined by OMG and the name is their trademark