Enterprise Architecture (Draft version)

 Togaf Roadmap

 Part 1 : Introduction (Basic and core concepts)

 Part 2 : Architecture Development Method (ADM)

 Part 3 : ADM Guidelines and Techniques

 Part 4 : Architecture Content Framework

 Part 5 : Enterprise continuum

 Part 6 : Architecture Capability Framework

Preliminary Phase

Preparation and Initiation activities to setup ARCH Capability.

Architecture Vision (Phase A)

Trigger the project, 

Some KEY Definitions of EA.

Drivers :  These are the events, conditions or circumstances that motivate an enterprise to change some aspect of its goals and consequently its objectives. Please find out below examples of drivers.

• Legal or Regulatory - a new law governing Credit Card Usage
• Cultural or Social - acceptance of a product in a new market
• Financial and Economic - reduction in profit due to changes of an exchange rate for borrowed foreign capital
• Organizational or Cultural - high staff turn-over in a particular division or business unit.

Architecture Content Framework : Its follow the below three categories to describe the type of architectural work product within the context of use:

• A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.
• An artifact is a more granular architectural work product that describes an architecture from a specific viewpoint. Examples include a network diagram, a server specification, a use-case specification, a list of architectural requirements, and a business interaction matrix. Artifacts are generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things). An architectural deliverable may contain many artifacts and artifacts will form the content of the Architecture Repository.
• A building block represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions.

  Building blocks can be defined at various levels of detail, depending on what stage of architecture development has been reached. For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to "architectures" or "solutions".

• Architecture Building Blocks (ABBs) typically describe required capability and shape the specification of Solution Building Blocks (SBBs). For example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software.
• Solution Building Blocks (SBBs) represent components that will be used to implement the required capability. For example, a network is a building block that can be described through complementary artifacts and then put to use to realize solutions for the enterprise.

Architecture capability: Arch. Function or practices

Four major domais in EA:

Business ARCH 1) How businesses operate.

                            2) How the important business process do what they do by using the right capability

Data ARCH :  How to maintain/manage complex dataset & persist in different storage like Database, Excell, MS Document.

Application ARCH : 

Technology ARCH : Physical machine, Software

ARCH. Landscape : 

1) Strategic Arch (Enterprise level ARCH)  ----------------------Bajaj-------------------------------------

2) Segment Arch (Portfolio/ Program ARCH ) ----------------- Loans, Cards, Landing, Investments

3) Capability Arch (Project level Arch) ------------------------- Card (Credit, debit)

View and View 

Views and Viewpoints are closely related to the notion of communicating with stakeholders, who commonly have different needs when it comes to understanding the architectures and the way they describe the things of interest to them.

There is theoretically an infinite number of viewpoints and views but in practice it turns out that many groups of stakeholders will benefit from a common set of views and viewpoints. It should be remembered that many stakeholders perform a number of roles and so an individual’s needs might be satisfied by a number of different views from different viewpoints. The view is what can be seen from a viewpoint but it can have different representations depending upon what the stakeholders want to see, including level of detail, fidelity, filtering, stylizations and more. So a Chief Information Officer (CIO) and a Development Manager might want to view the applications that realize a given business capability in the current state architecture, but the CIO will want a simple list or diagram. The Development Manager on the other hand might want a detailed diagram of the same applications, showing interfaces and payload information. A number of methods and languages promote the idea of a Viewpoint Library consisting of a series of useful and commonly used viewpoints.

Preliminary Phase

This Preliminary Phase is about defining "where, what, why, who, and how we do architecture" in the enterprise concerned. The main aspects are as follows:

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

Phase A: Architecture Vision

The steps in Phase A are as follows:
- Establish the architecture project
- Identify stakeholders, concerns, and business requirements
- Confirm and elaborate business goals, business drivers, and constraints
- Evaluate capabilities
- Assess readiness for business transformation
- Define scope
- Confirm and elaborate Architecture Principles, including business principles
- Develop Architecture Vision
- Define the Target Architecture value propositions and KPIs
- Identify the business transformation risks and mitigation activities
- Develop Statement of Architecture Work; secure approval

The life cycle of TOGAF.

  Continue ...