This chapter provides an overview of the contents of Part III.

18.1 Guidelines for Adapting the ADM Process

The Architecture Development Method (ADM) process can be adapted to deal with a number of different usage scenarios, including different process styles (e.g., the use of iteration) and also specific specialist architectures (such as security). Guidelines included within this part of TOGAF are as follows:

• Applying Iteration to the ADM (see 19. Applying Iteration to the ADM) discusses the concept of iteration and shows potential strategies for applying iterative concepts to the ADM.
• Applying the ADM at Different Enterprise Levels (see 20. Applying the ADM at Different Enterprise Levels) discusses the different types of architecture engagement that may occur at different levels of the enterprise. This section then also discusses how the ADM process can be focused to support different types of engagement.
• Security Architecture and the ADM (see 21. Security Architecture and the ADM) provides an overview of specific security considerations that should be considered during different phases of the ADM.
• Using TOGAF to Define & Govern SOAs (see 22. Using TOGAF to Define & Govern SOAs) shows how SOA concepts can be supported by the TOGAF framework and the specific SOA considerations for different phases of the ADM.

18.2 Techniques for Architecture Development

The following techniques are described within Part III: ADM Guidelines and Techniques to support specific tasks within the ADM:

• Architecture Principles (see 23. Architecture Principles) - principles for the use and deployment of IT resources across the enterprise - describes how to develop the set of general rules and guidelines for the architecture being developed.
• Stakeholder Management (see 24. Stakeholder Management) describes Stakeholder Management, an important discipline that successful architecture practitioners can use to win support for their projects.
• Architecture Patterns (see 25. Architecture Patterns) provides guidance on using architectural patterns.
• Business Scenarios (see 26. Business Scenarios) describes the Business Scenarios technique, a method for deriving business requirements for architecture and the implied technical requirements.
• Gap Analysis (see 27. Gap Analysis) describes the technique known as gap analysis. It is widely used in the TOGAF ADM to validate an architecture that is being developed.
• Migration Planning Techniques (see 28. Migration Planning Techniques) describes a number of techniques to support migration planning in Phases E and F.
• Interoperability Requirements (see 29. Interoperability Requirements) describes a technique for determining interoperability requirements.
• Business Transformation Readiness Assessment (see 30. Business Transformation Readiness Assessment) describes a technique for identifying business transformation issues.
• Risk Management (see 31. Risk Management) describes a technique for managing risk during an architecture/business transformation project.
• Capability-Based Planning (see 32. Capability-Based Planning) describes the technique of capability-based planning.

The TOGAF document set is designed for use with frames. To navigate around the document:

• In the main Contents frame in the left margin of the page, click the relevant hyperlink to load the Contents List for that Part of the TOGAF document or go direct to a chapter within the document.
  
• Within a chapter you can select Previous and Next at the top and bottom of the page to move to the previous or next chapter, or select Home to return to the welcome page.
  

Downloads of the TOGAF documentation, are available under license from the TOGAF information web site. The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A book is also available (in hardcopy and pdf) from The Open Group Bookstore as document G091.