Software Requirement Specifications

Submitted To: Mrs. Kakoli Banerjee Mrs. Rosy Chauhan

Submitted By: RADHIKA SINGH (IT-2 5thsem) NIKITA AGARWAL (IT-2 5th sem)

UPTU Roll no: 0909113081 0909122032

Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4. Definitions,Acronyms & Abbreviations 1.5.References 1.6 Overview 2. Overall Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Product Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 User Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Apportioning of Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3. Specific requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1. External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 . Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Logical Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Design Constraints 3.6 Software System Attributes 3.7 Organising the specific requirements 4. Supporting information ...................................... 4.1. Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1 Sequence Diagram 4.1.2 Context Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.3 E-R Diagram

1.

Introduction

1.1. Purpose
This Web Application provides facility to conduct online examination world wide. It saves time as it allows number of students to give the exam at a time and displays the results as the test gets over, so no need to wait for the result. It is automatically generated by the server. Administrator has a privilege to create, modify and delete the test papers and its particular questions. User can register, login and give the test with his specific id, and can see the results as well.

1.2. Document Conventions

The following are the list of conventions and acronyms used in this document and the project as well: Administrator: A login id representing a user with user administration privileges to the software User: A general login id assigned to users Client: Intended users for the software Examiner: Checks the test n gives result

1.3. Scope
Scope of this project is very broad in terms of other manually taking exams. Online Examination System is useful for both admin and student. In this system admin can add the questions and the admin take exam of a reg. student.

Objective: To follow SDLC to develop the system. To develop GUI as per convenience of the user. To implement the physical model, being tested as per the Standards. To document our efforts and analysis in a proper Comprehensible manner. Goal: To make a responsive, easy to operate, fast and efficient retrieval of information as per the user's convenience. To provide all information of student to admin according to requirement. To provide ease in the maintenance of different student scores. To make a database that is consistent, reliable and secure. To provide correct, complete, ongoing information. To develop a well-organized information storage system.

1.4 Definitions, Acronyms, and Abbreviations Definitions: 1. SDLC: The Systems Development Life Cycle (SDLC), or Software Develo-pment Life Cycle in systems engineering and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems

2. Use Case: A use case in software engineering and systems engineering is a description of a systems behavior as it responds to a request that originates from outside of that system 3. DFD : It is pictorial representation of the system that how it works.

Abbreviations: SDLC : Software/System Development Life Cycle GUI : Graphical User Interface

1.4. References
This web application has been prepared on the basis of discussion with Team Members, faculty members and also taken information from following books & website

1.4.1 Websites:
4) www.google.com 5) www.wikipedia.org 6) www.alexa.com 7) Fundamental of Software Engineering By Rajiv Mall 8) Software Engineering: A practitioners approach Ed. By Pressman, Roger 9) Software Engineering Seventh Edition Ian Sommerville

10) Software Engineering Ed.2 by Jalota & Pankaj. 11) Schaums Series, Software Engineering

1.5 Overview
By this system student give exam of various subjects as he/she wants. Firstly student wants to register and then choose the subject. Admin can add the various questions in different subject.

2. Overall Description
2.1 Product Perspective
The proposed Language Skill Exam System is an on-line Exam System. The online test created for taking online test has following stages Login Test Result Login:There is a quality login window because this is more secure than other login forms as in a normal login window there are multiple logins available so that more than one person can access to test with there individual login. But in this project there is only one login id i.e. administrator id and password by which a person enter the site. Hence it is more secure and 6

reliable than previously used on-line test simulators. TEST: Test page is the most creative and important page in this project. It consists of 2 modules namely: Subject selection Utilities Subject selection:-

From the given choices the candidate can select his

field (like C, C++ and JAVA etc) for taking on with the test. Utilities:It includes: Skip and come back to the question afterwards if needed. Gives the list of attempted and unattempted questions and can go to any question directly and can either attempt or change the answer of the already attempted question.

STUDENT

REGISTER

HELP DESK

ADMINISTRATOR

QUESTION

ADD
REPORT

UPDATE

DELETE

VIEW

