6th International Workshop on Software Engineering for E-learning (ISELEAR’15)
Authors: Miguel Á. Conde, Gonzalo Esteban-Costales, Victor Rodríguez-Méndez, Camino Fernández-Llamas and Luis A. Amador
https://www.youtube.com/watch?v=Ikv5L6poT8M&index=1&list=PLboNOuyyzZ86rx78ZLHzZN8c1MHPLVhFe
Deploying a non-formal learning environment with Moodle
1. Definition and deployment of a non-formal
learning environment in a business
context
TEEM 2015
Dr. Miguel Ángel Conde González
D. Gonzalo Esteban-Costales
D. Victor Rodríguez Méndez
Dra. Camino Fernández Llamas
D. Luis A. Amador
13. Background and Requirements (IV)
Courses Home Visualization
Adding information to reports
Definition of ad-hoc SQL reports
Incentive management system
Integration with Brainshark
Training program visualization
Completion reports
16. Moodle Deployment (I)
Number of concurrent users
Number and type of downloads
Availability
How to do it
3 physical servers
5 virtual servers (2 for web, 2 for ddbb and 1 for development)
SAN
2 load balancers
2 physical firewalls
20 MB dedicated bandwidth
17. Moodle Deployment (II)
Elastic Load Balancing Elastic Load Balancing
Amazon EC2 Amazon EC2 Amazon EC2
Amazon EC2Internet
Amazon S3 Amazon S3
Amazon Route 53
RDS DB instance
read replica
RDS DB instance
RDS DB instance
standby (Multi-AZ)
Apache Tomcat Apache Tomcat
MySQL 5.6
MySQL 5.6
Apache Tomcat Apache Tomcat
MySQL 5.6
US East – Region EU -1 Dublin Region
OpenSwan Ipsec
VM
OpenSwan IPSec
VM
AZ-1A AZ-1B
AZ-1A AZ-1B
18. Moodle Deployment (III)
Harcoded functionalities
Less portable solutions
“Easier” to develop
Some tasks involved
Hardcode several libraries
Define new renderers
Change Moodle theme
Include translation information in the database
20. Moodle Deployment (V)
Functionalities implemented as add ons
Completions report add-on
Incentive functionality
Module folder
More portable
With a defined structure
24. Conclusion
Learning platform selected, deployed and adapted to the
requirements of SunEdison company
Definition of requirements
Deployment of the platform
Definition of specific implementations for the platform
Main Problems
Cloud installation, content sharing, clustered database
Change of requirements during the development
Second stage of the project
Hinweis der Redaktion
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
hardcode several libraries, define new renderers, change the Moodle theme and include translation information in the database.
hardcode several libraries, define new renderers, change the Moodle theme and include translation information in the database.
hardcode several libraries, define new renderers, change the Moodle theme and include translation information in the database.
hardcode several libraries, define new renderers, change the Moodle theme and include translation information in the database.
hardcode several libraries, define new renderers, change the Moodle theme and include translation information in the database.
Courses Home Visualization. It is necessary to change the main screen of Moodle in order to show only the courses in which a user is enrolled. This view also should show if each course is started, in progress or completed. Moreover, the information about courses can be shown with different levels of detail.
Adding information to reports. Some of Moodle reports do not show the information that the company requires, so it was necessary to add new information. For instance, the creation date was included in the user list, and the institution information was added in the completion status report.
Definition of ad-hoc SQL reports. The institution does not only require the reports provided by Moodle. It also needs specific reports that can be accessible only by some kind of users.
Incentive management system. It is necessary to provide a block that allows different LCMS regional administrators to define achievement scales and associated incentives. Students could get achievements when they complete their courses and depending on their grades they will reach a status level. The level of a user could have some awards associated. This system goes beyond the badges functionality included into Moodle, because it should take into account different areas and groups, and how the area managers and the group leaders can see others status.
Integration with Brainshark. Importation of users and contents from Brainshark into Moodle before the former was closed.
The clustered database and the necessity to share contents were critical in order to ensure a proper platform performance, and in cloud-based solutions this is not as easy as it can be if were talking about physical nodes in the same machine.
Another important problem was the change of the requirements during the development. The platform began to work before the development was finished, and new requirements arose that should be also addressed by the development team. This meant changing the initial plan and also the delivery date of the project.
Despite these problems, the project has been finished successfully and a new stage will begin next year in which the integration of the learning platform with other tools of the company will be acomplished. This would require the use of Moodle Web Services layer and the use of a Single Sign On system for authentication.