this is for holding javascript data
kultsova edited section_Learning_Management_Systems_and__.tex
almost 9 years ago
Commit id: 981d11f8ebfd9fbfc0cc0ea257101f8f229661c5
deletions | additions
diff --git a/section_Learning_Management_Systems_and__.tex b/section_Learning_Management_Systems_and__.tex
index a64e315..2b915b7 100644
--- a/section_Learning_Management_Systems_and__.tex
+++ b/section_Learning_Management_Systems_and__.tex
...
\section{Learning
Management Systems and Learning Content Management
Systems} System}
The modern LMS and LCMS systems \cite{Hatzilygeroudis} usually includes the following components: subsystems for learning administration, users management (learners, tutors, learning courses authors, system administrators), testing and knowledge assessment (that generates reports about learners achievements in the course and allows to manage the learning of content during learning the course), course learning management, learning sequence management, learning content management, content delivery management, API for interaction with external subsystems.
The common structure of LMS and LCMS systems (Fig. \ref{fig:LMS}) includes the following relations: 1 - base information about LMS users, 2 - learning achievement reports, tests planning, 3 - learning course achievements, 4- current learning course achievements for modules of the course, modules tests results, 5 - learning content administration, 6 - testing results (for modules of the course), 7 - information about learning sequence of modules of the course, 8 - content selection for the learning course, 9 - content request, 10 - course learning management using the API (with third-party software), 11 - managing the content representation for the learner, 12 - content package, 13 - selected learning content, 14 - results of content selection from the content repository, 15 - representation of the learning content for learner, 16 - interactions using API with HTTP-requests.