2.1.1

Hardware Interfaces
Intel Processor 2.0 GHz or above. 256 MB RAM or more. 10 GB or more Hard Disk Drive or above.

2.1.2 Software Interfaces

Microsoft Windows 2000/XP. Jpanel. My Sql Ms Office package Ms Visual Studio 2008 Ms SqlExpress

2.1.3 Communication interfaces

The Customer must connect to the Internet to access the Website: Dialup Modem of 52 kbps Broadband Internet Dialup or Broadband Connection with a Internet Provider.

2.1.4 Memory Constraints

The product will be operating in windows environment. Also it will be compatible with the IE 6.0. Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher version. The only requirement to use this online product would be the internet connection.

2.2 Product Functions

There are three different users who will be using this product: University chancellor who will be acting as the administrator. Students who will be accessing the OES online. The features that are available to the Administrator are: The administrator has the full fledged rights over the OES. Can create/delete an account. Can view the accounts. Can change the password. Can hide any kind of features from the both of users. Insert/delete/edit the information of available on OES. Can access all the accounts of the faculty members/students. The features available to the Students are: Can view The different categories of Test available in their account. Can view their marks. Can view the various reading material. Can view and modify its profile but can modify it to some limited range. Can pay their fee online. 9

The features available to the Examiner are: Can view The different categories of Test conducted by users. Can view their marks. Can view and modify Results.

In On Line Examination System, the administrator can add/update/delete/view all the subjects and questions according to the subject. To Explain about the product functions, we use Use Case diagram as below:

Question

Report

Administrator

System

Fig: Use Case Diagram of Administrator And System

2.3 User Characteristics

There are various kinds of users for the product. Usually web products are visited by various users for different reasons. The users include :

10

 Chancellor who will be acting as the controller and he will have all the privileges of administrator. Students who will be using the above features by accessing the OES online. Examiner who will prepare& load database into the software.

2.4 Constraints
Thus software provides a secure system to handle records . The general constraints can include: It is not a large scale system. Only limited information provided by this system. The student does not have rights to check the status of other student.

The product will be operating in windows environment. Also it will be compatible with the IE 6.0. Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher version. The only requirement to use this online product would be the internet connection.

2.5 Assumptions and Dependencies

Full working of OES is dependent on the availability of Internet connection. Assumptions:

In general it has been assumed that the user has complete knowledge of the system that means user is not a nave user. Any data entered by him/her will be valid. To make the software as user friendly as possible but at the same time keeping in minds user requirements. Server OS should be Windows NT/2000/XP. Client PC should be Windows 9X/NT/WorkStation or Windows 2000

11

with latest service pack. Dependencies:

It depends that the one should follow the international standards for the generating the User ID & should fill the related information in the proper format.

2.6 Apportioning of Requirements

Not required.

3. Specific Requirements 3.1 External interfaces

For Administrator User: Admin needs to see all the questions. Admin can generate report according to the score.

For the Normal User:

User can view his/her account. Student can give exam. Student can only own score..

12

3.2 Functions
The Functions of system are as follows:

Administrator Login Question Report

1. Administrator/Normal User Login

Registered user should be allowed to Login into the On line examination system by entering his/her user name and password. The user name and password should be checked and only authorized user should be allowed to enter in on line exam System. For unauthorized users proper message should be displayed such as incorrect user name/ password, please enter correct entries etc.

Username - Mandatory Password Mandatory

2. Question In Question option User can Add/Update/Delete/View all question and their four options with correct answer but to take exam we admin want to add at least 30 question.

13

3. Report
In report section, admin can view the student report. In this admin can see the score of all students.

3.3 Performance Requirements

Some Performance requirements identified is listed below: The database shall be able to accommodate a minimum of 10,000 records of students. The software shall support use of multiple users at a time. There are no other specific performance requirements that will affect development.

3.4 Logical Database Requirements

Proposed Database is intended to store, retrieve, update, and manipulate information related to university which include Profile of both users Student details My account Test results

14

3.5 Design Constraints

