Part 2: Deliverables, Artifacts & Architectural Building Blocks
In Part 1 gave an overview of TOGAF ADM, ArchiMate & the BCLC / SDLC and how they integrate with one another.
Deliverables, Artifacts & Architectural Building Blocks (ABB’s)
It is key to understand the concept of architectural building blocks and how they relate to artefacts and how artefacts are then incorporated into deliverables.
One could view the architectural building blocks as those objects that you want to manage in your repository as “master” objects. With other words those objects that belong to the different architectural domain areas that needs to be managed. See sample of architectural building blocks per domain area that needs to be managed:
Architectural building blocks are then used to create models and matrices or artefacts. See illustration of typical artefacts and relationship to architectural building blocks below (sample):
The defined artefacts are then included in deliverables i.e. initial product requirement specifications (PRS v0.1), conceptual solution architecture document (CSAD), detail product requirement specifications (PRS v1.0), logical solution architecture document (LSAD), product design specification (PDS). See key artefacts that are included in the initial product requirement specification (PRS v0.1) as per the iBAS solution (integrated business architecture solution). The PDS (as well as all the other SDLC specifications / documents) are generated directly from the ARIS repository using the iBAS report script.
Here is a graphical representation of the PRS and the associated artefacts:
In part 3 I will explain the different options when executing the SDLC using waterfall vs. agile.