togaf - a teaser for our traning course
TRANSCRIPT
Welcome to theTOGAF 9.1 Combined course
Version 5.1
Our Vision: Business Transformation made easy – aid our customers develop and change their organizations.
Our goal: To offer Scandinavian's best education, certifying, coaching and consultants within Business Transformation based on international standards and best practice.
Biner Academy Biner Consulting
Course purposeLevel 1Provide validation that the Candidate has gained knowledge of the terminology, structure, and basic concepts of TOGAF 9, and understands the core principles of Enterprise Architecture and TOGAF
Level 2Provide validation that in addition to the knowledge and comprehension of Level 1, the Candidate is able to analyze and apply this knowledge. The learning objectives at this level focus on application and analysis, in addition to knowledge and comprehension
COM
B: M00 S-
01
Target Audience
Individuals – who require a deeper understanding of TOGAF 9.
Professionals – who are working in an organization where TOGAF 9 has been
adopted and who need to participate in architecture projects and initiatives.
Architects – who will be responsible for developing architecture artifacts.– who wish to introduce TOGAF 9 into an architecture practice.– who want to achieve a recognized qualification to demonstrate their
detailed knowledge of TOGAF 9.
Reference MaterialC: M
00 S-05
http://www.togaf.net
http://www.theopengroupbookshop.comhttp://www.biner.se/bokshop
Course ModulesC: M
00 S-03
Basic Concepts of Enterprise
Architecture and TOGAF
Core Concepts of TOGAF
Preliminary Phase
Architecture Partitioning
Architecture Repository
Architecture Deliverables
Views, Viewpoints & Stakeholders
Building Blocks
Content Framework
Iteration Phase A: Architecture
Vision
ADM Guidelines and Techniques
Stakeholder Management
Business Scenarios Technique
TOGAF Reference Models
Enterprise Continuum and
Tools
Phase B: Business
Architecture
Phase C: Info Systems
Architectures – Data
Phase C: Info Systems Arch –
Application
Phase D: Technology Architecture
Architecture Requirements Management
Phase E: Opportunities and Solutions
Migration Planning
Techniques
Phase F: Migration Planning
Phase G: Implementation
Governance
Phase H: Architecture
Change Management
Architecture Governance
Architecture Maturity Models
Architecture Skills Framework
Guidelines for adapting the
ADM: Security
Guidelines for adapting the
ADM: SOA
Certification
Course structure
EpilogueAdapting TOGAF Certification
Governing the changeGoverning the solution projects Managing the architecture
Planning the architectural changeIdentifying solutions and Opportunities Creating the migration plan
Defining the architectureBusiness Architecture Data Architecture Application Architecture Technology Architecture
Initiate the architecture workPreparing the capability to execute Defining your vision
ProloguePracticalities Introduction
Detailed Agenda Day 1 & 2 CombinedDay 1
09:00 Course Introduction
09.30 Basic Concepts of Enterprise Architecture & TOGAF
10:00 Core Concepts of TOGAF
11:00 Break
11:15 Preliminary Phase
12:00 Lunch
13:00 Architecture PartitioningArchitecture Repository
14:00 Break
14:15 ADM Deliverables
15:00 Architecture Views, Viewpoints & Stakeholders
16:00 Break
16:15 Building BlocksArchitecture Content Framework
17:00 End
Day 2
09:00 Recap Day
09.30 Iterations
10:00 Phase A: Architecture Vision
11:00 Break
11:15 ADM Guidelines & Techniques
12:00 Lunch
13:00 Stakeholder Management
14:00 Break
14:15 Business Scenario Techniques
15:00 TOGAF Reference Models
16:00 Break
16:15 Enterprise Continuum & Tools
17:00 End
COMB: M
00 S-06
Detailed Agenda Day 3 & 4 CombinedCOM
B: M00 S-07
Day 3
09:00 Recap day 2
09.30 Architecture Development B-D
10:00
11:00 Break
11:15 Requirements Management
12:00 Lunch
13:00 Phase E: Opportunities & SolutionsMigration Planning Techniques
14:00 Break
14:15 Phase F: Migration Planning
15:00 Phase G: Implementation Governance
16:00 Break
16:15 Phase H: Architecture Change Management
17:00 End
Day 4
09:00 Recap day 3
09.30 Architecture Governance
10:00 Architecture Skills FrameworkArchitecture Maturity Models
11:00 Break
11:15 Adapting the ADM: SecurityAdapting the ADM: SOA
12:00 Lunch
13:00 Certification
14:00
14:15
15:00
16:00
16:15
17:00 End
What do the Exams Cover?
TOGAF 9 Part 1 Basic Concepts
3 questions Core Concepts
3 questions Introduction to the ADM
3 questions The Enterprise Continuum
4 questions and Tools
ADM Phases
9 questions ADM Guidelines and
6 questions Techniques
Architecture Governance
4 questions Architecture Views,
2 questions Viewpoints and Stakeholders
Building Blocks
2 questions ADM Deliverables
2 questions TOGAF Reference Models
2 questions
TOGAF 9 Part 2 Project Establishment
1 question ADM Phases: Preliminary, Aand Requirement Management
Architecture Definition
1 question ADM Phases: B, C and D
Transition Planning
1 question ADM Phases: E and F
Governance
1 question ADM Phases: G and H
Adapting the ADM
1 question Architecture Content
1 question Framework
TOGAF Reference Models
1 question Architecture Capability
1 question Framework
C: M00 S-
08
What Does it Take to Pass?
TOGAF 9 Part 1 (1 h 30 min*)
Pass mark 55% (22 or more points out of a maximum of 40). This exam comprises 40 questions in simple multiple choice format, covering the Level 1 learning outcomes. Each correct answer scores a single point.
TOGAF 9 Part 2 (2 h 15 min*)
Pass mark 60% (24 or more points out of a maximum of 40). This exam comprises 8 complex scenario questions, with gradient scoring. This exam is open book and covers the complete Level 2 learning outcomes. The correct answer scores 5 points, the second best answer 3 points, the third best answer 1 point. The distracter scores zero points.
TOGAF 9 Combined Part 1 and 2 (3 h 45 min*) This is a combined TOGAF 9 Part 1 and Part 2 examination for candidates who want to achieve Level 2 certification directly in a single examination. It consists of two sections, with pass marks as per the TOGAF 9 Part 1 and 2 examinations. Each section must be passed in order to obtain an overall pass mark.
* The times above includes additional time for individuals for whom English is a second language.
C: M00 S-
09
Basic Concepts of Enterprise
Architecture and TOGAF
Core Concepts of TOGAF
Preliminary Phase
Architecture Partitioning
Architecture Repository
Architecture Deliverables
Views, Viewpoints & Stakeholders
Building Blocks
Content Framework
Iteration Phase A: Architecture
Vision
ADM Guidelines and Techniques
Stakeholder Management
Business Scenarios Technique
TOGAF Reference Models
Enterprise Continuum and
Tools
Phase B: Business
Architecture
Phase C: Info Systems
Architectures – Data
Phase C: Info Systems Arch –
Application
Phase D: Technology Architecture
Architecture Requirements Management
Phase E: Opportunities and Solutions
Migration Planning
Techniques
Phase F: Migration Planning
Phase G: Implementation
Governance
Phase H: Architecture
Change Management
Architecture Governance
Architecture Maturity Models
Architecture Skills Framework
Guidelines for adapting the
ADM: Security
Guidelines for adapting the
ADM: SOA
Certification
Basic Concepts of Enterprise Architecture & TOGAF
The purpose of this Learning Unit is to introduce the basic concepts of Enterprise Architecture and TOGAF.
C: M00 S-
03
Learning Outcomes
You should be able to:
F: M02 S-01
Describe what an enterprise is Explain the purpose of an enterprise architecture List the business benefits of having an enterprise architecture Define what an Architecture Framework is Explain why TOGAF is suitable as a framework for enterprise architecture Describe the structure of TOGAF, and briefly explain the contents of each of
the parts Briefly explain what TOGAF is Explain what architecture is in the context of TOGAF List the different types of architecture that TOGAF deals with
F
What is Enterprise ArchitectureGoogle search for ‘definition of enterprise architecture’ results in39 300 qualified and 10 800 000 unqualified hits
F: M02 S-02
Gartner – “Enterprise architecture is
the process of translating business
vision and strategy into effective
enterprise change by creating,
communicating and improving the key
principles and models that describe
the enterprise's future state and
enable its evolution.”
Wikipedia – “An enterprise architecture (EA) describes the structure of an enterprise, its decomposition into subsystems, the relationships between the subsystems, the relationships with the external environment, the terminology to use, and the guiding principles for the design and evolution of an enterprise.”
MIT – "Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.“
John Zachman – “Enterprise
Architecture is the set of descriptive
representations relevant for
describing an Enterprise”
What is an EnterpriseF: M
02 S-03
“TOGAF defines enterprise as any collection of organizations that has a
common set of goals.“Enterprise #1
Enterprise #2
Enterprise #4
Enterprise #3
What is Architecture?ISO/IEC 42010:2007 defines "architecture" as:"The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.“
In TOGAF, "architecture" has two meanings depending upon the context:
F: M02 S-04
A formal description of a system, or a detailed plan of the system at component level to guide its implementation
The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time
The Need for Enterprise ArchitectureThere are two key reasons why you need enterprise architecture1. Critical to business survival and success2. Enables managed innovation within the enterprise
This by:
F: M02 S-05
A more efficient business operation
A more efficient IT operation
Better return on existing investment, reduced risk for future investment
Faster, simpler, and cheaper procurement
Benefits from Enterprise Architecture
F: M02 S-06
Business Benefits
It helps an organization achieve its business strategy
Faster time to market for new innovations
and capabilities
More consistent business processes
and information across
More reliability and security, less risk
Shared Benefits
Better traceability of IT costs
IT Benefits
Lower IT costs – design, buy, operate,
support, change
Faster design and development
Less complexity
Less IT risk
Benefits from Enterprise Architecture
Stakeholder Benefit type Benefit Rationale KPI
Business/IT Bettertraceability ofIT costs
Enterprise architecture provides greater understanding of the inter-related nature of business, applications, and infrastructure assets.
Most organizations can identify the individual cost of an asset. However, many cannot understand the cost of an asset as it relates within the organization with all its inter-relatedness andInterdependencies
% of IT OPEX that can be allocated to specific applications or business units
F: M02 S-07
Better traceability of IT costs
What is an Architecture Framework?
F: M02 S-
08It should describe a method for designing a target state of the enterprise in terms of a set of building blocks, and for showing how the building blocks fit together
An architecture framework is a foundational structure, or set of structures, which can be used for developing a broad range of different architectures
It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks
What is TOGAF?TOGAF is an architecture framework – The Open Group Architecture Framework.
TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture.
It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.
F: M02 S-09
Why TOGAF as the Framework for EA?
TOGAF Architecture Characteristics: Consistent Reflects stakeholder needs Employs best practice Current and future requirements
considered
The TOGAF process: Helps ”de-mystify”... ...”de-risk” complex architecture
design Provides a platform for adding
value
F: M02 S-10
Types of Architectures AddressedF: M
02 S-11
Business Architecture
Data architecture
Application architecture
Technology architecture
Defines the business strategy, governance, organization, and key business processes.
This architecture might be described by: organization catalogs, actor catalogs, goals, processes flow diagrams or use case diagram
ManageEngineering
Changes
Support Primary
HumanResources
BusinessPlanning Engineering Manufacturing Distribution
Manage PublicRelations
Provide LegalServices
PerformAudit
& Controls
ManageTransportation
MaintainFacilities
ProvideAdministrative
Services
Develop & TrackFinancial Plan
AppropriateFunds
ManagePayables
ManageReceivables
Manage Assets
Plan HumanResources
AcquireHumanResources
DevelopEmployees
ProvideEmployeeServices
Manage UnionActivities
Terminate ActiveEmployment
FormulateStrategy
Develop andMaintain
Business Plan
EstablishCustomer
Requirements
Obtain SalesCommitments
ProvideCustomerSupport
Research andDevelop
Technology
Engineer andDesign Products
Engineer andDesign
Processes
Design Toolsand Equipment
Plan MaterialRequirements
ProcureEquipment
Material & Tools
ManageSuppliers
PlanManufacturingRequirements
Perform QualityEngineering
ConvertResourcesto Product
ControlProduction
Maintain PlantEquipment &
Tools
ManageWarrantyActivities
EngineerPackages
Develop &ManageProduct Cost
Develop NewBusiness
ManageInventory
ShipProducts
Marketing &
SalesAdmin Finance Inventory
Types of Architectures AddressedF: M
02 S-12
Business Architecture
Data architecture
Application architecture
Technology architecture
Describes the structure of an organization's logical and physical data assets and data management resources.
This architecture might be described by: data entity catalogues, data entity/business function matrices and conceptual data diagrams or logical data diagrams
Types of Architectures AddressedF: M
02 S-13
Business Architecture
Data architecture
Application architecture
Technology architecture
Provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.
This architecture might be described by: application portfolios, , application/organization matrices, role/application matrices and and application communication diagrams
Types of Architectures AddressedF: M
02 S-14
Business Architecture
Data architecture
Application architecture
Technology architecture
Describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services.
This architecture might would be described by: technology standards, the technology portfolio, application/technology matrices and and environment & locations diagram
Structure of the TOGAF DocumentF: M
02 S-15
Architecture Development Method
Architecture Content Framework
ADM Guidelines & Techniques
ReferenceModels
Enterprise Continuum & Tools
Architecture Capability Framework
Introduction
Structure of the TOGAF DocumentF: M
02 S-16
Why the Specification was Divided
Work together as a whole but itallows for independent usage/specialization E.g. may wish to adopt only the ADM
F: M02 S-17
Summary
What is an Enterprise? “a collection of organizations that has a common set of goals”
What is Architecture?1. A formal description for implementation2. The structure of components for governance through their lifecycle
What benefits are received from EA? Business / Shared / IT Reduce e.g. risk in transformations
What type of architectures does TOGAF handle? Business / Data / Application / Technology
F: M02 S-18