Integrating TOGAF ADM, ArchiMate, BPMN & UML into your SDLC (Part 1)

Part 1: Overview

What is TOGAF ADM?

The TOGAF ADM is the result of continuous contributions from a large number of architecture practitioners. It describes a method for developing an enterprise architecture, and forms the core of TOGAF. The Open Group

What is ArchiMate?

ArchiMate is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way. The Open Group

What is BPMN?

A standard Business Process Model and Notation (BPMN) will provide businesses with the capability of understanding their internal business procedures in a graphical notation and will give organizations the ability to communicate these procedures in a standard manner. Object Management Group

What is UML?

The Unified Modelling Language™ - UML - is OMG's most-used specification, and the way the world models not only application structure, behavior, and architecture, but also business process and data structure.  Object Management Group

What are BCLC / SDLC?

In the case of a business change lifecycle, this covers the process of managing all the stages of a product’s life from the original concept through design and manufacture to service and disposal. Investment can take place at any point during the cycle in order to lengthen the life of a product.

In the IT world, there is a similar concept known as the systems development lifecycle. This starts with the analysis of requirements and ends with the maintenance of the system. A systems development lifecycle typically goes through the stages of analysis, design, build, test and implementation. Following the implementation, the system moves into operation and needs to be maintained for the life of the system.

Tying it all together using ARIS?

BCLC / SDLC

The focus here is to describe the TOGAF concept of Deliverables, Artifacts & Building Blocks. Deliverables i.e. business requirement specifications (BRS) contain artifacts (models & matrices) that are constructed using architectural building blocks (objects). The key modelled deliverables are explained below when following a waterfall SDLC method:

1. Business strategy phase:
2. Portfolio demand phase:
3. Concept phase:
4. Scope phase: During the Scope Phase a "mille wide inch deep" view of the requirements (PRS initial: Product Requirement Specification V0.1) and envisaged solution (CSAD - conceptual solution architecture design) is created to:

• Identify the key business requirements
• Identify the key use cases
• Define the conceptual solution architecture
• Estimate the overall effort using use case point calculations
• Define the targeted implementation & migration plan
• Define the Define Phase iteration / sprints (if Agile)
• Define the target implementation & migration plan

1. Define phase: In the Define Phase an in-depth analysis (“inch wide, mile deep”) is performed to obtain a detailed understanding of the business needs as defined in the initial product requirements specification (PRS V0.1). Once these requirements are clearly defined, they are reviewed and agreed upon with client decision makers and key project stakeholders. The Define Phase includes:

• One or multiple detail product requirement specifications (PRS detail: V1.0) depending on the number of iterations identified during the Scope Phase.
• One or multiple logical solution architecture designs (LSAD) to realize the business requirements (BRS).
• Updated implementation & migration plan

1. Design phase: During the Design Phase, the system is designed to satisfy the requirements identified in the PRS V1.0.  The requirements identified in the Define Phase are transformed into a Product Design Specification (PDS) that accurately describes the design of the system and that can be used as an input to system development in the Build Phase. The PRS V1.0  is used as input into the Design Phase and is governed by the CSAD as defined during the Define Phase.
2. Build phase:
3. Test phase:
4. Deploy phase:

Part 2: Deliverables, Artifacts & Architectural Building Blocks