--> Provides "a structure to organise + manage the artifacts" that've been produced as a part of the Architecture Development Process
Includes everything --> right from building blocks, deliverables, artifacts & the governance structures that're necessary for us to develop, manage and communicate Enterprise Architecture effectively 👍
Key Components encompassing this framework:-
- Architecture Building Blocks or ABBs
- Solution Building Blocks - SBBs
- Deliverables
- Artifacts
- Governance
Let's start :-)
--> Architecture Building Blocks
ABBs are more of "an abstract concept"
They're high-level components that describe certain aspects of an architecture.
They're the base --> the foundational elements of an architecture. Primarily describe "the functionality" an architecture should offer.
Key features:-
--> It's intangible, high-level and is not tied to a specific technology.
--> They're reusable and can be used across different projects/ architectures, and are aligned with industry/ organisational standards
--> Solution Building blocks
How do we differentiate these from ABBs?
SBBs are the tangibles...
They represent the abstract ABBs in a tangible, concrete form. So, they're the actual implementations, created at the time of Architecture Realisation.
They're associated with specific platforms/ technologies. They include the detailed specifics (deployed and maintained as a part of the Architecture)
📌 Please Note:-
ABBs:- Describe the functionality (Intangibles).
SBBs:- Actually implement the functionality described by the ABBs (Tangible, concrete)
--> Deliverables:- They're the outputs, the models, documents that're produced as a part of the Architecture development Process. They're they "key" factors in driving communication, governance and decision making.
- Architecture Vision:- High-level overview, describes the desired target state
- Architecture Definition Document :- Detailed Specifics including the models & mapping
- Transition Architecture:- Intermediate stages, They guide from teh current state to the target state
--> Artifacts:- Architectural atrifacts are like individual pieces of information, that describe an architecture from different perspectives. they're used to create deliverables, and could be in various frmats, matrices, catalogs, diagrams or even narratives
--> Architecture Governance:- Framework and processes that'll ensure the architecture is developed, managed and controlled, in a consistent manner
It's more around establishing roles, policies, responsibilities, procedures to guide, and monitor arch. activities
- Architecture Board :- Oversees the implementation of the architecture, and ensures it's alignment with the business objectives
- Compliance Reviews :- The Board would assess if the architectural practices conform with the standards/ guidelines, that've been defined in the preliminary phase
- Change control - AMnaging plus approving changes to the architecture
Artifact is an individual, detailes pience of information, represnting a specific view of the architecture. It could be a catalog, list, diagram, or a matrix. They're more granular
An artifact is more raw than a deliverable. A deliverable is a more comprehensive, purpose-driven document. It's formally reviewed, contractually specified. And it needs to have a purpose, --> defining requirements, defining vision,
Deliverable actually encapsulates a variety of artifacts. It's more structured and well-laid out Examples include:-
- Architecture Roadmap
- Architecture Vision
- Architecture Definition Doument (This could include the Application Portfolio Catalog and a variety of other artifacts)
- Transition Architecture
These are the crucial for driving governance, decision making, and stakeholder management
Very crucial part of the Enterprise Architecture:-
1 --> Strategic Organisation of Information --> Clarity, reusability across teams/ projects/ consistent management , documentation of architecture-related artifacts, amps up Clarity
2 --> ABBS , SBBs , deliverables --> Make sure we're addressing all parts of an architecture, and nothing is overlooked
3 --> Helps in an effective communication, among stakeholders : tech and non-tech, Common language of communication with regards to the architectural work
4 --> The components of this framework aid in linking the the business goals, with the IT solutions. Plus, some processes for Governance & Compliance
The architecture should very well-support the business objecives . <-- The Underpinning Statement of TOGAF