SlideShare uma empresa Scribd logo
1 de 52
Baixar para ler offline
Summarised - 2010
Cross Layer Dependencies
 There are three main types of relationships between these layers:
1. Used by relationships, between application service and the different types of business behaviour elements, and
between application interface and business role. These relationships represent the behavioural and structural
aspects of the support of the business by applications.
2. A realization relationship from a data object to a business object, to indicate that the data object is a digital
representation of the corresponding business object.
3. Assignment relationships, between application component and the different types of business behaviour
elements, and between application interface and business service, to indicate that, for example, business
processes or business services are completely automated.
 There are two types of relationships between these
layers:
1. Used by relationships, between infrastructure service and the different types of application
behaviour elements, and between infrastructure interface and application component. These
relationships represent the behavioural and structural aspects of the use of technical
infrastructure by applications.
2. A realization relationship from artifact to data object, to indicate that the data object is
realized by, for example, a physical data file, and from artifact to application component, to
indicate that a physical data file is an executable that realizes an application or part of an
application.
Relationships
 The relationships can be classified as either:
◦ Structural, which model the structural coherence of
concepts of the same or different types
◦ Dynamic, which are used to model (temporal)
dependencies between behavioural concepts
◦ Other, which do not fall in one of the two above
categories
Archimate Viewpoints
 The composition relationship indicates that an object
consists of a number of other objects.
 The composition relationship has been inspired by the
composition relationship in UML class diagrams, but is applicable
to compose a wider range of concepts. In contrast to the
aggregation relationship, an object can be part of only one
composition.
 The aggregation relationship indicates that a concept
groups a number of other concepts.
 The aggregation relationship has been inspired on the
aggregation relationship in UML class diagrams, but is applicable
to aggregate a wider range of concepts.
 In contrast to the composition relationship, an object can be part
of more than one aggregation.
 The assignment relationship links active elements (e.g., business
roles or application components) with units of behaviour that are
performed by them, or business actors with business roles that are
fulfilled by them.
 The assignment relationship can relate a business role with a business
process or function, an application component with an application
function, a business collaboration with a business interaction, an
application collaboration with an application interaction, a business
interface with a business service, an application interface with an
application service, or a business actor with a business role.
 The realization relationship links a logical entity with a more
concrete entity that realizes it.
 The realization relationship indicates how logical entities (“what”), such
as services, are realized by means of more concrete entities (“how”).
 The realization relationship is used in an operational sense (e.g., a
process/function realizes a service), but also in a
design/implementation context (e.g., a data object may realize a
business object, or an artifact may realize an application component).
 The used by relationship models the use of services by processes,
functions, or interactions and the access to interfaces by roles,
components, or collaborations.
 The used by relationship describes the services that a role or component
offers that are used by entities in the environment.
 The used by relationship is applied for both the behaviour aspect and
the structure aspect
 The access relationship models the access of behavioural concepts to
business or data objects.
 The access relationship indicates that a process, function, interaction,
service, or event “does something” with a (business or data) object; e.g.,
create a new object, read data from the object, write or modify the
object data, or delete the object.
 The relationship can also be used to indicate that the object is just
associated with the behaviour; e.g., it models the information that
comes with an event, or the information that is made available as part of
a service.
 The arrow indicates the flow of information.
 An association models a relationship between objects that is not
covered by another, more specific relationship.
 Association is mainly used, as in UML, to model relationships between
business objects or data objects that are not modelled by the standard
relationships aggregation, composition, or specialization. In addition to
this, the association relationship is used to link the informational
concepts with the other concepts: a business object with a
representation, a representation with a meaning, and a business service
with a purpose.
Archimate Viewpoints
 The triggering relationship describes the temporal or causal relations
between processes, functions, interactions, and events.
 The triggering relationship is used to model the causal relationships
between behaviour concepts in a process.
 No distinction is made between an active triggering relationship and a
passive causal relationship.
 The flow relationship describes the exchange or transfer of, for
example, information or value between processes, function,
interactions, and events.
 The flow relationship is used to model the flow of, for example,
information between behaviour concepts in a process.
 A flow relationship does not imply a causal or temporal relationship.
Archimate Viewpoints
 The grouping relationship indicates that objects belong together
based on some common characteristic.
 Similar to the UML package, the grouping relationship is used to group
an arbitrary group of model objects, which can be of the same type or of
different types.
 In contrast to the aggregation or composition relationships, there is no
“overall” object of which the grouped objects form a part.
 A junction is used to connect dynamic relationships of the same
type.
 A junction is used in a number of situations to connect dynamic
(triggering or flow) relationships of the same type; e.g., to indicate splits
or joins.
 The specialization relationship indicates that an object is a
specialization of another object.
 The specialization relationship has been inspired by the
generalization/specialization relationship in UML class diagrams, but is
applicable to specialize a wider range of concepts.
 The specialization relationship can relate any instance of a concept with
another instance of the same concept.
 Specialization is always possible between two instances of the same
concept.
Structural Relationships
Concept Definition Notation
Association Association models a relationship between objects that is not
covered by another, more specific relationship.
Access The access relationship models the access of behavioural
concepts to business or data objects.
Used by The used by relationship models the use of services by
processes, functions, or interactions and the access to
interfaces by roles, components, or collaborations.
Realisation The realization relationship links a logical entity with a more
concrete entity that realizes it.
Assignment The assignment relationship links units of behaviour with active
elements (e.g., roles, components) that perform them, or roles
with actors that fulfil them.
Aggregation The aggregation relationship indicates that an object groups a
number of other objects.
Composition The composition relationship indicates that an object consists
of a number of other objects.
Summary of Relationships
Dynamic Relationships
Concept Definition Notation
Flow The flow relationship describes the exchange or transfer of, for
example, information or value between processes, function,
interactions, and events.
Triggering The triggering relationship describes the temporal or causal
relations between processes, functions, interactions, and
events.
Other Relationships
Grouping The grouping relationship indicates that objects, of the same
type or different types, belong together based on some
common characteristic.
Junction A junction is used to connect relationships of the same type.
Specialisation The specialization relationship indicates that an object is a
specialization of another object.
Summary of Relationships
Archimate Viewpoints
 If two structural relationships r:R and s:S are
permitted between elements a, b, and c such that
r(a,b) and s(b,c), then a structural relationship t:T is
also permitted, with t(a,c) and type T being the
weakest of R and S.
Archimate Viewpoints
 ArchiMate advocates a more flexible approach in
