References

https://celestialconsulting.atlassian.net/wiki/display/DIS/DIS+-+TOGAF+AIDES+Home https://delicious.com/celestial_consulting http://www.danroam.com/the-back-of-the-napkin/ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm http://www.mikethearchitect.com/2012/10/togaf-templates.html http://www.iso-architecture.org/ieee-1471/afs/frameworks-table.html http://opengroup.co.za/presentations http://blog.buildingautomationmonthly.com/togaf-foundation-exam-study-guide/ Module 1 Module 2 Module 3 Module 4 Module 5 Module 6 Module 7 Module 8 Preliminary Phase Module 9 Architecture Governance Module 10 Business Scenario

Introduction

What is an Enterprise? A set of organisations with a common set of goals. Define the enterprise. Work out where the boundaries are.

What is an Architecture? Components, relationships, principles governing its design and evolution.

What is an Enterprise Architecture? Think of it as town planning... PESTLE - need to understand the external policies which affect the business and the internal policies Need to have governance to enforce this:

  1. Somebody has to make the rules - legislation
  2. Make a judgement, interpret the law
  3. Enforce the law

Legislators need to be independent of the implementors. Architecture is separate to IT.

Domains

  • Technology Architecture - hardware, software e.g. operating system, network
  • Data Architecture - databases, data governance, data ownership
  • Application Architecture - contains infrastructure applications (out of the box email, word, CRM etc) and business applications (customised for your needs)
  • Business Architecture - business processes, organisation, people - how you make money, strategy to grow, customer needs and channels

BIDAT = business, information, data, appliation, technology

Architecturally significant - only some things are significant - these have an impact on the 4 domains

The Parts of TOGAF

There are 6 + 1 (introduction) parts to TOGAF

  • ADM - Architecture Development Methods - the Process. TOGAF is not the only one. Others are RAFIM, FEAF, TEAF, Zachman, RM-ODP, MODAF, DODAF. However TOGAF is the only one with a solid process.
  • Architecture Content Framework - the Terminology.
  • ADM Guidelines and techniques - the things which help you do your job
  • Architecture Capability Framework - determine the capabilities required for the requirement e.g. data migration will require more data architects
  • Reference models - there are 2 reference models:
    • TRM - Technical reference model - TOGAF delivers a generic one out of the box which can be applied to any situation
    • IIIRM - Integrated Information Infrastructure reference model
      • client devices
      • brokering applications
      • data in context = information
  • Enterprise Continuum - windows / way of looking at architecural assets - either buy or build - buy them if it isn't your core competancy - find reuse either internally or externally in the market

Phases

Phase P - Preliminary phase

Setting up the shop - targetting the customers - what is the enterprise - set up the tools - cost model - set up the teams - create governance framework - define principles - nail down the terminolgy

Make sure you read: * the objectives - why you do something - purpose * the approach - how you do something

Objectives

Mode of engagement. There is a problem. Tell me what the problem is. Mode of engagement. Define what the problem is. Define the scope, analyse the problem. Mode of engagement. Find a solution.

Work out the value proposition is to the business...

  1. Define the capability.
  2. Implement it.

Approach

  1. Define the Enterprise - whats in whats out
  2. Why have we been brought in?
  3. Formalise the requirements
  4. Identify Architecture principles - usually done by senior people - short statement of the principle - implication - hwat happens if you do do it / don't do it
    • primacy of principles - obey the principles
    • maximise benefit to the enterprise - their must be a business benefit
    • compliance with the law
    • business continuity

Inputs

BOM mostly has the strategies, goals, tactics - often have a shareholders report (contains the BOM - business operating model)

Steps (more formalised way of approach)

  5. Tailor TOGAF and any other frameworks
  6. Tools - mood, repo

Technology principles - only use hardware from a certain vendor, open source first

Phase H - Architechture Change Management

  • Is this an architecturally significant change? Monitoring station for the requirements.
  • What is the impact?

Phase A

Draft of a 20,000 foot view of current point, target point and how we're going to get there. Do all phases (e.g. B, C, D and also E, F), but at 20,000 feet. Start by harvesting what is real, but turn it into logical models and specifications and write the specifications for the target state - then go to market and see what products there are and how they map onto your requirements / map onto your roadmap. Identify the products - NOT select (selection of products is done right at the end). Good architecture is rooted in the specifications / logical space NOT the solution space. Identify risks and start monitoring them through phase B, C, D, E F to ensure you are mitigating them. Identify initial risk and any residual risk.

20,000 foot quadrant - https://celestialconsulting.atlassian.net/wiki/display/DIS/Phase+A+-+Vision+Phase

