TOGAF 9 Foundation Part 1 Certified Exam (William Manning) (Z-Library)

Author: William Manning

商业

The first edition of this book is regarded as a classic in its field. Now, in an expanded and updated version of The Art of Service's book, the authors once again present a step-by-step guide to getting your TOGAF 9 Foundation Part 1 Certificate. With the worldwide surge in the demand for IT Professional skills, the TOGAF 9 Foundation Part 1 is one of the hottest certifications today. To pass the TOGAF 9 Foundation Part 1 exam, you need a no-gimmicks, no-nonsense book on the exam objectives. This is that book! This book HELPS you a great deal in passing the exam. The questions are realistic, very realistic. Let me put it this way. When you take the exam, most of the questions will ring bells. And most of them will connect to the questions in this book. you can save hundreds of dollars by using this book along with your study guide. Best-selling author William Manning offers concise yet comprehensive coverage of each topic included in the TOGAF 9 Foundation Part 1 exam. With a laser sharp focus on the exam objectives, this study guide goes beyond being a simple exam cram. It includes numerous questions and detailed answers modeled after the actual exam. Maximize your learning and minimize your study time! Can you imagine valuing a book so much that you send the author a

📄 File Format: PDF
💾 File Size: 1.9 MB
8
Views
0
Downloads
0.00
Total Donations

📄 Text Preview (First 20 pages)

ℹ️

Registered users can read the full content for free

Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.

