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. 3 Microsoft Confidential 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 Simple Terminology t

4. 4 Microsoft Confidential 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 Common Terminology tt

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

6. 6 Microsoft Confidential 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 Scaling Up The Architecture Discussion tt

7. 7 Microsoft Confidential 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 What Is A Principle?

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

9. 9 Microsoft Confidential 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 Commonality

10. 10 Microsoft Confidential 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 Lessons Learned On Commonality

11. 11 Microsoft Confidential 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 critical enterprise architecture principles Enabler of speed and flexibility Reduces complexity of interfaces (systems and people) This is the concept of modularity at the enterprise level System Boundaries

12. 12 Microsoft Confidential 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 Lessons Learned On System Boundaries

13. 13 Microsoft Confidential Within SystemsBetween Systems Tightly Coupled Integrated Information Streamlined processes Monolithic systems with huge scope Very large replacement projects with high failure rates Loosely Coupled Slow processes Redundant data Spaghetti interfaces Modular, plug and play Speed and Agility Lessons Learned On System Boundaries

14. 14 Microsoft Confidential 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 The HUB Principle

15. 15 Microsoft Confidential Lessons Learned On Hubs This VS This

16. 16 Microsoft Confidential Lessons Learned on Hubs – Do the Math # of Points#Links to a Hub # Point to Point Links * 221 5510 45 15 105 30 435 100 4950 * (n squared-n)/2

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

18. 18 Microsoft Confidential 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 Lessons Learned on Governing Content

19. 19 Microsoft Confidential Lessons Learned on Governing Content – con’t Data Business ProcessTechnology Decreasing Content Stability

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

21. 21 Microsoft Confidential 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 Enterprise Architecture

22. Questions?