Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Version 1.0
Supervisors: Mr.Shantha Fernando Mr.Samantha Senaratne Prepared by: Team 11 Shammi J. Mathuvathanan M. Luckshy S. Sujeetha L.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 1
Table of Contents
Table of Contents ..........................................................................................................................................1 1. Introduction.............................................................................................................................................2 1.1 Purpose.........................................................................................................................................2 1.2 Document Conventions................................................................................................................2 1.3 Intended Audience and Reading Suggestions ..............................................................................2 1.4 Project Scope................................................................................................................................2 2. Overall Description .................................................................................................................................4 2.1 Product Perspective......................................................................................................................4 2.2 Product Features...........................................................................................................................4 2.3 User Classes and Characteristics..................................................................................................5 2.4 Operating Environment................................................................................................................5 2.5 Design and Implementation Constraints ......................................................................................6 2.6 User Documentation.....................................................................................................................7 2.7 Assumptions and Dependencies...................................................................................................7 3. System Features ......................................................................................................................................8 3.1 View the assignment results by sending a SMS...........................................................................8 3.1.1 Description and Priority...............................................................................................................8 3.1.2 Stimulus/Response Sequences .....................................................................................................8 3.1.3 Functional Requirements .............................................................................................................8 3.2 Get an alert message when there is any new announcement posted in moodle..................................9 3.2.1 Description and Priority...........................................................................................................9 3.2.3 Stimulus/Response Sequences ..................................................................................................9 3.2.2 Functional Requirements .........................................................................................................9 3.3 Send SMS about any announcement to update moodle (by a lecturer)......................................10 3.3.1 Description and Priority.........................................................................................................10 3.3.2 Stimulus/Response Sequences ...............................................................................................10 3.3.3 Functional Requirements .......................................................................................................10 3.4 Adding a discussion topic through the mobile ...........................................................................11 3.4.1 Description and Priority.........................................................................................................11 3.4.2 Stimulus/Response Sequences ...............................................................................................11 3.4.3 Functional Requirements .......................................................................................................11 4. External Interface Requirements...........................................................................................................12 4.1 User Interfaces ...........................................................................................................................12 4.2 Hardware Interfaces ...................................................................................................................12 4.3 Software Interfaces.....................................................................................................................13 5. Other Nonfunctional Requirements ......................................................................................................14 5.1 Performance Requirements ........................................................................................................14 5.2 Safety Requirements ..................................................................................................................14 5.3 Security Requirements ...............................................................................................................14 5.4 Software Quality Attributes .......................................................................................................15 6. Appendix A: References .......................................................................................................................16
Revision History
Name Date Reason For Changes Version
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 2
1. Introduction
1.1 Purpose
This document is the System Requirement Specification of M- Moodle System. This system is developing for the University of Moratuwa, to extend the E - Learning facilities to mobile. The ultimate goal of this to, develop a sms service through which the students and staffs can get the 90% benefits of the current E Learning system from wherever they are. This SRS will cover the whole proposed system. This is the SRS document of version 1.0 of M- Moodle System.
M- Moodle System
Page 3
mainly targeted the students and staffs of University of Moratuwa. This system mainly supports three kinds of functionalities. Send a sms and get a reply sms. E.g.: Sending a sms in order to see the results Get a notification messages when there is a new updates in E- Learning. E.g.: Announcements. Uploading information in E Learning through sms. E.g.: Add a discussion topic in E Learning. Not only above things, But also we are planning to develop a mobile interface for the E Learning system called Moodle.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 4
2. Overall Description
2.1 Product Perspective
This is not a standalone system. This is the extension of E Learning through mobile. The current E Learning system in University of Moratuwa is Moodle. Moodle is an open source course management system. Therefore in our system, we are going to interact with the Moodle through mobile. That means most of the actives can be carrying out using mobile rather than a web browser. This system will available at all and will be function in secure manner with filtering. The main parts of the systems are the filtering section and the administrator part. (Authentication part)
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 5
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 6
Operating system: It can be work on Linux /Windows/Solaris 10 (Sparc and x64), Mac OS X and Netware 6
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 7
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 8
3. System Features
3.1 View the assignment results by sending a SMS 3.1.1 Description and Priority This is one of the key features of the M-Moodle system. A student who has already registered in the M-Moodle system should be able to send a SMS in a given format to view their assignment results through their mobile (if any). If we can categorize the priorities of the features as high, medium and low, this feature will besides under high category. 3.1.2 Stimulus/Response Sequences Here the action will be started by the student. He/She will send a SMS from the mobile interface. The system should be able to receive those SMSs and should be able to filter according to the specified format whether it conforms to that. Then the system will retrieve the result from its database and again will send it to the mobile through the filter. (System should already have to pop up the results from the moodle database to itself if there any assignment results uploaded in moodle) 3.1.3 Functional Requirements REQ1: Should be able to receive the SMS details (receiver, time and the context) into the system database. REQ2: Should be able to filter the SMSs whether they conform to the specified format. If it is not, then should be able to discard the SMS. Also it should be check the mobile numbers whether they have authenticated in the system. REQ3: Should be able to connect to its own database and pop the results of the particular student. REQ4: Should be able to send the results back to the sender.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 9
3.2 Get an alert message when there is any new announcement posted in moodle
3.2.1 Description and Priority
This another key feature of our system. There can be many new announcements posted in moodle time to time. Not only announcements, but also there can be any messages from lecturers about their lecture time schedules (cancel/new arrangement). Then those messages should be notified to all students using the M-Moodle system. But by considering the cost incurred in this, we wish to select the receivers dynamically. Even though it seems to be a main feature, we considered this as a medium priority feature compared with others. 3.2.3 Stimulus/Response Sequences
Here the action will be started by the system itself. There should be a lifetime thread looking at the moodle database to check whether there are any new announcements posted. If so, those should be retrieved to the system database and should be sent to the students mobiles notifying the new event. There should be a format to the notifying SMS. If the number of characters are exceeded the allowed characters, then the format should be defined according to that. For example, if there any news about an assignment and if it exceeds the maximum character size, then the system should send the SMS just saying that a new news about the assignment for the particular subject is posted in moodle rather than sending the entire news about the particular assignment. 3.2.2 Functional Requirements
REQ1: There should be a life time thread running on moodle database to check whether there are any new updates. REQ2: System should retrieve the new updates from moodle and should save in its database. REQ3: System should check the number of characters of the message whether it exceeds the maximum character size for a SMS
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 10
REQ4: There should be a format to send the messages for the announcements which character size is unlimited. REQ5: System should fetch all the students mobile number and should send the news to their mobiles.
3.3 Send SMS about any announcement to update moodle (by a lecturer)
3.3.1 Description and Priority
This feature is added for the lecturers to give them more facilities when they are not able to connect to internet. This feature should facilitate the users to update the moodle through their mobile. So lecturers should be able to update the moodle when they are without internet connectivity. Here we considered the situations like lecture cancellation, request to bring any equipments/materials (calculator, past papers, reference text book etc.) to the upcoming lecture and so on. These situations might arise once in a while. So we can consider this as a low priority one. 3.3.2 Stimulus/Response Sequences
Here again the action should start by the user (Lecturer in this case). Users should send a SMS about the notification from their mobile interface. The system should capture this through the filter and should ensure that the SMS is coming from a lecturer. After the filtering, system should be able to connect to moodle server and update it in order to display the required task by the lecturer in the particular course forum. 3.3.3 Functional Requirements
REQ1: System should receive the SMS and should filter it according to the format. REQ2: System should connect to the moodle server. REQ3: It should write whatever the contents in the SMS to the course forum.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 11
There are several forums in the moodle for each and every subject that the student undertakes. Students can add a discussion topic and continue to send comments about that. It can be a question about the subject or a new technology he/she got to know about that subject or anything else related with the subject. So in our system we thought of giving a way to the students that they can add these comments whenever they want (when they cannot use the internet). This feature can be considered as a medium priority one.
3.4.2
Stimulus/Response Sequences
Here the action should be started by the user (Lecturer/ Student). User should able to send a SMS about their discussion topic. The system should filter those SMSs, then should connect to the moodle server and should update it in order to display the discussion topic in the course forum. 3.4.3 Functional Requirements
REQ1: System should receive the SMS and should filter it according to the format. REQ2: System should connect to the moodle server. REQ3: System should update the moodle to display the discussion topic inside the course forum.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 12
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 13
4.3 Software Interfaces M- Moodle system should compatible with all the windows operating systems. The server running on our system should use the database MySQL to connect to the moodle server as well as LearnOrg server and its databases. And there is an API for interfacing with the GSM modem connected with the computer. We found it as jsmsengine which converts the AT commands to the text format.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 14
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 15
5.4 Software Quality Attributes The system should reflect the changes done on moodle as soon as possible. It should keep all the incoming and outgoing messages of each and every student so that he/she can verify it later also. The system should be available to the user all the time to send and receive SMS messages whenever he/she wants. The system should be able to interoperate with the existing LearnOrg server. Since it is a lifetime system, it should be developed in such a way that it could be maintainable for long time. The system should correctly display the contents of the message on the moodle, and should correctly send the text message according to the change done on moodle. And the very important feature is that it should be reliable. The end user should rely on the system that it displays the correct information as expected.
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.
M- Moodle System
Page 16
6. Appendix A: References
1. http://www.developershome.com/sms 2. http://moodle.org
Copyright 2007 by Team 11, Computer Science & Eng, University of Moratuwa, SriLanka.