LEARNING MANAGEMENT SYSTEM
PROJECT REPORT
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE COURSES OF B.TECH AS WELL AS THE INSTITUTE, IDRBT.
SUBMITTED TO
INSTITUTE FOR DEVELOPMENT AND RESEARCH IN BANKING TECHNOLOGY, HYDERABAD
SUBMITTED BY
R JAYARAM NAYAK
COMPUTER SCIENCE AND ENGINEERING B.Tech. 3rd YEAR
IIT INDORE
SUPERVISED BY
Mr. S LALIT MOHAN
SENIOR TECHNOLOGY MANAGER IDRBT
LEARNING MANAGEMENT SYSTEM
PROJECT REPORT
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE COURSES OF B.TECH AS WELL AS THE INSTITUTE, IDRBT.
SUBMITTED TO
INSTITUTE FOR DEVELOPMENT AND RESEARCH IN BANKING TECHNOLOGY, HYDERABAD
SUBMITTED BY
R JAYARAM NAYAK
COMPUTER SCIENCE AND ENGINEERING B.Tech. 3rd YEAR
IIT INDORE
SUPERVISED BY
Mr. S LALIT MOHAN
SENIOR TECHNOLOGY MANAGER IDRBT
ACKNOWLEDGEMENT
Any accomplishment requires the effort of many people and there are no exceptions. The report being submitted today is a result o f co llective effort. Alt hough the report has been solely prepared by me with the purpose of fulfilling the requirements of the course o f B.Tech (Bachelor of techno logy) as well as at the inst itute, IDRBT; there are innumerous helping hands behind it who have guided me on my way.
I wish to express my profound gratitude to my Guide Mr. S Lalit Mohan for giving me opportunity to do this project in the Institute for Development and Research in Banking Technology. The supervision and support that she gave truly help the progression and smoothness of the internship program. The co-operation is much indeed appreciated.
Project during the semester would be nothing without the enthusiasm and imagination from our Research Associates at IDRBT, Ms. S Gayatri Hari Priyanka and Mr. P Santosh Kumar. Last but not least I would like to thank my other project trainees at IDRBT for nurturing my confidence.
CERTIFICATE
This is to certify that
Mr. R JAYARAM NAYAK
, pursuing B.Tech course at
Indian Institute of Technology, Indore
in Computer science and Engineering has
undertaken a project as an intern at
IDRBT, Hyderabad
from May 13, 2013 to
July 13, 2013. He was assigned the project “
LEARNING MANAGEMENT
SYSTEM
” under my guidance.
I wish him all the best for all his endeavors.
(Mr. S Lalit Mohan)
Senior Technology Manager
IDRBT, Hyderabad
Contents
1.
Introduction
2.
Project Description
3.
Program Office Module
3.1.
Planning
3.2.
Execution
3.3.
Check
3.4.
Notification
3.5.
Reports
4.
Class diagrams
5.
Activity diagrams
6.
MOODLE
7.
Gap analysis
8.
Moodle installation
9.
My contribution
10.
Conclusion
11.
References
1.
Introduction
Learning Management System (MOODLE) is a software application for the administration, documentation, tracking and reporting of training programs, classroom and online events, e-learning programs, and training content. It is supposed to be an online flexible course management software which mainly caters educational requirements for teachers and students.
LMS is supposed to have the following features:
1. Self registration and Enrollment options to teachers and students. 2. Adding/Deleting Courses by the teachers
3. Set the different User Roles and user account 4. Setting the course calendar
5. Quiz module
6. Upload and Retrieve Assignment and Resources 7. Forum or discussion module
8. Evaluate and Grade the students with the feedback 9. Instant messages
10.File download 11.Grading/feedback 12.Online calendar
13.Online news, updates and announcement
LMS is used by audiences like students, teachers and administrators. Also LMS can be used by anyone who is interested in conducting the online classes and who wants to store and retrieve the student’s documents.
2.
Project description
The aim of this project is to provide a Learning Management System for Program Office to conduct programs in IDRBT. Understanding the requirements of Program Office, search for an open source tool which satisfies all the requirements of Program Office, get installed in Systems and customize them as per Program Office need. To create, provide updates and information about programs (seminars, webinars, workshops etc...) to staff, students and Organizations (banks, insurance companies, educational institutions etc...) which are conducted in or out by IDRBT.
Understanding the requirement of Program Office and adding, customizing open source tool (MOODLE) to fulfill our needs
.
3.
Program Office Module
3.1 Planning
1) Request comes in an email/phone/feedback analysis/ongoing regular programs/interest. The requisition details to be captured in the system. System should have details of Source of request (person name, email id, telephone, organization name), request course name/course requirements and Timelines.
2) Program Office Calendar outlines day wise availability (look and feel should be similar to outlook calendar). Based on the conference room availability, information obtained in requisition process, system should suggest the next available slot.
3) If next available slot is accepted/over ridden, system should capture program details. The program details would have
a) Program Name
b) Program Domain (should be a master data. eg. Information Security, Big Data, etc) c) Program Delivery Mode (Classroom, Virtual, etc)
d) Program Type (Conference, Workshop, Classroom, Webinar)
e) Planned Start Date
f) Planned End Date
g) Faculty Name(s) h) Fee (can be blank)
i) Location (IDRBT premises/Venue name along with City Name). IDRBT should be the default value
j) Boolean to indicate available for all/Restricted
4) System should have Organization contact details Organization Name
Industry Type (Insurance, Banking, Investment, etc) Board Number
HR Contact (Name, Email, Phone#) IT Contact (Name, Email, Phone#) Chairman & MD (Name, Email, Phone#)
5) An email should be sent to Faculty requesting for program Brochure within 3 months of program start date. Reminders to be sent for receipt of Brochure
6) System should send an email to Organization IT Head and HR Contact with brochure. Postal mail can be decided by Program Office.
7) If there is postal mail, Inward/Outward correspondence team can take the list of emails sent and should send a physical copy of the brochure to member banks.
8) Organizations would send trainees contact details
a. Program Name b. Title c. Last Name d. First Name e. Email ID f. Telephone g. Designation h. Office Location
i. Accommodation Needed (Yes/No)
9) Agenda items should be added within a month from the start date of the program
10)The Faculty member could add program agenda clicking on Programs in his/her queue. The agenda should contain
a. Agenda Name (should include Lunch as an agenda item, the default would be 12 noon -1 pm) b. Date
c. Start Time d. End Time
e. Speaker Name and contact details(Name, email and telephone). The default should be faculty member name
f. Any payment to Guest speaker and their logistics ??
3.2 Execution
1) After agenda finalization, Actual Start Date and Actual End Date of the program are populated. 2) The participant names and calendar should be available to everyone in IDRBT
3) After agenda is finalized, system should generate an email to
a. An outlook calendar request is generated to block the timeslots of the speakers
b. Catering team with details of program name, start date and end date, lunch timings day wise. The email should also contain number of trainees, group by Location of the trainees. Catering could use this information to decide the menu. Catering team would send a confirmation email to Program Office mailbox.
c. Security team with details of participants (Title, Name, designation, Email Id and Contact#) for access/visitor badge preparation. Security team can also see these details upon clicking Visitors
d. Systems team would get an email requesting to create dummy user and machine set-up in the conference with details of Trainee(Name, email id and Phone)
e. An email should be sent to Guest House Caretaker with program name, Title, Person Name, Email ID and Phone
f. To Faculty Coordinator with details of the participants. Faculty Coordinator could also see the details of the participants logging into the Program office application
4) Faculty members to upload content of the program 7 days (configurable) before the program start date. If content is not uploaded, a notification is sent to program office head, 2 days before the program start date.
3.3 Check
1) Program office would upload the content into the system for each agenda item. This information can be made available.
2) Feedback
a. A standard template exists for all programs. The questions and grading are configurable. The questions that are generic to logistics (food, accommodation, etc) cannot be removed. The comments and utility section are mandatory.
b. The standard template can be modified before the program start date. Program Office and Faculty Coordinator finalizes the template
c. Trainee would login to the system with the provided default id and password to provide feedback. The trainee can provide feedback on agenda item and day wise and also on consolidated basis.
d. Faculty Coordinator, His/her Supervisor and Program office member would only see the feedback details
3) Invoicing
a. System should generate an invoice to HR Contact of the participant trainees
b. The details of invoices should be sent in an email and physical form. The email should be sent to IDRBT Accounts department sharing the details of Accounts Receivables. Accounts team can access the program office application to get details of Accounts Receivables.
c. System should reconcile the payments on receipt
3.4 Notification
a) An email should be sent 3 months prior to program name requesting for Brochure. A reminder email should be sent 11 weeks before the program start date. The reminder notification can be configured at program level or program office level.
b) An email notification should be sent to faculty member requesting for Agenda
c) Upon 1 week from first notification, a reminder coping to program office coordinator should be sent. 1 week – this can be configured at program level and also could be set at Program Office level. The default is program office level
d) 2 days after 2nd reminder, an email should be sent to Head of Program Office. Number of days, can be configured at program office level.
e) A reminder would be sent to Catering team to confirm Menu within a week of the program f) System should consider available holidays while sending reminder notifications. HR system
maintains the holiday calendar.
3.5 Reports
1) A common datawarehouse could be planned for Entire IDRBT needs
2) System should generate a report with Course Name, Start Date and End Date, Faculty Name and Contact Number with agenda items (Name, speaker, start and end time).
3) Should generate a report of number and name of courses by domain type 4) Courses by Faculty
5) Courses for Faculty with Guest Speakers
6) Payment Dues
7) Agenda item due
8) Brochure due
9) Participant Name – program wise
10)Status of Activity to be completed by Security, Systems, etc 11)Residential/Non-residential
12)Free/Fee courses 13)Adhoc reporting
6.
Moodle
To fulfill Program Office requirements we have selected Moodle as our Open Source tool. As it is easy to learn and maintain. One can easily handle Moodle without knowing its backend technical details.
Moodle is a software package for producing Internet-based courses and web sites. It is a global development project designed to support a social constructionist framework of education. It is provided freely as Open Source software under the GNU (General Public License). Basically this means Moodle is copyrighted, but that you have additional freedoms. You are allowed to copy, use and modify Moodle provided that you agree to: provide the source to others; not modify or remove the original license and copyrights, and apply this same license to any derivative work. Read the full license for details and please contact the copyright holder via the Moodle.com helpdesk if you have any questions.
Moodle can be installed on any computer that can run PHP, and can support an SQL type database (for example MySQL). It can be run on Windows and Mac operating systems and many flavors of Linux. There are many knowledgeable Moodle Partners to assist you, even host your Moodle site.
Moodle is used in many places such as:
Universities High schools Primary schools Government departments Healthcare organizations Military organizations Airlines Oil companies Homeschoolers Independent educators special educators
7.
Gap Analysis
Requirements Moodle’s Ours remarks
Get request for new program from any faculty/ Organizations
yes Yes
Check for available slots for programs no Yes By outlook calendar/ manually in moodle
Send slot availability and confirmation about program to organizations
no Yes
Profile (details of organizations, faculty, participants etc.)
No Yes Moodle has this functionality but it doesn’t have the whole details of other organization
Prepare agenda for program (security,
caterers, hospitality management etc.)
No Yes Set agenda according to provided program details
Send agenda to security, caterers. No Yes Create a group mail to send this data. Generate invoice of program No Yes Separate section for invoice
Send invoice to accounts department No Yes Generate a mail to Acc. Dept. Get feedback from participants Yes Yes
Update new item/ program / agenda Yes Yes Days wise changes in programs
Store earlier program files Yes Yes This should contain important/ useful files which taken for future references Download and upload option for important
files
Yes Yes
Program reminder for Program office to send request/ remind to respected persons about their events
Yes Yes
Webinar to conduct online seminars, talks . Yes Yes Information about postal mails(Reply to
postal mail through corresponding team) from Organizations
8.
Moodle Installation
Moodle[1][2] is primarily developed in Linux using Apache, MySQL and PHP (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:
The basic requirements for Moodle are as follows:
Hardware Requirements:
Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum.
Backups: at least the same again (at a remote location preferably) as above to keep backups of your site
Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 concurrent users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use.
Software Requirements:
An operating system, anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.
Web server. Primarily Apache, needs to be correctly configured to serve PHP files. The versions are not critical but try to use the newest web server build available to you.
PHP - The minimum version is currently 5.3.2. A number of extensions are required; see the PHP page for full details. Installation will halt at the environment check if any of the required extensions are missing.
A database. MySQL is the primary development database, the most comprehensively tested and have extensive documentation and support.
Minimum browser for accessing Moodle: Firefox 4, Internet Explorer 8, Safari 5, Google Chrome 11, Opera 9 plus whatever plugins and applications you will need for the content you plan to use.
Set up your server
There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at Installing AMP. If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.
Download moodle from http://moodle.org/downloads and place it in file
You can either place the whole folder in your web server documents directory, in which case the site will be located at http://localhost/moodle , or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply http://localhost . See the documentation for your system and/or web server if you are unsure.
Create the (
moodledata
) data directory
Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this
directory. On larger systems consider how much free space you are going to use when allocating this directory.
IMPORTANT: This directory must NOT be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient.
Here is an example (Unix/Linux) of creating the directory and setting the permissions for anyone on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for other scenarios...
# mkdir /path/to/moodledata # chmod 0777 /path/to/moodledata
Securing moodledata in a web directory
If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:
order deny,allow deny from all
Create an empty database
Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:
dbhost - the database server hostname. Probably localhost if the database and web server are the same machine, otherwise the name of the database server
dbname - the database name. Whatever you called it, e.g. moodle
dbuser - the username for the database. Whatever you assigned, e.g. moodleuser - do not use the root/superuser account. Create a proper account with the minimum permissions needed.
dbpass - the password for the above user
If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). We are using MySQL in our project.
It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.
Now check follow the instruction give in above screen shot and as per them, depending upon your Operating system the instructions will changes. After this click on continue
You will get above screen , it may take several minutes to finish. Now click continue to finish installation. It will ask for user details.
From here you should customize your Moodle as per your need.
Customized front page
Web based installer
To run the web installer script, just go to your Moodle's main URL using a web browser. The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new course. It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions.
Final configuration
There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:
Settings > Site administration > Server > Email: Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page.
Settings > Site administration > Server > System paths: Set the paths to du, dot and aspell binaries.
Settings > Site administration > Server > HTTP: If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.
Settings > Site administration > Location > Update timezones: Run this to make sure your timezone information is up to date.
Check mail works: Create a test user with a valid email address and Send them a message. Do they receive an email copy of the message? If not, check the settings in Settings > Site administration > Plugins > Message outputs > Email.
Installation is complete :) .
9.
My Contribution
Adding the new thing in User details which are not there in Moodle such as Organization type, User type, Department, Address etc.
10.
Conclusion
Overall, I found Moodle to be the easiest and most flexible LMS that I have used to date. Moodle was easy to navigate, had features that were directly applicable to the writing classroom and best of all, was free for me to download and customize. Moodle’s philosophical and pedagogical underpinnings are consistent and conducive to current writing classroom practices, allowing it to fit seamlessly into the activities of many writing classrooms. Furthermore, Moodle has a strong support community and strong online documentation to help you get started and work out any problems that may occur on the way. What sets Moodle apart from other potential open source LMS systems, notably Drupal or Mambo, is that Moodle is specifically designed with educators in mind, allowing for easy setup and maintenance.
11.