Layers in

Archimate

Ringkasan dari Help Archi Tools

Informatics Master Degree

Graduated Programs, FIT UII
 3 Layers

7/10/19 EA 08 2
 Business Template

7/10/19 EA 08 3
 Business Layer Icons

7/10/19 EA 08 4
 Business Role
 A business role is defined as a named specific behaviour
of a business actor participating in a given context. The
actor performs the behaviour of the role.
 A business role can be fulfilled by more than one
business actor. Conversely, a business actor may fulfil
more than one business role. For example, given a named
teacher, their roles may include those in the domains .
 A business role will usually exist in an organisation
whether or not a given actor fulfils it or not.
 A business role may be assigned to one or more business
processes or business functions. A business interface or
an application interface may be used by a business role,
while a business interface may be part of a business role
(composition relationship).
 The name of a business role should preferably be a noun.

7/10/19 EA 08 5
 Business Interface
 A business interface declares how a business role connects with
its environment.
 The functionality provided by a business role is exposed to its
environment by means of one or more business interfaces.
Conversely, a business role may consume the functionality
provided by other business roles via a business interface.
 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 provided by a
business role or business collaboaration to its environment. A
business service may also be exposed through different
interfaces.
 The name of a business interface should preferably be a noun.

7/10/19 EA 08 6
 Another Active Structure
Business actor
 Entity that performs behaviour in an
organisation such as business processes or
functions.

Business collaboration
 Configuration (possibly temporary) of two or
more business roles resulting in specific
collective behaviour in a particular context.

Location
 Conceptual point or extent in space.

7/10/19 EA 08 7
 Active Structure Example
 Business Actor: A Student, a Teacher, a Customer,
Marketing & Communications department, Director of
Finance, Secretary, Admissions department, Product
Development, Students' Union.

 Business Role: Customer, Insurer, Student, Lecturer,

Administrator, Buyer.

 Business Collaboration: The business roles of Home

Insurance Seller and Travel Insurance Seller may form a
temporary business collaboration in order to form
combined Insurance Selling service.

 Business Interface: Telephone, Email, Call centre, Web

form, Help desk.

 Location: Main Office, Local Office, Room.

7/10/19 EA 08 8
 Business Process
 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 required
behaviour is not of interest so a process is
designated "internal".
 The name of a business process should
preferably be or contain a verb in the simple
present tense.

7/10/19 EA 08 9
 Business Function
 A business function describes internal behaviour performed by a
business role that is required to produce a set of products and
services. It is performed by a single role within an organisation.
 Business processes describe a flow of activities. Business
functions group activities according to their required skills,
knowledge, and resources. A business process forms a string of
business functions.
 A business function may be triggered by, or trigger, any other
business behaviour element (business event, business process,
business function, or business interaction).
 A business function may access business objects. A business
function may realize one or more business services and may use
(internal) business services or application services. A business
role or an application component may be assigned to a business
function.
 The name of a business function should preferably be a verb
ending with "-ing"; e.g., "claims processing".

7/10/19 EA 08 10
 Business Service
 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.
 The name of a business service should preferably be a
verb ending with "-ing"; e.g., "transaction processing".
Also, a name containing the word "service" may be used.

7/10/19 EA 08 11
 Another Behavoiur
Business Interaction
 Unit of behaviour performed as a collaboration between 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.

Business Event
 Something that happens (internally or externally) and
influences behaviour (business process, business function,
business interaction).
 Unlike business processes, functions, and interactions, a
business event is instantaneous: it does not have duration.
 Events may originate from the environment of the organization
(e.g., from a customer), but also internal events may occur
generated by, for example, other processes within the
organization.

7/10/19 EA 08 12
 Behaviour Example
 Business Process: Receive request, Register, Pay,
Create contract, Sign agreement.
 Business Function: Financial Handling, Claims
Processing, Asset Management, Maintaining
Customer Relations.
 Business Service: Customer Information Service,
Claims Payment Service, Enrolment Service.
 Business Interaction: Formalise Request, Check
and Sign Contract, Take out Combined
Insurance.
 Business Event: Request for Insurance, Claim
Received, Application Form Received, Send
Product Portfolio.

7/10/19 EA 08 13
 Business Object
 A business object is defined as a unit of
information that has relevance from a
business perspective.
 A business object is used to model an
object type of which several instances
may exist within the organization. In this
case, it may be realised as a data object
or representation. It may also be
specialised by another business object.
 Business objects are passive. They do
not trigger or perform processes.
7/10/19 EA 08 14
 Business Product
 A product is defined as a coherent collection of
services, accompanied by a contract/set of
agreements, which is offered as a whole to
customers.
 A product consists of a collection of services, and
a contract that specifies the characteristics,
rights, and requirements associated with the
product.
 A product may be offered both internally to the
organisation and externally to customers.
 The name of a product is usually the name which
