At the end of this lesson you should be able to
Describe what an enterprise is
Explain the purpose of an Enterprise Architecture
Define further key terms and concepts related to Enterprise Architecture
Describe how the TOGAF Standard and the ArchiMate modeling language are related
2. Key Learning Points
At the end of this lesson you should be able to
Describe what an enterprise is
Explain the purpose of an Enterprise Architecture
Define further key terms and concepts related to
Enterprise Architecture
Describe how the TOGAF Standard and the
ArchiMate modeling language are related
3. The Enterprise
Enterprise
Collection of organizations
Common set of goals
May include locally distant organizations
Examples: Government agencies, corporation,
division, departments
Extended enterprise
Includes partners, suppliers and customers
4. Enterprise Architecture
Standard definition (TOGAF, Archimate)
Fundamental organization of a system
Embodied in its components
Relationship to each other
Principles of design and evolution
Variances
Organizing logic for business processes and IT
Infrastructure
Conceptual blueprint defining structure and operation
of an organization
Process of translating business vision and strategy
into effective enterprise change
5. Key concepts and terms
Stakeholders (Key roles with concerns)
Internal vs. External
Individuals, teams, organizations
Examples: Regulatory bodies, Suppliers, Customers, Internal
departments, Management (CEO, CIO, CFO, etc.)
Concern
Crucially important to stakeholders
Determine a system´s acceptability
E.g.: Security Architect: authentication, authorization, audit,
assurance, etc.
Viewpoint
Focus on particular aspects
Addresses a stakeholder´s particular concerns
Facilitate communication
6. Why EA???
More efficient business operation
More efficient IT operation
Better return on investment
Reduced risk for future investment
Procurement: faster, simpler and cheaper
7. Why EA reloaded (strategy
execution)
Missio
n
Vision
Strategy
Goals
Actions
Operations
As is To Be
Enterprise
Architecture
Culture
Processes Products
People
IT
8. ArchiMate version history
Based on IEEE 1471 (architecture description)
Developed from 2002-2004 (4M €) by Dutch
Government
Ownership since 2008: The Open Group
Archimate 1.0 – released in February 2009
ArchiMate 2.0 – A major update January 2012
Supports modeling throughout the TOGAF
Architecture Development Method
ArchiMate 2.1 – December 2013
A maintenance update addressing
Feedback and comments raised on ArchiMate 2.0
9. ArchiMate Modelling language
IEEE 1471 Architecture description = formal description
Reasoning about structural and behavioral properties
Of a system and its evolution
Define building blocks of overall information system
Provide a plan
Manage IT investment in a way that meets requirements
ArchiMate Specification
Common graphical modelling language for EA
Including transformation and migration planning
Motivations and rationale
Uniform representation for diagrams
Integrated approach
Different architecture domains
Underlying relations and dependencies
12. EA Frameworks
Zachmann
TOGAF
MDA
Others
Computation
Independent Model
(CIM)
Platform
Independent Model
(PIM)
Platform Specific
Model (PSM)
Business Model
Domain Model
Business Requirements
BPMN Model
UML Model
UML for Java
WS BPEL process model
13. TOGAF Standard and
Archimate
View
Points
Repository &
Reference Models
Process Language
TOGAF Standard
- Includes a process & techniques
- Defines reference models & repository
- Describes viewpoints
ArchiMate Standard
- Describes viewpoints
- Describes well-defined language
14. ArchiMate Core, Extensions and
TOGAF
Architecture Vision
Business Architecture
Information Systems
Architecture
Technology Architecture
Opportunities and
Solutions
Migration Planning
Implementation
Governance
Architecture Change
Management
Preliminary
Requirements
Management
Motivation
Extension
ArchiMate
Core
Implementation &
Migration Extension
