Architecting and designing : TOGAF : Building deliverables for the TOGAF Architecture Development Method : Building deliverables for phase D: Technology architecture
  
Building deliverables for phase D: Technology architecture
In Phase D of the TOGAF Architecture Development Method (ADM), you model the technology architecture of the organization.
Prerequisite
See the TOGAF documentation at:
http://www.opengroup.org/architecture/togaf9-doc/arch/
Phase D: Technology architecture
In Phase D of the TOGAF Architecture Development Method (ADM), you model the Technology Architecture of the organization.
The Technology Architecture breaks out into an eight-step method for developing the Technology Architecture, as shown in the image below.
The following information describes inputs and outputs for this phase that you create in System Architect. See the TOGAF documentation on the web for a full description of this phase:
http://www.opengroup.org/architecture/togaf9-doc/arch/
Viewpoints of phase D
Catalogs
The following catalogs are represented by applicable definition types, accessible via the applicable grouping in Explorer (Browser):
Technology Standards catalog
Technology Portfolio catalog
The Technology Portfolio catalog is available as an internal report as well - use System Architect Report Generator and open Togaf9Catalog.rpt in the Reports directory to run the report. Note that this report requires “iRMA” to be enabled as well, along with “Togaf”.
Matrices
System/Technology matrix: A matrix of System vs Technology definition types. To access, select View, Matrix Browser and in the Matrix Browser dialog. You will find this matrix in the TOGAF pane.
Core diagrams
Environments and Locations diagram: Depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally identifies the locations from which business users typically interact with the applications. You can use a Network Concept diagram for this (see Enabling advanced symbols for Network Concept diagrams).
See also Creating platform decomposition diagrams.
Extension diagrams
Processing diagram: Focuses on deployable units of code/configuration and how these are deployed onto the technology platform. You can use the UML Deployment diagram for this.
Networked Computing/Hardware diagram: The Network Concept diagram is ideal for this (see Enabling advanced symbols for Network Concept diagrams).
Communications Engineering diagram: Describes the method of sending and receiving information between resources on the network. It shows logical connections between client and server components and identifies network boundaries and network infrastructure required to physically implement those connections. For this, you can use the Network Concept diagram (see Enabling advanced symbols for Network Concept diagrams) or the UML Deployment diagram.