which architects and other stakeholders can define
their own views on the enterprise architecture.
 Viewpoints define abstractions on the set of
models representing the enterprise architecture,
each aimed at a particular type of stakeholder and
addressing a particular set of concerns.
 Viewpoints can both be used to view certain
aspects in isolation, and for relating two or more
aspects.
 Views are an ideal mechanism to purposefully convey information about architecture
areas. In general, a view is defined as a part of an architecture description that
addresses a set of related concerns and is addressed to a set of stakeholders.
 A view is specified by means of a viewpoint, which prescribes the concepts, models,
analysis techniques, and visualizations that are provided by the view.
 Simply put, a view is what you see, and a viewpoint is where you are looking from.
 The following are examples of stakeholders and concerns as a basis
for the specification of viewpoints:
◦ End user: For example, what are the consequences for his work and workplace?
◦ Architect: What is the consequence for the maintainability of a system, with respect
to corrective, preventive, and adaptive maintenance?
◦ Upper-level management: How can we ensure our policies are followed in the
development and operation of processes and systems? What is the impact of
decisions (on personnel, finance, ICT, etc.)?
◦ Operational manager, responsible for exploitation or maintenance: For example,
what new technologies are there to prepare for? Is there a need to adapt
maintenance processes? What is the impact of changes to existing applications?
How secure are my systems?
◦ Project manager, responsible for the development of new applications: What are the
relevant domains and their relations? What is the dependence of business processes
on the applications to be built? What is their expected performance?
◦ Developer: What are the modifications with respect to the current situation that
need to be done?
 The framework is based on two dimensions: purpose and
content. The following three types of architecture support the
purpose dimension of architecture views:
◦ Designing: Design viewpoints support architects and designers in the
design process from initial sketch to detailed design. Typically, design
viewpoints consist of diagrams, like those used in, for example, UML.
◦ Deciding: Decision support viewpoints assist managers in the process of
decision-making by offering insight into cross-domain architecture
relations, typically through projections and intersections of underlying
models, but also by means of analytical techniques. Typical examples are
cross-reference tables, landscape maps, lists, and reports.
◦ Informing: Informing viewpoints help to inform any stakeholder about the
enterprise architecture, in order to achieve understanding, obtain
commitment, and convince adversaries. Typical examples are illustrations,
animations, cartoons, flyers, etc.
 For characterizing the content of a view we define the
following abstraction levels:
◦ Details: Views on the detailed level typically consider one layer and one
aspect from the ArchiMate framework. Typical stakeholders are a software
engineer responsible for design and implementation of a software
component or a process owner responsible for effective and efficient
process execution. Examples of views are a BPMN process diagram and a
UML class diagram.
◦ Coherence: At the coherence abstraction level, multiple layers or multiple
aspects are spanned. Extending the view to more than one layer or aspect
enables the stakeholder to focus on architecture relations like process-
uses-system (multiple layer) or application uses- object (multiple aspect).
Typical stakeholders are operational managers responsible for a collection
of IT services or business processes.
◦ Overview: The overview abstraction level addresses both multiple layers
and multiple aspects. Typically, such overviews are addressed to
enterprise architects and decision makers, such as CEOs and CIOs.
Viewpoint Purpose Typical Stakeholders Purpose Examples
Designing architect, software
developer, business
process designer
navigate, design, support
design decisions, compare
alternatives
UML diagram, BPMN
diagram, flowchart, ER
diagram
Deciding manager, CIO, CEO decision-making cross-reference table,
landscape map, list, report
Informing employee, customer,
others
explain, convince, obtain
commitment
animation, cartoon,
process illustration, chart
Viewpoint Abstraction Levels
Details software engineer,
process owner
design, manage UML class diagram,
BPMN process diagram
Coherence operational managers analyze dependencies,
impact of-change
views expressing
relations like “use”,
“realize”, and “assign”
Overview enterprise architect, CIO,
CEO
change management landscape map
Basic Viewpoints in Archimate
Concepts and Relations
Example
It is typically used at the start of a design
trajectory, when not everything needs to be
detailed yet, or to explain the essence of an
architecture model to non-architects that
require a simpler notation.
Concepts and Relations
Example
 The Organization viewpoint focuses
on the (internal) organization of a
company, a department, a network
of companies, or of another
organizational entity.
Concepts and Relations
Example
 The Actor Co-operation viewpoint
focuses on the relations of actors
with each other and their
environment..
Concepts and Relations
Example
 The Business Function viewpoint shows the
main business functions of an
organization and their relations in terms of
the flows of information, value, or goods
between them.
Concepts and Relations
Example
 The Business Process viewpoint is used to
show the high-level structure and composition
of one or more business processes.
Concepts and Relations
Example
 Business Process Co-operation viewpoint is
used to show the relations of one or more
business processes with each other and/or
with their environment..
Concepts and Relations
Example
 Business Process The
Product viewpoint depicts
the value these products
offer to the customers or
other external parties
involved and shows the
composition of one or more
products in terms of the
constituting (business or
application) services, and
the associated contract(s) or
other agreements.
Concepts and Relations
Example
 The Application Behaviour
viewpoint describes the
internal behaviour of an
application; e.g., as it
realizes one or more
application services. This
viewpoint is useful in
designing the main
behaviour of applications,
or in identifying functional
overlap between different
applications.
Concepts and Relations
Example
 The Application Co-operation viewpoint describes the relations
between applications components in terms of the information flows
between them, or in terms of the services they offer and use.
Concepts and Relations
Example
 This viewpoint is useful in designing or understanding the
main structure of applications or components and the
associated data; e.g., to break down the structure of the
system under construction, or to identify legacy
application components that are suitable for
migration/integration.
Concepts and Relations
Example
 It can be used in designing an application by identifying
the services needed by business processes and other
applications, or in designing business processes by
describing the services that are available.
Concepts
and Relations
Example
 The Infrastructure viewpoint contains the software and
hardware infrastructure elements supporting the
application layer, such as physical devices, networks, or
system software (e.g., operating systems, databases, and
middleware).
Concepts
and
Relations
Example  Shows how applications are supported by the
software and hardware infrastructure: the
infrastructure services are delivered by the devices;
system software and networks are provided to the
applications.
Concepts and
Relations
Example  This comprises the mapping of (logical) applications
and components onto (physical) artifacts, such as
Enterprise Java Beans, and the mapping of the
information used by these applications and
components onto the underlying storage
infrastructure; e.g., database tables or other files.
Concepts and Relations
Example
 It shows the structure of the information
