Project Report

On

ONLINE EXAMINATION SYSTEM

By:
Gajera Dhaval(08ce13)
Agarwal Sarthak(08ce01)

B. Tech Semester VI Computer Engineering

Dec - April 2011

Submitted to,
Department of Computer Engineering / Information
Technology,
U. V. Patel College of Engineering
Ganpat University, Kherva - 382 711
1
 INDEX:

1. Abstract 4

2. Software Requirement Specification 5

............................................................................................................................................................1

1. INTRODUCTION..........................................................................................................................4
1.2 SCOPE.....................................................................................................................5
1.3 DEFINITIONS, ACRONYMS,AND ABBREVIATIONS.....................................6
Definitions:...............................................................................................................................6
1.4 REFERENCES ..............................................................................................................6

SPECIFIC REQUIREMENTS ..........................................................................................................8

3.1 FUNCTIONALITY.............................................................................................................8
3.1.1 Logon Capabilities.................................................................................................................8
3.2 USABILITY........................................................................................................................8
3.3 RELAIBILITY....................................................................................................................9
3.3.1 Mean Time Between Failures (MTBF)..................................................................................9
3.3.2 Mean Time to Repair (MTTR)...............................................................................................9
3.3.3 Accuracy.................................................................................................................................9
3.3.4 Maximum Bugs or Defect Rate..............................................................................................9
3.3.5 Access Reliability...................................................................................................................9
3.4 PERFORMANCE................................................................................................................9
3.4.1 Response Time.......................................................................................................................9
3.4.2 Administrator Response.......................................................................................................10
3.4.3 Throughput...........................................................................................................................10
3.4.4 Capacity................................................................................................................................10
3.4.5 Resource Utilization.............................................................................................................10
3.5 SUPPORTABILITY..........................................................................................................10
3.5.1 Internet Protocols.................................................................................................................10
3.5.2 Information Security Requirement.......................................................................................10
3.5.3 Result System Data Compatibility.......................................................................................10
3.5.4 Maintenance.........................................................................................................................10
3.5.5 Standards..............................................................................................................................11
3.6 DESIGN CONSTRAINTS................................................................................................11
3.6.1 Software Language Used......................................................................................................11
3.6.2 Development Tools..............................................................................................................11
3.7 ONLINE USER DOCUMENTATION AND HELP SYSTEM REQUIREMENTS........11
3.8.2 Hardware Interfaces.........................................................................................................12
3.8.3 Software Interfaces............................................................................................................12

4. SUPPORTING INFORMATION................................................................................................12

2
3. Methodology 14

4. List of Requirements 16

5. Use-case Diagrams 18

6. Class Diagrams 20

7. Activity Diagrams 21

8. Sequence Diagrams 22

9. Collaboration Diagram 22

11. Data Flow Diagram 23

12. Data Dictionary 25

13. Entity Relationship Diagram 28

14. Test Cases 29

15. Conclusion 32

PROJECT ABSTRACT

Online Exam is a web application. In which the candidate will be able to give an
online examination. This project divided into the three module which is as administrator,
user, guest user.

Admin can also delete or add or update the question. He/she can provide the date
of exam to the examiner. He/she arrange marks of question paper and after examination
display on screen. In this web application also provide to Admin show a detail of register
user delete user profile show history of visiting user and decide new user request accept
or reject.

3
 User can give the examination. If User has no valid information or dummy
account then that user is not able to give online exam.

Guest User is able to read the information about examination and updated news
about exam.

SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION

On line examination system is conducted for the students to give an exam

on a particular subject according to the specified time.

1.1 PURPOSE
On line examination can change the approach of admin. This
system can generate the report of the student according to the score. It is
time saving system because when the student gives test then the checking
4
time can be saved. The score of student is automatically generated by this
system.

1.2 SCOPE

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
registered 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.

Goals:
• 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 the 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.
• To make good documentation so as to facilitate possible
5
 future enhancements.

1.3 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 system’s 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

1. Roger S. Pressman, Software Engineering- A practitioner’s approach. NY Mc

