Functional Requirements Document

Online Test Taking System

CONTENTS
Introduction 1.1 Purpose 1.2 Background 1.3 Online Test Administration System 1.4 Test and Question management 1.5 Result and Award management 1.6 1.7 Assumptions CRs

Introduction
Tests are an essential part of a students life starting from the school days. With changing times, the mode of testing has also changed from a paper-pencil mode to an online format. Online testing has certain advantages over the older paper-pencil mode It requires very less manual intervention. Reports are generated automatically which saves manual effort Results can be declared quickly Online Test Taking System is also an environment friendly way of taking test as we do not use papers.

1.1 Purpose
The purpose of this document is to outline the detailed Functional Requirement that will enable design and development of the Online Test Taking System.

1.2 Background
In this system there are three modules, each module has a different functionality. The application has a number of users: Student, Teacher ,Administrator and Super admin. The responsibilities of these users are explained later. OTTS can be categorized into three modules 1. Online Test Administration System 2. Test and Question management 3. Result and Award management For performing any of the above mentioned operations, appropriate login is required by the user. Hence all modules should have the feature to login and validate the credentials.

1. Online Test Administration System This module will be used for creation of different types of users, managing student details and managing school details.

2. Test and Question management This module is used for test creation, creation of content and attending the test.

3. Result and Award management This module is used for managing the results of the test taken by a student. Apart from results, meritorious students can be Awarded Awards. New Awards can be created and existing Awards can be modified/seen/deleted using this module. The third feature of the module would be effectively managing the allocation of Awards.

1.3 Online Test Administration System

This module will be used for three distinct operations: 1. Creation of different types of users 2. Managing student details 3. Managing school details. Creation of different types of users There are three core users for the system. They are a. Super-admin b. Admin c. Teacher Note: 1. Student is not a core user of the application and will use this system only for taking a test. 2. Appropriate role assignment is done while a new user is created in the system. Login credentials should be provided on creation of the user. This module will be used for creation of different types of users for the application. The responsibility of this module is to manage the users and their different privileges. Information of these the users will be stored into the system using this module. A super-admin has the privilege to perform any function in OTTS. Also,he can be used to create/view/update/delete a new admin. An admin will be able create/view/update/delete a teacher into the system through a user interface.

When a user logs into the application, the system will compare the role of the logged in user with the roles present in the database. The application will show appropriate links and content in the welcome page based on the validated role. When a new user is created, a default password and a default userid should be generated for the newly created user. After logging in, user will be able to change his/her password and other profile details . However, this feature is available to teachers and admins only. Students can change their details with the help of the teacher. Password will be stored in system as a clear text password and password length should be between 7 and 12 characters. A password should contain atleast one special character and one numeral. The following details should be mandatorily captured for a user registration First name, Last name, Date of birth(dd-MMM-yyyy format), Email address, Phone number and Role . The following details can be optionally captured for a user registration Middle name and Address . Any captured detail should be valid logically in a real world scenario. A validated user can update his email address and phone number. Managing student details A teacher will have the privilege to manage the students details in OTTS. Teacher can c/v/u/d student details in the system. A newly created student should be assigned to the schools that are currently available in the system. The latest list of available schools should be provided for the above operation. When a student is registered, a default userid and password should be allotted to him. This will be communicated offline to the student who can use it to take tests. Userids should be unique. For details on the password, refer the previous module. The following details should be mandatorily captured for a student registration First name, Last name, Date of birth(dd-MMM-yyyy format), Gender, Email address, School id . The following details can be optionally captured for a student registration Middle name , Address and Contact number . Any captured detail should be valid logically in a real world scenario. A registered student can update his email address,school id and contact number with the help of a teacher.

Managing school details

An admin will have the privilege to c/v/u/d a school into the OTT system. The following details should be mandatorily captured for a school registration School name, Location, Contact number, Board(CBSE/ICSE/State syllabus), Email id. Any captured detail should be valid logically in a real world scenario. A registered school can update its location,email address and contact number with the help of an admin.

1.4 Test and Question management

This module will be used for three distinct operations: 1. Managing tests 2. Question management 3. Taking tests . Managing tests This module is responsible for management of tests. Test management will be in two steps. 1. Admin will create the tests and assign invigilators to the test. Only registered teachers can be assigned to tests. The following details should be mandatorily captured for a test Test name, Duration, Number of participants and invigilator id Any captured detail should be valid logically in a real world scenario. 2. Teacher will assign students to the created test. Only registered students can be assigned to tests. The number of participants should be considered while assigning students. The following details should be mandatorily captured Existing Test name, Student id Any captured detail should be valid logically in a real world scenario. Admin has the privilege to v/u/d any test he created. Teacher has the privilege to view test created by admin and v/u/d the students assigned to a test. Care should be taken to avoid clashes between admin u/d and teacher u/d. Question management. A teacher has got the privilege to create questions. While creating a question, the teacher has to mention the category of the question. The valid categories are English/Maths/Science/Computer. Only objective type, multiple choice questions (with one correct answer) will be supported in this system. Each question will have four options out of which one would be the correct answer. System will store all those four options including correct answer. There will be no negative marking. All inputs taken can be v/u/d by a teacher later.

An admin can assign the assign questions created to a test. He should have the option to view questions based on the category. Test id and question id should be taken from the admin as input from this module. All inputs taken can be v/u/d by an admin later. Care should be taken to avoid clashes between admin and teacher functionalities. Taking tests Students can login to OTTS to take a test. He can see the tests that have been assigned to him. Student can take the test by selecting the appropriate answer to the question. The testid, question id,student id and the selected answer should be the input of the student. Testid and Studentid should be a one time capture for one test. All inputs to be stored as such in the system. Student can v/u/d his answers in a test during the exam. Once the test is over, no operations can be done by the student.

1.5 Result and Award management

This module will be used for three distinct operations: 1. Result management 2. Award management 3. Award allocation Result management This module is used to generate the results of a student. The teacher has the privilege to generate a result. Based on the inputs given by the student while taking the test, the system should calculate the marks of the student by comparing his answer with the correct answer in the system. Correct answers are Awarded one mark while a wrong answer is Awarded zero marks. Total percentage should be calculated using this operation. Results of a student should be stored in the system. The teacher can view the details. U/D can be done by a teacher on providing the comments for the reason of the change.

Award management An admin can create Awards. Mandatory Inputs should be Award name, reason for Award , Award Category (Student/School)and Award amount. Optional input can be

other Award details. Any captured detail should be valid logically in a real world scenario. V/U/D can be freely performed by an admin. Award allocation An admin can allocate awards based on the following conditions 1. Student award - Students with minimum 90% are eligible. Such students should be shown to the admin while allocation of award. Admin should select award name for the student. 2. School award- Schools with minimum 3 students who have got an award are eligible for this feature. V/U/D can be freely performed by an admin while conforming to the business logic mentioned above.

1.6 Assumptions
Following are the assumptions and constraints that is used for outline the Functional requirements and there by the system behavior. The following is assumed while defining the Functional Requirement based on the current model. Only objective answer type question is allowed in the system. There will be four answer choices for each question. There should be equal marks for each question. At most 10 questions can be associated with a test. There is no negative marking for wrong answer.

1.7 CR for Modules

1. Implementation of new password policy. i.e. Hashed password will be stored in the system based on any encryption logic 2. Multi language support for OTT system. OTTS will support French and German together with English. Users can switch among languages anytime from any page anytime. 3. SSL implementation 4. Report generation in the user defined MIME format