Archimate Meta Model

 What is ArchiMate?
◦ A Research initiative that aims to provide concepts and techniques
to support enterprise architects in the visualization, analysis and
communication of integrated enterprise architectures.

High-level ArchiMate language
modelling
within a
domain Basis for visualisations

Modelling relations
Basis for analyses
between domains

Object Generic concepts
more specific
more generic

Relation

Enterprise
Application Process
architecture concepts

Company-specific
concepts, standards

 The language consists of active structure
elements, behavioural elements and passive
structure elements.
◦ The active structure elements are the business
actors, application components and devices that
display actual behaviour, i.e., the „subjects‟ of
activity
◦ Then there is the behavioural or dynamic aspect.
◦ The active structure concepts are assigned to
behavioural concepts, to show who or what
performs the behaviour.
◦ The passive structure elements are the objects on
which behaviour is performed.

 The distinguishing factor between behaviour that is performed by a single
structure element (e.g., actor, role component, etc.), or collective behaviour
(interaction) that is performed by a collaboration of multiple structure
elements.
 A collaboration is a (temporary) grouping (or aggregation) of two or more
structure elements, working together to perform some collective behavior.
This collective behavior can be modeled as an interaction.

1. The Business Layer offers products and services to external customers, which
are realized in the organization by business processes performed by business
actors.
2. The Application Layer supports the business layer with application services
which are realized by (software) applications.
3. The Technology Layer offers infrastructure services (e.g., processing, storage,
and communication services) needed to run applications, realized by computer
and communication hardware and system software.

 A business actor is defined as an organizational
entity capable of (actively) performing behaviour.
 Examples of business actors are humans, departments, and
business units.
 A business actor may be assigned to one or more business
roles. The name of a business actor should preferably be a
noun.

 A business role is defined as a named specific
behaviour of a business actor participating in a
particular context.
 Business processes or business functions are assigned to a
single business role with certain responsibilities or skills.
 A business actor that is assigned to a business role ultimately
performs the corresponding behaviour.
 In addition to the relation of a business role with behaviour, a
business role is also useful in a (structural) organizational
sense; for instance, in the division of labour within an
organisation.

 Business collaboration is defined as a (temporary)
configuration of two or more business roles
resulting in specific collective behaviour in a
particular context.
 A business process or function may be interpreted as the
internal behaviour assigned to a single business role.
 In some cases behaviour is the collective effort of more than
one business role; in fact a collaboration of two or more
business roles results in collective behaviour which may be
more than simply the sum of the behaviour of the separate
roles.
 Business collaborations represent this collective effort.

 A business interface declares how a business role
can connect with its environment.
 A business interface specifies how the functionality of a
business role can be used by other business roles (provided
interface), or which functionality the business roles requires
from its environment (required interface).
 A business interface exposes a business service to the
environment.
 The same business service may be exposed through different
interfaces.

 A business object is defined as a unit of
information that has relevance from a business
perspective
 Business objects represent the important “informational” or
“conceptual” elements in which the business thinks about a
domain.
 Generally, a business object is used to model an object type
(cf. a UML class), of which several instances may exist within
the organization.
 A wide variety of types of business objects can be defined.
 Business objects are passive in the sense that they do not
trigger or perform processes

Business Layer Metamodel
Behavioural Concepts

 A business process is defined as a unit of internal
behaviour or collection of causally-related units of
internal behaviour intended to produce a defined
set of products and services.
 A business process describes the internal behaviour
performed by a business role that is required to produce a set
of products and services.
 For a consumer the products and services are relevant and the
required behaviour is merely a black box, hence the
designation “internal”.

 A business function is defined as a unit of internal
behaviour that groups behaviour according to, for
example, required skills, knowledge, resources,
etc., and is performed by a single role within the
organization.
 A business function describes internal behaviour performed
by a business role that is required to produce a set of
products and services.
 For a consumer, the products and services are relevant and
