17. Access Rights
“The permissions that are
granted to a user, or to an
application, to read, write
and erase files in the
computer. Access rights
can be tied to a particular
client or server, to folders
within that machine or to
specific programs and
data files” (PCMag, n.d.).
20. References
• Foreman, S. (2013a). Five steps to evaluate and select an LMS: Proven
practices. Retrieved from
http://www.learningsolutionsmag.com/articles/1181/five-steps-toevaluate-and-select-an-lms-proven-practices
• Foreman, S. (2013b). Six steps for successful LMS implementation(part 1
of 2). Retrieved http://www.learningsolutionsmag.com/articles/1214/thesix-proven-steps-for-successful-lms-implementation-part-one
• Foreman, S. (2013c). Six steps for successful LMS implementation (part 2
of 2). Retrieved http://www.learningsolutionsmag.com/articles/1217/thesix-proven-steps-for-successful-lms-implementation-part-two
• Gonzalez- Barbone, V., & Anido-Rifon, L. (2009). From SCORM to common
cartridge: A step forward. Computers & Education, 54, 88-102. Doi:
10.1016/j.compedu.2009.07.009
• Hartnell, J. (n.d.). Internet Literacy Class Orientation. Retrieved from
http://www.hartnell.edu/library/interlit/orientation
Notes de l'éditeur
Created management teams:Core team (internal)-e.g. project managers, specialists, team leaderExtended team (external)-e.g. trainers, instructional designers, managers, administratorsEstimated length of time using cloud technology= 3-6 months (Forman, 2013b)
Utilize Pearson eCollege project planning templateLMS configuration (e.g. training personnel, profiles & demographics, domains, security, catalog of courses, curriculum, assessments, evaluations, reports and notification functions) (adapted from Forman, 2013b)System integration (e.g. combining university accounts, confirm compliance & licensing requirements, use of portals, involve both IT and Pearson teams)Stages of data migration (e.g. user, courseware, adaptation of SCORM, common cartridge, web2.0, authorization of content, collaboration, outcome reporting) (Gonzales-Barbone & Anido-Rifon, 2009)Testing (e.g. test all areas of LMS, procedures & policies)Opening system for live performance (e.g. notification of all parties involved, contingency plans, preparing helpdesk, maintenance, backup for unexpected problems)
LMS configuration (e.g. training personnel, profiles & demographics, domains, security, catalog of courses, curriculum, assessments, evaluations, reports and notification functions) (adapted from Forman, 2013b)
System integration (e.g. combining university accounts, confirm compliance & licensing requirements, use of portals, involve both IT and Pearson teams)
Stages of data migration (e.g. user, courseware, adaptation of SCORM, common cartridge, web2.0, authorization of content, collaboration, outcome reporting) (Gonzales-Barbone & Anido-Rifon, 2009)
Testing (e.g. test all areas of LMS, procedures & policies)
Opening system for live performance (e.g. notification of all parties involved, contingency plans, preparing helpdesk, maintenance, backup for unexpected problems)
