1 / 34

About Enterprise Architecture > Why we used EA >

This document outlines the integration of Enterprise Architecture (EA) in managing the external examiner process. It describes the steps involved in identifying candidates, entering data, and obtaining approvals from the review panel and quality team. The goal is to streamline operations by transitioning from manual to automated processes, highlighted by gap analysis for both current and desired states. Key resources, including ArchiMate and JISC tools, provide essential insights into optimizing organizational efficiency and ensuring that vital information is securely managed.

phuc
Télécharger la présentation

About Enterprise Architecture > Why we used EA >

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. About Enterprise Architecture >Why we used EA > Ray Reid

  2. Our External Examiner process > • Identify candidate • Enter information within database & spreadsheet • Approval panel to review new examiner • Quality team appoint candidate • Information is updated within database & faculty spreadsheet • Examiner is given an award to look after • Documents for award & application of Examiner is stored in both the faculties drive & Quality teams network drive

  3. As Is

  4. To Be

  5. Business Layer Actors Roles Processes

  6. Applications Layer Components Data Objects

  7. Artifacts Technology Layer System Software Devices

  8. A more complex example:Gap Analysis

  9. ‘As Is’

  10. Aim – automated process

  11. Manual steps gone

  12. What’s missing?

  13. Automated deployment

  14. ‘To Be’

  15. Gap Analysis

  16. A further complex example:Gap Analysis

  17. Server failure

  18. Artifacts unavailable

  19. Applications unavailable

  20. Impact on processes

  21. Getting more information

  22. Further Information • Enterprise Architecture • JISC Improving Organisational Efficiency Infokit: http://www.jiscinfonet.ac.uk/organisational-efficiency • Transformations Programme Resources: http://transformations.jiscinvolve.org/wp/jisc-resources/ • Archimate • http://www.opengroup.org/archimate • Specification: http://www.opengroup.org/archimate/doc/ts_archimate/ • Introduction: https://doc.novay.nl/dsweb/Get/Document-43839/ArchiMate_Language_Primer.pdf • Web site: http://www.archimate.org/ • Guides: https://doc.novay.nl/dsweb/View/Collection-4766 • Archi • http://archi.cetis.ac.uk

  23. http://www.opengroup.org/architecture/togaf/

  24. Archi

  25. Credits • Beijing City Planning Museum http://www.flickr.com/photos/ivanwalsh/3946668436/ photo by Ivan Walsh http://www.flickr.com/photos/ivanwalsh/

  26. Summary Process

  27. Summary create Process

  28. Summary create composed of Process Views

  29. Summary create composed of Stakeholders Process address concerns of Views

  30. Summary create composed of Stakeholders Process address concerns of Views describe The Enterprise

  31. Summary create composed of Stakeholders Process address concerns of Views coherence, overview describe Archimate The Enterprise

  32. Thank You

More Related