The whole implementation is done in two modules. The first one is Administrator and the second is Examinee. Module I:This first module tracks the path of Administrator. In this module it shows how the admin can log into the system with a valid password and can add new valid user to the database. His name and exam id is saved in the database .Also he can manipulate the database and add new question in the database from the webpage itself. It also shows how many questions are in database. Module II:This second module track the path for the examinee .The examinee can log into the system with a valid ID issued by the admin. After successfully login into the system the examinee moves to the instruction web page where he will get instruction about the examination process. Then after clicking the start button the exam starts and timer also starts .In this manner examinee can take up the test and clicking the submit button , he will get the result of that section immediately. At the end system displays the initial web page.

3.6 Software System Attributes

The Quality of the System is maintained in such a way so that it can be very user friendly to all the users. The software quality attributes are assumed as under: 1)Accurate 2Reliable. 2) Secured. 3) Fast speed. 4) Compatibility. 5) Maintainable 6)Portable

15

3.6.1 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure. Therefore, it is required to take the database backup.

3.6.2 Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious access, use, modification, destruction, or disclosure are described below. Keep specific log or history data sets Assign certain functions to different modules Restrict communications between some areas of the program Check data integrity for critical variables Later version of the software will incorporate encryption techniques in the user/license authentication process. Communication needs to be restricted when the application is validating the user or license. (i.e., using https).

3.7 Organising the specific requirements

3.7.1Stimulus / Response Sequences

Responses for Administrator: The administrator can Login and Logout. When the Administrator Logs into the Online Exam system. The system will check for validity of login .If the Login and 16

password are valid, the response to this action is the administrator will be able to modify, view, add, deleting and all other functions that can be performed on the database. Examination: First of all the user/examinee gets a valid identification number (same as the roll no for a normal examination).The user can log on with this identification no. and can take up the examination. After logging in the user can see various options and can choose the option from the menu.

3.7.2 Functional Requirements

This section gives the list of Functional and non functional requirements which are applicable to the Online Exam System. Functional requirements are nothing but the services provided by the system to its end users. There are three sub modules in this phase. Candidate module. Examiner module. Administrator module. The functionality of each module is as follows. Candidate module: The candidate will logon to the software and take his examination. He can also check his previous examinations marks and his details. The candidate will get result immediately after the completion of the examination. Examiner module: The database is prepared & loaded into the software. Selection for examination can be done language wise by the examiner. The results will be displayed immediately after completion of the examination. Administrator module: The administrator collects all the results after successful completion of the examination and sends to the head quarters as and when required.

17

3.7.2.1 Interface Requirements

This section describes how the software interfaces with other software products or users for input or output.

3.7.2.2 User Interface

Application will be accessed through a Browser Interface. The interface would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to access any part of the application without logging on to the system.

3.7.3 Non Functional Requirements

3.7.3.1 User Interfaces
Application will be accessed through a Browser Interface. The interface would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to access any part of the application without logging on to the system.

3.7.3.2 Hardware Interfaces

Server Side:

Operating System: Windows 9x/xp ,Windows ME Processor: Pentium 3.0 GHz or higher RAM: 256 Mb or more Hard Drive: 10 GB or more

Client side: Operating System: Windows 9x or above, MAC or UNIX. Processor: Pentium III or 2.0 GHz or higher. RAM: 256 Mb or more 18

3.7.3.3 Software requirements

Client Side : .HTML, Web Browser, Windows XP/2000/Vista ,Ms visual Studio,Ms Sqlserver express Web Server: .HTML, Windows XP/2000/Vista

4 Supporting Information 4.1 Appendices

4.1 Sequence Diagram : It is shown as below:

19

Sequence Diagram For Administrator:

20

4.2 Context Diagram:

ADMIN

View questions and reports

STUDENT

Give authority

Registered himself/herself

SYSTEM Enter username and password Generate test Add/update/delete questions

21

4.3

E-R DIAGRAM

subjectid Option1 id ques tion

canswer Option3 option2 Option4 id name

question

Related to

subject

has

examination

give

Student

subjectid id enroll Exam_d ate id name enroll

22