Skip to main content

TOGAF - ADM - Snapshot

Here is a snapshot of TOGAF - ADM Phases


·         Preliminary Phase

o   Defining the Enterprise
o   Identifying key drivers and elements in the organizational context
o   Defining the requirements for architecture work
o   Defining the architecture principles that will inform any architecture work
o   Defining the framework to be used
o   Defining the relationships between management frameworks
o   Evaluating the enterprise architecture’s maturity

·         Phase A – Architecture Vision
o   It starts with a ‘Request for Architecture Work’ from sponsoring organization to architecture organization
o   Key activities : Architecture Vision & Business Scenarios
o   Development of Business Scenarios
o   Define scope and Validate business principles, goals & drivers and establish EA KPIs
o   Stakeholder Analysis should be used to identify key players.
o   Identification of Business Transformation Risks

·         Phase B – Business Architecture
o   To develop business architecture to support agreed architecture vision
o   Describe baseline business architecture, target business architecture, analyze gaps between them
o   Select & develop relevant architecture viewpoints.

·         Phase C – Information Systems Architecture
o   Documenting fundamental organization of an Enterprise’s IT systems, embodied in major types of information & application systems
o   Two key artifacts can be developed either sequentially or concurrently :
§  Data Architecture
§  Application Architecture

·         Phase D – Technology Architecture
o   Map application components to Software & Hardware
o   Objective is to develop target technical architecture
o   Define physical realization of the architectural solution

·         Phase E – Opportunities & Solutions
o   Review target business objectives & capabilities
o   Consolidate gaps from phases B to D
o   Objective is identification of target delivery vehicles
o   It concentrates on how to deliver the architecture
o   Derive a series of Transition Architectures that deliver continuous business value
o   Generate & gain consensus on an outline Implementation and Migration strategy
o   Actual solutions (COTS, Packages etc.) are selected

·         Phase F – Migration Planning
o   Cost benefit analysis of the projects identified in the Phase E & risk assessment
o   Prioritization of the work packages, projects and building blocks
o   Finalize the Architecture vision & Architecture Definition document in line with the agreed implementation approach
o   Confirm the Transition architectures with stakeholders.
o   Finalize a detailed implementation & migration plan

·         Phase G – Implementation Governance
o   Objectives are
§  To formulate recommendations for each implementation project
§  To Govern and manage an architecture contract
§  To ensure conformance of deployed solution with Target Architecture
o   Defines an Operation Framework to ensure long life of deployed solution
o   Outputs are : Architecture Contract, Compliance Assessments, Change Requests, Implementation Governance Model

·         Phase H – Architecture Change Management
o   To ensure baseline architectures continue to fit for purpose
o   To maximize business value from architecture
o   To ensure that architecture achieves its original target business value
o   It is related to management of Architecture Contracts between architecture function and business users of the enterprise
o   Rule of thumb to identify the extent of change
§  If change impacts more than 2 stakeholders, then it may require architecture re-design and re-entry to ADM
§  If only one stakeholder, then may be a candidate for change management
§  If change can be allowed under dispensation, then candidate for change management.

·         Requirements Management
o   Objective is to define process to manage requirements for EA and its subsequent implementation

Let us see more on TOGAF - ADM in coming days 

Comments

Popular posts from this blog

Heterogeneous Cloud Integration

Heterogeneous integration is common scenario in the Enterprises where their IT portfolio is based on heterogeneous platforms. Various solution approaches such as message broker, messaging middleware, SOA – service based integration were employed to address heterogeneous integration challenges.

These solution approaches were good when the integration happens on premise, with in the data centers of an Enterprise. Problem here is non-availability of “elasticity”.

With the Enterprises started leveraging cloud platforms extensively for various solution aspects such as elastic computing, storage, it opens new capabilities that can be leveraged for heterogeneous integration. Also, similar to existing on premise scenario, Enterprises are also leveraging multiple cloud platforms to address their business needs. This scenario will pose same integration challenges as those that were faced within on premise datacenters

Within datacenters / on premise, integration products were expected to comply wi…

Lambda Architecture on Microsoft Azure

Gone are those days when Enterprises will wait for hours and days to look at the dashboards based on the old, stale data. In this fast world of BYOD, fitness gears and flooding of other devices, it is becoming super important  to derive out “actionable” information from huge volume of data / noise that is generated from these devices or any other data sources and act proactively on them  in real-time, to stay competitive.

At the same time, the need for having dashboards and other analytical capabilities based on the quality, cleansed, processed data still very much exists.

With the emergence of more data types and need to handle huge volume, shift is happening from the conventional data warehouse practice to cloud based data processing & management capabilities where high volume batch processing is possible at the optimized cost. Business scenarios demanding the need to process the data in real-time   More

Blockchain for a "Secured" AADHAAR

AADHAAR is gradually becoming the “Most Important” digital identity (like a social security number in US) for the citizens of India. It is considered to be more important than any other identities such as Passport, Driving License, PAN card etc. as it is being recognized as the “Mandatory” proof for the authenticity of an Indian citizen, for all the Govt. as well as private transactions, starting from availing the subsidized residential gas benefits  to operating a trading account or even getting a Passport. Because of this, the secured accessibility & immutability of that digital identity is very critical. The AADHAR card once issued to a citizen should not be subjected to change especially in terms of AADHAAR number, name of the person etc.; Any compromise on AADHAR can lead to problems related to mistaken identity. Storing AADHAAR information in a Blockchain platform is a natural choice , as Blockchain offers "Cryptographically" secured decentralized storage and facilit…