This video looks at the key points of the Architecture Development Cycle (ADC) and how you might need to change the cycle depending on your usage of the ADM
In our previous video blog we explored how the ADM relates to the other parts of TOGAF. This week's video discusses the key points of the Architecture Development Method, otherwise known as the ADM.
What to do with the Architecture Development Method?
You don’t have to tailor the ADM to your needs, but you might want to adapt it to meet your enterprise, your geographic region, your industry sector – or so that it fits with other frameworks you might be using.
You might also need to change the cycle if you don’t have the ideal resources or competence to use ADM as published. You should also consider realistically the value that you will get from each cycle.
In fact the ADM is iterative, and each time you use the ADM you need to make a fresh decision about the breadth and level of detail that you need to define. Each time you use ADM it will be to meet a different need – so consider which architectural assets you can leverage, either from previous iterations of the cycle or external reference models.
The architecture development method is shown in this diagram –[ Figure 5-1] known as the crop circle diagram.
Each Phase of ADM is defined in detail in Part II of TOGAF, where the objectives and approach are defined, along with the inputs, steps and outputs for each Phase.
Requirements Management is a continuous phase, used by all of the other phases. Outputs become inputs to other phases. Initial versions of deliverables are shown as version 0.1, while a formally reviewed version becomes 1.0