Enterprise architecture as practice


Published on

Enterprise Architecture as practice

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

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

No notes for slide
  • Zachman framework
  • Enterprise architecture as practice

    1. 1. Enterprise Architecture As practice Business Frameworks (e.g. BMM, Six Markets, Porters 5 Forces, McKinsey 7S, etc) Architecture Frameworks (e.g. PEAF, MODAF, TOGAF, TEAF, IAF, etc) - Programming Frameworks (e.g. .NET, J2EE, etc) - Project Management Frameworks (e.g. PRINCE2, MSP, etc) - Service Management Frameworks (e.g. ITIL, etc) Industry Operations Frameworks (e.g. eTOM, Pragmatic Marketing, etc)
    2. 2. What is Enterprise?7M Man, Material, Machine, Money, Method, Management, Moral Values (Governance) • ENTERPRISE - The word Enterprise should be interpreted as a general noun – the name of something - to refer to any and all of these types of thing; public and private companies, government agencies, charities, universities etc. This is not an exhaustive list but illustrates the point. In addition the word Enterprise should also be interpreted to mean any name give to any of these types of Enterprises, e.g. a private company may be referred to as a Company, Business, Corporation, Conglomerate, Organisation, SME, Firm, Establishment, Group, Multinational, Venture. The word Enterprise to refers to them all.
    3. 3. Architecture Vs Developer Developer Architect More into coding and concerned about best way to solve a particular problem. Sees big picture of the system before it is built. Usually no need to sell his way of working (which is often down to coding). Need to convince (or sell) stakeholders about vision, ideas and recommendation. No involvement in strategic decisions. Often recommends and selects tools for strategic implementation. Tend to recommend a tool/language he is most familiar with. Evaluates and compares all available options and selects one which is best for business. Goes for best technical solution. Goes for best fit solution for the organization. Less scope for delegation. More scope for delegation. Responsible for implementation Defines general layout of the system. Heavily involved in coding. Usually not involved in coding. Finds a solution to a problem according to design. Finds the definition of actual problem and suggests design to solve it. Soft skill is less important. Soft skill is more important. Often works in single project. Often works in multiple projects across the organization.
    4. 4. Make distinction more clear • Architect in software world is one who designs systems almost similar to Building Architect. • Difference between developer and architect is same as between civil engineer and Architect. • Both make building but architect designs it to specs after taking lots of factors into consideration and civil engineer see whether strength of cement mixture or width of steel rod enough to support building same way architect sees whether exposing it as webservices is advantageous to SAP or integrate with BAPI.
    5. 5. Categorization • Strategy – Value Creation e.g. CMMI, PCMMI • Valuation and Decision making: Break Even Point, six sigma. • Organization change culture: e.g. RACI (Responsible, Accountable, Supportive, Consulted, Informed) • Leadership And management: e.g. Activity Based accounting, Root cause Analysis
    6. 6. Frameworks (more than 153 in market) • AAF, AF-EAF, AGATE, AGILE, Altus EA Framework, AM, ARCHI, ARCON, AUSDAF, BCA, BEAM, BEAM, BMM, Bolman/Deal Four Frame Model , BPEAM, BSIMM, CEA, CEAF, CIAF, CLEAR, CMMI , CMU , COBIT, CORBA, CSC Catalyst, DAD, DNDAF, DoDAF, DRAGON1, DYA, E2AF, EA3 Cube Framework, EAAF, EAB, EABOK, EAM-PC, EEAF, EIF, EIF European Interoperability Framework, EPCAF, ESAAF, ESSAF, eTOM, EVM, EXAF, FCAPS, FDIC, FDIC Sogeti Framework, FEA, FEAF, FFLV+GODS, FMLS-ADF, Fragile to Agile, FSAM, FURP, GA, GAME, GEA, GEAF, GERAM, GOD, GOPP, HEAF, IADS, IAF, IBM SDS, ICODE, IDABC, IDEAS, IFEAD, IFW, IFW, Integration Framework, ISO 20000, ISO 25010, ISO 27000, ISO 42010, IT-CMF, ITIL, Krutchen 4+1 Model View, LEAN, LFA, LMO , MACCIS, McKinsey 7S, MEGAF, MIKE2.0 , MODAF, Model-driven architecture (MDA) , MoP, MoR, MoV, MSP, Mutual Learning approach, NAF, NCOIC, NCR Enterprise Architecture Framework , NIF, NIST-EAM, NORA, OBASHI, OEAF, OIO Framework, OOPP, OSGi, P3O, PEAF, PERA, Porters 5 Forces, PPOOA, Pragmatic Marketing, Praxeme , PRINCE2, PRISM, PROMIS Framework , Queensland Government Enterprise Architecture, RAS, RASDS, RM-ODP, RWSSA, S4V, SABSA, SAGA, SAM, SAPEAF, SASSY, ScIAM, SCOR, SDLC, SEI, SGCAF, SID, Six Markets, Snow man stack, SOA, SOMA, SPIRIT Platform Blueprint Issue 3.0, SPRING, SSM, STRUTS, Systems Dynamics, TAM, TEAF, Three Levels of Leadership, TOGAF, TRAK, UADF, UDS, VALUIT, VSM, xAF, ZF,
    7. 7. Zachman Framework
    8. 8. Activity performed
    9. 9. The Open Group Framework TOGAF
    10. 10. Example:TOGAF ADM to Cisco SONA
    11. 11. Oracle Enterprise Architecture
    12. 12. SAP Solution Manager
    13. 13. SAP Solution Manager Functionality
    14. 14. More details • http://sandyclassic.wordpress.com • Enterprise Architect: http://enterprisearchitectview.wordpress.com/ • Java Architect: http://javaarchitectview.wordpress.com/ • Product Management: http://productmanagementview.wordpress.com • Project Manager : http://projectmanagerview.wordpress.com