TOGAF 9 Level 1 + 2 Exam Study Guide



Similar documents
Module F13 The TOGAF Certification for People Program

Developing Business Architecture with TOGAF

Background: Business Value of Enterprise Architecture TOGAF Architectures and the Business Services Architecture

ArchiMate and TOGAF. What is the added value?

EA vs ITSM. itsmf

Enterprise Security Architecture for Cyber Security. M.M.Veeraragaloo 5 th September 2013

Enterprise Architecture with TOGAF 9.1 and ArchiMate Henk Jonkers, Dick Quartel, Bas van Gils and Henry Franken

The Open Group Architectural Framework

In this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?

Contents Foreword Preface Acknowledgments Introduction to Technical Architecture Chaos and Control

Setting up an Effective Enterprise Architecture capability. Simon Townson Principal Enterprise Architect SAP

Adapting IT Governance Frameworks to Ensure Control and Visibility of Open Source

MPD Technical Webinar Transcript

Enterprise Architecture 101. (Includes numerous samples/ templates produced using TOGAF methodology) Shail Sood

TOGAF and ITIL. A White Paper by: Serge Thorn Merck Serono International SA

11 Tips to make the requirements definition process more effective and results more usable

TOGAF. TOGAF & Major IT Frameworks, Architecting the Family. by Danny Greefhorst, MSc., Director of ArchiXL. IT Governance and Strategy

Sparx Enterprise Architect for Business Analysts

Software Engineering Reference Framework

Modelling the Business Case Study 3 Attendance Monitoring Project and Enterprise Architecture

Business Architecture with ArchiMate symbols and TOGAF Artefacts

TOGAF TOGAF & Major IT Frameworks, Architecting the Family

Enterprise Architecture Process, Structure and Organization

Chap 1. Introduction to Software Architecture

44-76 mix 2. Exam Code:MB Exam Name: Managing Microsoft Dynamics Implementations Exam

California Enterprise Architecture Framework

White Paper What Solutions Architects Should Know About The TOGAF ADM

Space project management

PASTA Abstract. Process for Attack S imulation & Threat Assessment Abstract. VerSprite, LLC Copyright 2013

How to bridge the gap between business, IT and networks

BUY ONLINE AT:

Appendix 2-A. Application and System Development Requirements

Why & How: Business Data Modelling. It should be a requirement of the job that business analysts document process AND data requirements

How To Understand The Business Analysis Lifecycle

PROJECT MANAGEMENT PLAN CHECKLIST

Advanced Topics for TOGAF Integrated Management Framework

3SL. Requirements Definition and Management Using Cradle

CDC UNIFIED PROCESS PRACTICES GUIDE

Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see

Managing Successful Programmes

Business Process Discovery

LeadingAge Maryland. QAPI: Quality Assurance Performance Improvement

Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see

16 Steps for Conducting an Audit By Leita Hart-Fanta, CPA

Major Project Governance Assessment Toolkit

A Process is Not Just a Flowchart (or a BPMN model)

DEPARTMENT OF INFORMATICS. Scenario-based Analysis of Collaborative Enterprise Architecture Management Tools

What is a life cycle model?

Project Management Process

Enterprise. Enterprise Architecture. Organization & Change Management. Life Cycle TOGAF 9. QRS research

NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0

Basic Unified Process: A Process for Small and Agile Projects

The role of integrated requirements management in software delivery.

A Practitioner s View

Introduction to OpenUP (Open Unified Process)

User experience storyboards: Building better UIs with RUP, UML, and use cases

Enterprise Architecture Review

Service Transition Planning & Support A Practical Perspective

The Project Planning Process Group

An Enterprise Architecture and Data quality framework

Surveying and evaluating tools for managing processes for software intensive systems

The Cornwell Enterprise Architecture Maturity Dashboard

Goal Setting. Your role as the coach is to develop and maintain an effective coaching plan with the client. You are there to

CMII-100H. CMII Standard for Enterprise-Wide Configuration Management and Integrated Process Excellence. by the Institute of Configuration Management

Issues in Internet Design and Development

Requirements Elaboration

It is vital that you understand the rationale behind the correct answer(s) as wel as the incorrect answer options.

Syllabus. REQB Certified Professional for Requirements Engineering. Foundation Level

1 Descriptions of Function

Software development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali

Bridging the IT Business Gap The Role of an Enterprise Architect

SOA Adoption Challenges

HOW TO GET THE MOST OUT OF YOUR ACCOUNTANT

System Development Life Cycle Guide

PROJECT RISK MANAGEMENT

Safety Management Systems (SMS) guidance for organisations

Software Requirements, Third Edition