the required behaviour is merely a black box, hence the
designation “internal”.

 Business interaction is defined as a unit of
behaviour performed as a collaboration of two or
more business roles.
 A business interaction is similar to a business
process/function, but while a process/function may be
performed by a single role, an interaction is performed by
multiple roles in collaboration.

 A business event is defined as something that
happens (internally or externally) and influences
behaviour (business process, business function,
business interaction).
 Business processes and other business behaviour may be
triggered or interrupted by a business event.
 Also, business processes may raise events that trigger other
business processes, functions, or interactions.
 A business event is most commonly used to model something
that triggers behaviour, but other types of events are also
conceivable; e.g., an event that interrupts a process.

 A business service is defined as the externally visible (“logical”)
functionality, which is meaningful to the environment and is realized
by business behaviour (business process, business function, or
business interaction).
 A business service exposes the functionality of business roles or
collaborations to their environment.
 This functionality is accessed through one or more business interfaces.
 A business service is realized by one or more business processes,
business functions, or business interactions that are performed by the
business roles or business collaborations, respectively.
 It may access business objects.

Business Layer Metamodel
Informational Concepts

 Representation is defined as the perceptible form of the information
carried by a business object.
 Representations (for example, messages or documents) are the
perceptible carriers of information that are related to business objects.
 If relevant, representations can be classified in various ways; for
example, in terms of medium (electronic, paper, audio, etc.) or format
(HTML, ASCII, PFD, RTF, etc.).
 A single business object can have a number of different representations,
but a representation always belongs to one specific business object.
 The name of a representation is preferably a noun.

 Meaning is defined as the knowledge or expertise present in the
representation of a business object, given a particular context.
 A meaning is the representation-related counterpart of a value: it
represents the functionality of a representation (for example, a
document, message; the representations related to a business object). It
is a description that expresses the intent of a representation; i.e., how it
informs the external user.
 A meaning can be associated with a representation that carries this
meaning.
 The name of a meaning should preferably be a noun or noun phrase.

 Value is defined as that which makes some party appreciate a service
or product, possibly in relation to providing it, but more typically to
acquiring it.
 Value may apply to what a party gets by selling or making available
some product or service, or it may apply to what a party gets by buying
or obtaining access to it.
 Value is often expressed in terms of money, but it has long since been
recognized that non-monetary value is also essential to business; for
example, practical/functional value (including the right to use a service),
and the value of information or knowledge.
 Though value can hold internally for some system or organizational
unit, it is most typically applied to external appreciation of goods,
services, information, knowledge, or money, normally as part of some
sort of customer-provider relationship.

 A product is defined as a coherent collection of services,
accompanied by a contract/set of agreements, which is offered as a
whole to (internal or external) customers.
 A (financial or information) product consists of a collection of services,
and a contract that specifies the characteristics, rights, and
requirements associated with the product.
 “Buying” a product gives the customer the right to use the associated
services.
 Generally, the product concept is used to specify a product type.
 The number of product types in an organization is typically relatively
stable compared to, for example, the processes that realize or support
the products.
 “Buying” is usually one of the services associated with a product, which
results in a new instance of that product (belonging to a specific
customer).

 A contract is defined as a formal or informal specification of an
agreement that specifies the rights and obligations associated with a
product.
 The contract concept may be used to model a contract in the legal
sense, but also a more informal agreement associated with a product.
 It may also be or include a Service Level Agreement (SLA), describing an
agreement about the functionality and quality of the services that are
part of a product.
 A contract is a specialization of a business object.

Structural
Concept Definition Notation
Business Actor An organizational entity that is capable of performing
behaviour.

Business Role A named specific behaviour of a business actor participating in
a particular context.

Business Collaboration A (temporary) configuration of two or more business roles
resulting in specific collective behaviour in a particular context.

Business Interface Declares how a business role can connect with its environment.

Business Object A unit of information that has relevance from a business
perspective.

