1 / 26

SURF and Architecture

SURF and Architecture. Ronald Ham. October 21 2008. Organisation. SURF is the collaborative organisation for universities , higher education institutions and research institutes aimed at breakthrough innovations in ICT . SURF. Innovation for Education Research &

garren
Download Presentation

SURF and Architecture

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. SURF and Architecture Ronald Ham October 21 2008

  2. Organisation SURF is the collaborative organisation for universities, higher education institutions and research institutes aimed at breakthrough innovations in ICT.

  3. SURF Innovation for Education Research & Business Processes Legal software for an illegal price Gigabit Internet for Higher Education and Research

  4. SURFfoundation Research Education Business Processes Innovation for Research Education and Business Processes SURF

  5. Why do we have SURF? • Collaboration makes sense • Economies of scale • Network effect • Chain effect • Information effect • Sharing also makes sense • Interoperability

  6. Strong – weak points + + Community Building + Overview of the workfield + Innovative - - From innovation to production - Architecture

  7. Projects to improve • Embrace SOA • e-Framework • EA • Projects aimed at Implementation

  8. SO(A) and e-Framework • Services are becoming more prevalent • A structure to document is needed • “Findability” • Usability • Reusability • Need for architecture is felt

  9. ARCHITECTURE • LEGO also needs to be tidied up • Map Services • Categorise Services • LEGO also has manuals to helpcreate the envisioned end product • Process descriptions Governance Business Process Models (BPM)

  10. Worlds that interconnect Processes and architecture Describing business processes Clarifying business processes Redesign where needed Services under architecture Describing what is already there / possible (as is) Describing what is envisioned (to be) Describing what is needed (gap) Describing what is used where and how

  11. What’s the reason for architecture • Communication • Communication • Communication • Alignment of Business to IT • Reduction of observed complexity • Improve decision process • Insight in processes • Communication

  12. Architecture as a theme • Communication platform (a web site) • Joint language selection • Sessions to promote architecture • Sessions to engage business and architecture (vendors) • Pilot projects 3TU – SaNS – e-Framework One thing is sure…Architecture is not something you can learn in a day!

  13. Architecture sessions • 3TU exemplar presentation • Layman course Archimate • TOGAF, DyA and Archimate • Open podium; Education logistics in Archimate • eFramework and Architecture • Architecture and semantics: can one survive without the other? • Input sessions for a new year

  14. Architecture activities • 3TU • SaNS • Mapping the e-Framework to Archimate • Architecture and standards

  15. evalueren onderwijs delen evalueren opleiding verzorgen management informatie Besturing bewaken studie voortgang ontwikkelen onderhouden onderwijs evalueren docenten Plannen kaders Rappor- tage Resultaat output Resultaat input afstuderen diplomeren uitschrijven studie intake studenten opstellen studieplan uitvoeren onderwijs Alumni, Studiestakers/ onderbrekers (Geïnteres- seerde) studenten werven/ beheren relaties begeleiden studie Mensen Middelen financiën roosteren faciliteren Ondersteuning SaNS: Process approach 14

  16. e-F and Archimate:How does it fit? Product domain Information domain Process domain Organisation domain Data domain Application domain Infrastructure domain

  17. Archimate domains

  18. Business function in symbols

  19. Architecture and standards: • Interoperability: • IT in the Chain • Collaboration in the chain • Aggregation over the chain • Architecture is a means to • Find the touch points • Comparable processes in the sector • Connections in the chain • Description of touchpoints • By matching services

  20. Standard part of the value chain Information processor e.g. UCAS/IBG Communication That sets the standard

  21. Standard in data Student data Comparable data: Comparable approach Student data

  22. Next phase • Programme information infrastructure

  23. Preliminary Framework And Principles A Architecture Vision H Architecture Change Management B Business Architecture Requirements management G Implementation Governance C Information Systems Architecture F Migration Planning D Technology Architecture E Opportunities And Solutions EA also requires • Vision • For SURF a common vision • Guided by Principles

  24. Joint activities • 3TU continued • Education logistics • Scheduling • Collaboration • Common language • Common vocabulary • Common vision?

  25. Lessons learned • One website does not make a community • One language does not mean one vision • Tool branding is stronger than standards branding • A shared vision will get you places… shared values will get you further, architecture is also about getting buy in. • Setting up information sessions works! • Ensure that you will get information from your community

  26. Thank you Ronald Ham 22 October 2008

More Related