used in the enterprise or in a specific
business process or application, in terms
of data types or (object-oriented) class
structures.
Concepts and Relations
Example
 The Service Realization viewpoint is used to show how one or more business services are realized
by the underlying processes (and sometimes by application components). Thus, it forms the bridge
between the business products viewpoint and the business process view. It provides a “view from
the outside” on one or more business processes.
Example
 There are two categories of layers, namely
dedicated layers and service layers. The
layers are the result of the use of the
“grouping” relation for a natural partitioning
of the entire set of objects and relations that
belong to a model.
Example
 There are two categories of layers, namely
dedicated layers and service layers. The
layers are the result of the use of the
“grouping” relation for a natural partitioning
of the entire set of objects and relations that
belong to a model.
If you have one last breath
use it to say...

Mais conteúdo relacionado

Mais procurados

From Business model to Capability Map
From Business model to Capability Map From Business model to Capability Map
From Business model to Capability Map COMPETENSIS
 
Effective Application Portfolio Management using ArchiMate
Effective Application Portfolio Management using ArchiMateEffective Application Portfolio Management using ArchiMate
Effective Application Portfolio Management using ArchiMateCorso
 
2019 07 Bizbok with Archimate 3 v3 [UPDATED !]
 2019 07 Bizbok with Archimate 3 v3 [UPDATED !] 2019 07 Bizbok with Archimate 3 v3 [UPDATED !]
2019 07 Bizbok with Archimate 3 v3 [UPDATED !]COMPETENSIS
 
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overview
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overviewEnterprise Architecture for Dummies - TOGAF 9 enterprise architecture overview
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overviewWinton Winton
 
Capability-based planning with TOGAF & ArchiMate
Capability-based planning with TOGAF & ArchiMateCapability-based planning with TOGAF & ArchiMate
Capability-based planning with TOGAF & ArchiMateAnastasios Papazoglou
 
Value analysis with Value Stream and Capability modeling
Value analysis with Value Stream and Capability modelingValue analysis with Value Stream and Capability modeling
Value analysis with Value Stream and Capability modelingCOMPETENSIS
 
ArchiMate application and data architecture layer - Simplify the models
ArchiMate application and data architecture layer - Simplify the modelsArchiMate application and data architecture layer - Simplify the models
ArchiMate application and data architecture layer - Simplify the modelsCOMPETENSIS
 
Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!Sam Mandebvu
 
Togaf introduction and core concepts
Togaf introduction and core conceptsTogaf introduction and core concepts
Togaf introduction and core conceptsPaul Sullivan
 
Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2Jean Gehring
 
ArchiMate 3.0: A New Standard for Architecture
ArchiMate 3.0: A New Standard for ArchitectureArchiMate 3.0: A New Standard for Architecture
ArchiMate 3.0: A New Standard for ArchitectureIver Band
 
Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Nathaniel Palmer
 
TOGAF 9.2 - Transforming Business
TOGAF 9.2  -  Transforming BusinessTOGAF 9.2  -  Transforming Business
TOGAF 9.2 - Transforming BusinessReal IRM
 
Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...
Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...
Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...Alan McSweeney
 
Enterprise Architecture - TOGAF Overview
Enterprise Architecture - TOGAF OverviewEnterprise Architecture - TOGAF Overview
Enterprise Architecture - TOGAF OverviewMohamed Sami El-Tahawy
 
Enterprise Architecture Implementation And The Open Group Architecture Framew...
Enterprise Architecture Implementation And The Open Group Architecture Framew...Enterprise Architecture Implementation And The Open Group Architecture Framew...
Enterprise Architecture Implementation And The Open Group Architecture Framew...Alan McSweeney
 
Review of Information Technology Function Critical Capability Models
Review of Information Technology Function Critical Capability ModelsReview of Information Technology Function Critical Capability Models
Review of Information Technology Function Critical Capability ModelsAlan McSweeney
 

Mais procurados (20)

From Business model to Capability Map
From Business model to Capability Map From Business model to Capability Map
From Business model to Capability Map
 
Effective Application Portfolio Management using ArchiMate
Effective Application Portfolio Management using ArchiMateEffective Application Portfolio Management using ArchiMate
Effective Application Portfolio Management using ArchiMate
 
Togaf 9.2 Introduction
Togaf 9.2 IntroductionTogaf 9.2 Introduction
Togaf 9.2 Introduction
 
2019 07 Bizbok with Archimate 3 v3 [UPDATED !]
 2019 07 Bizbok with Archimate 3 v3 [UPDATED !] 2019 07 Bizbok with Archimate 3 v3 [UPDATED !]
2019 07 Bizbok with Archimate 3 v3 [UPDATED !]
 
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overview
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overviewEnterprise Architecture for Dummies - TOGAF 9 enterprise architecture overview
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overview
 
Capability-based planning with TOGAF & ArchiMate
Capability-based planning with TOGAF & ArchiMateCapability-based planning with TOGAF & ArchiMate
Capability-based planning with TOGAF & ArchiMate
 
Value analysis with Value Stream and Capability modeling
Value analysis with Value Stream and Capability modelingValue analysis with Value Stream and Capability modeling
Value analysis with Value Stream and Capability modeling
 
ArchiMate application and data architecture layer - Simplify the models
ArchiMate application and data architecture layer - Simplify the modelsArchiMate application and data architecture layer - Simplify the models
ArchiMate application and data architecture layer - Simplify the models
 
MAPPING TOGAF® ADM AND AGILE APPROACH
MAPPING TOGAF® ADM AND AGILE APPROACHMAPPING TOGAF® ADM AND AGILE APPROACH
MAPPING TOGAF® ADM AND AGILE APPROACH
 
Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!Learn Togaf 9.1 in 100 slides!
Learn Togaf 9.1 in 100 slides!
 
Togaf introduction and core concepts
Togaf introduction and core conceptsTogaf introduction and core concepts
Togaf introduction and core concepts
 
Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2Enterprise Architecture & Project Portfolio Management 1/2
Enterprise Architecture & Project Portfolio Management 1/2
 