Graw Hill, 2005
2. Bob Hughes and Mike Cotterell – Software Project Management 2nd edition. By
Tata Mc Graw Hill, 2001.

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 subjects.

6
 2. GENERAL DESCRIPTIONS

2.1 PRODUCT PERSPECTIVE

• SMMS is a independent and totally self contained.

• Block Diagram of the System is below:
STUDENT

REGISTER

HELP DESK

ADMINISTRATOR

QUESTION
ADD UPDATE DELETE VIEW

REPORT

2.2 PRODUCT FUNCTION

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

2.3 USER CHARACTERISTICS

In this system there are two users:

Administrator User:

7
 • He/she have knowledge of System.
• He/she handle the system process.
• He/have rights to entry the records.

Normal User:

• Normal user can not handle the system.

• He/she can only view the record of his/her self.

2.4 GENERAL 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.

SPECIFIC REQUIREMENTS

This section describes in detail all the functional requirements.

3.1 FUNCTIONALITY

3.1.1 Logon Capabilities

The system shall provide the users with logon capabilities.

3.1.2 Alerts
The system can alert the administrator in case of any problems.

3.2 USABILITY

8
 • The system shall allow the users to access the system from the Internet using
HTML or it’s derivative technologies. The system uses a web browser as an
interface.

• Since all users are familiar with the general usage of browsers, no specific
training is required.

• The system is user friendly and self-explanatory.

3.3 RELAIBILITY

The system has to be very reliable due to the importance of data and the damages
incorrect or incomplete data can do.

3.3.1 Mean Time Between Failures (MTBF)

The system will be developed in such an efficient way that it could fail once in a
year.

3.3.2 Mean Time to Repair (MTTR)

Even if the system fails, the system will be recovered back up within an hour or
less.

3.3.3 Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the
uses use the system.

3.3.4 Maximum Bugs or Defect Rate

Not specified.

3.3.5 Access Reliability

The system shall provide 100% access reliability.

3.4 PERFORMANCE

3.4.1 Response Time

Response time should be minimum as much as possible.

9
 3.4.2 Administrator Response
The system shall take as less time as possible to provide service to the
administrator.

3.4.3 Throughput
The number of transactions is directly dependent on the number of users.
So throughput should be maximum as much as possible.

3.4.4 Capacity
The system is capable of handling requirement users (maxi.500 users) at a time.

3.4.5 Resource Utilization

The resources are modified according the user requirements.

3.5 SUPPORTABILITY

The system designers shall take in to considerations the following supportability

and technical limitations.

3.5.1 Internet Protocols

The system shall be comply with the TCP/IP protocol standards and shall be
designed accordingly.

3.5.2 Information Security Requirement

The system shall support the online examination information security
requirements.

3.5.3 Result System Data Compatibility

The result of examiner will be calculated correctly and that should be compatible
with the data type system and design.

3.5.4 Maintenance
The maintenance of the system shall be done as per the maintenance contract.

10
 3.5.5 Standards
The coding standards and naming conventions will be as per the American
standards.

3.6 DESIGN CONSTRAINTS

3.6.1 Software Language Used

The languages that shall be used for coding the Online Examination System are
php, HTML, JavaScript, and VBScript. For working on the coding phase of the
Online Examination System, the Internet Information Services (IIS) Server needs
to be installed.

3.6.2 Development Tools

Will make use of the available Microsoft Dreamwever Tool kits for working with
PHP languages. Also will make use of the online references available for
developing programs in HTML and the two scripting languages, JavaScript and
VBScript.

3.7 ONLINE USER DOCUMENTATION AND HELP SYSTEM

REQUIREMENTS

Online help is provided for each of the feature available with the Online
Examination System. All the applications provide an on-line help system to assist
the user. The nature of these systems is unique to application development as they
combine aspects of programming (hyperlinks, etc) with aspects of technical
writing (organization, presentation). Online help is provided for each and every
feature provided by the system.
The User Manual describes the use of the system to Admin and users. The user
manual should be available as a hard copy and also as online help.

3.8 INTERFACES

