1 / 12

MLE Developers Pack

MLE Developers Pack. Aim The MLE Developer’s pack will provide a single, coherent source of information for institutions that are interested in the development process for an institutional or cross-institutional Managed Learning Environment. Why.

cala
Download Presentation

MLE Developers Pack

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. MLE Developers Pack Aim • The MLE Developer’s pack will provide a single, coherent source of information for institutions that are interested in the development process for an institutional or cross-institutional Managed Learning Environment.

  2. Why • addressing the problem of disseminating and achieving programme aims • To access project materials, they needs to be organized and presented in way that allows the user to:- -understand all the steps and issues involved in developing an MLE; -dip in to relevant sections, depending where they are up to in the implementation process; -drill down the information to a supporting layer of practical example, guidance and tools.

  3. Key Requirements • will not claim to be ‘the right or only way ‘ to create a MLE, but will emphasis the different approaches taken and options available. • It will follow a process model, and attempt to provide step-by-step advice for institutions that are already, or are planning to, develop a MLE (as far as this is possible); • It will be based upon the key issues for MLE development identified by the MLE projects so far; • It will be much more detailed and provide practical advice and guidance rather than just brief overviews;

  4. Key Requirements It will closely refer to other reports and tools that have been produced, particularly by JISC-funded projects and will provide the main route into those resources; It will also refer to other relevant reports and studies, e.g. JCALT and TechWatch reports. The pack will be developed so that the framework can be expanded and developed further as new information and resources arise. This is important given that MLE is a developing concept.

  5. Overview of Structure Level 1 Introductory overview Overview of each section Overview of each section Overview of each section Level 2 [approx 7 sections] [Sub-sections of each section] Level 3 [Short description of each resource] Level 4 Resources – diagrams and models; case studies; technical tools; surveys; methodologies Level 5

  6. How Treat it like a book and commission consortium :- • lead consultant, • Professor Oleg Liber, Bolton Institute of Higher Education • commissioning editor • Sarah Holyfield - Bangor University • section editors • Paul Ricketts – VP City College Manchester • Professor Tony Toole - Carmarthenshire College

  7. Budget and Timescale • Budget :- 50,000 Time scale :- • testing and feedback from a user group by 1st July 2003. • launched in October 2003.

  8. Content - Sections • Policy issues: Why implement an MLE? • Organizational questions: What is the current state? • Technological options • Establishing requirements • Designing the MLE • Implementation issues • Embedding MLEs into Institutions

  9. Exit strategy • Emphasis on sustainability, not snap shot in time. • JISC InfoNET, will host pack and continue its update/development • Embedding materials ? • Potential model for other areas – content and the IE ?

  10. Relevant material Resource layer, examples of • User surveys, requirements • SW + HW reviews/evaluations • System designs • Guidelines • Process reviews, flow diagram's Case studies – this is how we tackled it

  11. Why we wanted an MLE Why did your institution decide it wanted to move in this direction? What were the drivers – external? Political? Internal? Particular ideas or vision? What was (is) the overall aim? How did it go about making a decision to do this? Who was involved? how were any advantages and disadvantages discussed? What institutional strategies were involved? What methods did it use – consultation, meetings, questionnaires etc?

  12. How did we do things before we began work on the MLE? What state was your institution in when you began the project? –how did things work then? (paper based/technology based systems?) –how did you find out/analyse/model things as they were? (systems analysis, focus gps, questionnaires, modeling, talking etc) Who were the key knowledge holders and how did you involve them? What technologies did the institution have in place? Did you use any formal methodologies? What did you learn? – that your approach worked well?, that you didn’t pay enough attention to certain things? etc? How did you capture and represent these models

More Related