ArchiMate 3.0: A New Standard for Architecture
ArchiMate 3.0: A New Standard for ArchitectureArchiMate 3.0: A New Standard for Architecture
ArchiMate 3.0: A New Standard for Architecture
 
Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)Understanding and Applying The Open Group Architecture Framework (TOGAF)
Understanding and Applying The Open Group Architecture Framework (TOGAF)
 
TOGAF 9.2 - Transforming Business
TOGAF 9.2  -  Transforming BusinessTOGAF 9.2  -  Transforming Business
TOGAF 9.2 - Transforming Business
 
Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...
Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...
Integrating It Frameworks, Methodologies And Best Practices Into It Delivery ...
 
Enterprise Architecture - TOGAF Overview
Enterprise Architecture - TOGAF OverviewEnterprise Architecture - TOGAF Overview
Enterprise Architecture - TOGAF Overview
 
Enterprise Architecture Implementation And The Open Group Architecture Framew...
Enterprise Architecture Implementation And The Open Group Architecture Framew...Enterprise Architecture Implementation And The Open Group Architecture Framew...
Enterprise Architecture Implementation And The Open Group Architecture Framew...
 
Review of Information Technology Function Critical Capability Models
Review of Information Technology Function Critical Capability ModelsReview of Information Technology Function Critical Capability Models
Review of Information Technology Function Critical Capability Models
 
TOGAF Complete Slide Deck
TOGAF Complete Slide DeckTOGAF Complete Slide Deck
TOGAF Complete Slide Deck
 

Destaque

An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...
An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...
An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...Iver Band
 
Enterprise communication using archiMate
Enterprise communication using archiMateEnterprise communication using archiMate
Enterprise communication using archiMateLouw Labuschagne
 
Removing the barriers to business transformation with ArchiMate
Removing the barriers to business transformation with ArchiMateRemoving the barriers to business transformation with ArchiMate
Removing the barriers to business transformation with ArchiMateCorso
 
Applying reference models with archi mate
Applying reference models with archi mateApplying reference models with archi mate
Applying reference models with archi mateBas van Gils
 
ArchiSurance Case Study
ArchiSurance Case StudyArchiSurance Case Study
ArchiSurance Case StudyIver Band
 
Modeling ACORD with ArchiMate Case Study Views
Modeling ACORD with ArchiMate Case Study ViewsModeling ACORD with ArchiMate Case Study Views
Modeling ACORD with ArchiMate Case Study ViewsIver Band
 
Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...
Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...
Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...Patrick Van Renterghem
 
An Introduction to the ArchiMate 3.0 Specification
An Introduction to the ArchiMate 3.0 SpecificationAn Introduction to the ArchiMate 3.0 Specification
An Introduction to the ArchiMate 3.0 SpecificationIver Band
 
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...Iver Band
 
Archimate: lenguaje para modelamiento de la arquitectura empresarial
Archimate: lenguaje para modelamiento de la arquitectura empresarialArchimate: lenguaje para modelamiento de la arquitectura empresarial
Archimate: lenguaje para modelamiento de la arquitectura empresarialJonathan Stalin Delgado Guerrero
 
Extracting archimate views from custom ontological ea models
Extracting archimate views from custom ontological ea modelsExtracting archimate views from custom ontological ea models
Extracting archimate views from custom ontological ea modelsMatteo Busanelli
 
Guiding Agile Solution Delivery with the ArchiMate Language
Guiding Agile Solution Delivery with the ArchiMate LanguageGuiding Agile Solution Delivery with the ArchiMate Language
Guiding Agile Solution Delivery with the ArchiMate LanguageIver Band
 
Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...
Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...
Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...Iver Band
 
3 things about EA that TOGAF doesnt say
3 things about EA that TOGAF doesnt say3 things about EA that TOGAF doesnt say
3 things about EA that TOGAF doesnt saycccamericas
 
Application Value Assessment
Application Value AssessmentApplication Value Assessment
Application Value AssessmentGerry Appeltants
 
Implementing ACORD with ArchiMate
Implementing ACORD with ArchiMateImplementing ACORD with ArchiMate
Implementing ACORD with ArchiMateIver Band
 
Building a strong Data Management capability with TOGAF and ArchiMate
Building a strong Data Management capability with TOGAF and ArchiMateBuilding a strong Data Management capability with TOGAF and ArchiMate
Building a strong Data Management capability with TOGAF and ArchiMateBas van Gils
 

Destaque (20)

An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...
An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...
An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...
 
Enterprise communication using archiMate
Enterprise communication using archiMateEnterprise communication using archiMate
Enterprise communication using archiMate
 
Removing the barriers to business transformation with ArchiMate
Removing the barriers to business transformation with ArchiMateRemoving the barriers to business transformation with ArchiMate
Removing the barriers to business transformation with ArchiMate
 
Applying reference models with archi mate
Applying reference models with archi mateApplying reference models with archi mate
Applying reference models with archi mate
 
ArchiSurance Case Study
ArchiSurance Case StudyArchiSurance Case Study
ArchiSurance Case Study
 
Modeling ACORD with ArchiMate Case Study Views
Modeling ACORD with ArchiMate Case Study ViewsModeling ACORD with ArchiMate Case Study Views
Modeling ACORD with ArchiMate Case Study Views
 
