Introduction
The Architecture Development Method (ADM) is a comprehensive framework used in enterprise architecture to create and implement effective business solutions. At the core of the ADM lies the concept of building blocks, fundamental components that collectively shape the architecture to address specific business problems. This article explores the relationship between building blocks and the ADM across different phases, highlighting their roles, principles, and the iterative process of building block specification.
Basic Principles of Building Blocks in Architecture Design: Building blocks, as outlined in the ADM, serve as the foundation for constructing architectures. The architecture itself is a collection of building blocks depicted in a model, demonstrating how these blocks interconnect to fulfill overall business requirements. Several principles guide the use of building blocks in architecture design:
Relevance to Business Problem:
- An architecture should only include building blocks directly relevant to the specific business problem it aims to address.
Complex Relationships:
- Building blocks can have intricate relationships with one another. They may support multiple blocks or partially support a single block, reflecting the interconnected nature of business processes.
Conformance to Standards:
Building blocks should adhere to relevant standards, both in terms of their type and the enterprise’s overarching principles.
Building Block Design: The process of identifying building blocks involves classifying them into three categories: re-usable building blocks (e.g., legacy items), building blocks for development (e.g., new applications), and building blocks for purchase (Commercial Off-The-Shelf applications). The desired level of integration binds functions into building blocks, with legacy elements often treated as large blocks to maintain coherence.
In the early stages of enterprise architecture, building blocks are kept at a broad integration level. As the ADM progresses, more detailed views of building blocks emerge, aiding in implementation decisions, strategic planning, and assessing commonality and re-usability.
Building Block Specification Process in the ADM: The specification of building blocks is an evolutionary and iterative process within the ADM, occurring mainly in Phases A, B, C, and D. This process is gradual, responding to the evolving understanding of functionality, architectural constraints, and product availability. The key phases and steps in which building blocks are designed and specified include:
- Identification of ABBs:
In the early phases, the focus is on identifying Architecture Building Blocks (ABBs) required to meet business goals and objectives.
- Refinement to SBBs:
The selected ABBs undergo iterative refinement to create Solution Building Blocks (SBBs), which can be off-the-shelf or custom developed based on business needs.
- Evolutionary and Iterative Process:
The specification of building blocks using the ADM is evolutionary and iterative, reflecting the dynamic nature of architecture development. As more information becomes available, building blocks are refined to align with evolving requirements.
Example: Evolution of Architecture Building Blocks
Let’s consider an example scenario where a company aims to enhance its customer relationship management (CRM) system to improve overall customer satisfaction. In this context, we’ll walk through the iterative process of identifying, refining, and evolving Architecture Building Blocks (ABBs) through different phases of the Architecture Development Method (ADM).
Phase A: Architecture Vision
- Identification of ABBs:
The initial focus is on identifying ABBs that contribute to the CRM system enhancement. Key ABBs might include “Customer Database,” “User Interface,” “Communication Module,” and “Analytics Engine.”
- High-Level Refinement:
ABBs are refined at a high level, specifying their essential functionalities. For instance, “User Interface” may involve elements such as customer profiles, dashboards, and interactive features.
Phase B: Business Architecture
- Detailed Refinement:
In this phase, the “Customer Database” ABB is further refined to include specific data entities like customer profiles, purchase history, and feedback.
Phase C: Information Systems Architectures
- Technology Refinement:
The “Communication Module” ABB is refined to include specific technologies, such as email integration, chat support, and social media connectivity.
Phase D: Technology Architecture
- Vendor Selection:
For the “Analytics Engine” ABB, a decision is made to either develop a custom analytics solution or purchase a Commercial Off-The-Shelf (COTS) application.
Iterative Refinement Across Phases:
- Feedback Loop:
Throughout the ADM process, there’s a continuous feedback loop. As the architecture evolves, feedback from stakeholders and emerging business requirements may prompt revisions to ABBs.
Phase E: Opportunities & Solutions
- Impact Assessment:
Changes in business requirements or technology constraints may necessitate reassessment of ABBs. For example, a new regulation might require additional features in the “User Interface” ABB to ensure compliance.
Phase F: Migration Planning
- Implementation Considerations:
As migration plans are developed, the company might realize that certain ABBs, such as the “Communication Module,” need to be phased in gradually to minimize disruptions to existing processes.
Phase G: Implementation Governance
- Monitoring and Adjustments:
During the implementation phase, real-world challenges may arise. ABBs might need adjustments based on performance metrics, user feedback, or unforeseen technical issues.
Phase H: Architecture Change Management
- Continuous Improvement:
Even after the CRM enhancement is implemented, the ABBs are subject to ongoing improvements. This could involve adopting new technologies, responding to changing business needs, or incorporating lessons learned from the initial deployment.
In this example, the identification, refinement, and evolution of ABBs are not linear but occur iteratively throughout the ADM. Each phase informs the next, and feedback loops ensure that the architecture remains aligned with business goals and adaptable to changing circumstances. The iterative nature of this process allows the company to create a CRM system that is not only functional but also responsive to dynamic business environments.
Let’s summarize the flow of how Architecture Building Blocks (ABBs) are refined to Solution Building Blocks (SBBs) using a table:
| Phase | Activity | Example |
|---|---|---|
| A: Architecture Vision | Identify high-level ABBs relevant to CRM enhancement | Customer Database, User Interface, Communication Module, Analytics Engine |
| High-level refinement of ABBs | Refine User Interface to include customer profiles, dashboards, etc. | |
| B: Business Architecture | Detailed refinement of ABBs | Further refine Customer Database to include specific data entities |
| C: Information Systems Architectures | Technology refinement of ABBs | Refine Communication Module to include specific technologies |
| D: Technology Architecture | Decision on ABBs development or purchase | Decide to purchase a COTS Analytics Engine application |
| E: Opportunities & Solutions | Impact assessment on ABBs | Assess impact of new regulations on User Interface ABB |
| F: Migration Planning | Implementation considerations for ABBs | Plan gradual implementation of Communication Module ABB |
| G: Implementation Governance | Monitoring and adjustments for ABBs | Make adjustments to ABBs based on real-world challenges |
| H: Architecture Change Management | Continuous improvement of ABBs | Iterate on ABBs for ongoing improvements and adaptability |
This table provides a concise summary of how ABBs are identified, refined, and evolved iteratively through various phases of the Architecture Development Method (ADM), ultimately leading to the creation of Solution Building Blocks (SBBs) that align with the company’s enhanced CRM system.
Conclusion
The relationship between building blocks and the ADM is symbiotic, with building blocks serving as the elemental components that shape architectures in response to specific business challenges. The iterative nature of the building block specification process within the ADM ensures that architectures remain adaptable and aligned with evolving business needs. As enterprises navigate the complexities of architecture design, understanding and effectively leveraging building blocks in conjunction with the ADM is essential for achieving successful and sustainable business solutions.