3.8.1 User Interfaces

11
 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 view only his/her own score..

3.8.2 Hardware Interfaces

• Intel Processor 2.0 GHz or above.

• 256 MB RAM or more.

• 10 GB Hard Disk Drive or more.

3.8.3 Software Interfaces

• Microsoft Windows 2000/XP.

• My Sql

• Ms Office Package

3.8.4 Communications Interfaces

The Online Examination System will be connected to the World Wide Web.

4. SUPPORTING INFORMATION

The use-case storyboards or the user-interface prototypes are not available. The
appendices are not to be considered as part of the requirements.

12
 METHODOLOGY

MODEL SELECTION:

There are many software development models available. Among all of

them, we consider the Prototype Model best for our system.

DESCRIPTION:

This application is developed with PROTOTYPING MODEL. As shown

in model, first of all we need to gather all the information about the
application as per the customer’s need .Then after quick design is carried out
and prototype is built .This prototype will be submitted to customer for
evaluation . If customer needs to modify the application then we can do it by
modifying the prototype .This cycle of obtaining customer feedback and
modifying the prototype continuous till the customer approves prototype
.After this if customer accepts then design will be created. The overall
development cost might turn out to be lower in prototype model. By
constructing the prototype and submitting it for user evaluation, many
customer requirements get properly defined and technical issues get resolved
by experimenting with the prototype. This minimizes the change requests
from the customer and the associated redesign costs
13
 Requirements
gathering

Quick
desig
n
Refine
requirements
Build
Incorporating
prototyp
Customer
e

Customer
Evaluation
of prototype

14
 Design

Implement

Test

Maintain

LIST OF REQUIREMENTS

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS:

1. Login

User can access the system after successful login. User can login successfully
if and if he/she is an authenticated user and authorized user. User prompted
for username and password. User gives username and password. If he/she
entered wrong username or password then system allow him/her to re-enter it.

2. Insert

This operation is used to insert the data into the different tables. First, Data are
15
 filled into the form by any user or administrator. Then the filled data are
submitted by verifying by internal queries. If the data are inserted correctly
then & then it will be inserted into the database otherwise it will give an error
to the user or administrator. Inserted data will be stored into the appropriate
table.

3. Update

Depending on the database that is selected, the user may wish to modify some
details under certain parameter(s) for an existing entity.

4. Delete

This operation is used to delete the data from the database which are
unwanted or duplicate. In this application, basically delete operation is
performed by the admin side.

5. Search

This operation is used to search the particular entry from the database. As per
delete operation, this operation also needs to give an id of particular entry of
the table.

6. Reliability

Reliability of the system is very important. As it would be accessed several

times in a day by different users across the department, it should be entirely
robust and reliable.
7. Usability

The system shall allow the users to access the system from the Internet using
HTML or it’s derivative technologies. The system uses a web browser as an
interface. Since all users are familiar with the general usage of browsers, no
specific training is required.The system is user friendly and self-explanatory.
8. Maintainability:
The system should be designed to be easily maintainable and get the least
Complaints from users, along with minimum downtime.

9. Extensibility:

16
 The system should be designed to be extensible to changes. A change might
be a result of either a change in the user requirements or required adherence
to some new company policy.

UML DIAGRAMS

USE CASE DIAGRAM:

 Online examination system:

17
 Login:

18
CLASS DIAGRAM:

19
ACTIVITY DIAGRAM:

20
SEQUENCE DIAGRAM:

21
COLLABORATION DIAGRAM:

22
DATA FLOW DIAGRAM:

STUDENT:

LEVEL-1

ADMIN:
23
DATA DICTIONARY
24
  Admin:

Column Name Data type Allow Description

Nulls
User name nvarchar(50) No Indicates the name of user account
password nvarchar(50) No Indicates the password of user

 Online test:

Column Name Data type Allow Description

Nulls
Que_no nvarchar(50) No Indicates the que. no
Que nvarchar(50) No Indicates the quetion
Ans nvarchar(50) No
Opn1 nvarchar(50) No Indicates the option 1 in que.
Opn2 nvarchar(50) No Indicates the option 2 in que.
Opn3 nvarchar(50) No Indicates the option 3 in que.
Opn4 nvarchar(50) No Indicates the option 4 in que.

 Username:

