1 / 44

Designing an Effective Organisational Infrastructure Jim Petch – Co Director eLRC

Institute of Education Learning Technologies Unit 18 th January 2006 London. Designing an Effective Organisational Infrastructure Jim Petch – Co Director eLRC. eLRC Manchester Position. E-Learning is a driver……for… Organisational change driven by need to industrialise

foster
Télécharger la présentation

Designing an Effective Organisational Infrastructure Jim Petch – Co Director eLRC

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. Institute of Education Learning Technologies Unit 18th January 2006 London Designing an Effective Organisational Infrastructure Jim Petch – Co Director eLRC

  2. eLRC Manchester Position • E-Learning is a driver……for… • Organisational change driven by need to industrialise • Redesign of teaching and learning provision

  3. Organisational Change • The commercial sector is experiencing radical and far reaching changes in thinking about how enterprises are run and how the challenges of technology-led business operations can be met • The emerging requirements point to an end-to-end view of business processes and to a service view of what an organisation offers.

  4. Organisational Change • To achieve these qualities the enterprise needs a certain approach, and informed thinking indicates a service-oriented, component-based architecture

  5. Organisational Change • The IT strategy should be aligned with the business strategy neither bolted on to it nor driving it. A service-oriented, business requirements driven approach ensures greater alliance between IT and the business.

  6. Object Management Group • Main Ideas • MDA Model driven approach • SOA Service Oriented Architectures • To which we add the idea of • QoS Quality of Service Framework • To which we add the idea of • maturity (CMM model) and benchmarking (eMM)

  7. Model Driven Architecture

  8. The eLearning Lifecycle time Phases (time) Practices (activities)

  9. Organisation along Time Phases Organisation along Content Inception Elaboration Construction Transition initial elab#1 elab#2 cons#1 cons#2 cons#n trans#1 trans#2 • Practices • Business Modelling • Business Analysis and Planning • Requirements Analysis • Activity Planning • Project Management • Change Management • Design • Development • Deployment • Evaluation • Testing • Teaching • Learning • Environmental Refinement • Staff Development • Research

  10. The Lifecycle and Linked Processes In order to control the lifecycle one has to build into the model the things that influence and change it. Modelling the response to changes arising from the influence of the linked processes This kind of domain model (or enterprise metamodel) acts as a blueprint for modelling a specific enterprise.

  11. End-to-End Process Model

  12. Reminder!! • NB the models are of technologies, artefacts, people, …. • NOT technology alone!!

  13. Layered Architecture for SOA in e-Learning

  14. COVARM: The Manchester Validation Process

  15. High level alignment of processes

  16. Canonical Models • Moving from use cases to models of use to synthesised models to canonical models • 2 approaches • Empirical modelling • Cross domain mapping

  17. Checklists and Cross Domain Mapping • Checklists provide fullest available articulation of processes • Extensive checklists are readily available • Examples later

  18. Growing the World of Web ‘Service’ Components • JISC Reference Model Projects • LADIE – activity design • FREMA – assessment • COVARM – Course validation • eP4LL – e portfolio • XCRI – exchanging course information

  19. marketing Course validation recruitment planning Course info. registration design Activity design production Delivery Assessment E-portfolios Student record

  20. Key Issues about the map • They map is defined by the reference model components not by a higher principle • The reference models are not joined up • What is this a map of? An enterprise?

  21. Some Uncomfortable assumptions • Reference models are developed using a common method and with common tools • There is an agreed level of granularity • There is a map that is known • It is a map of the enterprise

  22. Service Oriented Architectures

  23. eLearning Services Learning Activity Profile Student Course Information ePortfolio Assessment Validation QoS Framework Services Pattern Wizard Checklist Agent Process Director Mentor General Purpose Services Personal Folder Event Archive Registration Workflow Schedule XML manager Contract Mechanisms and Utilities Directory Services Legacy Adapter Authentication Repository VLE IDE Data Warehouse Execution Environment and Data Management Structured Data Operating System Unstructured Data QoS Framework Application Architecture

  24. Service B Service A Deployment to different platforms Deployment to different platforms DL DL DL DL DL DL DL DL Reuse QF DL DL DL QF QF QF QF DL QF QF QF QF QF QF QF QF GP GP GP GP GP GP GP GP GP GP GP GP MU MU MU MU MU MU MU MU MU EE EE EE EE EE Services composed of components from the framework

  25. Business components Service Unit Course Student Record VLE Autonomous Business Components and Services

  26. But how? • Moving to a new enterprise architecture is a process affecting organisational as well as technical aspects. • The new roles, concepts and techniques may form a barrier to successful transition and it is necessary to help people adopt and use the architecture by providing a framework of guidelines, best practices, templates and tools. • These are actively integrated into the workprocesses rather than being merely reference documents. • The Framework is essentially a quality assurance tool that addresses the end-to-end business processes, their context, requirements and implementation.

  27. The Framework must provide a coherent set of mechanisms by which business requirements are modelled, their logic is turned into a flow of activities, which is then executed by a set of components, and their performance is monitored and evaluated.

  28. The QoS Framework Elements • QA mechanisms • Metadata builders • Models and Patterns • Standards • Guidelines and Best Practice

  29. Process Driven Knowledgebase

  30. PDK: Planning Student Support

  31. Adding Idea of Bridging Principles

  32. Maturity and Bechmarking

  33. Level 5: Optimising Process change management Technology change management Defect prevention Continuously improving processes Level 4: Managed Software quality management Quantitative process management Predictable processes Level 3: Defined Peer reviews Integration co-ordination Software product engineering Integrated software management Training program Organisation process definition Organisation process focus Standard, consistent processes Level 2: Repeatable Software configuration management Software quality assurance Software subcontract management Software project tracking and oversight Software project planning Requirements management Disciplined processes Level 1: Initial Capability Maturity Model- eMM

  34. Capability Maturity Model- eMM

  35. Capability Maturity Model- eMM

  36. Capability Maturity Model- eMM

  37. Benchmarking - Strategic Objective • A driver for joined-up design of organisations • Focus on metrics • Focus on ‘evaluation systems’ – that is systems that are designed for change- that is learning organisations

  38. So what?

  39. The Concept Gap • Getting people to understand • Communicating • Aligning • Sharing process and therefore knowledge and power

  40. The Strategy Gap • Where to go? • From which place? • How to get there?

  41. The Implementation Gap

More Related