01-04-2011, 10:30 AM
By
Arvind Singh
Niraj Shirke
Kiran Shette
[attachment=11468]
1. Introduction
1.1. Project Overview
This project assesses students by conducting online objective tests. The tests would be highly customizable. This project will enable educational institutes to conduct test and have automated checking of answers based on the response by the candidates.
The project allows faculties to create their own tests. It would enable educational institutes to perform tests, quiz and create feedback forms. It asks faculty to create his/her set of questions. Faculty then creates groups and adds related students into the groups. Further the tests are associated with specific groups so that only associated students can appear for the test. The result of the response would be available to the faculty of the question set. Further the result would also be mailed to the student. This project would be helpful for creating practice tests, say for educational institutes and as a feedback form.
1.2. Purpose
• Responses by the candidates will be checked automatically and instantly.
• Online examination will reduce the hectic job of assessing the answers given by the candidates.
• Being an integrated Online Examination System it will reduce paper work.
• Can generate various reports almost instantly when and where required.
1.3. Scope
This project would be very useful for educational institutes where regular evaluation of students’ is required. Further it can also be useful for anyone who requires feedback based on objective type responses.
1.4. Definitions, Acronyms
The sub-section provides the definitions of all terms, acronyms, and abbreviations used in this document to understand the SRS properly.
2. Functional or Specific Requirements
Required software is for conducting on-line `objective’ type examination and providing immediate results. The system should satisfy the following requirements:
• Administrator Aspect
1. Taking backup of the database
2. Editing/Deleting/Creating the database.
3. Adding or expelling faculty
4. Changing the super password.
• Faculty Aspect
1. Logging into the system.
2. Sending invitations to specific student by mail
3. Accepting registrations of candidates
4. Adding the candidate to a group
5. Create/Edit/Delete candidate groups
6. Creating a test
7. Posting questions in the above test
8. Posting multiple options to respective question
9. Marking correct answer within the given options
10. Specifying to allow user defined answer
11. Time limit of the test if any.
12. Whether to randomize the questions
13. Whether to randomize the options displayed
14. To allow the test to be taken in practice mode where the correct answer is shown immediately after the candidate selects an option.
15. Set negative marks for wrong responses
• Student Aspect:
1. Requesting registration
2. Logging into the system.
3. Edit user information.
4. Selecting the test.
5. Selecting whether the test to be taken in practice mode where the correct answer is shown immediately after the candidate selects an option.
6. Appearing for the examination.
7. Printing the result at the end of the examination.
8. Reviewing the given responses.
9. Changing password.
10. Resetting of forgotten password
• Analysis
1. Authenticating users based on username and password
2. Keeping session track of user activity
3. Recording candidates’ responses to every question
4. Checking whether the given response is correct or not
5. Keeping history of test reports of all users
• Mailing
1. The reports are required to be mailed to the candidates on the registered mail address.
2. Temporary password will be mailed to the user incase the user forgets the password.
3. Invitations for the appearance for the new test will be mailed.
2.1. External Interface Requirements
2.1.1. Hardware Interfaces
Server side hardware
• Hardware recommended by all the software needed.
• Communication hardware to serve client requests
Client side hardware
• Hardware recommended by respective client’s operating system and web browser.
• Communication hardware to communicate the server.
2.1.2. Software Interface
Server side software
• Web server software, Apache Tomcat
• Server side scripting tools: PHP
• Database tools: Sedna native XML DBMS.
• Compatible operating system: Linux
Client side software
• Web browser supporting JavaScript, refer Browser Compatibility 2.3.1
2.1.3. Third Party Software Interfaces
None
2.1.4. Communication Protocol
Following protocols are required to be permitted on the server side
• HTTP incoming request
• HTTPS incoming request if secure gateway is implemented
Following protocols are required to be permitted on the client side
• HTTP outgoing request
• HTTPS outgoing request if secure gateway is implemented
2.1.5. Assumption and Dependency
1. Username are valid email addresses of respective user
2. Administrator has the authority to add/delete faculty level accounts.
3. Faculty have the authority to approve/expel student
4. Faculty have the authority to change student’s group
2.2. Non-Functional Requirements
• System should be able handle multiple users
• Database updating should follow transaction processing to avoid data inconsistency.
2.3. Software System Attributes
2.3.1. Browser Compatibility
The project being web based required compatibility with at least the popular web browsers. Microsoft Windows XP and above, Linux and Macintosh being the current popular operating system and Microsoft Internet Explorer, Mozilla Firefox, Opera, Safari and Google Chrome being the currently popular web browsers.
2.3.2. Globalization Support
The questionnaires and their respective options provided by the faculty may or may not be in English. Hence the questions and their options must be in Unicode format that will accept any Unicode character.
2.3.2.1. List of Locale
The system will mostly be in US English, although the questions and their options may not be in US English. Hence the questions and their options are to be in Unicode format.
Arvind Singh
Niraj Shirke
Kiran Shette
[attachment=11468]
1. Introduction
1.1. Project Overview
This project assesses students by conducting online objective tests. The tests would be highly customizable. This project will enable educational institutes to conduct test and have automated checking of answers based on the response by the candidates.
The project allows faculties to create their own tests. It would enable educational institutes to perform tests, quiz and create feedback forms. It asks faculty to create his/her set of questions. Faculty then creates groups and adds related students into the groups. Further the tests are associated with specific groups so that only associated students can appear for the test. The result of the response would be available to the faculty of the question set. Further the result would also be mailed to the student. This project would be helpful for creating practice tests, say for educational institutes and as a feedback form.
1.2. Purpose
• Responses by the candidates will be checked automatically and instantly.
• Online examination will reduce the hectic job of assessing the answers given by the candidates.
• Being an integrated Online Examination System it will reduce paper work.
• Can generate various reports almost instantly when and where required.
1.3. Scope
This project would be very useful for educational institutes where regular evaluation of students’ is required. Further it can also be useful for anyone who requires feedback based on objective type responses.
1.4. Definitions, Acronyms
The sub-section provides the definitions of all terms, acronyms, and abbreviations used in this document to understand the SRS properly.
2. Functional or Specific Requirements
Required software is for conducting on-line `objective’ type examination and providing immediate results. The system should satisfy the following requirements:
• Administrator Aspect
1. Taking backup of the database
2. Editing/Deleting/Creating the database.
3. Adding or expelling faculty
4. Changing the super password.
• Faculty Aspect
1. Logging into the system.
2. Sending invitations to specific student by mail
3. Accepting registrations of candidates
4. Adding the candidate to a group
5. Create/Edit/Delete candidate groups
6. Creating a test
7. Posting questions in the above test
8. Posting multiple options to respective question
9. Marking correct answer within the given options
10. Specifying to allow user defined answer
11. Time limit of the test if any.
12. Whether to randomize the questions
13. Whether to randomize the options displayed
14. To allow the test to be taken in practice mode where the correct answer is shown immediately after the candidate selects an option.
15. Set negative marks for wrong responses
• Student Aspect:
1. Requesting registration
2. Logging into the system.
3. Edit user information.
4. Selecting the test.
5. Selecting whether the test to be taken in practice mode where the correct answer is shown immediately after the candidate selects an option.
6. Appearing for the examination.
7. Printing the result at the end of the examination.
8. Reviewing the given responses.
9. Changing password.
10. Resetting of forgotten password
• Analysis
1. Authenticating users based on username and password
2. Keeping session track of user activity
3. Recording candidates’ responses to every question
4. Checking whether the given response is correct or not
5. Keeping history of test reports of all users
• Mailing
1. The reports are required to be mailed to the candidates on the registered mail address.
2. Temporary password will be mailed to the user incase the user forgets the password.
3. Invitations for the appearance for the new test will be mailed.
2.1. External Interface Requirements
2.1.1. Hardware Interfaces
Server side hardware
• Hardware recommended by all the software needed.
• Communication hardware to serve client requests
Client side hardware
• Hardware recommended by respective client’s operating system and web browser.
• Communication hardware to communicate the server.
2.1.2. Software Interface
Server side software
• Web server software, Apache Tomcat
• Server side scripting tools: PHP
• Database tools: Sedna native XML DBMS.
• Compatible operating system: Linux
Client side software
• Web browser supporting JavaScript, refer Browser Compatibility 2.3.1
2.1.3. Third Party Software Interfaces
None
2.1.4. Communication Protocol
Following protocols are required to be permitted on the server side
• HTTP incoming request
• HTTPS incoming request if secure gateway is implemented
Following protocols are required to be permitted on the client side
• HTTP outgoing request
• HTTPS outgoing request if secure gateway is implemented
2.1.5. Assumption and Dependency
1. Username are valid email addresses of respective user
2. Administrator has the authority to add/delete faculty level accounts.
3. Faculty have the authority to approve/expel student
4. Faculty have the authority to change student’s group
2.2. Non-Functional Requirements
• System should be able handle multiple users
• Database updating should follow transaction processing to avoid data inconsistency.
2.3. Software System Attributes
2.3.1. Browser Compatibility
The project being web based required compatibility with at least the popular web browsers. Microsoft Windows XP and above, Linux and Macintosh being the current popular operating system and Microsoft Internet Explorer, Mozilla Firefox, Opera, Safari and Google Chrome being the currently popular web browsers.
2.3.2. Globalization Support
The questionnaires and their respective options provided by the faculty may or may not be in English. Hence the questions and their options must be in Unicode format that will accept any Unicode character.
2.3.2.1. List of Locale
The system will mostly be in US English, although the questions and their options may not be in US English. Hence the questions and their options are to be in Unicode format.