The next 3 phases will tend to be done in the order of the biggest impact first. E.g. a data migration will start first to look at the data and therefore the information architecture.

Phase B - Business Architecture

Anything you do in phase B should support you in phases C and D. You can't change what you don't know - hence you need to spend a bit of time harvesting at Phase A. Understand the business, customers, channel, customer segments, relationships, connecting to customers. Only once you've done that can you look at your application, data and infrastructure. Business architecture quadrant.

Phase C - Information Architecture

Data - data models, CRUD, ownership of data, geographic location, policies around data Application - infrastructure / business specific Information architecture quadrant.

Phase D - Technology Architecture

Phase E -

Collaborative effort. First phase concerning implementing. Bring together the 4 quadrants from A, B, C, D and produce a more detailed quadrant from 2000 feet. Select solutions. Detailed planning of how you are going to move from current to planning. Involve the PMOs - they have the budget.

Phase F -

Continue to engage with the PMO - best to begin the engagement in phase E (or even earlier). Some things in this phase seem a bit late. Almost merged together into one phase. Show everybody all the stuff - key players - see what they think of the roadmaps you've drawn in E go back to E if necessary and tweak - back to F to validate etc

Tools and techniques (need to know - they name them in the exam)

Five key types of tables FOR THE EXAM

  1. Implementation Factor Assessment and Deduction Matrix (Impact table) WHAT you want to do v. IMPACT / HOW you're going to do it
  2. Consolidated Gaps, Solutions and Dependencies Matrix
  3. Architecture Definition Increments table (Roadmap)
  4. Transition Architecture State Evolution table - links to TRM - shows
  5. Business Value Assessment Technique - value vs risk - size of the circle indicates cost - colour is at RAG state - shows which projects should be canned - can do in Excel really easily if you put the data in

Tube maps for road maps - see samples in photos on the phone and also

Phase G - Implementation governance

Govern the implementation of the solution. Engage with the delivery team to deliver the solution.

Architecture repository

Confluence Archimate; Mega; System Architect; IServer; Mood

  • Repository of all the solutions
  • Meta model
  • Landscape - strategic (20,000 ft), segment (smaller chunks, e.g. time, gegraphy, business unit), capability
  • Organisation reference models
  • Standards - copy the standard rather than reference the standard (since they tend to change)
  • Governance Log - how did the decisions get made

Enterprise Continuum

The way you view your assets will determine how much reuse you can get.

Two rows:

  • Architecture C - specs
  • Solution C - real stuff

Four columns: Foundation = the lowest common denominator e.g. keyboards, screens Common > Industry specific > Organisation specific > Business specific (e.g. different versions) Left to right () Right to left (eclipse, netbeans, SMS) Common systems architecture - pattern which can apply to reoccuring problems

Core Content Metamodel

TOGAF have taken terminology from PRINCE, ITIL. They have used a technique called role based modelling. Core + Extensions - can't change anything

CMDs - catalogs, matrices, diagrams. For any domain we will have different types of these. There are templates for each domain based on the meta model. Stencils are provided based on excel and visio.

Governance

  • Enabler

  • Be creative within the constraints.

  • COBIT 4.1 - Control objectives for IT frameworks

  • Governance ensures business is conducted properly

  • Have processes in place

  • Monitor these

  • Need senior level buy in

  • Architecture Board - requires CIO / CTO, requires architect / EA, number of EAs (not everyone), people from the business to get buy in

  • PMO - Need to be lead by the architecture board

  • Architecture contract - phase G - need to govern the relationship between the business and the delivery team

  • Compliance

  • Don't have a governance framework / not even an compliance framework really

  • Irrelevant - doesn't match

  • Consistent - some parts match, some extra bits

  • Compliant - all parts match, not complete, but no extra

  • Comformant - all parts match, some extra bits

  • Fully conformant - exact match

  • Non conformant - similar to consistent - extreme conditions it starts to fail, it isn't the same actually

  • Do they already have any governance frameworks?

  • How will the EA integrate with theirs - work out in prelim phase - iseb fundamental test process, iso 9001/TickIT.

  • principles help your governance - TOGAF has a really good set of principles

TOGAF will gude the prince and itil frameworks - iserver repo supports

HSBC / ATOS governance framework examples TOGAF MAPPING 300 pdf atos and ns&i - 660m outsourcing - 15000 pages of schedule

governance and change control framework formulate req > assess impact > develop baseline and target arch (artefacts) > harvest current estate > develop current SBB > [develop current ABB > develop target ABB > develop target SBB] - change lifecycle