📄 Page 1
The first edition of this book is regarded as a classic in its field. Now, in an expanded and updated version of The Art of Service’s book, the authors once again present a step-by-step guide to getting your TOGAF 9 Foundation Part 1 Certificate. With the worldwide surge in the demand for IT Professional skills, the TOGAF 9 Founda- tion Part 1 is one of the hottest certifications today. To pass the TOGAF 9 Foundation Part 1 exam, you need a no-gimmicks, no-nonsense book on the exam objectives. This is that book! This book HELPS you a great deal in passing the exam. The questions are realistic, very realistic. Let me put it this way. When you take the exam, most of the questions will ring bells. And most of them will connect to the questions in this book. you can save hundreds of dollars by using this book along with your study guide. Best-selling author William Manning offers concise yet comprehensive coverage of each topic included in the TOGAF 9 Foundation Part 1 exam. With a laser sharp focus on the exam objectives, this study guide goes beyond being a simple exam cram. It includes numerous questions and detailed answers modelled after the actual exam. Maximize your learning and minimize your study time! Can you imagine valuing a book so much that you send the author a “Thank You” letter? What makes this book a must-have? Is it the authors years of experience? The endless hours of ongoing research? The interviews with those who failed the exam, to identify gaps in their knowledge? Or is it the razor-sharp focus on making sure you don’t waste a single minute of your time studying any more than you absolutely have to? Actually, it’s all of the above. This book includes new exercises and sample questions never before in print. Offering nu- merous sample questions, critical time-saving tips plus information available nowhere else, this book will help you pass the TOGAF 9 Foundation Part 1 exam on your FIRST try. Up to speed with the theory? Buy this. Read it. And Pass the TOGAF 9 Foundation Part 1 Exam. Considering the increasing number of IT Professionals and their Organizations who want to be actively involved, this book, which leads to TOGAF 9 Foundation Part 1 Certification, should do at least as well as the first edition, which is a bestseller. TO G A F 9 Foundation Part 1 Exam Preparation
📄 Page 2
1 1 Foreword This Exam Preparation book is intended for those preparing for The Open Group Architecture Framework (TOGAF) Certification. The Art of Service has been an Accredited Training Organization for this program since 1998. The strategies and content in this book are a result of experience and understanding of the TOGAF distinctions and the exam requirements. This book is not a replacement for completing the course. This is a study aid to assist those who have completed an accredited course and are preparing for the exam. While it is not possible to pre-empt every question and content that MAY be asked in the exam, this book covers the main concepts covered within The Open Group Architecture Framework discipline. The advantages of using the TOGAF approach are that it provides: • A process for designing an information system, in terms of a set of building blocks. • Establishes a common vocabulary for use in the design, implementation and governance. • Includes a list of recommended standards to use with the organization’s enterprise architecture. • Contains a set of structured and rigorous methods for the implementation and governance of enterprise architecture. Due to licensing rights, we are unable to provide actual TOGAF Exams. However, the study notes and sample exam questions in this book will allow you to more easily prepare for a TOGAF exam. Ivanka Menken Executive Director The Art of Service
📄 Page 3
2 Write a review to receive any free eBook from our Catalog - $99 Value! If you recently bought this book we would love to hear from you! Benefit from receiving a free eBook from our catalog at http://www.emereo.org/, if you write a review on Amazon (or the online store where you purchased this book) about your last purchase! How does it work? To post a review on Amazon, just log into your account and click on the Create Your Own Review button (under Customer Reviews) on the relevant product page. You can find examples of product reviews on Amazon. If you purchased from another online store, simply follow their procedures. What happens when I submit my review? Once you have submitted your review, send us an email at review@emereo.org with the link to your review and the eBook you would like as our thank you from http://www.emereo. org/. Pick any book you like from the catalog, up to $99 RRP. You will receive an email with your eBook as a download link. It is that simple!
📄 Page 4
3 Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. Notice of Liability The information in this book is distributed on an “As Is” basis without warranty. While every precaution has been taken in the preparation of the book, neither the author nor the publisher shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations appear as requested by the owner of the trademark. All other product names and services identified throughout this book are used in editorial fashion only and for the benefit of such companies with no intention of infringement of the trademark. No such use, or the use of any trade name, is intended to convey endorsement or other affiliation with this book.
📄 Page 5
4
📄 Page 6
5 2 Contents 1 Foreword 1 2 Contents 4 3 The Open Group Architecture Framework 9 4 Exam Specifics 10 5 The Open Group Architecture Framework 11 5.1 TOGAF Overview 11 5.1.1 Defining Architecture 11 5.1.2 Approaches to Architecture Development 12 5.1.3 Architecture Capability 12 5.1.4 Architecture Integration 13 5.1.5 Interoperability 13 5.2 Components of TOGAF 14 5.2.1 Architecture Development Method 14 5.2.2 Architecture Content Framework 14 5.2.3 Enterprise Continuum 15 5.2.4 Architecture Repository 15 5.2.5 Architecture Capability Framework 15 5.3 The Enterprise Continuum 17 5.3.1 Basics of the Enterprise Continuum 17 5.3.2 Components of the Enterprise Continuum 18 5.3.3 Technical Reference Model (TRM) 18 5.3.4 Standards Information Base (SIB) 20 5.3.5 Integrated Information Infrastructure Reference Model (III-RM) 21 5.4 Architecture Governance 22 5.4.1 Benefits of Architecture Governance 22 5.4.2 Implementation of Architecture Governance 22 5.4.3 Architecture Governance Framework 23 5.4.4 Architecture Board 24 5.4.5 Architecture Compliance 24 5.4.6 Architecture Contracts 25 5.4.7 Architecture Content Framework 25
📄 Page 7
6 5.4.8 Stakeholder Management 28 5.5 Architecture Views and Viewpoints 29 5.5.1 Terms Related to Views 29 5.5.2 Core Taxonomy of Views 29 5.5.3 Common Views and Viewpoints 30 5.6 Building Blocks and the ADM 31 5.6.1 Architecture Building Blocks 31 5.6.2 Solution Building Blocks 31 5.6.3 Building Blocks 32 6 The Architecture Development Method 33 6.1 The ADM Phases 33 6.1.1 Preliminary 33 6.1.2 A. Architecture Vision 34 6.1.3 B. Business Architecture 37 6.1.4 C. Information Systems Architectures 39 6.1.5 D. Technology Architecture 43 6.1.6 E. Opportunities and Solutions 45 6.1.7 F. Migration Planning 48 6.1.8 G. Implementation Governance 50 6.1.9 H. Architecture Change Management 51 6.1.10 Requirements Management 54 6.2 Adapting the ADM 56 6.2.1 Techniques for Architecture Development 56 6.2.2 Architecture Partitioning 56 6.2.3 Architecture Patterns 57 6.2.4 Architecture Principles 58 6.2.5 Risk Assessments 59 6.2.6 Gap Analysis 60 6.2.7 Service Oriented Architectures 61 6.2.8 Applying Iteration 61 6.2.9 Business Scenarios 62 6.2.10 Security Architectures 63 6.2.11 Architecture Skills Framework 64
📄 Page 8
7 7 Architecture Reference Materials 65 7.1 Common Principles 65 7.2 Architecture Artifacts 70 7.2.1 Architecture Contract 70 7.2.2 Architecture Definition Document 71 7.2.3 Architecture Principles 71 7.2.4 Architecture Repository 71 7.2.5 Architecture Requirements Specification 72 7.2.6 Architecture Roadmap 72 7.2.7 Architecture Vision 73 7.2.8 Capability Assessment 73 7.2.9 Change Request 73 7.2.10 Communications Plan 74 7.2.11 Compliance Assessment 74 7.2.12 Implementation and Migration Plan 74 7.2.13 Implementation Governance Model 75 7.2.14 Organizational Model for Enterprise Architecture 75 7.2.15 Request for Architecture Work 75 7.2.16 Requirements Impact Assessment 76 7.2.17 Statement of Architecture Work 76 7.2.18 Tailored Architecture Framework 77 7.2.19 Transition Architecture 77 7.3 Glossary 78 8 Practice Exam 83 8.1 Refresher “Warm up Questions” 83 9 Answer Guide 97 9.1 Answers to Questions 97 10 References 106 11 Index 107
📄 Page 9
8
📄 Page 10
9 3 The Open Group Architecture Framework The Open Group is a consortium neutral to vendor and technology and intent on creating open standards and global inter-operability to enable access to integrated information within and between enterprises. One of the certification programs, The Open Group Architecture Forum (TOGAF), provides an opportunity for service providers and tool vendors to demonstrate their products and service ability to support the enterprise. TOGAF is an industry standard architecture framework to develop information systems architecture within the enterprise using the TOGAF Architecture Development Method (ADM). Certification for TOGAF comes in two levels or parts: Foundation and Certified. • Foundation Certification demonstrates a candidates knowledge of the terminology and basic concepts of TOGAF, as well as the core principles. • The Certified level shows a candidate’s ability to apply their knowledge of TOGAF. The TOGAF 9 Part 1 exam covers the following eleven topics: 1. Basic Concepts 2. Core Concepts 3. Introduction to the ADM 4. The Enterprise Continuum and Tools 5. ADM Phases 6. ADM Guidelines and Techniques 7. Architecture Governance 8. Architecture Views, Viewpoints and Stakeholders 9. Building Blocks 10. ADM Deliverables 11. TOGAF Reference Models The TOGAF 9 Part 2 exam draws its questions from the following topic areas: • ADM Phases: Project Establishment • ADM Phases: Architecture Definition • ADM Phases: Transition Planning • ADM Phases: Governance • Adapting the ADM • Architecture Content Framework • TOGAF Reference Models • Architecture Capability Framework
📄 Page 11
10 4 Exam Specifics TOGAF 9 Part 1 – Foundation exam is comprised of 40 simple multiple choice questions to be completed in one hour. A candidate must pass the exam with 55% of the questions answered correctly. There are no prerequisites to take this exam. TOGAF 9 Part 2 – Certified exam is comprised of eight complex scenario-based questions with gradient scoring to be completed in 90 minutes. A candidate must pass with a score of 60% or better. In order to take the exam, the candidate must be certified to TOGAF 9 Foundation or take and pass the Part 1 exam on the same day from the same test provider providing the Part 2 exam. This test is open book. The exams can be taken as separate exams or as a combined exam. If taken as a combined exam, the above rules still apply to each section of the combined exam (i.e. part 1 and part 2). The Open Group exams are proctored by Prometric Services. Scheduling and location of test sites can be obtained at www.prometric.com. Tests are conducted at a testing center. Two valid forms of ID are required when arriving at the center. Training in TOGAF is required and a voucher for completing training, self-study or classroom is required. If a candidate fails an exam, they must wait at least one month before retaking.
📄 Page 12
11 5 The Open Group Architecture Framework 5.1 TOGAF Overview The Open Group Architecture Framework (TOGAF) provides several opportunities for enterprise architects and IT organizations, including: • An iterative process model supported by best practices • A re-usable set of existing architecture assets • Methods and tools for the acceptance, development, use, and maintenance of an enterprise architecture 5.1.1 Defining Architecture The definition of ‘architecture’ from ISO/IEC 42010:2007 is: “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.” TOGAF supports this definition by remaining consistent with the terminology of the ISO/IEC 42010:2007 but views the meaning of ‘architecture’ differently based on the context used. For TOGAF, architectures are: • A formal description of a system or detailed plan of a system at the component level for guiding implementation. • The structure of components, their relationships to each other, and the principles and guidelines underlining there design and evolution over time. An enterprise architecture is comprised of four commonly accepted domains: • Business Architecture • Data Architecture • Applications Architecture • Technology Architecture
📄 Page 13
12 5.1.2 Approaches to Architecture Development On large scale, complex architecture development projects, the focus and scope of the project is a critical component to the project’s success. Two approaches are typically adopted: • Vertical Approach—enterprise is divided into segments representing independent business sectors • Horizontal Approach—enterprise is divided into architecture domains 5.1.3 Architecture Capability Creating architecture for an enterprise requires the organization to have the business capability to support the architecture through structures, roles, responsibilities, skills, and processes. TOGAF architecture capability builds on the Architecture Repository and Enterprise Continuum by identifying the architecture components providing the capability and their relationships to each other. The components include: • Skilled Resource Pool • Roles and Responsibilities • Contracts • Projects and Portfolios • Governance of Projects and Portfolios • Business Operations • Governance Bodies Enterprise Architectures look to establish capabilities in the areas of: • Financial Management • Performance Management • Service Management • Risk Management • Communications and Stakeholder Management • Quality Management
📄 Page 14
13 • Supplier Management • Configuration Management • Environment Management 5.1.4 Architecture Integration Integrating individual architectures provide the foundation for interoperability, migration, and conformance between those architectures. Referred to as a meta-architecture framework, its purpose is to: • Provide a basis for understanding how components fit into the overall framework • Enable architectural models to be created that focus on enterprise-level capabilities • Define the conformance standards to enable maximum leverage and re-use of architecture components 5.1.5 Interoperability Interoperability is categorized often in the following classes: • Operational or Business Interoperability—defines the sharing behaviors for business processes • Information Interoperability—defines the sharing behaviors for information • Technical Interoperability—defines the sharing behaviors for technical services The Enterprise Application Integration (EAI) defines interoperability in terms of: • Presentation Integration/Interoperability—provides a common look and feel approach • Information Integration/Interoperability—corporate information is seamlessly shared between corporate applications to obtain a common set of client information • Application Integration/Interoperability—corporate functionality is integrated and shared to prevent duplicate applications • Technical Integration/Interoperability—common methods and shared services for the communication, storage, processing, and access to data in the application platform and communications infrastructure domain
📄 Page 15
14 5.2 Components of TOGAF 5.2.1 Architecture Development Method The Architecture Development Method (ADM) is the core component of TOGAF, providing a tested and repeatable process for developing architectures. The phases of the ADM include: • Preliminary—prepares the organization • Architecture Vision—sets the scope, constraints, and expectations • Business Architecture—develops baseline and target architectures for Business Architecture • Information Systems Architecture—develops baseline and target architectures for Information Systems Architecture • Technology Architecture—develops baseline and target architectures for Technology Architecture • Opportunities and Solutions—performs initial implementation planning • Migration Planning—analyses costs, benefits, and risks • Implementation Governance—provides architectural oversight to implementation • Architecture Change Management—provides continual monitoring and a change management process • Requirements Management—validates and enforces business requirements 5.2.2 Architecture Content Framework The output of the ADM comes in many forms. To ensure consistency, the Architecture Content Framework defines the type of architectural work product found, such as: • Deliverable—a formally agreed upon work product of the project output • Artifact—an architectural work product describing the architecture from a specific viewpoint • Building Block—a component of business, IT, or architecture capability combined with other building blocks to create architectures and solutions. Building blocks typically include: о Architecture Building Blocks (ABB) о Solution Building Blocks (SBB)
📄 Page 16
15 5.2.3 Enterprise Continuum Architecture and solution artifacts are collected into an Architecture Repository. The Enterprise Continuum is a comprehensive view of this repository and is comprised of two concepts: • Architecture Continuum • Solutions Continuum The Architecture Repository stores architecture output at different levels of abstraction created by the ADM. In conjunction with the Enterprise Continuum, stakeholders and providers have the means to understand and cooperate within the architecture. 5.2.4 Architecture Repository The primary components of the Architecture Repository include: • Architecture Metamodel—the application of an architecture framework for a specific enterprise • Architecture Capability—the parameters, structures, and processes supporting the governance of the Architecture • Architecture Landscape—the architecture view of building blocks currently in use within the enterprise • Standards Information Base (SIB)—the standards requiring compliance for architectures • Reference Library—provides the guidelines, templates, patterns, and reference materials to leverage during the creation of the enterprise • Governance Log—a record of governance activity across the enterprise 5.2.5 Architecture Capability Framework The Architecture Capability Framework is based on the Capability Maturity Models (CMM), which provide an effective method for enabling an organization to gain control and improve its IT-related development processes in a gradual manner. Several models are available for use: • Capability Maturity Model Integration (CMMI)
📄 Page 17
16 • Software Acquisition Capability Maturity Model (SA-CMM) • Systems Engineering Capability Maturity Model (SE-CMM) • People Capability Maturity Model (P-CMM) • IDEAL Life Cycle Model for Improvement • IT Architecture Capabilities Maturity Model (ACMM) The ACMM is comprised of three sections: • The IT architecture maturity model • IT architecture characteristics of processes at different maturity levels • The ACMM scorecard Six levels of maturity are present for nine architecture characteristics: • The Levels о 0 None о 1 Initial о 2 Under Development о 3 Defined о 4 Managed о 5 Measured • The Characteristics о IT architecture process о IT architecture development о Business linkage о Senior management involvement о Operating unit participation о Architecture communication о IT security о Architecture governance о IT investment and acquisition strategy
📄 Page 18
17 5.3 The Enterprise Continuum The Enterprise Continuum is used to communicate and understand an individual enterprise, as well as the enterprises of a customer or vendor. Architecture is context-specific and, therefore, will differ from one enterprise to the next. The Enterprise Continuum provides the language to allow enterprises to work together. 5.3.1 Basics of the Enterprise Continuum The Enterprise Continuum is a combination of two concepts: • The Architecture Continuum—provides a method of defining and understanding the rules, representations, and relationships present in an information system. • The Solutions Continuum—supports the Architecture Continuum by providing a method to describe and understand the implementation of rules, representations, and relationships found in the Architecture Continuum. The content of the Enterprise Continuum is all the architecture assets that exist within the enterprise and the IT industry, including: • Models • Patterns • Architecture Descriptions Assets are generally available for re-use and the Enterprise Continuum acts as a catalog for these assets. The TOGAF Architecture Development Method is a process for moving from the TOGAF Foundation Architecture to an enterprise-specific architecture. The Enterprise Continuum is used to determine what assets already exist to make transition easier. TOGAF provides two reference models that could be included in an organization’s Enterprise Continuum: • The TOGAF Foundation Architecture—a set of generic services and functions that provide a foundation for more specific architectures to be developed • The Integrated Information Infrastructure Reference Model (III-RM)—based on the TOGAF Foundation Architecture to enable and support a Boundaryless Information Flow vision
📄 Page 19
18 5.3.2 Components of the Enterprise Continuum The Architecture Continuum is a composition of architectures, Architecture Building Blocks (ABBs), and architectural models used to create an enterprise-specific architecture. The Architecture Continuum is developed through four architectures, not phases, which address enterprise needs and business requirements in varying degrees of detail. The different architectures are: • Foundation Architectures—building blocks and standards that support all common systems architectures • Common Systems Architectures—provides guidance to the selection and integration of specific services used to create common solutions across multiple domains • Industry Architectures—integrates common systems components with industry- specific components to create solutions for target customer problems • Organization Architectures—represents the deployed solutions for a particular enterprise The Solutions Continuum consists of the architectures at each level of the Architecture Continuum and, in short, is considered an inventory or library of solutions available to an organization, specifically: • Products and Services—procurable hardware, software, or service components • Systems Solutions—a set of certified or branded products and services used to fulfill common requirements and capabilities • Industry Solutions—implementations of a specific Industry Architecture • Organization, or Enterprise, Solutions—combined implementations of industry solutions, system solutions, and products and services to fulfill specific requirements for an enterprise. 5.3.3 Technical Reference Model (TRM) The Technical Reference Model (TRM) is a component of the TOGAF Foundation Architecture, which provides a model and taxonomy of generic platform services. It is comprised of taxonomy and a graphic. The taxonomy provides a list of terms and a coherent description of the components and conceptual structure of an information system. The TRM graphic is a visual representation of the taxonomy.
📄 Page 20
19 The TRM has two common architectural objectives: Application Portability and Interoperability. The major entities of the TRM are: • Application Software • Application Platforms • Communication Infrastructure The entities are connected using the Application Platform Interface and the Communication Infrastructure Interface. Application software is categorized under: • Business Applications—used to implement business processes for a specific enterprise or vertical industry • Infrastructure Applications—provides general purpose business functionality The Application Platform is a single, generic entity of concept where a set of Application Software sits with the intentional objective of meeting an enterprise’s business requirements. The Application Platform Interface (API) is the connecting component between Application Software and the Application Platform. IT focuses on providing application portability, which requires the conformity of both applications and the platform to the interface. High-level services for the Application Platform are defined as: • Data Interchange Services • Data Management Services • Graphics and Imaging Services • International Operation Services • Location and Directory Services • Network Services • Operating System Services • Software Engineering Services • Transaction Processing Services • User Interface Services • Security Services • System and Network Management Services
The above is a preview of the first 20 pages. Register to read the complete e-book.

💝 Support Author

0.00
Total Amount (¥)
0
Donation Count

Login to support the author

Login Now
Back to List