Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

TOGAF - foundation - core stuff

No description
by

Patrice Kerremans

on 17 April 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of TOGAF - foundation - core stuff

TOGAF
Foundation
Core Stuff

ADM:
A BIT O' MIA
What is architecture?

A tool For AcPrUsMa
What should an Arch FW offer?A method for designing target state of the enterprise in terms of building blocks
a method for showing how those blocks fit together
a set of tools
a common vocabulary
a list of recommended standards
a list of compliant products
The value of a FW
avoids initial panic when scale of task becomes apparent
Codified common sense
tested in real life
baseline set of resources to reuse
What is an Architecture?

An architecture is the fundamental organization of a system embodied in:
its components,
the relationship between the components and the environment
and, the principles governing its design and evolution
What is a Business Architecture?

An business architecture is the fundamental organization of a BUSINESS embodied in:
its business processes and people,
the relationship between them and the environment
and, the principles governing its design and evolution
What is a IT System Architecture?

An IT system architecture is the fundamental organization of an IT SYSTEM embodied in:
its (major types of) {information} and {application systems} that process them,
the relationship between them and the environment
and, the principles governing its design and evolution
What is a Technology Architecture?

An technology architecture is the fundamental organization of an IT SYSTEM embodied in:
its hardware, software and communications technology,
the relationship between them and the environment
and, the principles governing its design and evolution
What is an Enterprise?

A collection of organizations that share a common set of goals.

As an EA you scope the enterprise of your Enterprise Architecture.
Architecture Types:
Business
Technology
Application
Data
1. Business Vision
2. Business Requirements
3. Legacy
4. Business Drivers
5. Goverance strategy & Principles
1. Business Scenarios
2. Programs & Projects
3. Architecture Governance
4. Architecture Contracts
5. People, process & technology
ENTERPRISE ARCHITECTURE
Why EA? Part 1 - INTERNAL FACTORS

- Good information managements = competitive advantage
- Avoid Current IT System syndromes:
- fragmented
- not flexible
- poorly understood
- complex
- Improve investment in IT
- today too much focus on IT and tactical development
- should be more strategic and more effectively applied
Why EA? Part 2 - EXTERNAL FACTORS
- Laws and regulations
- More extended enterprises
- More co-operative IT operations
- Greater publicity to failures
- Increase of litigations
- Audit Requirements
Business Benefits of EA
- helps organization achieve business strategy
- better TTM
- Streamlined Business processes and information across business units
- Better security, more reliability, less risk
- More efficient business and IT operation
- better ROI
- faster, simpler, cheaper procurement
ADM
ADM
Guidelines
& Techniques
Architecture
Content
Framework
Enterprise
Continuum
Reference
Models
Architecture
Capability
Framework
TOGAF 9.1
COMPONENTS
ADM: Iterative sequence of steps to develop an enterprise-wide architecture
ADM Guidelines & Techniques:
Guidelines to adapt the ADM
Techniques to apply the ADM
Architecture Content Framework: detailed model of architecture work products
Enterprise Continuum
model for structuring a virtual repository, and
method for classifying architecture and solution artifacts
Reference Models
Technical Reference Model
Integration Information Infrastructure Reference Model

Business
Vision
&
Drivers

Business
Capabilities
TOGAF Capability Framework
TOGAF Enterprise Continuum & Tools
TOGAF ADM & Content Framework
Architecture
Capability
Framework
ADM
ADM G&T
Enterprise
Continuum
RM
Arch Cont FW
The Architecture Content Framework:
-
drives higher consistency
in TOGAF outputs
-
provides checklist
for architecture outputs
- it
promotes better integration
of work products
- it
provides an open standard way to describe an architecture
- it
includes a detailed meta-model
The Core Content Metamodel: The core meta model provides a
minimum set of architectural content to support traceability across artifacts
. Additional metamodel concepts to support more specific or more in-depth modeling are contained within a group of extensions that logically cluster extension catalogs, matrices, and diagrams, allowing focus in areas of specific interest and focus.

Core Architecture Artifacts: set of artifacts intended to accompany the core content metamodel.
The following core terms are used:
Actor:
A person, organization, or system that is outside the consideration of the architecture model, but interacts with it.
Application Component:
An encapsulation of application functionality that is aligned to implementation structuring.
Business Service:
Supports business capabilities through an explicitly defined interface and is
explicitly governed by an organization
.
Data Entity:
An encapsulation of data that is
recognized by a business domain expert as a discrete concept
. Data entities can be tied to applications, repositories, and services and may be structured according to implementation considerations.
Function:
Delivers business capabilities closely aligned to an organization, but
not explicitly governed by the organization
.
Information System Service:
The
automated elements of a business service
. An information system service may deliver or support part or all of one or more business services.
Organization Unit:
A self-contained unit of resources with goals, objectives, and measures. Organization units may include external parties and business partner organizations.
Platform Service:
A technical capability required to provide enabling infrastructure that supports the delivery of applications.
Role:
An actor assumes a role to perform a task.
Technology Component:
An encapsulation of technology infrastructure that represents a class of technology product or specific technology product.
Architecture Repository: one part of the wider Enterprise Repository, which provides the capability to link architectural assets to components of the Detailed Design, Deployment, and Service Management Repositories.
At a high level, six classes of architectural information are expected to be held within an Architecture Repository:
The Architecture
Meta
model d
escribes the organizationally tailored application of an architecture framework
, including a method for architecture development and a metamodel for architecture content.
The Architecture
Cap
ability defines the
parameters, structures, and processes that support governance of the Architecture Repository
.
The Architecture
Land
scape
presents an architectural representation of assets in use
, or planned, by the enterprise at particular points in time.
The
S
tandards
I
nformation
B
ase
captures the standards with which new architectures must comply
, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.
The
Ref
erence
Li
brary
provides guidelines, templates, patterns, and other forms of reference material
that can be leveraged in order to accelerate the creation of new architectures for the enterprise.
The
Gov
ernance
Log

provides a record of governance activity
across the enterprise.

Enterprise Repository=SolRep + ReqRep + Architecture Rep
Architecture Rep = Meta Cap Land SIB RefLi
GovLog
The Enterprise Continuum provides an overall context for architectures and solutions and classifies assets that apply across the entire scope of the enterprise. The Architecture Continuum provides a classification mechanism for assets that collectively define the architecture at different levels of evolution from generic to specific. The Solutions Continuum provides the classification for assets to describe specific solutions for the organization that can be implemented to achieve the intent of the architecture.
Reference Models: Diagrams + Taxonomy(Vocabulary)
TRM: Technical Reference Model
III-RM: Integrated Information Infrastructure Reference Model

TRM
IIRM
Architecture Capability Framework provides guidance on establishing an operational EA practice
Architecture Development Method
Full transcript