Understanding TOGAF

TOGAF History.

TOGAF describes itself as a framework which is owned by The Open Group. The first version of TOGAF, developed in 1995, was based on the US Department of Defense’s Technical Architecture Framework for Information Management (TAFIM). Following on from this, The Open Group Architecture Forum has developed successive versions of TOGAF at regular intervals and published each one on The Open Group public website.

Each version of the TOGAF standard is developed collaboratively by the members of the Architecture Forum – currently more than 200 corporate members, including vendor and customer organizations. The development is carried out by architecture practitioners, with the content based on proven best practices that evolved within the participating member companies.

The first seven versions of TOGAF addressed technology architecture based on the adoption of architecture in businesses at the time each was written. In 2002, Version 8 (the ‘Enterprise Edition’) was published, and was followed by a series of improvements to Version 8.1 in 2003 and Version 8.1.1 in 2006. It expanded the scope of TOGAF from a purely technology architecture to an Enterprise Architecture, by including business and information systems architecture in the new version.

TOGAF Business Continuum

Business Change Process Model

Enterprise Architecture

Enterprise architecture is the description of the structure and behavior of an organization’s process, Information System, Technology, personal and organizational sub units, aligned with organizations core goals and strategic directions. TOGAF divides an enterprise architecture into four categories, as follows:

• Business architecture—Describes the processes the business uses to meet its goals
• Application architecture—Describes how specific applications are designed and how they interact with each other
• Data architecture—Describes how the enterprise datastores are organized and accessed
• Technical architecture—Describes the hardware and software infrastructure that supports applications and their interactions

TOGAF describes itself as a “framework,” but the most important part of TOGAF is the Architecture Development Method, better known as ADM. ADM is a recipe for creating architecture. A recipe can be categorized as a process.

ADM (Architecture Development Method).

The ADM forms the core of TOGAF. The result of contributions from many architecture practitioners. It is specifically designed to address enterprise’s business and IT needs by providing.

1. A set of architecture views (business, data, application, technology)
2. Guidelines on tools for architecture development
3. A set of recommended deliverables
4. Links to practical case studies
5. A method for managing requirements

The ADM is an iterative process which can manages the cases Over the whole process, Between phases and Within phases. ADM reconsiders  Scope, Detail, Schedules, milestones For each iteration. ADM Consider assets from: Previous iterations, Marketplace, according to availability, competence, and value.

• Preliminary Framework and Principals: – Prepare the organization for a successful architecture project.
• Requirement Management: – Ensure that very stage of a TOGAF project is based on and validates business requirements.
• Architecrure Vision: – Set the scope, constraints and expectations for a TOGAF project. create the Architecture Vision validate the business context create the Statement of Architecture Work.
• Business Architecture: – Develop Business Architecture Develop baseline and target architectures and analyze the gaps.
• Information System Architecture: – Develop Information Systems Architectures Develop baseline and target architectures and analyze the gaps.
• Technology Architecture: – Develop Technology Architecture Develop baseline and target architectures and analyze the gaps.
• Opportunity and Solutions: – Perform initial implementation planning. Identify major implementation projects.
• Migration Planning: – Analyze costs, benefits and risks. develop detailed Implementation and Migration Plan.
• Implementation Governance: – Provide architectural oversight for the implementation. Ensure that the implementation project conforms to the architecture.
• Architecture Change Management: – Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise.

To Be Continued………….

About Praveen Prakash

I am here to help you :)

PMP Process – Integration Management – Input, Tools an Outputs ›

Posted in TOGAF 9 Certification