25
Column Name Data type Allow Description
Nulls
fname nvarchar(50) No Indicates the name of user
lname nvarchar(50) No Indicates the lastname of user
uname nvarchar(50) No Indicates the username
password nvarchar(50) No Indicates the password of user
dob nvarchar(50) No Indicates the birthdate of user
gender nvarchar(50) No Indicates the gender of user
email nvarchar(50) No Indicates the mail id of user
city nvarchar(50) No Indicates the city of user
country nvarchar(50) No Indicates the country of user
pcode nvarchar(50) Yes Indicates the pincode of user’s city
Sq_que nvarchar(50) No Indicates the admin’s questions if
he/she forgot password
Sq_ans nvarchar(50) No Indicates the answer of above que.
isuser Numeric(1,0) No Indicates the validation

Material:

Column Name Data type Allow Description

Nulls
cat nvarchar(50) No Indicates the cat
subcat nvarchar(50) No Indicates the subcat
fn nvarchar(50) No Indicates the faculty

Display:

Column Name Data type Allow Description

Nulls
rules nvarchar(50) No Indicates the rules
marks nvarchar(50) No Indicates the marks

26
date nvarchar(50) No Indicates the date

ENTITY RELATIONSHIP DIAGRAM

27
password rollno name
password

userid
Stdid courseName

lls
enro
Student Admin

iv n
G co uct
e d
s

Exam

exami questionpape
studentmap
d r

TEST CASES

Administrator Module

28
 Obtained
Sr.No Scenario Expected Result
Result
“Invalid Username or
Username is correct, Password is
1 Password” messge is TRUE
incorrect.
displayed.
“Invalid Username or
Username is incorrect, Password is
2 Password” message is TRUE
correct.
displayed.
“Invalid Username or
Incorrect values for username and TRUE
3 Password” message is
password are submitted.
displayed.
Navigates to the next page
Correct values for username and
4 based on the user who is TRUE
password are submitted.
logging in.

User Registration Module

Sr. No Scenario Expected Result Obtained

Result
1 Name field is empty. “Please Enter Name” message is TRUE
displayed.
29
 2 Email id field is empty. “Please Enter Emailid” message is TRUE
displayed.
3 Password field is empty. “Please Enter Password” message is TRUE
displayed.
4 Emailid is invalid. “Please Enter Valid Emailid” message TRUE
is displayed.
5 Emailid already registered. “Emailid Already Exista,Please Enter TRUE
Another Emailid” message is
displayed.
6 Session id field is empty. “Please Enter Session id” message is TRUE
displayed.
6 All field values are properly “Registration Completed TRUE
entered and clicking Save Successfully” message is displyed.
button.
7 All field values are properly Email is sent to the candidate on the TRUE
entered and clicking Save Emailid sepecified by the candidate.
button.
8 Onclicking Cancel button. All fields values are cleared. TRUE

Display Module:

Sr. No Scenario Expected Result Obtained

1 Administrator wants to
add/remove or modify
the result
2 Set priority for the rules
Result
“Please Login” message is displayed. TRUE
“Please Login” message is displayed TRUE
and then the admin can set priorities.

30
 3 Student/candidates wish The result is displayed. TRUE
to view the result and
click on its link

CONCLUSION

The following project will be useful for all the educational organisations
who wish to have an online examination conducted thereby reducing the paper work.
It is user friendly to all the people. In developing the modules and all the coding
scheme, system architecture has been kept in mind. All the modules are added in the
system in such a way that they would not cause any harm to other modules.

We will be able to convert the traditional examination system for the

students into the e-system that has less redundancy and can be accessed throughout
any part of the world. This project allows the administrator to authorize students
when they are logged in to the system, after confirming his/her information
automatically and dummy students would be restricted. The current system does not
31
yet support all the desired facilities. Currently this project is only limited to the
college level.

32