Enterprise Architecture at Work

VIII. Project Management Glossary

Development Process Automation Experiences in Japan

Protecting Business Information With A SharePoint Data Governance Model. TITUS White Paper

Extended Enterprise Architecture Framework Essentials Guide

SysML Modelling Language explained

(Refer Slide Time: 01:52)

Benefits of the SAP Enterprise Architecture Framework for Enterprise SOA

A Practical Roadmap to SOA Governance Enterprise Integration Services

SAP Enterprise Architecture Framework Unveiled: Aligning IT to the Business

Enterprise Architecture Glossary by Set

Meta-Model specification V2 D

D6.1: Service management tools implementation and maturity baseline assessment framework

How To Write An Slcm Project Plan

Software Development in the Large!

IS&T Project Management: Project Management 101. June, 2006

Modelling, Analysing and Improving an ERP Architecture with ArchiMate

Overview of SAP BusinessObjects Risk Management 10.0

Achieving a Step Change in Digital Preservation Capability

Enterprise IT Architectures Enterprise Architecture Governance

Performance Development and Review Template Guide

MNLARS Project Audit Checklist

Managing Projects with ServiceNow at the University of San Francisco

Transcription:

TOGAF 9 Level 1 + 2 Exam Study Guide Created by Nik Ansell http://ae.linkedin.com/in/nikansell Introduction This document was created to help focus the study areas of TOGAF 9 students, studying for the Level 1 + Level 2 exams. High level study areas are defined as well as the information within each area which will help students to answer questions correctly in the exams. In some cases examples of questions in the exam are given to further focus an area of study. Level 1 Exam Tips This is a 40 question multiple choice exam which is closed book. It focuses on ensuring the student has an understanding of TOGAF, the TOGAF document, the ADM, TOGAF definitions, TOGAF techniques and tools. Passing the exam is partly based on being able to remember chunks of information (Objectives, Categories, Definitions etc) but also being able to demonstrate an understanding of particular aspects of the TOGAF framework. Questions in the exam will be a mix of things like Business Goals, Principles etc are defined in what ADM phase, A tool used to classify artifacts and provide a view of the architecture repository can be found in which section of the TOGAF document and Residual Risk is classified as Level 2 Exam Tips This is an 8 question scenario based exam and is open book. A PDF version of the TOGAF document is provided for each question. Learning where to find particular pieces of information in the document is a must for this exam as the search functionality can often provide too many results. Passing the exam is based on being able to identify which element/s of TOGAF are most useful by picking out key pieces of information within the scenario or specific question. The format of each scenario based question is typically: Long Scenario giving you a company background, an objective or set of objectives and how TOGAF 9 was selected for a particular piece of work o The bottom of the scenario is the most useful as the start (general company info etc) is often not that relevant to the question T O G A F 9 L e v e l 1 + 2 E x a m S t u d y G u i d e N i k A n s e l l 2 0 1 0 Page 1

A set of concerns or objectives i.e. things that must be addressed and why o This is generally the area of the scenario that will allow you build up what the question is really getting at The question o This is sometimes a simple question like You have been asked to define what steps you should take in order to best meet the objective or sometimes a longer question which give a bit more information to further focuses on an area to look for in the answers, like adding more concerns or constraints In some cases the scenario, question and answers are very wordy but actually quite simple. The longest scenario question I got was based around which artifacts to create which address specific concerns. There was a big long list of concerns worded something like: 1. Needs to be able to understand which systems are used by which business process 2. Must show what data needs to be shared 3. Must show the locations particular business functions are carried out 4. 5.. 6... The answers were like: A. Use a xx matrix, use a yyy diagram, a zzz matrix, use a bbb catalog B. Use a bbb catalog, a ccc matrix, a ppp diagram C. D... The best technique for answering a long and sometimes overwhelming question like this, is to use the paper/scratch pad the testing centre provides. Write each answer down, then mark off which concern is addressed by each answer. The one that addresses all the concerns if obviously the right answer EG: A. 1,2,5,6 B. 2,5 C. 1,6 D. 1,2,3,4,5,6 T O G A F 9 L e v e l 1 + 2 E x a m S t u d y G u i d e N i k A n s e l l 2 0 1 0 Page 2