Behavioural
Business Process A unit of internal behaviour or collection of causally related
units of internal behaviour intended to produce a defined set of
products and services.
Business Function A unit of internal behaviour that groups behaviour according to,
for example, required skills, knowledge, resources, etc., and is
performed by a single role within the organization.
Business Interaction A unit of behaviour performed as a collaboration of two or
more business roles.

Business Event Something that happens (internally or externally) and
influences behaviour.

Business Service An externally visible unit of functionality, which is meaningful
to the environment and is provided by a business role.

Informational
Representation The perceptible form of the information carried by a business
object.

Meaning The knowledge or expertise present in the representation of a
business object, given a particular context.

Value That which makes some party appreciate a service or product,
possibly in relation to providing it, but more typically to
acquiring it.
Product A coherent collection of services, accompanied by a
contract/set of agreements, which is offered as a whole to
(internal or external) customers.
Contract A formal or informal specification of agreement that specifies
the rights and obligations associated with a product.

Application Layer Metamodel
Structural Concepts

 The main structural concept for the application layer is the
application component.
 The Component Concept strictly models the structural aspect of an
application: its behaviour is modelled by an explicit relationship to
the behavioural concepts.
 Application collaboration, is defined as a collective of application
components which perform application interactions
 An application interface is the (logical) channel through which the
services of a component can be accessed
 The data object concept is used in the same way as data objects (or
object types) in well known data modelling approaches

 An application component is defined as a modular, deployable, and
replaceable part of a system that encapsulates its contents and
exposes its functionality through a set of interfaces.
 An application component is a self-contained unit of functionality.
 As such, it is independently deployable, re-usable, and replaceable.
 An application component performs one or more application functions.
It encapsulates its contents: its functionality is only accessible through a
set of application interfaces.
 Co-operating application components are connected via application
collaborations.
 The name of an application component should preferably be a noun.

 Application collaboration is defined as a (temporary) configuration of
two or more components that co-operate to jointly perform
application interactions.
 An application collaboration specifies which components (have to) co-
operate to perform some task.
 The collaborative behaviour, including, for example, the communication
pattern of these components, is modelled by an application interaction.
 The name of an application collaboration should preferably be a noun.

 An application interface declares how a component can connect with
its environment.
 An application interface specifies how the functionality of a component
can be accessed by other components (provided interface), or which
functionality the component requires from its environment (required
interface).
 An application interface exposes an application service to the
environment.
 The same application service may be exposed through different
interfaces.
 The name of an application interface should preferably be a Noun.

 A data object is defined as a coherent, self-contained piece of
information suitable for automated processing.
 An application function operates on a data object. A data object may be
communicated via interactions and used or produced by application
services.
 It should be a useful, self-contained piece of information with a clear
meaning to the business, not just to the application level.
 Typical examples of data objects are a customer record, a client
database, or an insurance claim.
 The name of a data object should preferably be a noun.

Application Layer Metamodel

 There is a distinction between the external behaviour of application
components in terms of application services, and the internal
behaviour of these components
 An application service is an externally visible unit of functionality,
provided by one or more components, exposed through well-defined
interfaces, and meaningful to the environment.
 An application function describes the internal behaviour of a
component needed to realize one or more application services.
 An application interaction is the behaviour of a collaboration of two
or more application components.

 An application function is defined as a representation of a coherent
group of internal behaviour of an application component.
 An application function describes the internal behaviour of a
component; for the user of a component that performs an application
function, this function is invisible.
 If its behaviour is exposed externally, this is done through one or more
services. An application function abstracts from the way it is
implemented.
 Only the necessary behaviour is specified.
 The name of an application function should preferably be a verb ending
with “-ing”; e.g., “accounting”.

 Application interaction is defined as a unit of behaviour performed
by a collaboration of two or more components.
 An application interaction describes the externally visible behaviour that