is used in the communication with customers, or
possibly a more generic noun (e.g., "travel
insurance").
7/10/19 EA 08 15
 Business Value
 A 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 may be expressed in terms of money, but 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 organisational 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.
 It is recommended to try and express the name of a value as an
action or state that can be performed or reached as a result of
the corresponding service being available.

7/10/19 EA 08 16
 Another Passive Structure
Contract
 Formal or informal specification of an agreement that specifies the rights
and obligations associated with a product. A contract 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 specialisation of a business object.

Representation
 The perceptible form (messages or documents) of the information carried by
a business object.
 A single business object can have a number of different representations, but
a representation always belongs to one specific business object. A
representation may realize one or more business objects. A meaning can be
associated with a representation that carries this meaning.

Meaning
 The knowledge or expertise present in the representation of a business
object, given a particular context.
 It represents the functionality of a representation. It describes the intent of a
representation, how it informs the external user. A certain interpretation of a
representation to a certain user carries a certain meaning
7/10/19 EA 08 17
 Passive Structure Example
 Business Object: Invoice, Customer file,
Student record, Attendance record, Ledger.
 Product: A Travel Insurance Product consisting
of Insurance Services and a contract.
 Value: Be insured, Improve relationship,
Improve knowledge, Experience benefit of a
product.
 Contract: Travel Insurance Policy.
 Representation: Paper Bill, Request Form,
Claim Form, Online Form.
 Meaning: Policy explanation, Insurance Policy
notification.

7/10/19 EA 08 18
 Application Template

7/10/19 EA 08 19
 Application Layers Icons

7/10/19 EA 08 20
 Application Component
 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 at the Application level. It performs one or more
application functions.
 It is re-usable, and replaceable. It is only accessible through a
set of application interfaces.
 Co-operating application components are connected via
application collaborations.
 An application component may be assigned to one or more
application functions, business processes, or business functions.
 An application component has one or more application
interfaces, which exposes its functionality.
 The name of an application component should preferably be a
noun.

7/10/19 EA 08 21
 Application Interface
 An application interface declares how a component connects
with its environment.
 An application interface specifies how the functionality of a
component can be accessed by other components. It can also
specify which functionality the component requires from 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 application service may be exposed through
different interfaces.
 An application interface can be assigned to application services
or business services.
 The name of an application interface should preferably be a
noun.

7/10/19 EA 08 22
 Application Collaboration
 An 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 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.

7/10/19 EA 08 23
 Active Structure Example
 Application Component: CRM System, Web
portal, Financial Application, Customer Data
Access.

 Application Interface: Transaction data

exchange.

 Application Collaboration: Two application

components collaborate in transaction
administration, an Accounting component and
a Billing component. This collaboration
performs the application interaction
"Administrate transactions".
7/10/19 EA 08 24
 Application Function
 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 an application component. The function's internal
behaviour is invisible to the user of an application
component.
 An application function's behaviour is exposed externally
through one or more services. An application function
may realize application services. Application services of
other application functions and infrastructure services
may be used by an application function.
 The name of an application function should preferably be
a verb ending with "-ing"; e.g., "accounting".

7/10/19 EA 08 25
 Application Service
 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" or a name explicitly containing
the word "service".

7/10/19 EA 08 26
 Application Interaction
 An 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.
 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.

7/10/19 EA 08 27
 Behaviour Example
 Application Function: Accounting,
Billing, Policy Creation, Calculate
Premium, Financial Administration.

 Application Service: Transaction

Processing, Payment Service,
Customer Admin Service.

 Application Interaction:
Administrate transactions.
7/10/19 EA 08 28
 Data Object
 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.
 The name of a data object should preferably be a
noun. It should be a useful, self-contained piece
of information with a clear meaning to the
business, not just to the application level.
 Examples: Customer File Data, Insurance Policy
Data, Insurance Request Data, Client Database.

7/10/19 EA 08 29
 Infrastructure Template

7/10/19 EA 08 30
 Infrastructure Layer Icons

7/10/19 EA 08 31
 Infrastructure Node
 A node is defined as a computational resource upon
which artifacts may be deployed for execution.
 Nodes execute and process artifacts, which are the
representation of components and data objects.
 Nodes are used to model application servers,
database servers, or client workstations.
 Nodes can consist of sub-nodes representing
physical devices and execution environments for
artifacts.
 Artifacts deployed on a node may either be drawn
inside the node or connected to it with an
assignment relation.
 The name of a node should preferably be a noun.

7/10/19 EA 08 32
 Infrstrct. System Software
 A 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 specialisation of a node that is used
to model the software environment in which artifacts
run. System software can also be used to represent
communication middleware.
 Usually, system software is combined with a device
representing the hardware environment to form a general
node. System software may contain other system
software; e.g., an operating system containing a
database.
 The name of system software should preferably be a
noun referring to the type of execution environment; e.g.,
"J2EE server".

7/10/19 EA 08 33
 Infrastructure Interface
 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 may be part of a node
through composition. 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.
7/10/19 EA 08 34
 Active Structural Sample
 Node:Mainframe, Unix Server Farm,
Application Server, Firewall.
 System Software: DBMS, DB2
System Software, Message
Queuing, Operating System, J2EE
Application Server
 Infrastructure Interface: Client
software.

7/10/19 EA 08 35
 Infrastructure Function
 An infrastructure function describes the internal
behaviour of a node.
 It groups infrastructural behaviour that can be
performed by a node. For the user of a node that
performs an infrastructure function, this function is
invisible. If its behaviour is exposed externally, this is
done through one or more infrastructure services. An
infrastructure function abstracts from the way it is
implemented. Only the necessary behaviour is specified.
 A node may be assigned to an infrastructure function
(which means that the node performs the infrastructure
function).
 The name of an infrastructure function should preferably
be a verb ending with "-ing"

7/10/19 EA 08 36
 Infrastructure Service
 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.
 An infrastructure service may include messaging,
storage, naming, and directory services.
 The name of an infrastructure service should
preferably be a verb ending with "-ing"

7/10/19 EA 08 37
 Behaviour Sample
 Infrastructure Function: Providing
Data Access, Managing Data.

 Infrastructure Service: Messaging

Service, Customer File Service,
Claim Files Service.

7/10/19 EA 08 38
 Infrastructure Artifact
 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.
 A node may be assigned to an artifact (i.e., the artifact is
deployed on the node).
 The name of an artifact should preferably be the name of
the file it represents; e.g., "order.jar".
 Examples: Risk Management EJB, Jar file, Widget, Plug-
in.

7/10/19 EA 08 39