Saturday, July 10, 2010

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 

Thursday, July 1, 2010

Web to Mobile #1

Some of the highlights of the Gartner’s 2010 “End User Predictions” report:

  • By 2014, more than three billion of the world’s adult population will be able to transact electronically via mobile and Internet technology.

  • By 2015, context will be as influential to mobile consumer services and relationships as search engines are to the Web.

  • By 2013, mobile phones will overtake PCs as the most common Web access device worldwide.
These highlights indicate how important it is for every Enterprise to have a strategy in place for enabling their enterprise / consumer facing applications on the mobile devices. Even though there is a debate going on whether Native Mobile apps or mobile web apps are best, Enterprises cannot ignore the path in which existing applications should be web enabled, as it ensures a wider reach.

Any initiative on mobile enabling web applications will revolve around 2 key concepts:

  • Markups

  • Style sheets

Both of these ensure an optimized /tailored delivery of the content of a web application on mobile browsers. Without having understanding fundamentals behind these 2 concepts, no team can succeed in mobile enabling web applications.

Adding to these, 2 key building blocks of any mobile web applications are:

  • Content Adaptation Facility

  • Device Database

They are available both as “open source” softwares and as part of COTS products that are used for developing mobile web applications.

Let us see more on “web to mobile” in coming days J