You are on page 1of 43

Project Report on ONLINE EXAMINATION SYSTEM for BS(CS)

by

misbah Fatima (50) komal Naz (47)

Saneea Rasheed (70)

Guide Mrs.Mariyam

Chapter 1
Introduction

1.

INTRODUCTION

1.1

PROJECT PROFILE

1. Project Partners Strength :- 3 Names:- o Misbah Fatim (50) o Komal o Saneea (70) (47)

Chapter-1

Introduction

1.2

SYSTEM OVERVIEW
Online Examination System is built on Asp.net, Crystal Reports and SQL Server 2005. The Web application is built to server the following areas. To make the examination process in the institutes fast, reliable, and error free. Hosting on the Intranet can provide a secured Examination channel for any institute. Registration of users can be used to generate revenue and thus can be profited form the system. Real time report generation gives quick results to given exams. Entrance examinations can also be conducted. The database is self explanatory as the code.

1.3

OBJECTIVE
Create a Web application to be used in place of old paper based user examination process. Use ASP.NET and SQL Server technology to create strong and secured database connectivity. Incorporate the server software within the code. Runtime package and deployment instructions are given.

1.4

SCOPE
Online Examination System is designed for Educational Institutes like Schools, Colleges, and Private Institutes to conduct logic tests of their students on a regular basis. The system handles all the operations and generates reports as soon as the test is completed which saves the precious time of faculties spent on reviewing answer sheets. The existing system is weak when it comes to surprise test organizations whereas this system can make it possible very easily.

Chapter 2
System Requirement Study

3.

SYSTEM REQUIREMENT STUDY

3.1

USER CHARACTERISTICS
This system will be used in Three User Modules which are Administrator, Faculty and Student. As all of these have different requirements the modules are designed to meet their needs and avoid any type Of confusion. The Uses of all three User Modules have been described below.

[1]

User can do the following functions in the Supplier Module


[2]

Add & Edit Course Add & Edit Year Add & Edit Subject Add & Edit Faculty Add Receipt for User Edit User

View Results Generate Reports.

User can do the following functions in the Faculty Module

[3]

Add & Edit Question

Search the Question

User can do the following functions in the Student Module

Give Exam

View Result

Chapter 4
System Analysis

4.
4.1

SYSTEM ANALYSIS
STUDY & WEAKNESSES OF CURRENT SYSTEM.
Current System The Current system of examinations is highly complicated and expensive. Whenever exams are to be conducted there are various tasks that have to be done again and again.
Setting question paper Checking for errors Printing question papers Scheduling Exams

Conducting Exams
Checking Answer Papers Preparing Result Charts Solving Question Papers

Weaknesses in Current System The current system is as mentioned earlier very complicated and expensive as compared to the new system. It also wastes the precious time of the faculties which can then be used in solving student queries and helping them improvise.

Taking surprise tests of students is also not feasible in the current system as planning for the exam and checking answer papers takes a lot of time and thus cannot be completed on schedule.

It also has no measures to prevent students from copying the answers rather than printing different sets of question papers which in turn can result expensive.

10

Chapter-4

System Analysis

As Faculties are humans and so prone to errors, there can be mistakes in checking answer papers, calculating marks and the result charts prepared may also have these errors. Only preventive measures are taking a double check to ensure these errors dont happen which would again require extra time and may also result in a mentally tired faculty.

After the exams have been conducted the faculty has to provide solutions to the questions asked in exam. It would mean extra time and extra work for the faculty and also result in extra expenses of stationary.

Thus, the current system is in every way ineffective for conducting examinations in these days when time is more costly than anything and they also pose a threat to the environment when we are amidst a global crisis and in the need of a Green Revolution.

4.2

REQUIREMENTS OF NEW SYSTEM.

4.2.1 User Requirements. The User requirements for the new system are to make the system fast, flexible, less prone to errors and reduce expenses and save time. o Time can be saved in scheduling the exams if it were available to make question banks to store questions for different subjects in advance and can be used as per required. o A system that can automate the checking of answers which are pre-stored so that results can be generated as soon as the student gives the exam. o A facility that can generate result charts as per required without manual interference for providing how a task is to be done instead only asking what is to be done. o The system should have Student and Faculty records on hand which can be used as per required only by authorized personnel. 11

