Open Group Standard

1. Enterprise System Architecture
Mohamed Saifedine Hadj sassi & Ines Beltaief

2. What’s TOGAF ?
 TOGAF, an Open Group Standard:
 A proven enterprise architecture methodology and framework used by
the world's leading organizations to improve business efficiency.
 The most prominent and reliable enterprise architecture standard,
ensuring consistent standards, methods, and communication among
enterprise architecture professionals.
 TOGAF helps practitioners avoid being locked into
proprietary methods, utilize resources more efficiently and
effectively, and realize a greater return on investment.

3. Who is in charge of TOGAF?
 The Open Group Architecture Forum
 Architecture Framework (TOGAF)
 Architecture Tools
 Certification
 TOGAF is freely available for internal use of
organizations.

4. TOGAF Timeline

5. TOGAF components
ADM
Enterprise Continuum
Resource Base

6. ADM : Architecture Development
Method
➢Objectives
➢Approach
➢Inputs
➢Steps
➢Outputs
For each phase, TOGAF has defined :

7. Architecture Development Method
A-H
phases

8. ADM Phase A: Architecture
Vision
Value chain of the DiscountTravel company

9. ADM Phase A: Architecture
Vision
Value chain diagrams
A value chain diagram provides a high-level orientation
view of an enterprise and how it interacts with the
outside world.

10. ADM Phase B:Business Architecture
The purpose of a Goal/Objective/Service diagram is
to define the ways in which a service contributes to
the achievement of a business vision or strategy.
Goal/Objective/Service diagrams

11. Goal/Objective/Service diagram
ADM Phase B : Business
Architecture

12. ADM Phase C :Information System
Architecture
The TOGAF class diagram as defined is situated
at an early, conceptual stage.
Class diagrams

13. Main business entities of the DiscountTravel domain, and their relationships

14. An environments and locations diagram depicts which locations host
which applications, identifies what technologies and/or applications are
used at which locations, and finally identifies the locations from which
business users typically interact with the applications.
Environments and locations diagrams
ADM Phase D : Technology Architecture

15.  The main
applications and
devices are
located in Dallas
In this diagram, devices (servers, workstations) are embedded into (deployed)
locations. Application components are in addition embedded within the devices.
ADM Phase D : Technology Architecture

16. ADM Phase E : Opportunities and Solutions

17. ADM Phase E : Opportunities and Solutions
A project context diagram shows the scope of a
work package to be implemented as a part of a
broader transformation roadmap. The project
context diagram links a work package to the
organizations, functions, services, processes,
applications, data and technology that will be
added, removed or impacted by the project.
Project context diagrams

18. Migration strategy in three steps
In this diagram, the "Travel" application
component will be developed in three
versions. The first one will still be based
on the TravelPortfolioManagement
(legacy) application, the second version
will work on its own.
Each version of the IS is represented by
a different "system element" in which
occurrences of application components
are deployed. This allows you to show
that the same application component is
used in several versions, or that an
application component in version N will
migrate into one or several application
components in version N+1.
Example

19. ADM Phase F : Migration Planning
The application migration diagram identifies application migration
from baseline to target application components. It enables a
more accurate estimation of migration costs by showing precisely
which applications and interfaces need to be mapped between
migration stages.
Application migration diagrams

20. ADM Phase E : Opportunities and Solutions

21.  provide for the continual monitoring
of such things as new developments
in technology and changes in the
business environment, and for
determining whether to formally
initiate a new architecture evolution
cycle.
ADM Phase H : Architecture Change
Management

22. In this diagram, the context is centered on the "DiscountTravelOrderingSite"
ADM Phase E : Opportunities and Solutions

23.  formulate recommendations for
each implementation project
 perform appropriate governance
functions while the system is
being implemented and deployed
 pensure conformance with the
defined architecture
ADM Phase G : Implementation
Governance

24.  not a static set of requirements,
but a dynamic process whereby
requirements for enterprise
architecture and subsequent
changes to those requirements
are identified, stored, and fed
into and out of the relevant ADM
phases.
 Changes such as changing
market conditions, new
legislation, etc.
ADM Architecture Requirements
Management

25. Enterprise Continuum
⇒ a “virtual repository” of all the architecture assets – models, patterns, architecture descriptions.

26. Resource Base
 a set of resources - guidelines, templates,
checklists, and other detailed materials
supporting the TOGAF ADM

27. Summary
TOGAF, an Open Group Standard, is:
❖ An effective, industry standard framework and method for enterprise
architecture.
❖ Complementary to, not competing with, other enterprise frameworks
❖ A repository of best practice
❖ Vendor, tool, and technology neutral
❖ A framework and method for achieving the “Boundaryless Information
Flow” vision