Stepping-stones of enterprise-architecture: Process and practice in the real enterprise


Published on

What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]

Published in: Business, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Tetradian Consulting Unit 215, Communications House 9 St Johns Street Colchester Essex CO2 7NN England [email_address] Twitter: @tetradian © Tom Graves / Tetradian 2009
  • A simple question: what do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast ? Those are real concerns – especially in the present business climate. But whilst the TOGAF ADM tells us what to do within an architecture cycle, it doesn’t tell us where to start. To help with that, we turn to a less-well-known part of TOGAF: the Maturity Model.
  • It’s tucked away at the back of the document, in Chapter 51. For each of its five maturity-levels, it tells us what our architecture should look like at that level. But in practice what’s more of interest is the steps between those levels – because they tell us what we can and should do at each stage, to extend the maturity and capability of the architecture. These then are the stepping-stones of architecture .
  • There are five levels in the TOGAF model, hence seven ‘stones’ – the foundations below, the five levels, and a plateau of continual improvement above. These seven steps summarise the kinds of work that our architecture-group has done in a variety of organisations and industries in Australia and elsewhere. To be honest, there’s a lot more to enterprise architecture than TOGAF itself can show us. But with a bit of help we can use TOGAF’s general tools and models all the way through.
  • First, we build the foundations. In our own work, we categorise these under five distinct headings: - purpose, and overall strategy; - people, and the governance concerns; - planning, and the role and choice of frameworks; - practice, and the methods to use for architecture development - performance-metrics for business-value, and the artefacts we will produce within the work
  • Looking at strategy, the main role of enterprise architecture is as a body of knowledge on enterprise structure and purpose - in the broadest sense of those terms. It’s about decision-support for others, particularly strategy and the PMO. It’s not about trying to take control of the business - so the business-folk don’t need to panic! But we must break away from TOGAF on one crucial point. TOGAF’s ‘enterprise architecture’ is essentially about IT, yet IT itself is only one tiny part of the business – barely 2%-3% in British Airways’ case, for example. Right from the start, enterprise architecture has to be about the whole of the enterprise – not just its IT.
  • The reason for this is that everything connects with everything else. Look at enterprise-architecture’s own history: we may have started with technology-infrastructure, but the trails of dependencies mean that eventually we must end up connecting across the whole of the enterprise. Enterprise IT-architecture is the architecture of the enterprise IT alone. But enterprise architecture is the architecture of the enterprise – of everything in the enterprise. We don’t have to leap to that level straight away: but we must accept, right from the start, that that’s the full scope we’ll need by the end.
  • So where do TOGAF’s classic ‘four architectures’ come into this? Business architecture, data architecture, applications architecture and technology architecture? They do matter, of course, and matter a lot. But complex as it is, IT is only a small part of the enterprise cost-base and complexity. What TOGAF blithely calls ‘business architecture’ may well be thirty times the size of all of the IT put together: so TOGAF’s views on architecture are a bit out of balance, to say the least. To be blunt, TOGAF’s ‘business architecture’ is little more than a random grab-bag for ‘everything not-IT’, with high-level strategy all jumbled up with low-level process and everything in between. If we’re going to use TOGAF for real enterprise architecture, we’ll need to disentangle that mess as we go along here.
  • This image gives us a better idea of the real scope we need in enterprise architecture. It also shows us why IT-centric architecture can be such a problem: it only covers a small part of what’s really needed, but pretends that it’s everything. IT doesn’t even cover the whole of information, because there’s also all the people-based ‘tacit’ information, for example, which is central to knowledge-management. So the architecture strategy we’ve used in all our work is that we aim to cover the whole enterprise – not just the IT. More on how to do this in a moment, when we look at frameworks. First we need to deal with some of the ‘people-stuff’.
  • Most of the governance issues are well-described in the TOGAF document. We need to do some translation to break out of its IT-centrism, but that’s about all. A key governance point is that ‘the whole enterprise’ is far too large for a classic-TOGAF ‘big cycle’. To make it work, we’ll have to split it into smaller Agile-style iterations. And to bridge across all of the silos, we’ll need high-level support, usually right up to the CEO. We may not need it right from Day One, but we’d better plan for it right from the start.
  • In planning, we need some kind of framework to tell us what everything means . Again, TOGAF does help in this, with its ‘Enterprise Continuum’ and the like – though unfortunately the new Architecture Metamodel is all but useless for this kind of work. A reference-architecture is a set of rules and guidelines that specify the ‘bindedness’ of each component in the structure. Behind this, we need some kind of base-ontology to define categories of meaning and function. In our own work we use for this an extended version of Zachman.
  • Zachman’s framework is the architecture equivalent of chemistry’s Periodic Table of Elements. Zachman’s point is that the elements or ‘primitives’ exist within a cell, composites straddle across cells: “Primitives guide architecture; composites guide solutions”. We need primitives which cover the full enterprise scope. The original Zachman layers work well enough for this, though we also add one layer above, to align with ISO-9000 and the like. But Zachman’s columns don’t work so well, especially outside of IT. So as you’ll see, we’ve restructured them somewhat, to align better with BPMN and other cross-enterprise needs. Composites are also patterns . A ‘complete’ composite crosses all columns, and must be complete at the ‘Operations’ layer (row-6). A useful cue is that a composite is usable to the extent that it is complete; but it’s re-usable, as a pattern, to the extent that it is not complete.
  • More important is that Zachman is missing an entire dimension, which we’ve labelled ‘segments’: physical ‘things’ such as servers, physical locations, events virtual data, virtual locations, signals and message-events relational links to people, social-network locations, sales-lifecycle events aspirational keys such as brand, morale, reputation and the enterprise itself and abstracts such as time and money These distinctions often aren’t critical in the upper framework layers, but they matter more and more as we move down towards the real world. This provides the base-skeleton for a ‘holograph’ of the enterprise, to which we add more detail and depth with each architecture iteration.
  • The TOGAF ADM is our obvious choice for an architecture method. One difference is that we’ll need to use it in an iterative Agile style. In theory, TOGAF 9 does now provide better support for iterations, but to be blunt it doesn’t work in practice: we’ll need to amend that. And its fixed IT-centric scope is a serious problem. The current Phases B, C and D are architecture-iterations in their own right, each with their own as-is, to-be and gap-analysis. Instead, we generalise from TOGAF’s ‘four architectures’. We set an appropriate iteration-scope in Phase A, then do the as-is in Phase B, the to-be in Phase C, and the gap-analysis in Phase D. That then works for any architecture, of any scope, at any scale.
  • It also sorts out a governance-problem in that TOGAF 9’s architecture cycle demands a near-infinity of stakeholder-reviews. In this split, the reviews occur only at phase-boundaries – in fact they are the phase-boundaries. This cycle is recursive, so it can be used at any timescale. The classic TOGAF cycle takes a couple of years, but at AusPost our some of cycles were no more than a couple of hours. It’s simpler than the existing ADM; it fits well with an iterative approach; and also fits well with ‘product’-based governance such as in ITIL and PRINCE2.
  • The other key point is that we link every architecture-cycle to explicit business-value. We don’t start any work until we’ve identified how we’ll measure that. The visible outcomes of the work include all the models and documents. Less visible, but perhaps even more important, is communication with stakeholders. Ultimately, the architecture is the dialogue about the idea of integration across the enterprise. Once we’ve defined all of that, we’ve reached Level Zero : we’re ready to go.
  • The very first part of architecture is to establish what business we’re in. This may sound obvious, but it’s rarely done in conventional IT-architecture - and we need it as the anchor for all subsequent architecture-compliance. This is typically done as a short-term project, and often by outside consultants – almost the only time, in fact, when outsiders can define the architecture of the enterprise.
  • Identifying and modelling all of this provides the initial content for our ‘holograph’ of the enterprise, using that Zachman-like framework: - the topmost layers of vision, values, principles and core business-drivers - key assets, functions, locations, capabilities, events and decisions – the framework columns; and - the balance between framework segments – for example, how central is information here, compared to things, to people-relationships, to brands and so on? Much of this is what TOGAF would call ‘business architecture’. But note that we only set up the full architecture capability – TOGAF’s Preliminary Phase – at the end of this work, when we’ve established our ‘business-cred’.
  • One essential artefact for ‘business-cred’ is the function-model, or business-service model. It’s a way to summarise the whole of the enterprise on a single page. It’s typically created in three or four tiers. The first tier is literally a summary. It’s useful, but it doesn’t tell us much that we don’t already know.
  • But when we split each of those ‘business services’ into its next-tier functions, we start to get a better idea of what really goes on in the organisation. It’s also clear that this is about the whole enterprise – not just its IT. That helps to allay a lot of business-folks’ fears about enterprise-architecture.
  • And by the time we get to tier-3, we have something that’s of direct, practical use to the business. Almost all of the managers at AusPost printed out their own large-sheet copies of this to pin on the wall, often covered with personal annotations and PostIt tags. (For confidentiality, by the way, I’ve changed the detail here, to look like a plastics factory. The point is that the same principles apply to every enterprise.) This gave us the credibility to get architecture established as an ongoing capability rather than solely as a short-term project. At this point, we’ve have reached Level 1. Ad-hoc projects can now make sense in relation to the architecture.
  • Here we step into classic TOGAF territory – ‘horizontal’ optimisation of systems, cleaning up the mess in the IT context, and in end-to-end processes and elsewhere. And it wil l be a mess, too - don’t be under any illusions about that. There’ll be a jumble of undocumented point-solutions, legacy-systems that can’t talk to each other, people running ragged with all the fire-fighting… But you’re not alone in this. Everyone ’s systems are in this kind of mess when they start architecture. That clean-up must be done first, though - otherwise adding anything new will only make the mess worse.
  • Again, don’t be under any illusions about timescale. There’s no getting round the reality that, in any reasonable-sized organisation, this is going to take at least a couple of years overall. But the key – as we did at AusPost – is to start off by splitting up the work into distinct ‘Business Systems’, each with their own information-systems and ‘single source of truth’. If you then clean up one Business System at a time, each iteration is much shorter – often a month or two at most. And the return on investment is much quicker too – which again is crucial for maintaining business-credibility.
  • And it’s in the clean-up that that amendment to the ADM starts to show its value. In this case, the scope for each iteration is defined by the boundaries of the respective Business System, which we identified and modelled in the previous step. The principles for this assessment-work are well described in the TOGAF 9 document for each of their ‘architectures’. If you generalise from those principles, and apply them to the Business System scope rather than to a predefined IT-specific ‘architecture’, you’ll see that it fits into this sequence here. Note that architecture governance-rules apply most here – as opposed to change -governance rules, which take priority in the following phases.
  • The solution-design, project-plan and develop/deploy phases are all much the same as in TOGAF. Which they should be, because most of this is under change-governance, not architecture-governance. Architecture is just the ‘client’ here. ‘ Lessons-learned’ here may differ slightly different from the TOGAF description – because the scope is determined by the Business System, not solely by IT – but otherwise the principles are much the same. Exactly as in TOGAF, the results feed into requirements for new architecture iterations.
  • And once we’ve done the rationalisation – or even just its assessment and solution-design phases - we have a complete portion of an architecture ready to use as a reference-model for compliance. Having cleaned-up in that area, we now need to ensure that new projects don’t mess it up all over again. Guiding change was a central part of our earlier work at AusPost. To avoid the dreaded role of ‘architecture police’, the trick was to get in early, at the first idea-stages for each project. Getting architecture included into the regular PMO processes as described here was a major milestone for architecture acceptance. Making architecture repeatable brought us to Level 2 in the Maturity Model.
  • One of the key aims of TOGAF 9 is to drive the architecture from strategy – though note that even in TOGAF we don’t get there till the second and subsequent cycles. The difference here is that we can start building that support as soon as we’ve done the first Business System – a matter of months, not years. The key emphasis here is top-down assessment and integration.
  • The main focus is ‘this goes with that’ – identifying top-down trails of dependencies and impacts from change and innovation. The TOGAF 9 document mentions two themes that can help here: service-oriented architecture, and security-architecture. But again we need to generalise these somewhat, away from TOGAF’s IT-centric assumptions. Service-orientation at an abstract business level, for example, helps us understand the trade-offs between different technologies, and allows us to identify what’s common between different implementations. That’s important in business-continuity planning, as we’ll see later. And security is only one of many qualitative ‘pervasive services’ for which we need to build support throughout the architecture. When we’ve finished all this, we have an overall architecture defined from top to bottom – in other words, Level 3 .
  • In the next step we switch the emphasis the other way round – bottom-up rather than top-down. This allows us to tackle the architecture of key operations-level concerns such as load-balancing and business-continuity planning. It also provides a way to link to operations-level process-management and quality-management. That was a key part of my own work at AusPost.
  • Here we’ll model issues such as service-escalation, and switching between service-implementations for disaster-recovery. This builds on the previous step’s work on abstract-services and service trade-offs. For disaster-recovery we need to look closely at ‘safe-fail’ fallback – most of which only makes sense if we can connect the bottom-up view to the previous top-down dependency-trails. The same is true of quality-management: strategy sets the direction, but it does need to connect right down into the real-world practice. This way, the architecture links to other forms of management, and is itself consistently managed – so we’ve reached Level 4 .
  • By this stage we can model in any direction: overview and focus, horizontal, top-down, bottom-up. We now link all these approaches together, to architecture the kind of themes that business really wants us to tackle: - the role of service in its broadest sense – and its links to business value - business ‘pain-points’ and other so-called ‘wicked-problems’ - enhancing overall effectiveness across the whole enterprise We’re a long way past TOGAF here, by the way. This is real enterprise architecture – not just IT-architecture.
  • The crucial point is that this kind of work will only succeed if we include the human side of systems into the architecture. For example, service-oriented architecture at last makes sense when we extend it across the whole enterprise, and link it to some ‘old-fashioned’ yet essential notions about service and responsibility. Business-problems turn ‘wicked’ when technical complexity meets social complexity. It’s why BPR failed so badly, and why the current hype about cloud-computing will likely fail the same way. The blunt fact is that complex business-problems cannot be solved by IT alone. We’ve come across plenty of examples of that at AusPost and elsewhere. And ultimately it’s all about effectiveness: not just efficient, but ‘efficient on purpose’ and everything else. When we’ve addressed these issues appropriately, our architecture is optimised – and hence at Level 5 in that maturity model.
  • But we don’t stop there just because we’ve reached some imaginary milestone. Architecture isn’t a project – it’s an ongoing capability, whose role is to support continual improvement and adaptation of the enterprise. And rather than us keep on changing it from outside, we need to bring the architecture to the point where the enterprise can adapt itself to its changing conditions and needs. To get there, we need to do something that will feel really scary: we must let go of both the command and the control of the architecture.
  • The key understanding here is that whilst we’re responsible for the architecture, we don’t possess it. It belongs to the enterprise as a whole, in the same sense that a city-plan belongs to every citizen. One way to help this happen is to relinquish control by shifting to a ‘hands-off’ architecture. This is like the ‘building-regulations’ and ‘planning-permission’ in a city - and for the same reasons it only works when all of those support-structures are already in place. So don’t try this too early – and especially, not just as a cost-cutting exercise! In the same way, the architecture needs to be relevant to people’s business lives. To do that, we let go of command, and shift to dialogue about architecture, through conferences, communities-of-practice and other forms of committed communication. Ultimately, architecture is just an idea , that integration across the enterprise helps everyone. In that sense, the architecture is the dialogue here.
  • So, to recap, conventional ‘enterprise architecture’ is mainly for IT-architecture in information-centric industries. To go beyond that, to a true ‘architecture of the enterprise’, TOGAF and the like will still work well if we tweak them a bit to expand their scope and versatility. The sheer scale of the enterprise-as-a-whole means that we must use an iterative, Agile approach – and this brings faster return-on-effort, too. And TOGAF’s maturity-model provides a structured ‘stepping-stones’ approach – overview and focus, horizontal, top-down, bottom-up, spiral-out - to develop architectures for any domain, any scope, at any scale, and in any type of industry.
  • There’s more detail on all of this in the book – “Doing Enterprise Architecture” – but that’s all we have time for here. I hope this has helped for your own enterprise architecture, anyway. But in the meantime, any questions? Any answers, perhaps? And thank you.
  • Stepping-stones of enterprise-architecture: Process and practice in the real enterprise

    1. 1. Stepping-stones of enterprise-architecture Process and practice in the real enterprise Tom Graves , Tetradian Consulting TOGAF London, April 2009 /
    2. 2. Doing enterprise-architecture <ul><li>What do we do </li></ul><ul><li>when we’re doing enterprise architecture? </li></ul><ul><li>Enterprise architecture isn’t a project </li></ul><ul><ul><li>it’s more like a way of life! </li></ul></ul><ul><li>Creating an architecture is a long-term process </li></ul><ul><ul><li>conventional: 1-2 years to start to see business-value </li></ul></ul><ul><li>BUT in these times no-one will wait for value </li></ul><ul><ul><li>so we need to do it differently from ‘the book’ </li></ul></ul><ul><li>How do we get results fast? Where do we start? </li></ul>
    3. 3. Use the TOGAF maturity-model
    4. 4. Stepping-stones of architecture <ul><li>TOGAF’s model has 5 levels, hence 7 ‘stones’ </li></ul><ul><li>Each stepping-stone builds on those before: </li></ul><ul><li>Prepare (and maintain) the foundations </li></ul><ul><li>Step 1: Build an overview of the business </li></ul><ul><li>Step 2: Clean up the mess (and keep it clean) </li></ul><ul><li>Step 3: Guide and manage strategic change </li></ul><ul><li>Step 4: Ensure robust resilience, continuity </li></ul><ul><li>Step 5: Service the business’ deeper needs </li></ul><ul><li>Maintain as an enterprise-wide shared capability </li></ul>
    5. 5. Prepare architecture foundations <ul><li>Emphasis: support for whole-enterprise scope </li></ul><ul><li>Examples : business, IT-, manual- and machine-based processes, capabilities, customer, partner, supply-chain, shared enterprise </li></ul>Purpose – strategy People – governance Planning – frameworks Practice – methods Performance – metrics
    6. 6. Purpose – strategy <ul><li>Enterprise architecture acts as custodian for a body of knowledge on structure and purpose : </li></ul><ul><ul><li>“ what structure changes do we need for this strategy?” </li></ul></ul><ul><ul><li>“ what strategy can we support with this structure?” </li></ul></ul><ul><ul><li>“ what risks, opportunities does this strategy create?” </li></ul></ul><ul><li>Provides bridge between strategy and PMO etc </li></ul><ul><li>-- BUT NOTE -- </li></ul><ul><li>IT is only one small part of the enterprise </li></ul><ul><ul><li>“ typically 2% to 3% of business cost” (Paul Coby, CIO of BA) </li></ul></ul><ul><li>A real EA must have whole-of-enterprise scope </li></ul><ul><ul><li>it’s essential in long-term – so best to start there! </li></ul></ul>
    7. 7. Whole-of-enterprise architecture <ul><li>Each EA generation has had to extend the scope: </li></ul><ul><li>‘ Classic’ EA starts with IT infrastructure </li></ul><ul><li>IT tech-architecture depends on applications </li></ul><ul><li>Applications-architecture depends on data </li></ul><ul><li>Data-architecture depends on business-info need </li></ul><ul><li>Information-architecture depends on business </li></ul><ul><li>Business-architecture depends on enterprise </li></ul><ul><li>Enterprise-architecture defines the context </li></ul><ul><li>An enterprise-architecture must have whole-of-enterprise scope – it’s not just detail-level IT! </li></ul>
    8. 8. TOGAF and architecture scope <ul><li>Classic scope of IT-based ‘enterprise architecture’ </li></ul>IT (3% of enterprise) Everything not-IT ? (97% of enterprise)
    9. 9. Scope of IT in enterprise context <ul><li>Whole-of-enterprise scope </li></ul>IT is only a small subset (not even all of Information) <ul><ul><li>three layers: Business, Integration (Common), Detail </li></ul></ul><ul><ul><li>three columns: People, Information, Physical Assets </li></ul></ul>
    10. 10. People – governance <ul><li>Governance is well-described in TOGAF 9 spec </li></ul><ul><ul><li>Architecture Charter, Architecture Governance etc </li></ul></ul><ul><ul><li>but EA-governance is not a subset of IT-governance! </li></ul></ul><ul><ul><ul><li>organisationally, EA should be outside IT, not subordinate to it </li></ul></ul></ul><ul><li>Skillsets well-described in Capability Framework </li></ul><ul><ul><li>but will also need broad range of skills from beyond IT, to cover needs of much broader architecture scope </li></ul></ul><ul><li>Process-governance as per Agile, not Waterfall </li></ul><ul><ul><li>multiple, simultaneous, recursive architecture-cycles </li></ul></ul><ul><li>Will need executive-level support from the start </li></ul><ul><ul><li>will need that support to bridge across all silos etc </li></ul></ul>
    11. 11. Planning - frameworks <ul><li>Frameworks define structure and meaning </li></ul><ul><li>TOGAF provides ‘Enterprise Continuum’ </li></ul><ul><ul><li>‘ Architecture Continuum’ and ‘Solutions Continuum’ </li></ul></ul><ul><ul><li>four layers: Foundation, Common-systems, Industry and Organisation-specific </li></ul></ul><ul><li>Reference-frameworks define ‘bindedness’ </li></ul><ul><ul><li>mandatory, recommended, suggested etc </li></ul></ul><ul><li>All items ultimately anchor to base-framework </li></ul><ul><ul><li>layers of ‘composites’ resolve to explicit ‘primitives’ </li></ul></ul><ul><li>Zachman as an archetypal base-framework </li></ul>
    12. 12. Base-framework columns <ul><li>Columns need restructure to support whole-EA </li></ul>At Operations level, we should be able to describe every service as: -- this is an ‘architecturally complete’ pattern or composite
    13. 13. Base-framework segments Needs dimension of ‘segments’ within columns
    14. 14. Practice – methods <ul><li>TOGAF ADM as the obvious choice for method </li></ul><ul><ul><li>long-proven in IT-architecture </li></ul></ul><ul><ul><li>ADM is designed for adaptation and extension </li></ul></ul><ul><li>Must use ADM in Agile style for rapid ROI </li></ul><ul><ul><li>business will not wait 2+ years before any returns! </li></ul></ul><ul><li>TOGAF 9 has better support for iterations </li></ul><ul><ul><li>but may not be usable out-of-the-box for Agile </li></ul></ul><ul><li>Amend fixed IT-centric scope of TOGAF 9 </li></ul><ul><ul><li>ADM for whole-enterprise: Phase A=iteration scope, Phase B=‘as-is’, Phase C=‘to-be’, Phase D=gap-analysis </li></ul></ul>
    15. 15. Methods – governance for Agile EA Statement of Architecture Work (for iteration) Stakeholder review for ‘as-is’ Stakeholder review for ‘to-be’ Gap-analysis / requirements review Solution design review Project plan review Project architecture compliance review Benefits realisation (‘lessons learned’ etc) Architecture Charter Governance-artefacts define methodology’s phase-boundaries
    16. 16. Performance – metrics and products <ul><li>Need processes to measure benefits-realisation </li></ul><ul><ul><li>need to prove the value of enterprise architecture </li></ul></ul><ul><ul><li>link every iteration to explicit business value </li></ul></ul><ul><li>Artefacts from architecture work include: </li></ul><ul><li>Models, metamodels and reference-models </li></ul><ul><li>Change-roadmaps and portfolio ‘blueprints’ </li></ul><ul><li>Requirements-repository </li></ul><ul><li>Risks, opportunities and issues registers </li></ul><ul><li>Architecture-dispensations register </li></ul><ul><li>Glossary and thesaurus </li></ul>
    17. 17. Step 1: Know your business <ul><li>Emphasis: ‘big-picture’ </li></ul><ul><li>Examples : whole-of-enterprise overview, end-to-end and top-to-bottom integration </li></ul>1A: Vision, values, principles and purpose 1B: The enterprise context 1C: Functions and services 1D: Architecture governance
    18. 18. Step 1: Know your business <ul><li>1A: Vision, values, principles </li></ul><ul><ul><li>Vision, role, mission, goal </li></ul></ul><ul><ul><li>Values, principles, business purpose </li></ul></ul><ul><li>1B: The enterprise context </li></ul><ul><ul><li>Compliance, constraints, standards, expectations </li></ul></ul><ul><ul><li>Assets, locations, events </li></ul></ul><ul><li>1C: Functions and services </li></ul><ul><ul><li>Services; functions; capabilities; the Function Model </li></ul></ul><ul><li>1D: Architecture governance </li></ul><ul><ul><li>Creating architecture capability; creating engagement </li></ul></ul>
    19. 19. Function-model: tier-1 example
    20. 20. Function-model: tier-2 example
    21. 21. Function-model: tier-3 example
    22. 22. Step 2: Clean up the mess <ul><li>Emphasis: ‘ horizontal’ </li></ul><ul><li>Examples : optimise systems, reduce redundancy </li></ul>2A: Business-systems and information-systems 2B: What do we have? 2C: Guiding the process of change
    23. 23. Step 2: Clean up the mess <ul><li>2A: Business / information-systems </li></ul><ul><ul><li>Business systems; identifying business-systems; modelling individual business-systems </li></ul></ul><ul><ul><li>Information systems and ‘single source of truth’; identifying single-source-of-truth </li></ul></ul><ul><li>2B: What do we have? </li></ul><ul><ul><li>Assessment for rationalisation: iteration-scope; as-is; to-be; gap-analysis for requirements </li></ul></ul><ul><ul><li>Implementation for rationalisation: solutions; projects; development and deployment; lessons-learned </li></ul></ul><ul><li>2C: Guide the process of change </li></ul><ul><ul><li>Guiding compliance to architecture roadmap </li></ul></ul>
    24. 24. 2B: What do we have? [1] <ul><li>Assessment phases (under architecture governance): </li></ul><ul><li>Phase A: define scope for rationalisation </li></ul><ul><ul><li>typically defined by boundaries of Business System etc </li></ul></ul><ul><li>Phase B: inventory the existing items in scope </li></ul><ul><ul><li>develop an ‘as-is’ inventory of the respective items </li></ul></ul><ul><li>Phase C: identify the required rationalisation </li></ul><ul><ul><li>develop a ‘to-be’ inventory of the respective items </li></ul></ul><ul><li>Phase D: establish gaps, change-requirements </li></ul><ul><ul><li>identify requirements, risks and responsibilities </li></ul></ul><ul><li>Note difference to TOGAF here – not centred on IT </li></ul>
    25. 25. 2B: What do we have? [2] <ul><li>Implementation phases (under programme governance): </li></ul><ul><li>Phase E: outline required rationalisation action </li></ul><ul><ul><li>guide handover of requirements to solution-architects </li></ul></ul><ul><li>Phase F: assist detailed rationalisation-design </li></ul><ul><ul><li>provide architectural guidance during detailed-design </li></ul></ul><ul><li>Phase G: assist rationalisation implementation </li></ul><ul><ul><li>provide architectural guidance during gateway review </li></ul></ul><ul><li>Phase H: do rationalisation ‘lessons-learned’ </li></ul><ul><ul><li>benefits-realisation and lessons-learned </li></ul></ul><ul><li>These phases remain similar to those in TOGAF 9 </li></ul>
    26. 26. 2C: Guide the process of change <ul><li>Guiding compliance to architecture roadmap : </li></ul><ul><li>Assist in defining requirements for change </li></ul><ul><ul><li>(equivalent to Phases A-D) </li></ul></ul><ul><li>Assist in solution-architecture </li></ul><ul><ul><li>(equivalent to Phase E) </li></ul></ul><ul><li>Assist in detailed project-design </li></ul><ul><ul><li>(equivalent to Phase F) </li></ul></ul><ul><li>Review and advise in project implementation </li></ul><ul><ul><li>(equivalent to Phase G) </li></ul></ul><ul><li>Review ‘lessons-learned’ from project </li></ul><ul><ul><li>(equivalent to Phase H) </li></ul></ul>
    27. 27. Step 3: Strategy and stuff <ul><li>Emphasis: top-down </li></ul><ul><li>Examples : impact of strategy, change of regulation, service-design </li></ul>3A: Expand out from IT 3B: This goes with that 3C: Abstract-services 3D: Compliance and quality
    28. 28. Step 3: Strategy and stuff <ul><li>3A: Expand outward from IT </li></ul><ul><ul><li>The enterprise as whole - extending scope-awareness; including people and ‘things’ in the architecture </li></ul></ul><ul><li>3B: This goes with that </li></ul><ul><ul><li>Strategy drives change; innovation invokes strategy </li></ul></ul><ul><li>3C: Abstract-services </li></ul><ul><ul><li>Technologies and trade-offs; services in abstract; services for real </li></ul></ul><ul><li>3D: Compliance and quality </li></ul><ul><ul><li>From value to quality; pervasive-services; develop awareness; develop capability; verify and audit </li></ul></ul>
    29. 29. Step 4: Work with the real world <ul><li>Emphasis: bottom-up </li></ul><ul><li>Examples : disaster-recovery, risk-assessment, run-time load-balancing </li></ul>4A: Design for service flexibility 4B: Plan for business-continuity 4C: From qualities to values
    30. 30. Step 4: Work with the real world <ul><li>4A: Design for service flexibility </li></ul><ul><ul><li>Design for escalation; the service of escalation </li></ul></ul><ul><ul><li>Design for resilience; the services balancing-act </li></ul></ul><ul><li>4B: Plan for business-continuity </li></ul><ul><ul><li>The impact of disaster; impact from the bottom up; the impact dashboard </li></ul></ul><ul><ul><li>Fail-safe and safe-fail; design for failure </li></ul></ul><ul><li>4C: From qualities to values </li></ul><ul><ul><li>Quality in practice; connecting to quality </li></ul></ul>
    31. 31. Step 5: Pull it all together <ul><li>Emphasis: ‘spiral-out’ </li></ul><ul><li>Examples : data-quality, service-management planning, business ‘pain-points’ </li></ul>5A: The service-oriented enterprise 5B: Dealing with ‘wicked problems’ 5C: Enhancing enterprise effectiveness
    32. 32. Step 5: Pull it all together <ul><li>5A: Service-oriented enterprise </li></ul><ul><ul><li>Everything is a service; interdependencies of service </li></ul></ul><ul><ul><li>Being of service; responsibility, capability as services </li></ul></ul><ul><li>5B: Deal with ‘wicked problems’ </li></ul><ul><ul><li>Tame-problems and wicked-problems </li></ul></ul><ul><ul><ul><li>technical complexity interacts with social complexity </li></ul></ul></ul><ul><ul><li>Identifying ‘wickedness’; resolving wicked-problems </li></ul></ul><ul><li>5C: Enhance effectiveness </li></ul><ul><ul><li>Enhancing effectiveness </li></ul></ul><ul><ul><ul><li>keywords : efficient, reliable, elegant, appropriate, integrated </li></ul></ul></ul><ul><ul><li>Reviewing effectiveness, enhancing agility </li></ul></ul>
    33. 33. Beyond level 5: What next? <ul><li>Emphasis: integration </li></ul><ul><li>Examples : architecture as an enterprise-wide responsibility </li></ul>XA: Hands-off architecture XB: Architecture as relevance
    34. 34. Beyond level 5: What next? <ul><li>XA: Hands-off architecture </li></ul><ul><ul><li>Preparation for hands-off architecture </li></ul></ul><ul><ul><li>Project-gateway notification and response </li></ul></ul><ul><ul><li>Project-completion review </li></ul></ul><ul><li>XB: Architecture as relevance </li></ul><ul><ul><li>Conferences </li></ul></ul><ul><ul><li>Communities of practice </li></ul></ul><ul><ul><li>Communication </li></ul></ul>
    35. 35. Summary: Doing whole-enterprise EA <ul><li>Adapted TOGAF-ADM for whole-enterprise EA </li></ul><ul><ul><li>restructure of Phases A-D to resolve IT-centrism </li></ul></ul><ul><li>Extended-Zachman as base-framework for EA </li></ul><ul><ul><li>complete coverage of full whole-of-enterprise scope </li></ul></ul><ul><li>Agile-style model permits rapid return-on-effort </li></ul><ul><ul><li>consistent for all architecture-iteration timescales </li></ul></ul><ul><li>TOGAF maturity-model as ‘stepping-stones’ </li></ul><ul><ul><li>gives graded plan for whole-enterprise architecture </li></ul></ul><ul><li>Proven in real-world practice in and beyond IT </li></ul><ul><ul><li>logistics, utilities, government, telco etc </li></ul></ul>
    36. 36. Stepping-stones of enterprise architecture <ul><li>Any questions? </li></ul><ul><li>(or answers, perhaps?) </li></ul><ul><li>Thank you! </li></ul>
    37. 37. Resources: “ Tetradian Enterprise Architecture” series <ul><li>Books on enterprise-architecture by Tom Graves: </li></ul><ul><li>Real Enterprise Architecture : beyond IT to the whole enterprise </li></ul><ul><li>Bridging the Silos : enterprise architecture for IT-architects </li></ul><ul><li>SEMPER and SCORE : enhancing enterprise effectiveness </li></ul><ul><li>Power and Response-ability : the human side of systems </li></ul><ul><li>The Service Oriented Enterprise : enterprise architecture and viable systems </li></ul><ul><li>Doing Enterprise Architecture : process and practice in the real enterprise </li></ul><ul><li>See for more details. </li></ul>