Recommended
More Related Content
What's hot
What's hot (20)
Similar to Introduce TOGAF in your organization - sample
Similar to Introduce TOGAF in your organization - sample (20)
Recently uploaded
Recently uploaded (20)
Introduce TOGAF in your organization - sample
- 2. What is Enterprise Architecture? Enterprise Architecture Committee
- 3. The world of Program and Project Management Alignment Strategy Planning Execution Lessons Learned Adjustment Business Process Improvement It is a journey Vision Mission about This methodology supports Constant Change Effectively The Enterprise Architecture Framework
- 4. So, what’s the problem we are trying to address? Enterprise Architecture Committee
- 5. Misalignment of strategies: • Struggle for business and IT to be consistently on the same page • Business leaders frequently view IT as a roadblock The Business – IT Challenges: IT may have trouble proving which of their projects support which business strategies Theresult?
- 6. Misalignment of funding: • Lack of understanding and visibility into the business goals, priorities, and demands Funding decisions for IT projects that provide little or no value to the business Theresult?
- 7. Dependencies and impacts not understood: • Lack of up-to-date information on H/W, S/W, application, lifecycle, procurement, funding, political dependencies When business goals, priorities or project timelines change, neither the business nor IT can easily determine the impact let alone quickly respond and adjust Theresult?
- 8. How do we tackle these? Enterprise Architecture Committee
- 9. TOGAF – The Open Group Architecture Framework
- 10. 1. TOGAF - Introduction 2. Why TOGAF 3. What is TOGAF
- 11. TOGAF – The Open Group Architecture Framework The Open Group VISION Boundaryless Information Flow TM achieved through global interoperability in a secure, reliable and timely manner
- 12. EA principles out there… 1987 Zackmann 1992 EAP EnterpriseArchitecturePlanning TreasuryInformationSystem ArchitectureFramework 1997 TISAF 1999 FEAF FederalEnterpriseArchitecture Framework 1995 TOGAF TheOpenGroupArchitectureFramework DODArchitectureFramework 2003 DOD AF Finally, how about….. AZArchitectureFramework ???? AZ AF2009 TOGAF 9.1 TheOpenGroupArchitectureFramework (9.1)
- 13. They are all interrelated
- 14. Why TOGAF? Enterprise Architecture Committee
- 15. The ADOA* MISSION Proudly serving the people of Arizona, the Arizona Department of Administration enables government agencies to operate efficiently and effectively by providing support services and serving as a leader of statewide programs and solutions *AZ Department of Administration
- 16. It’s all about ALIGNMENT, constantly ADOA TOGAF Enables government agencies Serve the people of Arizona Boundaryless(in a) (manner) By providing support services To operate efficiently and effectively Information flow Global interoperability Secure, Reliable and Timely manner (for free) (through) (in a) (and)
- 17. What is TOGAF? Enterprise Architecture Committee
- 18. • Consists of VII parts which form the framework • A detailed method and a set of supporting tools for developing an enterprise architecture TOGAF is a framework • It may be used freely by any organization wishing to develop an enterprise architecture for use within that organization
- 19. BusinessVisionandDrivers PART I (Introduction) • High-level introduction to the key concepts of Enterprise Architecture and in particular the TOGAF approach • Contains the definitions of terms used throughout TOGAF • Release notes detailing the changes between this version and the previous version of TOGAF BusinessCapabilities
- 20. BusinessVisionandDrivers BusinessCapabilities PART II (Architecture Development Method) • Core of TOGAF • Describes the TOGAF Architecture Development Method (ADM) - a step-by-step approach to developing an enterprise architecture PART III (ADM Guidelines and Techniques) • Contains a collection of guidelines and techniques - available for use in applying TOGAF and the TOGAF ADM ADM Guidelines and Techniques (Part III) Architecture Development Method (Part II)
- 21. BusinessVisionandDrivers PART VI (TOGAF Reference Tools) • Architectural reference models - TOGAF Foundation architecture - Integrated Information Infrastructure Reference Model (III-RM) Enterprise Continuum And tools (Part V) TOGAF Reference Models (Part VI) Architecture Content Framework (Part IV) ADM Guidelines and Techniques (Part III) Architecture Development Method (Part II) PART IV (Architecture Content Framework) • Describes the TOGAF content framework • Re-usable architecture building blocks • Overview of typical architecture deliverables BusinessCapabilities PART V (Enterprise Continuum & Tools) • Discusses appropriate taxonomies • Tools to categorize and store outputs of architectural artifacts
- 22. BusinessVisionandDrivers Enterprise Continuum And tools (Part V) TOGAF Reference Models (Part VI) Architecture Content Framework (Part IV) ADM Guidelines and Techniques (Part III) Architecture Development Method (Part II) PART VII (Architecture Capability Framework) Discusses the • Organization, skills, roles, & responsibilities to operationalize the EA function BusinessCapabilities Architecture Capability Framework (Part VII)
- 23. Connecting the dots on TOGAF 9.1 FRAMEWORK Enterprise Architecture Committee
Editor's Notes
- Welcome to the Executive presentation on Enterprise Architecture for the State of AZ As you are aware we have been putting renewed emphasis on EA since the beginning of 2011 and it is also highlighted in the Statewide Strategic Plan as well as the ADOA 5-year strategic plan. EA itself has been in place in the State for the past 10 years and we do have a reasonable set of policies, standards and procedures. We have been collecting IT plans from agencies and also have a rudimentary inventory of assets. However, it is time to take this to the next level and keep pace with new demands and lesser resources. To meet these requirements we have to strategize, plan and execute in a disciplined and systematic manner so that the dots can be connected and we can see the bigger picture.
- What is it about? Every agency has a vision, mission, process, technology and people to deliver services to the citizens. A vision that arises out the demands of the citizens. To deliver any service effectively we need to follow a process and methodology from a holistic perspective never losing sight of the mission and purpose. To deliver these services in a rapidly changing environment, EA provides the framework. It aligns with execution through Project/Program management and facilitates change in a controlled fashion by keeping pace with any business process change or improvement. This gives rise to a need for a methodology that supports business as it constantly balances demands and services. IT is a key enabler that has to work in tandem with business. Enterprise Architecture is the discipline ensures business – IT alignment.
- How many applications are out there that have limited or no use – The users still have their own applications and ignore the one provided by IT because ‘it doesn’t do what they want’..
- How many agencies have a robust ITSM discipline? How many have true asset management? How many us have the information on financial impact readily available? It increases the risk of making bad decisions. Having all this information reduces that risk and makes us nimble and responsive
- In order to get everybody on the same page, we have put together a brief presentation on methodology and principles that will be used to adopt EA statewide The following topics will be covered during this brief presentation: What is TOGAF, Why TOGAF, How are we going to use it, Governance, Who are the participants, Next Steps, Reporting/Feedback/Intake mechanisms As we go about maturing EA across the State we will be reporting to you periodically on our progress
- TOGAF – stands for The Open Group Architecture Framework It’s vision – Boundaryless Information Flow ™ achieved through global interoperability in a secure, reliable and timely manner
- There are many principles out there for EA starting from Zackmann in 1987 EAP, TOGAF, TISAF, FEAF, DOD AF..etc. The fundamental principles are the same – except they have been tailored for the individual agencies Note: some of them are for the Government!!! Well at some time, who knows, we may have our own.
- It is interesting that these principles did not get developed in isolation. On the contrary they influenced and fed on each other – an example of evolution and improvement in itself, over the years. TOGAF is on ver 9.1 currently and as we mature, we may track the changes more closely to ensure alignment or tailoring. Typical changes introduced are mostly as a result of changing business models and improved IT. Demand changes prompt business changes. Business Changes prompt IT changes. Usually Technology challenges business models. That’s when EA comes in with Policies, Standards and Procedures. E.g. Cloud, personal mobile devices, Privacy etc. (TAFIM – Technical Arch. Framework for Info. Mgmt. POSIX – Portable OS Interface for Unix JTA – Joint Technical Architecture – for military interoperability JTAA– Joint Technical Architecture (Army) C4 ISR – Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance)
- Before we answer that question, let us review ADOA’s mission in that context as well and later we will go through a mapping exercise which will show us alignment and answer some of the questions above
- Note there is reference to both business and IT indirectly. EA is about BITS Architecture not just IT!!!
- PART IV (Architecture Content Framework) Describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable architecture building blocks, and an overview of typical architecture deliverables. PART V (Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise. PART VI (TOGAF Reference Models) This part provides a selection of architectural reference models, which includes the TOGAF Foundation Architecture, and the Integrated Information Infrastructure Reference Model (III-RM).
- PART IV (Architecture Content Framework) Describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable architecture building blocks, and an overview of typical architecture deliverables. PART V (Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise. PART VI (TOGAF Reference Models) This part provides a selection of architectural reference models, which includes the TOGAF Foundation Architecture, and the Integrated Information Infrastructure Reference Model (III-RM). PART VII (Architecture Capability Framework) This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture function within an enterprise.
- We built a set of blocks for each part of EA in TOGAF This diagram shows how are the blocks connected
- Welcome to the Executive presentation on Enterprise Architecture for the State of AZ As you are aware we have been putting renewed emphasis on EA since the beginning of 2011 and it is also highlighted in the Statewide Strategic Plan as well as the ADOA 5-year strategic plan. EA itself has been in place in the State for the past 10 years and we do have a reasonable set of policies, standards and procedures. We have been collecting IT plans from agencies and also have a rudimentary inventory of assets. However, it is time to take this to the next level and keep pace with new demands and lesser resources. To meet these requirements we have to strategize, plan and execute in a disciplined and systematic manner so that the dots can be connected and we can see the bigger picture.