Presentacion: Usando Archimate
Presentacion: Usando ArchimatePresentacion: Usando Archimate
Presentacion: Usando Archimate
 
Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...
Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...
Use of ArchiMate at Colruyt Group (presentation by Brechtel Dero at the I.T. ...
 
An Introduction to the ArchiMate 3.0 Specification
An Introduction to the ArchiMate 3.0 SpecificationAn Introduction to the ArchiMate 3.0 Specification
An Introduction to the ArchiMate 3.0 Specification
 
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...
 
Archimate: lenguaje para modelamiento de la arquitectura empresarial
Archimate: lenguaje para modelamiento de la arquitectura empresarialArchimate: lenguaje para modelamiento de la arquitectura empresarial
Archimate: lenguaje para modelamiento de la arquitectura empresarial
 
Archimate Introduction
Archimate IntroductionArchimate Introduction
Archimate Introduction
 
Extracting archimate views from custom ontological ea models
Extracting archimate views from custom ontological ea modelsExtracting archimate views from custom ontological ea models
Extracting archimate views from custom ontological ea models
 
Archimate Overview
Archimate OverviewArchimate Overview
Archimate Overview
 
Guiding Agile Solution Delivery with the ArchiMate Language
Guiding Agile Solution Delivery with the ArchiMate LanguageGuiding Agile Solution Delivery with the ArchiMate Language
Guiding Agile Solution Delivery with the ArchiMate Language
 
Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...
Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...
Cloud-Based CRM with On-Premises Integration at a Diversified Financial Servi...
 
3 things about EA that TOGAF doesnt say
3 things about EA that TOGAF doesnt say3 things about EA that TOGAF doesnt say
3 things about EA that TOGAF doesnt say
 
Application Value Assessment
Application Value AssessmentApplication Value Assessment
Application Value Assessment
 
Implementing ACORD with ArchiMate
Implementing ACORD with ArchiMateImplementing ACORD with ArchiMate
Implementing ACORD with ArchiMate
 
Building a strong Data Management capability with TOGAF and ArchiMate
Building a strong Data Management capability with TOGAF and ArchiMateBuilding a strong Data Management capability with TOGAF and ArchiMate
Building a strong Data Management capability with TOGAF and ArchiMate
 

Semelhante a Archimate Viewpoints

ECEG 4702-Class7-Entity-Relationship modeling.pptx
ECEG 4702-Class7-Entity-Relationship modeling.pptxECEG 4702-Class7-Entity-Relationship modeling.pptx
ECEG 4702-Class7-Entity-Relationship modeling.pptxmiftah88
 
Intro to UML 2
Intro to UML 2Intro to UML 2
Intro to UML 2rchakra
 
Lecture 16 requirements modeling - scenario, information and analysis classes
Lecture 16   requirements modeling - scenario, information and analysis classesLecture 16   requirements modeling - scenario, information and analysis classes
Lecture 16 requirements modeling - scenario, information and analysis classesIIUI
 
An artifact centric view-based approach to modeling inter-organizational busi...
An artifact centric view-based approach to modeling inter-organizational busi...An artifact centric view-based approach to modeling inter-organizational busi...
An artifact centric view-based approach to modeling inter-organizational busi...Dr. Sira Yongchareon
 
ASP.NET System design 2
ASP.NET System design 2ASP.NET System design 2
ASP.NET System design 2Sisir Ghosh
 
Interaction Modeling
Interaction ModelingInteraction Modeling
Interaction ModelingHemant Sharma
 
UML-Advanced Software Engineering
UML-Advanced Software EngineeringUML-Advanced Software Engineering
UML-Advanced Software EngineeringAmit Singh
 
UML and Software Modeling Tools.pptx
UML and Software Modeling Tools.pptxUML and Software Modeling Tools.pptx
UML and Software Modeling Tools.pptxNwabueze Obioma
 
ERD - Entity Relationship Diagram
ERD - Entity Relationship DiagramERD - Entity Relationship Diagram
ERD - Entity Relationship DiagramAsher Jawad
 
UML-Advanced Software Engineering
UML-Advanced Software EngineeringUML-Advanced Software Engineering
UML-Advanced Software EngineeringAmit Singh
 
OOAD with UML (Interaction Diagramming)
OOAD with UML (Interaction Diagramming)OOAD with UML (Interaction Diagramming)
OOAD with UML (Interaction Diagramming)jsm1979
 
Lecture#02, building blocks of uml ASE
Lecture#02, building blocks of uml ASELecture#02, building blocks of uml ASE
Lecture#02, building blocks of uml ASEbabak danyal
 
UML- Unified Modeling Language
UML- Unified Modeling LanguageUML- Unified Modeling Language
UML- Unified Modeling LanguageShahzad
 
Interaction overview and Profile UML Diagrams
Interaction overview and Profile UML DiagramsInteraction overview and Profile UML Diagrams
Interaction overview and Profile UML DiagramsHusnain Safdar
 

Semelhante a Archimate Viewpoints (20)

ECEG 4702-Class7-Entity-Relationship modeling.pptx
ECEG 4702-Class7-Entity-Relationship modeling.pptxECEG 4702-Class7-Entity-Relationship modeling.pptx
ECEG 4702-Class7-Entity-Relationship modeling.pptx
 
Intro to UML 2
Intro to UML 2Intro to UML 2
Intro to UML 2
 
Lecture 16 requirements modeling - scenario, information and analysis classes
Lecture 16   requirements modeling - scenario, information and analysis classesLecture 16   requirements modeling - scenario, information and analysis classes
Lecture 16 requirements modeling - scenario, information and analysis classes
 
An artifact centric view-based approach to modeling inter-organizational busi...
An artifact centric view-based approach to modeling inter-organizational busi...An artifact centric view-based approach to modeling inter-organizational busi...
An artifact centric view-based approach to modeling inter-organizational busi...
 
ASP.NET System design 2
ASP.NET System design 2ASP.NET System design 2
ASP.NET System design 2
 
Interaction Modeling
Interaction ModelingInteraction Modeling
Interaction Modeling
 
UML-Advanced Software Engineering
UML-Advanced Software EngineeringUML-Advanced Software Engineering
UML-Advanced Software Engineering
 
UML and Software Modeling Tools.pptx
UML and Software Modeling Tools.pptxUML and Software Modeling Tools.pptx
UML and Software Modeling Tools.pptx
 
Uml report
Uml reportUml report
Uml report
 
ERD - Entity Relationship Diagram
ERD - Entity Relationship DiagramERD - Entity Relationship Diagram
ERD - Entity Relationship Diagram
 
UML-Advanced Software Engineering
UML-Advanced Software EngineeringUML-Advanced Software Engineering
UML-Advanced Software Engineering
 
Archimate Meta Model
Archimate   Meta ModelArchimate   Meta Model
Archimate Meta Model
 
OOAD with UML (Interaction Diagramming)
OOAD with UML (Interaction Diagramming)OOAD with UML (Interaction Diagramming)
OOAD with UML (Interaction Diagramming)
 
Service specification and service compliance how to consider the responsibil...
Service specification and service compliance  how to consider the responsibil...Service specification and service compliance  how to consider the responsibil...
Service specification and service compliance how to consider the responsibil...
 
Lecture#02, building blocks of uml ASE
Lecture#02, building blocks of uml ASELecture#02, building blocks of uml ASE
Lecture#02, building blocks of uml ASE
 
Uml
UmlUml
Uml
 
UML- Unified Modeling Language
UML- Unified Modeling LanguageUML- Unified Modeling Language
UML- Unified Modeling Language
 
Types of UML diagrams
Types of UML diagramsTypes of UML diagrams
Types of UML diagrams
 
Interaction overview and Profile UML Diagrams
Interaction overview and Profile UML DiagramsInteraction overview and Profile UML Diagrams
Interaction overview and Profile UML Diagrams
 
Unit 3
Unit 3Unit 3
Unit 3
 

Mais de Maganathin Veeraragaloo

Cybersecurity Capability Maturity Model (C2M2)
Cybersecurity Capability Maturity Model (C2M2)Cybersecurity Capability Maturity Model (C2M2)
Cybersecurity Capability Maturity Model (C2M2)Maganathin Veeraragaloo
 
ZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORK
ZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORKZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORK
ZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORKMaganathin Veeraragaloo
 
CYBERSECURITY MESH - DIGITAL TRUST FRAMEWORK
CYBERSECURITY MESH - DIGITAL TRUST FRAMEWORKCYBERSECURITY MESH - DIGITAL TRUST FRAMEWORK
CYBERSECURITY MESH - DIGITAL TRUST FRAMEWORKMaganathin Veeraragaloo
 
Enterprise security architecture approach
Enterprise security architecture approachEnterprise security architecture approach
Enterprise security architecture approachMaganathin Veeraragaloo
 

Mais de Maganathin Veeraragaloo (20)

MULTI-CLOUD ARCHITECTURE
MULTI-CLOUD ARCHITECTUREMULTI-CLOUD ARCHITECTURE
MULTI-CLOUD ARCHITECTURE
 
Cloud security (domain11 14)
Cloud security (domain11 14)Cloud security (domain11 14)
Cloud security (domain11 14)
 
Cloud security (domain6 10)
Cloud security (domain6 10)Cloud security (domain6 10)
Cloud security (domain6 10)
 
Cloud Security (Domain1- 5)
Cloud Security (Domain1- 5)Cloud Security (Domain1- 5)
Cloud Security (Domain1- 5)
 
BTABOK / ITABOK
BTABOK / ITABOKBTABOK / ITABOK
BTABOK / ITABOK
 
Observability
ObservabilityObservability
Observability
 
Foresight 4 Cybersecurity
Foresight 4 CybersecurityForesight 4 Cybersecurity
Foresight 4 Cybersecurity
 
Cybersecurity Capability Maturity Model (C2M2)
Cybersecurity Capability Maturity Model (C2M2)Cybersecurity Capability Maturity Model (C2M2)
Cybersecurity Capability Maturity Model (C2M2)
 
CLOUD NATIVE SECURITY
CLOUD NATIVE SECURITYCLOUD NATIVE SECURITY
CLOUD NATIVE SECURITY
 
ZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORK
ZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORKZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORK
ZERO TRUST ARCHITECTURE - DIGITAL TRUST FRAMEWORK
 
ISO 27005 - Digital Trust Framework
ISO 27005 - Digital Trust FrameworkISO 27005 - Digital Trust Framework
ISO 27005 - Digital Trust Framework
 
ITIL4 - DIGITAL TRUST FRAMEWORK
ITIL4 - DIGITAL TRUST FRAMEWORKITIL4 - DIGITAL TRUST FRAMEWORK
ITIL4 - DIGITAL TRUST FRAMEWORK
 
CYBERSECURITY MESH - DIGITAL TRUST FRAMEWORK
CYBERSECURITY MESH - DIGITAL TRUST FRAMEWORKCYBERSECURITY MESH - DIGITAL TRUST FRAMEWORK
CYBERSECURITY MESH - DIGITAL TRUST FRAMEWORK
 
COBIT 2019 - DIGITAL TRUST FRAMEWORK
COBIT 2019 - DIGITAL TRUST FRAMEWORKCOBIT 2019 - DIGITAL TRUST FRAMEWORK
COBIT 2019 - DIGITAL TRUST FRAMEWORK
 
Open Digital Framework from TMFORUM
Open Digital Framework from TMFORUMOpen Digital Framework from TMFORUM
Open Digital Framework from TMFORUM
 
Enterprise security architecture approach
Enterprise security architecture approachEnterprise security architecture approach
Enterprise security architecture approach
 
Cloud and Data Privacy
Cloud and Data PrivacyCloud and Data Privacy
Cloud and Data Privacy
 
XaaS Overview
XaaS OverviewXaaS Overview
XaaS Overview
 
Multi cloud security architecture
Multi cloud security architecture Multi cloud security architecture
Multi cloud security architecture
 
Multi Cloud Architecture Approach
Multi Cloud Architecture ApproachMulti Cloud Architecture Approach
Multi Cloud Architecture Approach
 

Último

UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7DianaGray10
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXTarek Kalaji
 
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdfPaige Cruz
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
The Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API ManagementThe Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API ManagementNuwan Dias
 
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"DianaGray10
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IES VE
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemAsko Soukka
 
100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimization100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimizationarrow10202532yuvraj
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?Juan Carlos Gonzalez
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfinfogdgmi
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintMahmoud Rabie
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024D Cloud Solutions
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 

Último (20)

UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBX
 
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf99.99% of Your Traces  Are (Probably) Trash (SRECon NA 2024).pdf
99.99% of Your Traces Are (Probably) Trash (SRECon NA 2024).pdf
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
The Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API ManagementThe Kubernetes Gateway API and its role in Cloud Native API Management
The Kubernetes Gateway API and its role in Cloud Native API Management
 
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
UiPath Clipboard AI: "A TIME Magazine Best Invention of 2023 Unveiled"
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability Adventure
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystem
 
100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimization100+ ChatGPT Prompts for SEO Optimization
100+ ChatGPT Prompts for SEO Optimization
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?Governance in SharePoint Premium:What's in the box?
Governance in SharePoint Premium:What's in the box?
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdf
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership Blueprint
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 

Archimate Viewpoints

  • 3.  There are three main types of relationships between these layers: 1. Used by relationships, between application service and the different types of business behaviour elements, and between application interface and business role. These relationships represent the behavioural and structural aspects of the support of the business by applications. 2. A realization relationship from a data object to a business object, to indicate that the data object is a digital representation of the corresponding business object. 3. Assignment relationships, between application component and the different types of business behaviour elements, and between application interface and business service, to indicate that, for example, business processes or business services are completely automated.
  • 4.  There are two types of relationships between these layers: 1. Used by relationships, between infrastructure service and the different types of application behaviour elements, and between infrastructure interface and application component. These relationships represent the behavioural and structural aspects of the use of technical infrastructure by applications. 2. A realization relationship from artifact to data object, to indicate that the data object is realized by, for example, a physical data file, and from artifact to application component, to indicate that a physical data file is an executable that realizes an application or part of an application.
  • 6.  The relationships can be classified as either: ◦ Structural, which model the structural coherence of concepts of the same or different types ◦ Dynamic, which are used to model (temporal) dependencies between behavioural concepts ◦ Other, which do not fall in one of the two above categories
  • 8.  The composition relationship indicates that an object consists of a number of other objects.  The composition relationship has been inspired by the composition relationship in UML class diagrams, but is applicable to compose a wider range of concepts. In contrast to the aggregation relationship, an object can be part of only one composition.
  • 9.  The aggregation relationship indicates that a concept groups a number of other concepts.  The aggregation relationship has been inspired on the aggregation relationship in UML class diagrams, but is applicable to aggregate a wider range of concepts.  In contrast to the composition relationship, an object can be part of more than one aggregation.
  • 10.  The assignment relationship links active elements (e.g., business roles or application components) with units of behaviour that are performed by them, or business actors with business roles that are fulfilled by them.  The assignment relationship can relate a business role with a business process or function, an application component with an application function, a business collaboration with a business interaction, an application collaboration with an application interaction, a business interface with a business service, an application interface with an application service, or a business actor with a business role.
  • 11.  The realization relationship links a logical entity with a more concrete entity that realizes it.  The realization relationship indicates how logical entities (“what”), such as services, are realized by means of more concrete entities (“how”).  The realization relationship is used in an operational sense (e.g., a process/function realizes a service), but also in a design/implementation context (e.g., a data object may realize a business object, or an artifact may realize an application component).
  • 12.  The used by relationship models the use of services by processes, functions, or interactions and the access to interfaces by roles, components, or collaborations.  The used by relationship describes the services that a role or component offers that are used by entities in the environment.  The used by relationship is applied for both the behaviour aspect and the structure aspect
  • 13.  The access relationship models the access of behavioural concepts to business or data objects.  The access relationship indicates that a process, function, interaction, service, or event “does something” with a (business or data) object; e.g., create a new object, read data from the object, write or modify the object data, or delete the object.  The relationship can also be used to indicate that the object is just associated with the behaviour; e.g., it models the information that comes with an event, or the information that is made available as part of a service.  The arrow indicates the flow of information.
  • 14.  An association models a relationship between objects that is not covered by another, more specific relationship.  Association is mainly used, as in UML, to model relationships between business objects or data objects that are not modelled by the standard relationships aggregation, composition, or specialization. In addition to this, the association relationship is used to link the informational concepts with the other concepts: a business object with a representation, a representation with a meaning, and a business service with a purpose.
  • 16.  The triggering relationship describes the temporal or causal relations between processes, functions, interactions, and events.  The triggering relationship is used to model the causal relationships between behaviour concepts in a process.  No distinction is made between an active triggering relationship and a passive causal relationship.
  • 17.  The flow relationship describes the exchange or transfer of, for example, information or value between processes, function, interactions, and events.  The flow relationship is used to model the flow of, for example, information between behaviour concepts in a process.  A flow relationship does not imply a causal or temporal relationship.
  • 19.  The grouping relationship indicates that objects belong together based on some common characteristic.  Similar to the UML package, the grouping relationship is used to group an arbitrary group of model objects, which can be of the same type or of different types.  In contrast to the aggregation or composition relationships, there is no “overall” object of which the grouped objects form a part.
  • 20.  A junction is used to connect dynamic relationships of the same type.  A junction is used in a number of situations to connect dynamic (triggering or flow) relationships of the same type; e.g., to indicate splits or joins.
  • 21.  The specialization relationship indicates that an object is a specialization of another object.  The specialization relationship has been inspired by the generalization/specialization relationship in UML class diagrams, but is applicable to specialize a wider range of concepts.  The specialization relationship can relate any instance of a concept with another instance of the same concept.  Specialization is always possible between two instances of the same concept.
  • 22. Structural Relationships Concept Definition Notation Association Association models a relationship between objects that is not covered by another, more specific relationship. Access The access relationship models the access of behavioural concepts to business or data objects. Used by The used by relationship models the use of services by processes, functions, or interactions and the access to interfaces by roles, components, or collaborations. Realisation The realization relationship links a logical entity with a more concrete entity that realizes it. Assignment The assignment relationship links units of behaviour with active elements (e.g., roles, components) that perform them, or roles with actors that fulfil them. Aggregation The aggregation relationship indicates that an object groups a number of other objects. Composition The composition relationship indicates that an object consists of a number of other objects. Summary of Relationships
  • 23. Dynamic Relationships Concept Definition Notation Flow The flow relationship describes the exchange or transfer of, for example, information or value between processes, function, interactions, and events. Triggering The triggering relationship describes the temporal or causal relations between processes, functions, interactions, and events. Other Relationships Grouping The grouping relationship indicates that objects, of the same type or different types, belong together based on some common characteristic. Junction A junction is used to connect relationships of the same type. Specialisation The specialization relationship indicates that an object is a specialization of another object. Summary of Relationships
  • 25.  If two structural relationships r:R and s:S are permitted between elements a, b, and c such that r(a,b) and s(b,c), then a structural relationship t:T is also permitted, with t(a,c) and type T being the weakest of R and S.
  • 27.  ArchiMate advocates a more flexible approach in which architects and other stakeholders can define their own views on the enterprise architecture.  Viewpoints define abstractions on the set of models representing the enterprise architecture, each aimed at a particular type of stakeholder and addressing a particular set of concerns.  Viewpoints can both be used to view certain aspects in isolation, and for relating two or more aspects.
  • 28.  Views are an ideal mechanism to purposefully convey information about architecture areas. In general, a view is defined as a part of an architecture description that addresses a set of related concerns and is addressed to a set of stakeholders.  A view is specified by means of a viewpoint, which prescribes the concepts, models, analysis techniques, and visualizations that are provided by the view.  Simply put, a view is what you see, and a viewpoint is where you are looking from.
  • 29.  The following are examples of stakeholders and concerns as a basis for the specification of viewpoints: ◦ End user: For example, what are the consequences for his work and workplace? ◦ Architect: What is the consequence for the maintainability of a system, with respect to corrective, preventive, and adaptive maintenance? ◦ Upper-level management: How can we ensure our policies are followed in the development and operation of processes and systems? What is the impact of decisions (on personnel, finance, ICT, etc.)? ◦ Operational manager, responsible for exploitation or maintenance: For example, what new technologies are there to prepare for? Is there a need to adapt maintenance processes? What is the impact of changes to existing applications? How secure are my systems? ◦ Project manager, responsible for the development of new applications: What are the relevant domains and their relations? What is the dependence of business processes on the applications to be built? What is their expected performance? ◦ Developer: What are the modifications with respect to the current situation that need to be done?
  • 30.  The framework is based on two dimensions: purpose and content. The following three types of architecture support the purpose dimension of architecture views: ◦ Designing: Design viewpoints support architects and designers in the design process from initial sketch to detailed design. Typically, design viewpoints consist of diagrams, like those used in, for example, UML. ◦ Deciding: Decision support viewpoints assist managers in the process of decision-making by offering insight into cross-domain architecture relations, typically through projections and intersections of underlying models, but also by means of analytical techniques. Typical examples are cross-reference tables, landscape maps, lists, and reports. ◦ Informing: Informing viewpoints help to inform any stakeholder about the enterprise architecture, in order to achieve understanding, obtain commitment, and convince adversaries. Typical examples are illustrations, animations, cartoons, flyers, etc.
  • 31.  For characterizing the content of a view we define the following abstraction levels: ◦ Details: Views on the detailed level typically consider one layer and one aspect from the ArchiMate framework. Typical stakeholders are a software engineer responsible for design and implementation of a software component or a process owner responsible for effective and efficient process execution. Examples of views are a BPMN process diagram and a UML class diagram. ◦ Coherence: At the coherence abstraction level, multiple layers or multiple aspects are spanned. Extending the view to more than one layer or aspect enables the stakeholder to focus on architecture relations like process- uses-system (multiple layer) or application uses- object (multiple aspect). Typical stakeholders are operational managers responsible for a collection of IT services or business processes. ◦ Overview: The overview abstraction level addresses both multiple layers and multiple aspects. Typically, such overviews are addressed to enterprise architects and decision makers, such as CEOs and CIOs.
  • 32. Viewpoint Purpose Typical Stakeholders Purpose Examples Designing architect, software developer, business process designer navigate, design, support design decisions, compare alternatives UML diagram, BPMN diagram, flowchart, ER diagram Deciding manager, CIO, CEO decision-making cross-reference table, landscape map, list, report Informing employee, customer, others explain, convince, obtain commitment animation, cartoon, process illustration, chart Viewpoint Abstraction Levels Details software engineer, process owner design, manage UML class diagram, BPMN process diagram Coherence operational managers analyze dependencies, impact of-change views expressing relations like “use”, “realize”, and “assign” Overview enterprise architect, CIO, CEO change management landscape map
  • 33. Basic Viewpoints in Archimate
  • 34. Concepts and Relations Example It is typically used at the start of a design trajectory, when not everything needs to be detailed yet, or to explain the essence of an architecture model to non-architects that require a simpler notation.
  • 35. Concepts and Relations Example  The Organization viewpoint focuses on the (internal) organization of a company, a department, a network of companies, or of another organizational entity.
  • 36. Concepts and Relations Example  The Actor Co-operation viewpoint focuses on the relations of actors with each other and their environment..
  • 37. Concepts and Relations Example  The Business Function viewpoint shows the main business functions of an organization and their relations in terms of the flows of information, value, or goods between them.
  • 38. Concepts and Relations Example  The Business Process viewpoint is used to show the high-level structure and composition of one or more business processes.
  • 39. Concepts and Relations Example  Business Process Co-operation viewpoint is used to show the relations of one or more business processes with each other and/or with their environment..
  • 40. Concepts and Relations Example  Business Process The Product viewpoint depicts the value these products offer to the customers or other external parties involved and shows the composition of one or more products in terms of the constituting (business or application) services, and the associated contract(s) or other agreements.
  • 41. Concepts and Relations Example  The Application Behaviour viewpoint describes the internal behaviour of an application; e.g., as it realizes one or more application services. This viewpoint is useful in designing the main behaviour of applications, or in identifying functional overlap between different applications.
  • 42. Concepts and Relations Example  The Application Co-operation viewpoint describes the relations between applications components in terms of the information flows between them, or in terms of the services they offer and use.
  • 43. Concepts and Relations Example  This viewpoint is useful in designing or understanding the main structure of applications or components and the associated data; e.g., to break down the structure of the system under construction, or to identify legacy application components that are suitable for migration/integration.
  • 44. Concepts and Relations Example  It can be used in designing an application by identifying the services needed by business processes and other applications, or in designing business processes by describing the services that are available.
  • 45. Concepts and Relations Example  The Infrastructure viewpoint contains the software and hardware infrastructure elements supporting the application layer, such as physical devices, networks, or system software (e.g., operating systems, databases, and middleware).
  • 46. Concepts and Relations Example  Shows how applications are supported by the software and hardware infrastructure: the infrastructure services are delivered by the devices; system software and networks are provided to the applications.
  • 47. Concepts and Relations Example  This comprises the mapping of (logical) applications and components onto (physical) artifacts, such as Enterprise Java Beans, and the mapping of the information used by these applications and components onto the underlying storage infrastructure; e.g., database tables or other files.
  • 48. Concepts and Relations Example  It shows the structure of the information used in the enterprise or in a specific business process or application, in terms of data types or (object-oriented) class structures.
  • 49. Concepts and Relations Example  The Service Realization viewpoint is used to show how one or more business services are realized by the underlying processes (and sometimes by application components). Thus, it forms the bridge between the business products viewpoint and the business process view. It provides a “view from the outside” on one or more business processes.
  • 50. Example  There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relation for a natural partitioning of the entire set of objects and relations that belong to a model.
  • 51. Example  There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the “grouping” relation for a natural partitioning of the entire set of objects and relations that belong to a model.
  • 52. If you have one last breath use it to say...