[¤1]
D. Technology Architecture
[¤2] Phase D: Technology Architecture (Introduction)
[¤3] Objective Approach
Inputs Steps
Outputs
[¤5] The objective of this phase is to develop a technology architecture that will form the
basis of the following implementation work.
[¤8] Detailed guidelines for this phase, including Inputs, Steps, and Outputs, are given
under Target Technology Architecture - Detailed Description.
[¤9] Architecture Continuum
[¤10] As part of this Phase, the architecture team will need to consider what relevant
technology architecture resources are available in the Architecture Continuum.
[¤11] In particular:
-
[¤12] The TOGAF Technical Reference Model
-
[¤13] Generic technology models relevant to your organization's industry "vertical"
sector. For example:
-
[¤15] Technology models relevant to common systems architectures. For example:
[¤18] Inputs to this phase are:
-
[¤34] Technology Baseline Description.
-
[¤35] Review Business Baseline, Data Baseline and Application Systems
Baseline, to the degree necessary to inform decisions and subsequent work.
-
(m_iacob) 'as described under' instead of 'as describe under'
[¤36] Develop a baseline description of the existing Technology Architecture, to the extent
necessary to support the target Technology Architecture. The scope and level of detail to
be defined will depend on the extent to which existing Technology components are likely to
be carried over into the target Technology architecture, and on whether existing
architectural descriptions exist, as describe under Approach,
above. Define for each major hardware or software platform type:
-
[¤37] Name (short and long)
-
[¤38] Physical location
-
[¤39] Owner(s)
-
[¤40] Other users
-
[¤41] Plain language description of what the hardware / software platform is and what it is
used for
-
[¤42] Business functions supported
-
[¤43] Organizational units supported
-
[¤44] Networks accessed
-
[¤45] Applications and data supported
-
[¤46] System inter-dependencies (for example, fall-back configurations)
-
(m_iacob) 'and document them' instead of 'and document'
[¤47] To the extent possible, identify candidate technology architecture building blocks
(potential re-usable assets) and document.
-
[¤48] Draft the Technology Baseline Report: summarize key findings and conclusions, developing
suitable graphics and schematics to illustrate baseline configuration(s). If
warranted, provide individual Technology Baseline Descriptions as Annexes.
-
(m_iacob) 'Route the Baseline Description for review' instead
of 'Route for review'
[¤49] Route for review by relevant stakeholders, and incorporate feedback. Refine the Baseline
Description only if necessary.
-
[¤50] Target Technology Architecture. See detailed steps. Detailed activities
for this step, including Inputs, Activities, and Outputs, are given under Target Technology Architecture - Detailed Description.
[¤52] The outputs of this phase are:
-
[¤53] Statement of Architecture Work (updated if necessary)
-
[¤54] Technology Baseline Description - if appropriate
-
[¤55] Validated Technology Principles, or new Technology Principles (if generated here)
-
[¤57] Technology Architecture Report, summarizing what was done and the key findings
-
[¤58] Target Technology Architecture Version 1
-
[¤59] Technology Architecture - gap report
-
[¤60] Viewpoints addressing key stakeholder concerns.
-
[¤61] Views corresponding to the selected viewpoints.
[¤63] The outputs of this phase are:
[¤66] Copyright © The Open Group, 2002
Objective