1 / 40

MCS E-learning Development Overview

MCS E-learning Development Overview. Presented by Brajesh Upadhyay Jordan Berkow Terri Sanborn. Points We’ll Cover. MCS Workflow Types of Lesson Players Prioritization LMS vs. Hosted Lessons Instructional Design Multimedia Development & Technology; QA Web Development & ID/templates; QA

allayna
Download Presentation

MCS E-learning Development Overview

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. MCS E-learning Development Overview Presented by Brajesh Upadhyay Jordan Berkow Terri Sanborn

  2. Points We’ll Cover • MCS Workflow • Types of Lesson Players • Prioritization • LMS vs. Hosted Lessons • Instructional Design • Multimedia Development & Technology; QA • Web Development & ID/templates; QA • Planning 2008 Enhancements

  3. MCS Workflow Product Owners Development LMS Client Services E-learning planning & scoping Source content Peer review Editing Copyediting/proofing CD duplication/inserts & marketing materials Instructional design (formatting only) Web development (internal only) Media production Assembly & QA Online reviews Revisions & updates Custom work & demos Maintain source files & templates; back-end Lesson database mgmt. MCS online catalog Library cards Certificates Evaluations User management Build releases ‘Skills’ & non-content activities MCS Change Control Committee Learner support Client support

  4. MCS E-learning Development Brajesh (Director) Jordan (Multimedia & Technology) Terri (Web Development) Staff of 3 Vendors Contractors Staff of 3 Instructional Design (formatting only) LearningMate (production related)DHD Entertainment (video & audio)Contract media developers (Flash media)

  5. Types of Lesson Players(a.k.a. “interface” or “skin”) • KDS I – Old style MCS lessons (open browser) (content model 1) • KDS II – New style lessons (closed browser) (content model 2) • Limited Service - SME uses simple SME Guidelines; core templates • Full Service - Trained ID must be involved; all templates Both can use all our Flash exercise templates (6-8 new in 2008) Two new lesson players coming in 2008 (1 open; 1 closed) • Hosted or hybrid(content model 3)(a.k.a. “linked” or “third party”) _________________________________________________________________ Non-Web friendly or built via authoring tools • Conversion issues w/non-Web types (Director, Authorware, ToolBook) • Should avoid authoring tool generated (Lectora, Trainersoft)

  6. How We Prioritize • Scoped internal project work • Scoped custom client work • Change requests for LMS lessons • Change requests for hosted lessons (SBN CE, ENA ENO, etc.) • Courseware features/functionality enhancements • Out-of-scope project work (including custom screens & media) • Special requests for product owners (demos, one-offs, etc.) • Special requests for clients (unless paid for) • Special requests for MNS (L. Zacks), MNC/MNI (L. Pilla) or others

  7. Elsevier ‘Multimedia Task Force’ • John Wheeler (book ancillaries), Jim Twickler (Evolve) and Brajesh Upadhyay (MCS and MNS) • Global Elsevier supplier consolidation • Cost control for commodities • Standardization • ‘Preferred Vendor’ status • Elsevier Chennai (India) office

  8. Pros/cons of LMS vs. Hosted Lessons Hosted - More customizable (design & functionality) - Portable(but no copy protection) - Integrates into any LMS w/SCORM(but not always smoothly) - Quicker development of features/functions - Total filesize generally larger; less efficient - SCORM issues - Vendor owns the back-end; proprietary authoring system is used - Changes/updates take longer & cost money - Version control issues - Possible backward compatibility issues later LMS Integrated - Smoother functionality; fewer bugs - MCS owns the back-end - Efficient (ASP/database; load-once elements & centralized media) - Benefits from LMS build releases (all parties get same features/functions) - Easier to make change requests; no external cost for most - Not portable (better copy prevention) - Must rely on Kevin for most enhancements (takes longer)(but no external cost)

  9. Importance of Instructional Design (ID) • Develops blueprint for web development, media production & assembly (storyboard) • 50% content manipulation; 50% technical/formatting • Content manipulation • Ensures all the learning objectives are addressed in the content, exercises, and post-test • Infuses innovative, engaging, and interactive learning (fully aware of development parameters and customization capabilities) • Organizes the content topics and exercises in a logical manner for online learning (may change content; rewrite) • Ensures the content and corresponding media clearly support the content topics • Validates the content is clearly and concisely written for the online medium • Designs, creates, or reviews exercises and the post-test to successfully check the learner’s knowledge of actual presented content

  10. Importance of Instructional Design (ID)(contd.) • Technical/formatting • Full knowledge of screen/media templates (storyboard tool) and development capabilities • Cannot design in a vacuum; dictated by delivery format • Consequences of non-compliant SBs to scope • Internal resources (time) • External vendor/contractors (time & cost)

  11. Multimedia DevelopmentJordan Berkow Stakeholders Standards Content Vs. LMS Changes IT Development 2007 Accomplishments

  12. Standards • Media Standards • Templates • Current Trends • Storage • Back up, source files • Exercise Standards • Templates • Version control

  13. Lesson Info Page Library Card Lesson Screens Screen QARs Test Questions Choices Answers Rationales Lesson Assignment Pages Test Instruction Page Test question layout Format pages load Evaluations Certificates Content Dev. vs. LMS/Platform

  14. Items outside our control User’s Browser Monitor size Resolution/aspect ratio ISP Connection speed Potential User-end issues

  15. IT Development/Applications • Reliant on IT/Apps for certain enhancements • Handle all platform issues • Work with Skills, etc. • Posts Linked Content to server

  16. LMS Database HTML Flash - Action Script Lesson Screens Screen Text Images Exercises Back-end vs. Front-end

  17. Approx. 40 SBN CE Lesson revisions to date Minor changes in ReadyRN, ENA, Periop & Neonatal Receive Change Doc Evaluate internal vs. LM Make changes Evaluate on internal site Alpha Review IT Dev. Update Live site Beta Review Support of Hosted Content

  18. 1806 LMS Lessons 1067 – Segment Owned (Nursing, Coding, CDS, USA Prepare) 739 – Customer Owned (primarily Joint Commission customized work) AHM – 18 Buck – 94 AHA Coding Clinic – 24 CME Doc – 11 Faye Brown 8 – 35 HFMA – 552 Jems Prepare – 140 Joint Commission – 15 eBDLS – 10 EMT Basic - 35 2007 Accomplishments 2007 change requests (total): 15,735

  19. 397 LMS Lessons 78 – Segment Owned 319 – Customer Owned Buck – 27 Joint Commission – 12 Spanish JC – 5 ENA Triage – 8 2008 CPT Changes – 6 Wound Management Tests - 10 Current 2008 Accomplishments 2008 change requests (to date): 3,806

  20. Web Development Dept. Role in Production & Assembly Terri Sanborn

  21. 3 Types of Development Tasks • Projects • Change Requests • Custom Lessons

  22. Projects • Scoped and scheduled • Take priority • Assigned to a lead person – others may help as permitted in their schedule

  23. Workflow in Projects • Word document/storyboard • Create block name info (lesson id) • Create screens and test questions • Copy screen/test information from SB • Tag screens for layout and functionality • Lesson added in SQL • Posted and added to module • Reviewed/QA’d • Sent to product owner/client

  24. Block Name

  25. Block Name Information

  26. Screens and Test • Once the block name is created its time to add the screens and/or test screens • Standard naming convention for the screen and test numbers

  27. Screen or Test

  28. Screens

  29. Test

  30. Tagging Elements • Once the information is copied to the screen it is then tagged with HTML code for functional and visual output • Time spent on a screen is determined by the type of elements the screen has • Subscreens • PDFs • Tables

  31. Sample codingfor a ‘Did You Know’ note

  32. Sample codingfor embedding an interactive media

  33. Sample codingfor a simple table

  34. Sample codingfor a text-top/icons-bottom screen

  35. Change Requests • Updates to lessons already created • Each team member is assigned a group of states and projects • Checked daily • Notification with 72 hours of when change(s) can be completed

  36. Web Editor

  37. How We Get Change Requests

  38. Types of Custom Lessons • Customers unique lesson material • Joint Commission for repurposing Custom Client Lessons are assigned to staff when there is an open slot in the development schedule *custom development work is 2nd priority to segment owned work

  39. Enhancements for 2008: Web Development • Pre/post-test enhancement for learners • Support for multi-select choices (checkboxes) • Support for an optional final only feedback to questions • Addition of media icon next to any question (embedded or opens new window) • Removal of unnecessary 'go to question n' anchor links • Graphical banner • Mouse-over glossary pop-up boxes • Via JavaScript layers, as in old lesson types) • Not manually created, rather pulled dynamically from the same Glossary list

  40. Enhancements for 2008: Multimedia • Two new lesson players (interfaces/skins), so we have 4 total to offer • (1) open size any screen resolution higher than 800x600 • One would have a drop-down menu design to reduce button clutter • (1) fixed for 800x600 screen resolution • Both would employ a curvy and/or retro look (more polished) • Both would use same color scheme to match current players/exercises • New set of Flash exercise templates/engines • Between 6-8 new types • A branching case study • Image map • Global/common enhancements to existing Flash exercise templates/engines • Addition of a pop-up layer for longer feedback in applicable exercises (as in old ENA lessons) • Up to 2-screen exercises, for those applicable (as opposed to creating separate 2-part exercises)

More Related