• Save
eFramework Presentation MinEd Bill Olivier
Upcoming SlideShare
Loading in...5
×
 

eFramework Presentation MinEd Bill Olivier

on

  • 794 views

Presentation by Bill Olivier at eFramework meeting Oslo 26012007

Presentation by Bill Olivier at eFramework meeting Oslo 26012007

Statistics

Views

Total Views
794
Views on SlideShare
794
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

eFramework Presentation MinEd Bill Olivier eFramework Presentation MinEd Bill Olivier Presentation Transcript

    • The e-Framework for Education & Research
    • an Overview
    • Ministry of Education, Norway 25 Jan 2007
    • Bill Olivier, JISC
  • The e-learning framework
    • Started in 2003
    • Emerged from JISC’s work on virtual learning environments and managed learning environments
    • Attempt to address various problems by using service oriented approaches
  • The challenges: silos
    • Core data and functionality are locked up in individual applications .
      • Monolithic applications duplicate functionality.
      • Difficult to customise systems to meet diverse requirements
      • Legacy systems (& integration) costly to replace
    • Result: obstacles to deliver users with:
      • The right information
      • At the right time
      • In a familiar environment
  • The challenges: lack of co-ordination
    • In isolation, different communities and different domains:
      • duplicate effort
      • solve the same problem in incompatible ways
      • solve different problems in incompatible ways
    • Result:
      • no network effect
      • lost opportunities for synergy
  • The challenges: isolated innovation
    • New e-learning tools fail to flourish because:
      • too many resources are lost solving ‘boring’, known problems
      • too many dependencies on unique infrastructures
      • too idiosyncratic to be sustainable beyond a particular person or project
    • Result:
      • poor return on R&D investment
      • slow development of new practice
  • A potential solution
    • Service oriented approach:
      • Breaks down common functions into discrete services…
      • … used independently of underlying systems, applications and platforms.
  • E-Learning Framework origins
    • The ELF built on previous work:
      • the Open Knowledge Initiative (OKI) and Sakai
      • designs by Carnegie-Mellon Learning Systems Architecture Lab
      • Sun e-learning platform
      • the IMS Abstract Framework
      • large number of SOAs from other domains
  • Take one
  • Take two
  • Developing components of the e-learning framework
    • Funded projects during 2004-2006 and ongoing
    • Toolkit projects to build web service interfaces
    • Demonstrator projects to show how web services can be implemented and used in university or college systems
    • Examples
    • Why the e-Framework?
      • Growing awareness that the problem that the ELF was trying to solve was a wider issue
      • JISC already using SOA for its Information Environment activity (architecture for digital library resources)
      • Same issues and approaches in research area (e-Science and the Grid using Web Services)
      • Same issues for administration
    • Successful expansion of the ELF to support other domain areas, building on previous activities
    • Gained a high level of international interest and enthusiasm to collaborate
  • What is the e-Framework now?
    • The International e-Framework Initiative
      • JISC
      • Australian Dept for Education, Sc. & Technology
      • SURF in Holland
      • New Zealand Ministry of Education
    • The e-Framework Knowledge Base/Web site
      • Most visible output of the Initiative
    • Each Partner’s own e-Framework Programme
      • Supports the first two
      • Co-operates with other Partners
      • Works with its other Programmes to add to & gain from the e-Framework
  • Sharing Services
  • Scope
    • The e-Framework context is the communities active in education and research, and the technical infrastructure that supports them.
    • (Technical infrastructure is defined as including applications, services and the network.)
    • The e-Framework analyses, models & documents USER DOMAINS (goals, tasks, processes, info, etc.) and the supporting SERVICES .
  • Guiding Principles
    • A service-oriented approach to system and process integration
    • Development, promotion and adoption of Open Standards
    • Community involvement in development of the e-Framework
    • Open collaborative development activities
    • Flexible and incremental deployment
  • Purpose
    • To:
    • Provide a strategic approach to technical infrastructure development within and across domains
    • Provide a consistent technical vocabulary
    • Provide a focal point for interaction with software developers and those providing services to education and research.
    • Act as a catalyst for the development of further specifications and standards
  • Benefits - Partners
    • A map of a complex environment
    • A strategic planning tool for
      • Prioritised investment in standards
      • Prioritised investment in interoperability technologies
    • Improved return on investment through coordination and collaboration between Partners
  • Benefits - Institutions
    • Alignment of strategies and infrastructure development
    • More choice of systems and suppliers
    • Improved return on investment in existing systems
    • More effective communications between communities through shared understanding
    • Establishing interoperability within and across institutions and national boundaries
  • Benefits - Developers
    • Better engagement with, & understanding of, institutions, domain experts and users
    • More rapid development cycles through reusable components
    • Faster response to new requirements
    • Entry of small innovative players into the market
    • Communication and collaboration between developers
    • Flexible business models for software development
  • How Do We Identity Problems?
    • Work with existing communities – for JISC these might be
      • UCISA (have Identified Top 10 Issues)
      • CETIS SIGs (start from existing Reference Models)
      • AUA, HEA Subjects Centres…
    • Work with them to Map their Territory (Domain Map)
      • Start Rough and get Approximate ‘Big Picture’
      • Fill in Detail over Time to Evolve Models (Agile Modelling)
    • Reflect on the Map
      • Identify Problem Areas
      • Agree Priorities
      • Study Problems in the Real World
  • Applying this in the e-Framework
    • Technical development takes place in a vacuum
    • There is always a human context
    • A key aspect of the SOA approach is seeking to link ICT services to human tasks and context of use
    • In JISC e-Learning Programmes this has been done through:
      • Reference Models (now Domain & Process Models)
      • Service Adapter Toolkits
      • Demonstrators
      • Pilots
  • From Reference Modelling to Domain Mapping
    • The-Learning Reference Models have now completed
    • They have produced very useful resources as a starting point for any development project in their domain
    • But “Reference Model” has narrower, normative associations
    • Seeking reusable Domain Knowledge, that is relatively stable
    • This forms the basis for Practitioners to:
      • Identify and agree Key Problem Areas
      • Collaborate with Developers (open source or commercial) in Co-evolving Practices, Processes & Software
      • Ensure Coherence across their ‘Family’ of Applications
      • Save re-doing the same work (differently) each time
  • Process Models Domain Learning/Teaching/Research/… Process Learner / Teacher / Researcher Need User’s Computer Use Case 1 User’s Computer Use Case 2 User’s Computer Use Case 3 Many tasks require several people to work together in a workflow. In such cases Scenarios & Process Models set this out, showing how people and computers work together to accomplish the task.
  • Process Models Domain Learning / Teaching / Research /… Process Personal Environment Container with Lightweight Application User Interface Application Specific Functions Service A Interface Service B Interface Service C Interface Service A Interface Service A Service B Interface Service B Service C Interface Service C Hot-download Application Components
  • Service Usage Models User’s Computer/Portal Use Case ‘ Orchestration’ Web Service Service A Invoke Service B Invoke Typically User Tasks need to call on several services. ’Orchestration’ standards are emerging for creating ‘composite services’. Typically User Tasks need to call on several services. ‘Orchestration’ standards are emerging for coordinating a set of services. The e-F calls a coordinated set of services a ‘Service Usage Model’.
  • Emerging Tools to Support Process Modelling & Development
    • As well as standards to describe processes there is an emerging standard for graphically displaying processes
    • The OMG has developed BPMN 1.0 & now working on v2 (Business Process Modelling Notation)
    • Developers are incorporating it into graphical tools
      • To model processes
      • To generate executable code
    • ICT support becomes flexible, easy to create and change, rather than set in hard to change system
    • The lightweight composite application is easier to create
    • Interchange between practice and process becomes easier
  • Domain Maps & Models Domain Map (informal) or Model (formal) Workflow/Process Models (Human + Systems) As-Is & To-Be Service Usage Model (a set of services organised and coordinated to provide an function within an application) Application (UI, application specific software, service coordination) Domain Model Stakeholder & Role Models Goal & Function Models Domain Information Model Domain Context Model Scenarios (Workflow Narratives) Domain System Model Workflow/Process Models (Human + Systems) As-Is & To-Be Application (UI, application specific software, service coordination) Workflow (Practice & Process) Models (Human + Systems) As-Is & To-Be Project Case Studies Process Model Process-specific Information Model Practice Description / Model Use Case Model Service Usage Model SUM Description and Use Case Services Used Service Use Cases Internal Service Co-ordination Orchestration Choreography Application Specific Layer User Interface Application Specific Functions Service Consumer Interface Service Consumer Interface Service Consumer Interface
  • Documented by:
    • Domain, Information, Process and Service Usage Models
    • Services: Interface Types, Definitions and Descriptions
    • Guides, Methodologies, Analysis
    Service Usage Models
  • Partner Collaboration
    • 6 Collaboration Themes... 20 SUMs for:
      • National level implementations of Shibboleth / SAML for authentication and authorisation
      • Examples of Enterprise Architectures in institutions based on SOA
      • Federated Repositories
      • Movement of student data between institutions
      • Collation of research quality data
      • e-Portfolios (separate from 4)
  • Progress
    • Partnership now active
    • Initiatives in each partner country
    • Knowledge base now ‘live’
      • Free to use
      • Soon open to contributions
      • www.e-framework.org