Chapter-4

System Analysis

o The New system should be more secure in managing user records and reliable enough to be used in any condition. o Finally, it should prove cost effective as compared to the current system.

4.3

Feasibility Study
A key part of the preliminary investigation that reviews anticipated costs and benefits and recommends a course of action based on operational, technical, economic, and time factors. The purpose of the study is to determine if the systems request should proceed further.

4.3.1 Does the New System Contribute to the Overall Objectives of the Organization? The new system would contribute to the overall objectives to of the organization. It would provide a quick, error free and cost effective solution to the current process. It would provide a solution to many issues in the current system. As the new system is flexible and scalable it can also be upgraded and extended to meet other complex requirements which may be raised in the future. However it is up to the organization to upgrade or extend it.

4.3.2 Can the New System be Implemented Using Current Technology? The organization has a computer laboratory which has about 50 machines connected by Internet Lan and managed by a server. It would be very easy to set up the system in the current environment as the application is web based it does not require to be installed on every machine. The database and IIS are set up on the server and the .Net Framework installed on every machine, the system can be started as quick as required by the management.

12

Chapter-4

System Analysis

4.4

Features of the New System.


The new system has been designed as per the user requirements so as to fulfill almost all them. Quick Scheduling Exams can be created very quickly as compared to the existing system as it allows the use of previously entered questions to be used again. It saves time required to get the question papers printed and distributed before the students are allowed to appear for the examination. Questions entered once can be accessed by students as soon as they login to their account. Immediate Results and Solutions One of the most important draw backs of the current system is that the faculties are required to check the answer papers which is again a lengthy process and prone to errors. The new system will generate the result as soon as the test is finished by the user and will also store it in the database for further usage. The solution is also available as soon as the questions are inserted in the database. Easy to Store and Retrieve Information
The new system makes it easy to store and retrieve information as required and does not involve storing information in separate sheets or papers. It thus saves data management problems faced in the current system as it has a Database Management System of it own which allows 33 reports to be generated when needed.

Cost Effective One of the main reasons of the new system is its cost effectiveness. It saves the amount spend on stationary as well as overall cost of conducting an examination which also involves paying supervisors, paper checkers, question paper printers etc.

13

Chapter 5
System Design

5.
5.1 CONTEXT DIAGRAM.

SYSTEM DESIGN

The context diagram is a top-level view of an information system that shows the boundaries and scope. It describes the main objective of the system and the entities involved.

Administrator

Insert/update subject Insert/update course Insert/update faculty Insert/del receipt

Insert question Change password

Faculty

Accept or Reject Change password Request report Return report

Online examination system

AcceptOr Reject Change password Give exams Register using recipt

Accept or reject Request report Return report

User

14

Chapter-5

System Design

5.2

DATA FLOW DIAGRAM (DFD)


The DFD (also known as bubble chart) is a simple graphical formalism that can be used to represent a system in terms of the input data into the system, various processes carried on these data, and the output data generated by the system.

The main reason why the DFD technique is so popular is because the fact that the DFD is a very simple formalism it is simple to understand and use. A DFD model uses a very limited number of primitive symbols to represent the functions performed by a system and the data flow among the functions. Starting with a set of high-level functions that a system performs, a DFD model hierarchy represents various sub-functions.

5.2

DFD Level 0

15

Chapter-5

System Design

5.3

Registrations (DFD Level 1)

16

Chapter-5

System Design

5.4

Question Insert (DFD Level 1)

LCCA (Group No: 61)

17

Chapter-5

System Design

5.5

Examination (DFD Level 1)

18

Chapter-5

System Design

5.6

Reporting (DFD Level 1)

19

Chapter-5

System Design

5.7

Registrations (DFD Level 2)

20

Chapter-5

System Design

5.8

Question Insert (DFD Level 2)

21

Chapter-5

