1 / 21

Tool Support for the “Evolving EA” Gradual Adoption of TOGAF 9 with iServer

Enterprise Architecture for Microsoft Office and Visio users. Tool Support for the “Evolving EA” Gradual Adoption of TOGAF 9 with iServer. t. +44 (0) 870 991 1851 f. +44 (0) 870 011 6412 e. enquiries@orbussoftware.com. www.orbussoftware.com/ea. Background.

thurman
Download Presentation

Tool Support for the “Evolving EA” Gradual Adoption of TOGAF 9 with iServer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Architecture for Microsoft Office and Visio users Tool Support for the “Evolving EA” Gradual Adoption of TOGAF 9 with iServer t. +44 (0) 870 991 1851 f. +44 (0) 870 011 6412 e. enquiries@orbussoftware.com www.orbussoftware.com/ea

  2. Background Peter Bates – Product Manager @ Orbus Software Orbus Software develop the iServer product range • The Enterprise Architecture Tool for Microsoft Visio & Office users • Including.. a TOGAF 9 Starter Pack Regional Customers Include..

  3. This Presentation Challenges for Organisations starting out with TOGAF9 What is iServer? Tool Support for the “Evolving EA” – How iServer supports the gradual adoption of TOGAF 9 • Structuring EA content within a TOGAF Architecture Repository • The First TOGAF ADM Iteration • Future ADM Iterations…

  4. Many of the Organisations we speak to… The EA Practice is Often Relatively New • Early Phase “EA Maturity” • Limited Resources • Restricted Budget for EA tools Have identified TOGAF 9 as the chosen method Architects have completed T9 Certification TOGAF 9 adoption perceived as difficult with current resources/tools

  5. What tools do they currently use? Microsoft Visio Microsoft Excel Microsoft Word Process Models Lists of “stuff” Documents Architecture Models Data Models PowerPoint Network Diagrams Stakeholder Presentations Servers / hardware Functions, Applications, Interfaces... Org Charts, UML diagrams, Roadmaps, Flow charts...

  6. The Need for an EA Tool When the Microsoft products aren’t enough! Lack of Common Modeling standards. Everyone does their own thing. No collaboration. People work as individuals or in Silos No single source of Truth. Information is stored all over the place. Limitations of Microsoft Office/Visio Duplication rather than re-use (constantly re-invent the wheel) Very difficult to make informed business decisions Time consuming to manage complex content (eg. relationships) in Excel

  7. What is iServer? An Enterprise Architecture Repository and Modelling Environment for Microsoft Office and Visio Users 1. Stay in Microsoft Visio Visio, Word, Excel and PowerPoint are the core interfaces for creating process information 3. Quick Start 2. Easy to Use Re-use your existing models and documents Easy to learn, because users are familiar with Visio and Office 4. TOGAF Starter Pack Complete TOGAF 9 Implementation – ADM support, meta-model, templates and tools

  8. Phase 1 – Structuring EA Content within an Architecture Repository

  9. Adopting the Architecture Repository Import your existing Microsoft Visio, Word, Excel, PowerPoint Documents Visio “Shapes” and Excel “Rows” become re-usable “Building Blocks” in the repository, aligned to the types within the TOGAF meta-model Initial focus on early phases of ADM Repository Structured upon TOGAF 9 ADM

  10. Understand Existing Content and Gaps Content Meta-model Content Meta-model View Points • How does existing content align to meta-model? • Identify Gaps • Select and adapt Viewpoints relevant to stakeholders • Remove complexity – hide what isn’t needed

  11. Templates for each phase of ADM Model Templates, with Examples Document Templates Catalogues Matrices

  12. Phase 1 – Key Wins Not yet attempted an ADM Cycle.. But a definite improvement.. Single Source of Truth (Repository) Collaboration on EA content now possible Understand how existing content aligns to TOGAF 9 Started to introduce standards around EA content creation – Viewpoints / Templates, Notations Started to bring structure to Content (T9 Meta-model)

  13. Phase 2 – Tool Support for TOGAF ADM

  14. Supporting an ADM Iteration Initial ADM Iteration is often limited in scope - customers focus on first half of ADM - using subset of meta-model - with selection of relevant viewpoints / docs Generate Documents, Models, Matrices and Catalogues Develop AS-IS and TO-BE Architectures Use Gap Analysis reports to identify gaps

  15. Make Informed Business Decisions UNDERSTAND THE IMPACT OF CHANGE Use the Impact Analysis tool to understand the dependencies across the domains with an enterprise architecture. Eg. Understand the impact / cost benefit of retiring an application

  16. Create Dynamic Views HEAT MAPS Use heat maps to create dynamic visualisations – - Highlight Problem areas or Duplication - Identify or visualise retirement targets

  17. Visualise Change over Time BASELINE, TARGET AND TRANSITION ARCHITECTURES Roadmaps to show work packages delivering capabilities Present the transition from baseline to target via a number of transition states

  18. Further ADM Iterations Evolve the scope of each ADM cycle • View points / templates used • Meta-model scope Support for multiple co-existing Strategic, Segment and Capability ADM Iterations Re-use Models, documents, “solutions”, “patterns” and building blocks from previous iterations Integration with… Process Modelling, ITIL, EA frameworks, Reference Models (eg. FEA, AGA), CMDB, ..

  19. Showcase EA Work to the Business INTRANET ACCESS TO REPOSITORY Showcase EA Models and Deliverables online – Engage the business and gather feedback

  20. Summary TOGAF 9 Adoption with iServer Start Small Gradual Adoption of TOGAF 9 Slowly Expand Scope over many ADM Cycles iServer A Microsoft Visio/Office – based approach to EA Simplifies TOGAF 9 adoption Increase Visibility of EA within the Enterprise - Portal Tools to support different levels of EA Maturity

  21. Further information: www.orbussoftware.com Peter Bates – Product Manager, Orbus Software e. peter.bates@orbussoftware.com t. +61 42 459 1999

More Related