Architecture Development Method (ADM)

Just hot out of the presentation.
I just had presented the TOGAF Architecture Development Method with the Development Team and here is how it goes. Basically Architecture Development Method or ADM as defined in Wikipedia

The Architecture Development Method (ADM) is applied to develop an enterprise architecture which will meet the business and information technology needs of an organization. It may be tailored to the organization’s needs and is then employed to manage the execution of architecture planning activities.

The process is iterative and cyclic. Each step checks with Requirements. Phase C involves some combination of both Data Architecture and Applications Architecture. Additional clarity can be added between steps B and C in order to provide a complete information architecture.

Performance engineering working practices are applied to the Requirements phase, and to the Business Architecture, Information System Architecture, and Technology architecture phases. Within Information System Architecture, it is applied to both the Data Architecture and Application Architecture.

This means its the method to follow when you are developing an architecture it is similar to Software Development Life Cycle which is a set of methodologies in developing your software and these methodologies form the framework for planning and controlling the creation of an Software or System.  One thing to make note of is that ADM is so flexible that you can adapt it in any scenarios you might have, you can change the order or even omit one, you can do it iteratively the whose cycle or as a part. To give you more information here is the slides I presented.

Slide 1 – Agenda

Slide 2 – ADM Cycles Defined

Slide 3 – ADM Iteration Concept

Slide 4 – Steps in a Phase

Slide 5 – Relationship of ADM with Parts of TOGAF

Slide 6 – Key Points of the ADM Cycle

Slide 7 – Adapting ADM

Slide 8 – ADM Governance

Slide 9 – Scoping Architecture Activity (Limits)

Slide 10 – Scoping Architecture Activity (Dimensions)

Slide 10 – Integrating Architecture Domains

Presenting TOGAF

Today I had presented TOGAF Enterprise Architecture Framework to our Technical Team, it will be a good introduction for them to understand Enterprise Architecture better as we are now implementing Architecture throughout our organization.

So why do Enterprise Architecture? A lot of reasons one is having a very efficient IT Operation, imagine you need something changed in your application lets say a field on a database table what would be the best way to know what applications will be affected by the change? Normally you just refer to people who know the application or if lucky you read through a good 100 page documentation. With EA combined with proper tools like Troux Architect its just a click of a mouse and magic you see all the dependencies (yeah you have t start creating relationships first and populate the repository either manual or automated).

Like this

Troux Architect

Another good reason will be reduced risk on future investments and better return on existing investment, faster cheaper and simpler procurement, the list goes on and on.  So to prevent lengthening this post here is the gallery of the slide show I presented.

Slide 1 : Agenda

Slide 2 : What is TOGAF

Slide 3 : Structure of TOGAF

Slide 3 : What is an Enterprise

Slide 5 : What is Architecture in context of TOGAF

Slide 6 : What is Enterprise Architecture

Slide 7 : Why do I need Enterprise Architecture

Slide 8 : Why do I need Enterprise Architecture

Slide 9 : What is an Architecture Framework

Slide 10 : Other Frameworks

Slide 11 : Zachman

Slide 12 : Clear Framework

Slide 13 : TOGAF

Slide 14 : Why do I need a Framework?

Slide 15 : Why Togaf is a suitable Framework?

Slide 16 : TOGAF Architecture Domains

Slide 17 : What does TOGAF Contain

Slide 18 : Architecture Development Method (ADM)

Slide 19 : ADM Techniques

Slide 20 : Architecture Content Framework

Slide 21 : Enterprise Continuum

Slide 22 : TOGAF Reference Models

Slide 23 : Architecture Capability Framework

Troux Architect