System Design

5.9

Examination (DFD Level 2)

22

Chapter-5

System Design

5.10

User Authentication (DFD Level 3)

23

Chapter-5

System Design

5.11

User Authentication (DFD Level 4)

24

Chapter-5

System Design

5.3

DATA MODELLING
5.3.1 Data Dictionary Table 5.1 User Master Description: Details of User

FIELD NAME User_ID

DESCRIPTION unique user id is given to each user registration no is given

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

Reg_No to each user reference no is given to Ref_No each user F_Name L_Name Course_ID course the user is listed year id in which year Year_ID the user is listed unique username of the Username user Password Email Gender Date_Birth user password email of the user user gender birth date of user description of user Education education user first name user last name course id in which

Foreign Key

Integer

Foreign Key

Integer

15 15 Foreign Key 3

Varchar Varchar Integer

Foreign Key

Integer

Not Null

10

Varchar

Not Null

10 50 7

Varchar Varchar Varchar Date Time

10

Varchar

25

Chapter-5 Occupation Address user occupation users postal address country in which the Country user resides state in which the user State resides city in which the user City resides zip code of the area in Zip which the user resides is the account active or Active not Created_Date created date of user date on which user Modified_Date modified 10 20 Not Null 10 20 20 20 10 60

System Design Varchar Varchar

Varchar

Varchar

Varchar

Varchar

bit

Varchar

Varchar

26

Chapter-5 Table 5.2 Faculty Master Description: Details of Faculty FIELD NAME Faculty_ID given to each faculty reference no is given to Ref_No each faculty F_Name L_Name faculty first name faculty last name unique username of the Username user Password Gender Education education Occupation Address Contact_No Main_Subject Created_Date faculty occupation facultys postal address faculty contact no main subject of faculty created date of faculty date on which faculty Modified_Date modified is the account active or Active not Not Null 10 10 60 10 20 20 faculty password faculty gender description of faculty 10 Not Null 10 7 Not Null 10 Not Null Not Null 15 15 Foreign Key 9 DESCRIPTION unique faculty id is CONSTRAINTS SIZE Primary Key 3

System Design

DATA TYPE Integer

Integer

Varchar Varchar

Varchar

Varchar Varchar Varchar

Varchar Varchar Integer Varchar Varchar

Varchar

Bit

27

Chapter-5 Table 5.3 Admin Master Description: Details of Admin

System Design

FIELD NAME Admin_ID

DESCRIPTION unique admin id is given to each admin

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

F_Name L_Name

admin first name admin last name admin username of the

Not Null Not Null

15 15

Varchar Varchar

Username user Password Created_Date Modified_Date modified is the account active or Active not admin password created date of admin date on which admin

Not Null

10

Varchar

Not Null

10 20 10

Varchar Varchar Varchar

Not Null

Bit

28

Chapter-5 Table 5.4 Receipt Master Description: Details of Receipt

System Design

FIELD NAME Receipt_ID

DESCRIPTION unique receipt id is given to each receipt unique registration no is

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

Reg_No given to each receipt reference no is given to Ref_No each receipt F_Name L_Name first name last name course id in which Course_ID course the receipt is listed year id in which year Year_ID the receipt is listed Created_Date created date of user is the receipt active or Active not

Not Null

Integer

Not Null

Integer

Not Null Not Null

15 15

Varchar Varchar

Foreign Key

Integer

Foreign Key

Integer

20

Varchar

Not Null

bit

29

Chapter-5

System Design

Table 5.5 Question Master Description: Details of Questions FIELD NAME Question _ID given to each question subject id in which the Sub_ID question is listed Question question first option for the Answer1 question second option for the Answer2 question third option for the Answer3 question fourth option for the Answer4 question correct answer to the Correct_Answer question question created by Created_Date faculty date the question was Created_By created date the question was Modified_Date modified Date Time 10 Varchar Date Time 50 Varchar 50 Varchar 50 Varchar 50 Varchar 50 varchar Not Null 100 Varchar Foreign Key 3 Integer DESCRIPTION unique question id is CONSTRAINTS SIZE Primary Key 3 DATA TYPE Integer