iServer repo - provider RW - director RO - director what if RW

Business Scenario

Business scenario is a textual represenation of a business process - check out case study interview v2.1.pdf TOGAF dictates "developing a business scenario" but there are much better things to use instead e.g. use cases, business process modelling HOWEVER for the purposes of the exam use the TOGAF stuff

1962 - monkey - BPM - purpose is to uncover business processes and why they are done like this.

for greenfield this works really well requirements > use cases > scenarios > models (class diagrams) > software and hardware

brownfield - need to do the reverse harvest the current > models > scenarios and use cases > requirements for change

Stakeholder Management (Communications Planning)

RASCI chart the other way Respnsible (doer); Accountablility (butt kicked); Support; Consulted (talk to, advise); Informed (kept in the loop) e.g. upgrade all the desktops - then go down with the stake holder on the left and identify who is in which group.

RASCI normal way actors on the left, activity on the top - put RASCI in each square...

Classify Stakeholder Positions

Stakeholder Analysis Matrix - Power / Interest Matrix - http://www.mindtools.com/ under Toolkit Stakeholder map - size of the circle / weight of the line Actor interaction graph - stateholders with the relationships mapped out The effect of change Stakeholder Map - stakeholder /

Phase A - Vision Phase

VIEW - Thing you see VIEWPOINT - perspective of what you see

Can't have a view without a viewpoint .dotx = template = stencil = viewpoint .docx = view

Concern + stakeholder + technique Stakeholders have concerns and we address the converns using a technique

Building block

A BB is something well defined interfaces.

A BB direct correlation to a TYPE in the metamodel (e.g. role, org unit, ) Role is a building block - can take you out and put someone else in. You are a building block - can take on different roles. Protocol is an interface, a way of communicating.

ABB - architecture building block - specficiation SBB - solution building block - real thing

When you describe a phone - ABB Create a standard with various people who can implement this -

Software

Specification - ABB Instantion of the software - SBB Install it - SBB instance - these are what require the licence

component - specification artefact -

Architecture Definition Document - Chapter 6 - Architecture Devliverables (hout foundation unit 11.pdf) RAW - Request for Architecture work SAW - Statement of Architecture work

Interoperability

Have interoperability between systems and people.

Business Transformation (BTEP Canada) Readiness Assessment

Assess the readiness factors - the table doesn't make sense... They didn't take the correct table from the BTEP outputs.

Capability Planning

Capability can be defined as - the ability to achieve a desired effect in a specific operating environment, it is a logical construct that is made manifest through the components of an organisation.

Capability planning is about changing one capability and increasing others -

Other Frameworks

Zachman

Zachman framework - created in the 1980s by an IBM person - John Zachman. Simply a system for collecting and organising. Present it using something else. Interrogrative - number of questions - come from Rudyard Kipling Rows represent stakeholders: Scope - Business Model - ops system model - devs tech - infrasture people details - outsourced partners

E.g I notice we have ops in France (WHERE)... WHY? Bought a company ages ago - legacy. WHO? Sales people, trainers. What type of things do we do (functions - HOW) - deliver courses, sell courses Do we have any key assets? Any buildings? (WHAT)

Fill in data in the cells, link data in the cells - usually just text in the cells. Often create sentences out of the text in the cells using nouns for the words in the cells and verbs for the columns.

Really good tool for collecting data, harvesting your estate.

Tom Graves http://weblog.tetradian.com/ : Every enterprise architecture

BMC - Business Model Canvas

Looked after by Business Model Generation - Scandinavian company. http://www.businessmodelgeneration.com/canvas/bmc In dropbox under "methods, frameworks and styles". Good book - profiles the top 100 companies.

Looking at the company and trying to understand the ecosystem. Steve Jobs made it famous. "Apple ecosystem" http://livingenterprise.net/the-apple-ecosystem-and-the-concept-of-lock-in/ - need a good business plan.

Helps you understand the flow of how things happen (the jet stream and why it is affecting the weather).

You do stuff (author courses, sell courses, buy other courses, book people on courses)

What makes you different? What is your USP? What is your value proposition?

Business Module YOU (for your own career progression)

Revenue stream - Pay on demand, subscription based, invoice based..

process role to process role to process to data role to process to data to application role to process to data to application to technology (infrastructure)

BCD do the same thing meet regularly to ensure all models are consistent - should have a bunch of data diagrams, business process diagrams etc which can't be related to each other and match up. don't talk about data / products etc in business architecture - only types

Requirements Management

RQ tools Open Source Process for doing Requirements Management VOLARE process