Business Architecture Driven Solution Delivery

The Business Architecture Solution Delivery method ensures that you have alignment between the business layer and the supporting application & technology layers. Below you will find a short summary of how this is achieved.

1.Project Context

Make sure you identify your L1 processes from your Business Architecture and indicate the association to the project i.e.

Project refers to Process

Project adds Process

Project removes Process

Project changes Process

This allows one to have a view of which projects impact which processes in the enterprise and ensures that all design artifacts associated to the process is maintained for future change requests

2.Define (Update) L2 process

Define or design the L2 process associated to the parent L1 process indicating mostly sub-processes. Sub-processes with associated requirements (user stories) are then candidates for sea level use cases or user goal use cases. Each sub-process can have zero to many associated user stories (requirements).

3.Design sea level use case diagram

Harvest sub-processes with associated requirements from the L2 process diagrams and design the use case diagram. The purpose here is to understand the impact on human actors and technical actors (applications) and to estimate the development effort using use case point calculations. This drives the target solution architecture and can be complimented by adding the Logical Views, Implementation Views & Deployment Views

4.Detail Analysis & Design

Now you have an initial product backlog consisting of L2 processes, associated use cases (sea level) and associated user stories. The product backlog can now be prioritized and work can start on expanding the high priority use cases into the relevant detail i.e.