The final version of the Moodle virtual learning environment was deployment within Danum school on Wednesday 29th March 2006. Danum current Intranet server, code named “frank”, this means pupils could gain access to the VLE by typing http://danumintranet/danum_vle/ into their browsers address bar after they can logged onto a computer.
Various setting had to be changed once the VLE was live, firstly to comply with the requirement in re- gards to user, guest logins had to be disabled, this was done using the administration menu and selecting user polices from the user permission menu and disabling the auto-login guests. While within the user administration the authenitcation for the VLE was updated to allow only manual accounts, and the in- struction for login where also updated.
The next stage was to add the required users to the VLE, these included pupils currently studying ICT at AS Level, the teaching and non-teaching staff within the ICT department. The automate the tasks, class lists where provided in CVS files, these then required a bit of formatting before they could be used upload the users onto the VLE. Once all user where authorised to use the VLE, the appropriate privileges needed to be set using the permission areas of the Moodle administration.
Figure 6.1: Design for front page /
Before deployment could be classed as complete, the last task was to create six new courses i.e. one for each module of the AS Level ICT course and assign which teachers to them. Before leaving the school to make use of the VLE, a demonstration of the various features was given to both Peter Hayton and Ron
Chapter 7
Evaluation
7.1
Solution Evaluation
This section of the report evaluates what the end user thought of the finished virtual learning environment, as well as looking at how usability of the virtual learning environment has been affected, and whether the changes to the comply with the development rules set out by Moodle. Evaluation with the end users, Mr. Ron Hale and Mr. Peter Hayton took place on Wednesday 18th December, a full write up the meeting is available.
7.1.1 Evaluation against User Requirements
Requirement 1.1 - Development of Moodle Theme
A Danum theme for Moodle was created and could be distributed to other schools if needed. The theme follows the school current colour scheme, and uses the schools logo. All relevant information is now on the front page and the appearance has been greatly improved. Comments from the end user Ron Hale include “the VLE now looks very professional, as all pages are consistent with same header and footer, the colours chosen are easy on the eye”, Peter Hayton also noted that “helps the school with its branding, i.e. it various system all appear to belong to the same pace”‘.
Requirement 1.2 - Changes to the categories and course pages
This requirement was satisfied as all changes suggested by the end user where implemented. These changes included removing the search option available to users, and implementing department descrip- tions. The use of HTML Editor means that use can write a description which can include images,
of “who would spend the time to actually read the description”. One thought may to have a setting a department description to make them visible or hidden.
Requirement 1.3 - Changes to the edit course page
The hiding of advanced option has been implement. This means for less experienced users, they are not overwelmed by the vast number of setting for a course, and for the more advanced user, the setting are still available should they wish to change something. Ron Hale believes that “because fot the change, adding courses will be faster to add”, this is true because all other setting have had their defaults updated.
Requirement 2.1 - Minor Changes as a result of Iteration One
All the changes identifed as a result of changes for Iteration one have been implemented, and have overall increasing the aestetic look of Moodle, i.e. bettern spacing betewen drop down menu and forum contents etc. The change in link colour has meant reading the content of blocks is far clearer.
Requirement 2.2 - Examination of User Privileges
The Virtual Learning environment is now alot more secure as a result of the changes implemented. Now users can only view their profile if they are allowed do. By testing two contexts, it does not matter if a user has only been assigned a role on a site level or if they have only been assigned a role at a user level they are both checked. The changes implemented within this project to users being able to view their profiles has been fed back to the Moodle communintity using the various forums.
Requirement 2.3 - Development of E-portfolios for Moodle
Even through the e-portfolio system has not been fully implemented this requirement has been statisfied. Administrator have control however who can maintain a e-portfolio and can do this by either allowing or removing a user from the e-portfolio system. The system also caters for the cases where several users will be to be added into the system in one go, by allowing the use of CVS file. Only the portfolio owner can edit their own portfolio and cannot edit someone else. Although inline with the requirement an administrator can edit any portfolio. The only use case not currently cater for is the removal of posted resources.
7.1.2 Evaluation against Moodle coding guidelines
The Moodle developers have produced coding guidelines to guide anyone developing functionality for Moodle. They are a set of rules all developer must comply with, the full guidelines are available from [21].
All the general rules set out by Moodle have been adhered too, they include using full php tags, each file including config.php. All access to the database has been done using the Moolde database func- tion contained with dmlib.php, the only occasion this has not be followed is in setup.php for e-portfolios where actual tables needed to be created, though no password, usernames or database names are have been hard coded into the file, they are all retrieved from the config.php.
In regards to coding style call no indentation has been used, only spaces. All variable names are easy- to-read which constants appearing in upper case. All code is well commented and where possible the phpDoc format has been used, meaning that other user will be able to fellow the code easily. Lastly all code is well spaced out to aid readability.
The guidelines for database structures have also been followed, as for the e-portfolio system, two new table where required. Both new tables have a auto-incrementing id field set as the primary key. The boolean field within the eportfolio system is implemented using small integer field, containing only 0 or 1. In regards to all tables starting with the database prefix, this has been adhered to. When the new tables for e-portfolios are created, the table prefix is looked up using the global variable $CGF->prefix.
7.1.3 Usability Evaluation
Throughout the design phaes an emphasis was placed on usability. To assess usability, Nielson usability heuristics wher used. Right the way through the virtual learning environment the system status is visable due to the new theme as login information is detailed constantly. Also when any updation of the system occur i.e. a new department description is added, relevant messages are shown to important the user what is happening. The second rule of “match between system and real world” have been done, for the example of e-portfolio, all language with the system is used within the school environment, i.e. year of entry, level of study etc. Because of the new theme Nielson fourth rule of “consistency and standards” is also met, as the standard colours never change, and the top and bottom of all pages are always the same due to the header and footer implemented within the theme.
Various methods have been put in place to prevent error happening and also to provide appropraite feed- back to the user should an error occurs, an example of this is when the user wants to update a profile picture on their e-portfolio, they are imformed is they fail to load a jpeg image and are given the option to try again. The same is also true when adding users to the e-portfolio system, when the user details are entered, the results of the add or remove operation are presented, for example if a user wishes to add a
user, but they are all allowed to use an e-portfolio, an appropriate message is displayed saying that they are already on the system.
Nielson 8 rule of “Aesthetic and minimalist design” as all be followed and even implemented. For the example of editing course setting, the amount of information has been cut down to help aid usability and cut down the time needed to set up a course. Within the e-portfolio system, this minimalist principle has also been followed, which only the most relevant information being dispalyed. [23]