Reference Hub4
A Software Design Model for Integrating LMS and MOOCs

A Software Design Model for Integrating LMS and MOOCs

Talent T. Rugube, Colin Chibaya, Desmond Wesley Govender
Copyright: © 2022 |Volume: 15 |Issue: 1 |Pages: 14
ISSN: 1938-7857|EISSN: 1938-7865|EISBN13: 9781683180340|DOI: 10.4018/JITR.299375
Cite Article Cite Article

MLA

Rugube, Talent T., et al. "A Software Design Model for Integrating LMS and MOOCs." JITR vol.15, no.1 2022: pp.1-14. http://doi.org/10.4018/JITR.299375

APA

Rugube, T. T., Chibaya, C., & Govender, D. W. (2022). A Software Design Model for Integrating LMS and MOOCs. Journal of Information Technology Research (JITR), 15(1), 1-14. http://doi.org/10.4018/JITR.299375

Chicago

Rugube, Talent T., Colin Chibaya, and Desmond Wesley Govender. "A Software Design Model for Integrating LMS and MOOCs," Journal of Information Technology Research (JITR) 15, no.1: 1-14. http://doi.org/10.4018/JITR.299375

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

Instructors often experience difficulties in selecting and sequencing relevant content for deployment into learning management systems. Human error and subjectivity is apparent. This study focuses on integrating learning management systems and massive open online courses with the goal of eliminating the human element in uploading content. As far as data sharing is concerned, learning management systems and massive open online courses have known weaknesses. The proposed integration aims to reach a tradeoff between the two systems. A requirements elicitation exercise was conducted towards identification of the component units of a hybrid system. The study utilized a mixed method approach to realize the foundation of the integrated design model. The findings, based on evaluation, showed that experts established completeness of the software design model. They, however, expressed the need for the designs to be extended towards accommodating artificial intelligence features. The proposed designs, thus, present a baseline framework upon which implementation considerations may be built on.