is performed by components that participate in an application
collaboration.
 This may, for example, include the communication pattern between
these components.
 An application interaction can also specify the externally visible
behaviour needed to realize an application service.
 The name of an application interaction should preferably be a verb.

 An application service is defined as an externally visible unit of
functionality, provided by one or more components, exposed
through well-defined interfaces, and meaningful to the environment.
 An application service exposes the functionality of components to their
environment.
 This functionality is accessed through one or more application
interfaces.
 An application service is realized by one or more application functions
that are performed by the component.
 It may require, use, and produce data objects.
 The name of an application service should preferably be a verb ending
with “-ing”; e.g., “transaction processing”. Also, a name explicitly
containing the word “service” may be used.

Structural
Application Component A modular, deployable, and replaceable part of a system that
encapsulates its contents and exposes its functionality through
a set of interfaces
Application Collaboration An application collaboration defines a (temporary) configuration
of two or more components that co-operate to jointly perform
application interactions.
Application Interface An application interface declares how a component can connect
with its environment.

Data Object A coherent, self-contained piece of information suitable for
automated processing.

Behavioural
Application Function A coherent group of internal behaviour of a component.

Application Interaction A unit of behaviour jointly performed by two or more
collaborating components.

Application Service An externally visible unit of functionality, provided by one or
more components, exposed through well-defined interfaces,
and meaningful to the environment.

Technology Layer Metamodel
Structural Concepts

 The main structural concept for the technology layer is the
node.
 An infrastructure interface is the (logical) location where the
infrastructure services offered by a node can be accessed by
other nodes or by application components from the
application layer.
 Nodes come in two flavours: device and system software.
 A device models a physical computational resource, upon
which artifacts may be deployed for execution.
 System software is classified as a behavioural concept, since
it defines what a device “does”.
 The communication path models the relation between two or
more nodes, through which these nodes can exchange
information.

 A node is defined as a computational resource upon which artifacts
may be deployed for execution.
 Nodes are active processing elements that execute and process artifacts,
which are the representation of components and data objects.
 Nodes are, for example, used to model application servers, database
servers, or client workstations.
 They can consist of sub-nodes representing physical devices and
execution environments for artifacts.
 Nodes can be interconnected by communication paths. Artifacts can be
assigned to (i.e., deployed on) nodes.
 The name of a node should preferably be a noun. A node can consist of
sub-nodes.

 A device is defined as a physical computational resource upon which
artifacts may be deployed for execution.
 A device is a specialization of a node that represents a physical resource with
processing capability.
 It is typically used to model hardware systems such as mainframes, PCs, or
routers.
 Usually, they are part of a node together with system software. Devices may be
composite; i.e., consist of sub-devices.
 Devices can be interconnected by networks. Artifacts can be assigned to (i.e.,
deployed on) devices.
 System software can be assigned to a device. A node can contain one or more
devices.
 The name of a device should preferably be a noun referring to the type of
hardware; e.g., “IBM System z mainframe”.
 A device can consist of sub-devices.

 An infrastructure interface is defined as a point of access where the
functionality offered by a node can be accessed by other nodes and
application components.
 An infrastructure interface specifies how the infrastructure services of a node can
be accessed by other nodes (provided interface), or which functionality the node
requires from its environment (required interface).
 An infrastructure interface exposes an infrastructure service to the environment.
 The same service may be exposed through different interfaces.
 An infrastructure interface may be part of a node through composition (not
shown in the standard notation), which means that these interfaces are provided
or required by that node, and can be used by other nodes.
 An infrastructure service can be assigned to an infrastructure interface, which
exposes the service to the environment.
 The name of an infrastructure interface should preferably be a noun.

 A network is defined as a physical communication medium between two or
more devices.
 A network represents the physical communication infrastructure. This may
comprise one or more fixed or wireless network links.
 The most basic network is a single link between two devices.
 A network has properties such as bandwidth and latency.
 It embodies the physical realization of the logical communication paths between
