Phase D – The Final Design Blueprint
After defining the detailed business model in Phase B and designing the data and application systems in Phase C, the ADM cycle proceeds to Phase D – Technology Architecture. This is the final design phase, where the logical components of the architecture are transformed into a concrete, physical blueprint for the technical infrastructure.
The main purpose of Phase D is to define the hardware, software, and network infrastructure required to support the applications and data that will deliver the business vision. It ensures the technology foundation is robust, scalable, and secure.
Key Inputs of Phase D
To begin Phase D, architects rely on the detailed designs from the previous phases:
- Target Data Architecture & Application Architecture: The detailed designs of the data and applications from Phase C. These documents provide the requirements for the underlying technology.
- Architecture Vision Statement: The guiding document that ensures the technology design aligns with the overall business goals.
- Architecture Principles: The principles that govern all architectural decisions, particularly those related to technology (e.g., Technology Independence).
- Organizational Context: Information about existing technical standards, vendor preferences, and IT skill sets.
Core Activities and Steps of Phase D
The activities in Phase D focus on developing a comprehensive model of the technology environment.
- Develop a Baseline Technology Architecture: A detailed inventory of the current technology stack, including hardware, software platforms, and network components. This provides a clear understanding of the existing infrastructure.
- Develop a Target Technology Architecture: Based on the requirements from Phase C, a blueprint for the future technology environment is designed. This involves:
- Identifying Required Technology: Specifying the types of hardware, operating systems, databases, and middleware needed.
- Utilizing the Technical Reference Model (TRM): A key TOGAF concept, the TRM provides a structural view of the components and services of the platform. It helps categorize and organize the technology components.
- Defining the Foundation Architecture: A set of common building blocks (or standards) that can be reused across the organization to promote efficiency and consistency.
- Perform Gap Analysis: A detailed comparison is conducted between the Baseline and Target Technology Architectures to identify the technical gaps. This helps determine what needs to be upgraded, purchased, or retired.
- Define Architecture Requirements: The technical specifications and requirements for the new infrastructure are formally documented.
Key Outputs of Phase D
The successful completion of Phase D produces several crucial outputs that guide the implementation and migration efforts.
- Target Technology Architecture: A comprehensive blueprint of the future technology environment, including diagrams of the technical infrastructure, specifications for hardware and software, and a list of technology components.
- Updated Gap Analysis Report: An updated analysis of the gaps, focusing on the technology domain.
- Architecture Requirements Report: A refined list of technical requirements for the technology solutions.
- Technology Roadmap: A preliminary plan outlining the major phases and steps for transitioning to the new technology architecture.
Conclusion
Phase D – Technology Architecture is the final design phase in the ADM, translating logical designs into a physical reality. By meticulously planning the underlying technology, architects can ensure that the entire enterprise architecture is not only functional but also secure, scalable, and resilient.
In our next article, we will move beyond design and into Phase E – Opportunities & Solutions, where we will begin to plan for the actual implementation of the architecture.