Study Areas TOGAF Document Be comfortable with what topics are covered in each in each part of the TOGAF document (Part 1, Part 2 etc). This will make it easier to find things in the open book exam and you may also get a question related to where you find particular things in the book. I got a question on where you would find the Enterprise Continuum Ensure you have a good appreciation for the definitions (Concerns, Foundation Architecture, Reference Model, Application, Model etc) as you will get questions on these and the wording is sometimes very particular in the exam questions/answers ADM Memorize the Name, Order and Associated Letter of each ADM Phase Memorize the Objectives, Steps and Deliverables for each ADM Phase. The order of steps is also sometimes important. E.G I was asked a question on what comes before creating a baseline architecture in phases B,C,D Learn the Iterations that can be carried out within the ADM (Context, Definition, Governance, Planning) Be comfortable with the different ways the ADM can be tailored and for what reasons Learn the Techniques available and which phase they would be used (Architecture Patterns, Gap Analysis etc) Enterprise Continuum Be comfortable that the this is a view of the architecture repository to classify architecture and solution artifacts, to guide an architecture exercise from the generic to the organization specific and to promote reuse Memorize the architectures and solutions (Foundation, Common Systems Etc) available in the continuum and what you would likely see in each (E.G a Generic Supply Chain Process, Email Solution etc) You may get asked a question on where in the Enterprise Continuum you would find the TOGAF TRM (Foundation Architectures) or the IIIRM (Common Systems Architectures) You may also get asked a question on what the TRM or IIRM is used for Building Blocks Know the difference between Solution Building Blocks (Specific Implementation) and Architecture Building blocks (Fundamental Functionality), what they are used for and at what points in the ADM you define and refine them Generic Memorize the components of an Architecture Library (Architecture MetaModel, Landscape, Governance Log etc). Be comfortable with the purpose and TOGAF definition for each one Memorize the Architecture domains (Technology, Application, Data, Business) Memorize the Document and Metamodel Categorization (Core, Mandated, Recommended, Supporting) Understand the difference between a concern (key interest areas of a stakeholder) and a requirements (Derived from concerns, they are S.M.A.R.T and generally a need that must be fulfilled by an architecture or solution) T O G A F 9 L e v e l 1 + 2 E x a m S t u d y G u i d e N i k A n s e l l 2 0 1 0 Page 3

Memorize the 3 different Strategic Implementation Directions (Green Field, Evolutionary, Revolutionary) and what they mean Memorize the 3 different categories of change (Simplification, Incremental and Re-Architecting). What actions are required (Change Request or Architecture work) and how to classify a category of change. EG I got a question that asked to categorize a particular type of change proposed Stakeholders, Views, Viewpoints Be comfortable with the TOGAF stakeholder management techniques and what deliverables you would create to help you do this Remember a viewpoint is a perspective (where you are looking from) and generally specific to a stakeholder group Remember a view is what you see and is created to ensure that particular stakeholders can see an architecture from a point of view which matches their concerns Governance Know what is in the Governance Repository (Reference Data, Process Status, Audit Information) Learn what stage in the ADM (Phase G) this is carried out and how Learn the roles and responsibilities within any governance framework Be comfortable with the TOGAF techniques and process provided for governance activity (Compliance Assessments etc) Memorize the levels of Architecture Conformance, I remembered it this way: o Fully Conformant: Everything delivered and conforms o Conformant: Extra stuff delivered that does not confirm (I linked the or in conformant with the Aug in augment to memorize) o Compliant: Not everything was delivered o Consistent: Extra stuff and stuff missing o Irrelevant: Nothing delivered that matches the enterprise architecture Remember that Architecture Contracts are created in this phase Metamodel Be comfortable with why it exists, how it is used and the core entities (Business: Actor, Process, Function etc Technology: Platform Service etc) Scoping the Enterprise Memorize the different dimensions that can be used to refine the scope of an Architecture or Solution: o Breadth/Scope o Level of Detail (Enterprise/Strategic, Segment, Capability) o Time Horizon o Architecture Domain (Technology, Business etc) T O G A F 9 L e v e l 1 + 2 E x a m S t u d y G u i d e N i k A n s e l l 2 0 1 0 Page 4

Risk Management Memorize the steps in the process and what each step involves at a very high level: o Classification o Identification o Initial Risk Assessment o Risk Mitigation o Residual Risk Assessment o Risk Monitoring Be comfortable with the risk classification matrix and the categories of Effects (Catastrophic, Marginal etc), Impacts (Extremely High, High etc) and Frequencies (Frequent, Negligible etc) Footnote I hope you find this guide useful, my aim was to be helpful and guide study into the right areas, rather than simply provide lists of things or questions and answers to memorize. This way I feel helps students to fully appreciate and understand TOGAF so it will be easier to apply in their respective organizations. If you have any comments please feel free to pass them on via email to nikansell00@gmail.com or get in touch via linkedin at: http://ae.linkedin.com/in/nikansell. T O G A F 9 L e v e l 1 + 2 E x a m S t u d y G u i d e N i k A n s e l l 2 0 1 0 Page 5