30

Chapter-5 question modified by Modified_By faculty is the question active or Active not Not Null 10

System Design

varchar

Bit

Table 5.6 Subject Master Description: Details of Subject

FIELD NAME Sub_ID

DESCRIPTION unique subject id is given to each subject year id in which the

CONSTRAINTS SIZE Primary Key 39

DATA TYPE Integer

Year_ID subject is listed course id in which the Course_ID subject is listed Sub_Name Sub_Description subject name subject description is the subject active or Active not

Foreign Key

Integer

Foreign Key

Integer

15 100

Varchar Varchar

Not Null

bit

31

Chapter-5 Table 5.7 Exam Master Description: Details of Exams FIELD NAME Exam _ID DESCRIPTION CONSTRAINTS SIZE unique exam id is given Primary Key 3 to each exam question id of the Question_ID question attended by the user subject id in which the Sub_ID question attended by the user is listed username of the user Username appearing for the exam has the user attended Attend the question answer selected for the User_Answer question by the user marks obtained by the Marks user for answering the question date on which the user ExamDate had appeared for the exam 3 10 Not Null 10 Foreign Key 3 Foreign Key 3

System Design

DATA TYPE Integer

Integer

Varchar

varchar

bit

Varchar

integer

Date Time

32

Chapter-5

System Design

Table 5.8 Result Master Description: Details of Results

FIELD NAME Result _ID

DESCRIPTION CONSTRAINTS SIZE unique result id is given Primary Key 3 to each result subject id of the subject

DATA TYPE Integer

Sub_ID

the user has taken the exam username of the user

Foreign Key

Varchar

Username appearing for the exam marks obtained by the Marks user date on which the user ExamDate had appeared for the exam

Not Null

10

varchar

integer

Date Time

33

Chapter-5

System Design

Table 5.9 Course Master Description: Details of Course

FIELD NAME Course _ID

DESCRIPTION unique course id is given to each course course name of the

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

Course_Name course usually unique description or Course_Desc abbreviation of the course name user id of the admin Created_By user who created the course date on which the Created_Date course has been created user id of the admin Modified_By user who modified the course date on which the Modified_Date course has been modified

Not Null

10

varchar

20

varchar

10

varchar

10

Date Time

20

Varchar

Date Time

34

Chapter-5

System Design

Table 5.10 Year Master Description: Details of Year

FIELD NAME Year _ID

DESCRIPTION unique year id is given to each year course id of the course

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

Course_ID

in which the year is listed course name of the

Foreign Key

Integer

Year_Name course usually unique duration of that course Duration in that particular year

Not Null

10

varchar

integer

Table 5.11 Country Master Description: Details of Country

FIELD NAME Country _ID

DESCRIPTION CONSTRAINTS SIZE unique country id of the Primary Key 3 country listed name of the country country code Not Null 20 5

DATA TYPE Integer

Course_Name Course_Code

varchar varchar

35

Chapter-5 Table 5.12 State Master Description: Details of State

System Design

FIELD NAME State_ID

DESCRIPTION unique state id of the state country id of the

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

Country _ID

country in which the state is listed

Foreign Key

Integer

State_Name State _Code

name of the state state code

Not Null

20 5

varchar varchar

Table 5.13 City Master Description: Details of City

FIELD NAME City_ID

DESCRIPTION unique city id is given to each city country id of the

CONSTRAINTS SIZE Primary Key 3

DATA TYPE Integer

Country _ID

country in which the city is listed state id of the state in

Foreign Key

Integer

State_ID which the city is listed City_Name name of the city

Foreign Key

Integer

Not Null

20

varchar

36

Chapter-5 5.3.2 Entity Relationship Diagram

System Design

An Entity-relationship model is an abstract conceptual representation of structured data. Entity relationship modeling is a relational schema database medeling method, used in Software Project Management to produce a type of conceptual data model (or semantic data model) of a system, often a relational database, and its requirements in top-down fashion.

5.12

Entity Relationship Diagram

78