Enterprise Architecture

1. Enterprise Architecture Melissa A. Cook | Director | Enterprise Strategy & Architecture

2. Agenda • Architecture – Simple Terminology • Scaling Up the Architecture discussion • Lessons learned from the trenches • Principles • Governance

3. Simple Terminology • Architecture • The roots of the word are a few thousand years old • Archi: • to govern or rule • Modern words: monarchy, anarchy, • Tekton: • Builder, skill • Modern words: technical, technology • Architecture is about governing builders t

4. Common Terminology • System • Systema: an assemblage or combination of things or parts forming a complex or unitary whole • A solution is a system • The enterprise is a system • They both need architectures to govern the builders t t

5. Common Terminology • Definitions from ANSI/IEEE 1471 • architecture*: The fundamental organization of a system embodied in its components…..and the principles guiding its design and evolution. t t *Embraced by The Open Group Architecture Framework (TOGAF)

6. Scaling Up The Architecture Discussion • Useful ways to think about the architecture of an enterprise • A system of systems • An Ultra Large Scale System (ULS) • ..will be decentralized in a variety of ways, developed and used by a wide variety of stakeholders with conflicting needs, evolving continuously, and constructed from heterogeneous parts.* • sound familiar? *Software Engineering Institute – Carnegie Mellon t t

7. What Is A Principle? • Principle: A statement that guides decision making… “guiding sense of right conduct”. • Lessons learned on principles • Should stand the test of time • Fundamental • Should be succinct • No white papers, compliance should be clear • Should be controversial or reflect lessons learned • Should not repeat well accepted practices or current policies

8. The Big Three Enterprise Architecture Principles • The Commonality Principle • The System Boundary Principle • The Hub Principle

9. Commonality • Commonality Principle • Data, Business Process and Technology: • Should be common when there is a compelling business case or… • Should be common unless there is a compelling business case • One of the most controversial enterprise architecture principles • Usually requires executive level discussion • This is the concept of re-use at the enterprise level

10. Lessons Learned On Commonality • People can assume “common” costs less than “uncommon” • There is a cost for one-size-fits-all • Sometimes failure of very large, costly projects… • It’s important to make the business case for commonality and hold people accountable for realizing it • It’s also important to scope projects using the system boundary principle • Incorrect boundaries are usually a key contributor to failure of large projects

11. System Boundaries • System Boundaries Principle • Should design around natural “system” boundaries • Tight coupling within • Loose coupling between • Defines the fundamental components of your enterprise • Key to the definition of architecture • One of the most criticalenterprise architecture principles • Enabler of speed and flexibility • Reduces complexity of interfaces (systems and people) • This is the concept of modularity at the enterprise level

12. Lessons Learned On System Boundaries • System boundaries are not arbitrary • Like carving a turkey • Find natural points of loose coupling – the joints • You can have both autonomy and integration! • Allows for speed and flexibility in the enterprise • With the minimum number of interfaces

13. Lessons Learned On System Boundaries

14. The HUB Principle • Should minimize point to point linkages • All industries that have many-to-many points evolve to hub and spoke architectures • Airlines • Logistics • Related technology concepts • Service bus • Master data hubs

15. Lessons Learned On Hubs This VS This

16. Lessons Learned on Hubs – Do the Math * (n squared-n)/2

17. Enterprise Architecture Governance(governing governance) • Two governance topics • Governance of content • E.g. principles, models, standards… • Governance of usage • E.g. compliance

18. Lessons Learned on Governing Content • Tackle enterprise architecture content just-in-time • Forces pragmatic approach • Use a “lens” into the framework • What decision needs to be made? • What new framework content is needed to make the decision? • Build on existing governance bodies and processes • E.g. use existing Steering Committees or an existing policy or standards setting process

19. Lessons Learned on Governing Content – con’t Data Business Process Technology Decreasing Content Stability

20. Lessons Learned On Governing Usage • Key business processes that should trigger the use of Enterprise Architecture content • The 5 P’s • Planning • Portfolio Management • Procurement • Project Management • Problems!

21. Enterprise Architecture • Why Microsoft? • One of the worlds largest software companies • We understand solutions architecture • We’re making a significant investment in Enterprise Architecture • Logical outgrowth of solutions architecture • New Enterprise Strategy & Architecture Organization within Enterprise Services • New customer service offerings • E.g. Enterprise Strategy Portfolio/Foundation/Projects • Delivered by Enterprise Architects- highly skilled and accomplished professionals • Executive level engagements

22. Questions?