nodes.
 A network connects two or more devices.
 A network realizes one or more communication paths.
 A network can consist of sub-networks.

 A communication path is defined as a link between two or more nodes,
through which these nodes can exchange information.
 A communication path is used to model the logical communication relations
between nodes.
 It is realized by one or more networks, which represent the physical
communication links.
 The communication properties (e.g., bandwidth, latency) of a communication
path are usually aggregated from these underlying networks.
 A communication path connects two or more nodes. A communication path is
realized by one or more networks.
 A communication path is atomic

 An infrastructure service describes the
externally visible and accessible functionality
of a node.
 System software represents the software
environment for specific types of components
and data objects that are deployed on it in
the form of artifacts.

 An infrastructure service is defined as an externally visible unit of
functionality, provided by one or more nodes, exposed through well-defined
interfaces, and meaningful to the environment.
 An infrastructure service exposes the functionality of a node to its environment.
 This functionality is accessed through one or more infrastructure interfaces.
 It may require, use, and produce artifacts.
 An infrastructure service should be meaningful from the point of view of the
environment; it should provide a unit of functionality that is in itself useful to its
users, such as application components and nodes.
 Typical infrastructure services may, for example, include messaging, storage,
naming, and directory services. It may access artifacts; e.g., a file containing a
message.
 The name of an infrastructure service should preferably be a verb ending with “-
ing”; e.g., “messaging”. Also, a name explicitly containing the word “service” may
be used.
 An infrastructure service may consist of sub-services.

 System software represents a software environment for specific types of components
and objects that are deployed on it in the form of artifacts.
 System software is a specialization of a node that is used to model the software environment
in which artifacts run.
 This can be, for example, an operating system, a J2EE application server, a
 CORBA ORB, a database system, a workflow engine, or COTS software such as ERP or CRM
packages.
 Also, system software can be used to represent, for example, communication middleware.
 Usually, system software is combined with a device representing the hardware environment
to form a general node.
 System software can be assigned to a device.
 Artifacts can be assigned to (i.e., deployed on) system software. A node can contain system
software.
 The name of system software should preferably be a noun referring to the type of execution
environment; e.g., “J2EE server”. System software may contain other system software; e.g., an
operating system containing a database.

Informational Concepts

 An artifact is a physical piece of information
that is used or produced in a software
development process, or by deployment and
operation of a system.
 It is the representation, in the form of, for
example, a file, of a data object, or an
application component, and can be deployed
on a node.

 An artifact is defined as a physical piece of information that is used or produced in a
software development process, or by deployment and operation of a system.
 An artifact represents a concrete element in the physical world. It is typically used to model
(software) products such as source files, executables, scripts, database tables, messages,
documents, specifications, and model files.
 An instance (copy) of an artifact can be deployed on a node.
 The two typical ways to use the artifact concept are as an execution component or as a data
file.
 In fact, these could be defined as specializations of the artifact concept.
 The name of an artifact should preferably be the name of the file it represents; e.g.,
“order.jar”.
 An artifact may consist of sub-artifacts.

Structural
Node A computational resource upon which artifacts may be
deployed for execution.

Device A physical computational resource upon which artifacts may be
deployed for execution.

Infrastructure Interface A point of access where the functionality offered by a node can
be accessed by other nodes and application components.

Network A physical communication medium between two or more
devices.

Communication Path A link between two or more nodes, through which these nodes
can exchange information.

Behavioural
Infrastructure Service A point of access where the functionality offered by a node can
be accessed by other nodes and application components.

System Software A software environment for specific types of components and
objects that are deployed on it in the form of artifacts.

Informational
Artifact A physical piece of information that is used or produced in a
software development process, or by deployment and operation
of a system.

If you have one last breath
use it to say...

Archimate Meta Model

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Archimate Meta Model (20)

More from Maganathin Veeraragaloo (20)

Archimate Meta Model