Chapter 1: Introduction

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.

Online Exams is being launched because a need for a destination that is beneficial for
both institutes and students. With this site, institutes can register and host online exams.
Students can give exams and view their results. This site is an attempt to remove the
existing flaws in the manual system of conducting exams.

The two primary benefits of administering examinations online were identified above:

(1) the large cost savings of the substitution of machines for labor in grading, and

(2) the potential for enhanced student learning due to more frequent assessment.
Another significant benefit is immediate feedback to students on homework
assignments and examinations.

Vision: The online examination system aims at providing the quick results to the
students and teachers.

Mission: Our mission is to shape the examination process in a new dimension of e-

examination at Jazan University.

Objectives of Existing Project:

1. To evaluate the students capabilities.
2. To grade students in accordance to their performance.

Problems of Existing System:

1. Difficult in managing the manual system.
2. Lot of preparation is required.
3. Lot of paper work required.
4. Time consuming.

1
 5. Lot of staff engagement required.
6. It takes time to declare examination result.
Objective of the Project:
1. Reduce examination operating costs
2. Reduce time costs of preparing for final examinations.
3. Render the students and teachers to accept and use the online exam.
4. This website reduces the manual work.
5. To maintaining accuracy, increasing efficiency and saving time.
6. For students, it saves time of going too far away centers and also they can view
their result then and there.

Scope:
The scope of the project is defined to the parameter of Jazan University online
examination system. The scope of the online examination is restricted to the
boundary of Jazan University campus, i.e those students who want to appear for
the examination need to physically present in the campus of university. The
system will only accept the registered students in that particular course. The
system authenticate the students with their user id and password but fails to
authenticate the authenticity of the student. The online examination facility is not
functional beyond the parameter of Jazan University as the data base access is
limited to the premise of Jazan University. There is some restriction been made
on the start and end time of the examination i.e is the examination of course will
open only at the schedule time.

Data Flow Diagram (DFD)

Model - Students

Students can login user their university Id and password.

The enrolled students can see their courses they have opted for.

The scheduled course for the exam will be highlighted accordingly.

2
On clicking the scheduled examination the questions will appear in the screen.

The student is required to choose the answer from MCQ.

Then he has to submit the option in last.

The server will analyze the answers and display the result.

Model - Faculties

The faculty can login to server using their user ID and password .

The courses are displayed on the screen which he is teaching.

He can choose the course and see the displayed result and make necessary report.

He can even filter the results and generate the report.

Model Question

In this option the question bank is created.

Each question carries MCQ.

The answer is having radio button to be chosen only one option

In database options are mentioned when the student press submit button the analysis
is made in the data base and the result is displayed.

Model Management

Management can login to their account using their user ID and Pwd.

Option is given to filter their search course wise and level wise.

3
The report can be generated based on that search.

4
Chapter 2: Feasibility Study

a. Purpose of the Study:

A feasibility study aims to objectively and rationally uncover the strengths and
weaknesses of an existing business or proposed venture, opportunities and threats
present in the environment. A feasibility study evaluates the project's potential for
success; therefore, perceived objectivity is an important factor in the credibility of the
study for potential investors and lending institutions.

It focuses on these major questions:

1. What are the users demonstrable needs and how does a candidate system meet
them?

2. What resources are available for given candidate system?

3. What are the likely impacts of the candidate system on the organization?

4. Whether it is worth to solve the problem?

During feasibility analysis for this project, following primary areas of interest are to be
considered. Investigation and generating ideas about a new system does this.

Steps in feasibility analysis:

Form a project team and appoint a project leader.

Prepare system flowcharts.
Enumerate potential proposed system.
Define and identify characteristics of proposed system.
Determine and evaluate performance and cost effective of each proposed
system.
Weight system performance and cost data.
Select the best-proposed system.

5
b. Justification for the proposed system

We all know the importance of computerization. The world is moving ahead at lightning
speed and everyone is running short of time. The application areas for the
computerization have been selected on the basis of following factors:

Minimizing the manual records kept at different locations.

There will be more data integrity.
Facilitating desired information display, very quickly, by retrieving information
from users.

Facilitating various statistical information which helps in decision-making.

To reduce manual efforts in activities that involved repetitive work.
Updating and deletion of such a huge amount of data will become easier.

c. Economic Feasibility
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economical feasibility, the development
cost in creating the system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any addition hardware or
software. Since the interface for this system is developed using the existing resources
and technologies available at Jazan University, there is nominal expenditure and
economical feasibility for certain.

d. Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation
includes the following:

Does the necessary technology exist to do what is suggested?

6
 Do the proposed equipments have the technical capacity to hold the data
required to use the new system?
Will the proposed system provide adequate response to inquiries, regardless of
the number or location of users?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data
security?

7
Chapter 3: Project Plan

Gantt chart
A Gantt chart is a type of bar chart, adapted by Karol Adamiecki in 1896 and
independently by Henry Gantt in the 1910s, that illustrates a project
schedule. Gantt charts illustrate the start and finish dates of the terminal
elements and summary elements of a project.

A Gantt chart, commonly used in project management, is one of the most popular and
useful ways of showing activities (tasks or events) displayed against time. On the left of
the chart is a list of the activities and along the top is a suitable time scale. Each activity
is represented by a bar; the position and length of the bar reflects the start date,
duration and end date of the activity. This allows you to see at a glance:

What the various activities are

When each activity begins and ends
How long each activity is scheduled to last
Where activities overlap with other activities, and by how much
The start and end date of the whole project

Activity Job Duration

1 Research proposal Submission From 01 Sept - 16 Sept 2015
System Requirement & System
2 Design From 04 Oct 2015 - 29 Oct 2015
3 Output Design From 04 Nov 2015 - 13 Nov 2015
4 Documentation From 15 Nov 2015 - 30 Nov 2015

8
9
Chapter 4: System Requirement Specification

a. SYSTEM REQUIRIMENTS ANALYSIS:

The existing system work manually. The existing system has got lot of complexity within
itself and need lot of human effort and cost. All above the data need to be maintained
on different places and maintaining this is a tedious and risky process. So the task of
maintaining them increases exponentially.

To provide flexibility to the users, the interfaces have been developed that are
accessible through a browser. The GUIS at the top level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper authentication
for the data collection. These interfaces help the administrators with all the transactional
states like Data insertion, Data deletion and Date updating along with the extensive data
search capabilities.

The operational or generic user interface helps the end users of the system in
transactions through the existing data and required services. The operational user
interface also helps the ordinary users in managing their own information in a
customized manner as per the included flexibilities

HARDWARE REQUIREMENTS SPECIFICATION:

Pentium-IV with dual processor

RAM 2GB and above

HDD 80 GB Hard Disk Space and Above with SCSI Controller

Keyboard ,Mouse, Monitor

10
SOFTWARE REQUIREMENTS SPECIFICATION:

WINDOWS 2000 OS or above

ASP .Net (VB.NET Script)
MS SQL
IIS server Internet Explorer as browser software.
ANTI VIRUS

Why use ASP.NET and MS SQL?

In ASP.NET, since we can develop the applications using C#, we can create simple
classes of the data and then work with the data using those classes inside our
application without having to worry about any side-code.

ADO.NET is a part of ASP.NET (.NET Framework) that lets us work with data. We are
familiar with LINQ, that enables us to work with data, slicing and dicing of the data is a
great plug point in ASP.NET.

Whereas we can still do that in PHP, wel require to write the code yourself. We can
include third-party plugins to lessen the pain of code, but in ASP.NET we get all these
features built-in directly on the .NET Framework.

ASP.NET itself is a basic implementation of the .NET Framework over the Internet
services and the websites. We can create as much projects as we want, and run on the
same server. Almost all of the major companies are running on ASP.NET because it
lets you gain control of it yourself.

C# and other .NET languages let us create your own modules, use some library tools
from MSDN (Microsoft Developer Network) and create our own web applications.
ASP.NET is vast enough for us to develop any sort of application, and we don't even
have to worry about the platform, thanks to the Mono Project, you can now write the

11
ASP.NET applications on the non-Windows OS too. Before Mono Project, PHP was the
multi-platform language, but now, ASP.NET too is a multi-platform language.

Security Features

ASP.NET is more secure than PHP, PHP is more secure than ASP.NET!

ASP.NET has a security namespace that defines all the methods that a company can
use to protect its system. You can create Roles, use Membership class, etc.

SQL Server is a Microsoft product used to manage and store information. Technically,
SQL Server is a relational database management system (RDMS). Broken apart, this
term means two things. First, that data stored inside SQL Server will be housed in a
relational database, and second, that SQL Server is an entire management system,
not just a database. SQL itself stands for Structured Query Language. This is the
language used to manage and administer the database server.

The second term in our SQL Server definition is Management System. This means
that SQL Server is more than just an application to hold data; it also includes the tools
needed to structure, manipulate, and manage that data. In addition, when we can install
SQL Server, there are options for including Report Writing tools, Data Import Export
applications, Analysis tools, and Management Interfaces.

12
Chapter 5: System Design

SYSTEM DESIGN

Systems design is the process of defining the architecture, components, modules,

interfaces, and data for a system to satisfy specified requirements. Design is the first
step in the development phase for any engineered product or system. The designers
goal is to produce a model or representation of an entity that will later be built.
Beginning, once system requirement have been specified and analyzed, system design
is the first of the three technical activities -design, code and test that is required to build
and verify software.

The importance can be stated with a single word Quality. Design is the place
where quality is fostered in software development. Design provides us with
representations of software that can assess for quality. Design is the only way that we
can accurately translate a customers view into a finished software product or system.
Software design serves as a foundation for all the software engineering steps that
follow. Without a strong design we risk building an unstable system one that will be
difficult to test, one whose quality cannot be assessed until the last stage.

During design, progressive refinement of data structure, program structure, and

procedural details are developed reviewed and documented. System design can be
viewed from either technical or project management perspective. From the technical
point of view, design is comprised of four activities architectural design, data structure
design, interface design and procedural design.

a. APPLICATION ARCHITECTURE DESIGN:

System design provides the understandings and procedural details necessary for
implementing the system recommended in the system study. Emphasis is on the
translating the performance requirements into design specifications. The design phase

13
is a transition from a user-oriented document (System proposal) to a document oriented
to the programmers or database personnel.

System design goes through two phases of development:

1) Logical Design

2) Physical Design

A data flow diagram shows the logical flow of the system. For a system it describes
the input (source), output (destination), database (data stores) and procedures (data
flows) all in a format that meets the users requirement. When analysis prepares the
logical system design, they specify the user needs at a level of detail that virtually
determines the information flow into an out of the system and the required data
resources. The logical design also specifies input forms and screen layouts.
The activities following logical design are the procedure followed in the physical
design e.g., producing programs, software, file and a working system. Design
specifications instruct the user about what the system should do.
1) Logical Design: The process of logical design involves arranging data into a
series of logical relationships called entities and attributes. An entity represents
a chunk of information. In relational databases, an entity often maps to a table.
An attribute is a component of an entity and helps define the uniqueness of the
entity.

2) Physical Design: The physical design is a graphical representation of a system

showing the systems internal and external entities, and the flows of data into and
out of these entities. An internal entity is an entity (person, place, or thing) within
the system that transforms data. Internal entities include, for example, accounting
clerks (persons), departments (places), and computers (things). Whereas, an
external entity is an entity (person, place, or thing) outside the system that
transforms data .Actually, the physical design relates to the actual input and
output processes of the system. This is laid down in terms of how data is given
as an input into a system, how it is authenticated, how it is processed, and how it

14
 is displayed as output. Put another way, the physical portion of systems design
can generally be broken down into three sub-tasks

SOFTWARE DESIGN

Software design is the process of implementing software solutions to one or more set
of problems.

a) System Design

It aims to identify the modules that should be in the system, the specification of these
modules and how they interact with each other to produce the desired result.

b) Detailed Design

The internal goal of each of the modules specified in the system design is decided

Implementation Technologies

The objective of this project is to develop an Online Examination System. When the
user types in the URL (ex:http://www.jazanun.com) in the address field of the browser
will route to a Web Server of the university. In the .NET Framework, IIS (Internet

15
Information Service) acts as the Web Server. The sole task of the Web Server is to
accept the incoming HTTP requests and to return the requested resource in an HTTP
response. The first thing IIS does when a request comes in is to decide how to handle
the request. Its decision is based upon the requested file's extension. For example, if
the requested file has the .asp extension, IIS will route the request to be handled by
asp.dll. If it has the extens ion of .aspx, .ascx, etc, it will route the request to be handled
by ASP.NET Engine.

The ASP.NET Engine then gets the requested file, and if necessary contacts the

database through ADO.NET for the required file and then the information is sent back to

the Clients browser.

Identification of Modules

The major Classes which we will be using are:

1. Admin.
2. Teacher.
3. Student.

16
 High Level Case Diagram

Data Input / Output

User Input Output

Admin - input his user ID and password to login - show the data of the users.
the system. - view existing user
- Add many Users.

Teacher -input his user ID and password to login - View Exam Data bank

17
 the system. -View Student result

- Create Exam

Student -input his user ID and password to login - view Quiz

the system.- - view result

- Write Exam

Use Case Diagram

A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the different use cases in
which the user is involved. A use case diagram can identify the different types of users
of a system and the different use cases and will often be accompanied by other types of
diagrams as well.

ADMIN User: User is a person who enters the site for the first time to make his
registration and create account. User actor can do the following:

Create account.
Login.
Get forgotten password.
Add/ Modify/ Remove/ Select

18
Use of Simple Diagram

19
Simple Diagram

20
Admin Page

21
ADMIN Login

22
ADMIN: Add User

23
ADMIN: Delete User

24
ADMIN: Edit User

25
Teacher Logon:

26
Teacher Create Exam:

27
Teacher Update Exam:

28
Student: Login

29
Student: Do Quiz

30
System Architecture Diagram

31
Description of Architectural Design

System architecture reflects the important strategic design decisions which is

sufficient to form that system.
A stable architecture is important to every successful system for two reasons.
First, the creation of a stable architecture which helps to drive the highest risks
out of the project.
Second, the presence of a stable architecture will provide the basis of system
which may be continuously evolved with minimal scrap and rework.
In web application development, three-tier architecture refers to separating the
application process into three specific layers.
It improves performance and scalability

Data Base Design:

Database design is the process of producing a detailed data model of a database.
This data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a data definition language,
which can then be used to create a database.

32
System Logical Design

33
Logical Design Exam Management Sub System

34
Data Flow Model

It Captures the flow of data in a system.

It helps in developing and understanding of systems functionality.
It depicts the different sources of data, and different transformations that take
place on data and what the final outputs generated by these transformations.
It also describes data origination, transformations and consumption in a system.
Information is organized and disseminated at different levels of abstraction. Thus
this technique becomes a conduit for top down system analysis and
requirements modeling.

The Notation

Following for notion are being used:

Process
Different processes or work to be done in the system.

Transforms of data.

External Agent
External systems which are outside the boundary of this system, these are represented
using the squares

35
Data Store
Where data is being stored for later retrieval.
It Provides input to the process
Outputs of the processes may be going into these data stores.

Data Store

Data Flow
Where the data is flowing.
Represents the movement of the data in a data flow diagram.

36
Level 0-DFD

Level-1 DFD

37
Level 2-DFD

38
ER Diagram

An ERD is a data modeling technique that can help define business processes and can
be used as the foundation for a relational database.

Notion used in ER Diagram

Rectangles entity sets
Ellipses attributes
Diamonds relationship sets
Double ellipses multi valued attributes
Dashed ellipses derived attributes
Double lines total participation
Double rectangles weak entity sets
Double diamonds identifying relationship sets

Admin ER Diagram:

39
Teacher ER Diagram:

Student ER Diagram:

40
Exam ER Diagram:

41
All System ER Diagram:

Data Dictionary:-

A data dictionary is a collection of descriptions of the data objects or items in a

data model for the benefit of programmers and others who need to refer to them. A first
step in analyzing a system of objects with which users interact is to identify each object
and its relationship to other objects.

Database Tables :

TABLE DISCRIPTION

42
 admin Contains the information about the admin.

Teacher Contains the information about the teacher.

Student Contains information student

Exam Contains information of Exam

Question Contains information of Question

Answer Contains information of answer

admin table

Column Name Data Type Size Extra

ID Integer-int 6 Primary Key and Auto

Increments

Password Text-nvarchar 250 Not Null

Teacher Detail table

Column Name Data Type Size Extra

ID Integer-int 6 Primary Key and Auto

Increments

Name Text-nvarchar 250 Not Null

Password Text-nvarchar 15 Not Null

Exam Integer-int 6 Foreign key of Exam

43
Student Table

Column Name Data Type Size Extra

ID Integer-int 6 Primary Key and Auto

Increments

Name Text-nvarchar 250 Not Null

Password Text-nvarchar 15 Not Null

Exam Integer-int 6 Foreign key of Exam

Mark double 3 Not Null

Quiz Detail table

Column Name Data Type Size Extra

ID Integer-int 6 Primary Key and Auto

Increments

Question integer 6 Foreign key of Exam

Answers integer 6 Foreign key of Exam

Question Detail table

Column Name Data Type Size Extra

Question Integer-int 6 Not Null

44
 Qid Text-nvarchar 250 Primary Key

Answers Detail table

Column Name Data Type Size Extra

Answers Text-nvarchar 250 Not Null

Qid Integer-int 6 Foreign key of Question

anID Integer-int 6 Primary Key and Auto

Increments

Answers_ Mark Detail table

Column Name Data Type Size Extra

anID Integer-int 6 Foreign key of

Answer_mark

Mark Integer-int 6 Foreign key of Question

User Interface
This is by means by which the user and a computer system interact, in particular the
use of input devices and software.

Rules considered For designing the interface:

1. Place the user in control

2. Reduce the users memory load

45
3. Make the interface consistent

Place the User in Control

Interaction modes in a way that does not force a user into unnecessary or undesired
actions.
Provide for flexible interaction. Because different users have different interaction
preferences, choices should be given to provide by using keyboard commands,
mouse movements, digitizer pen or voice recognition commands.
Allow user interaction to be interruptible and undoable. A user should be able to
interrupt a sequence of actions to do something else without losing the work that has
been done. The user should always be able to undo any action.
Streamline interaction as skill levels advance and allow the interaction to be
customized. Allow to design a macro if the user is to perform the same sequence of
actions repeatedly.
Hide technical internals from the casual user. The user interface was should move
the user into the virtual world of the application. A user should never be required to
type O/S commands from within application software.
Design for direct interaction with objects that appear on the screen. The user feels a
sense of control when able to manipulate the objects that are necessary to perform a
task in a manner similar to what would occur if the object were a physical thing.

Reduce the Users Memory Load

Reduce demand on short-term memory. Provide visual cues that enable a user to
recognize past actions, rather than having to recall them.
Establish meaningful defaults. A user should be able to specify individual
preferences; however, a reset option should be available to enable the redefinition of
original default values.

46
 Define shortcuts that are intuitive. Example: Alt-P to print. Using easy to remember
mnemonics.
The visual layout of the interface should be based on a real world metaphor. Enable
the user to rely on well-understood visual cues, rather than remembering an arcane
interaction sequence. For a bill payment system use a check book and check
register metaphor to guide the user through the process.
Disclose information in a progressive fashion. The interface should be organized
hierarchically. The information should be presented at a high level of abstraction.

Make the Interface Consistent

The interface should present and acquire information in a consistent manner:

1. All visual information is organized according to a design standard that is

maintained throughout all screen displays,
2. Input mechanisms are constrained to a limited set that is used consistently
throughout the application,
3. Mechanisms for navigating from task to task are consistently defined and
implemented.

47
Home Page

48
Admin Page

49
Admin New Teacher Page:

50
Admin New Student

51
Admin edit Student

Teacher Page

52
Teacher New Exam

53
Teacher Edit Exam

54
Student Page

55
Exam Page

56
Student Page View Result

57
College Management Page:

58
59
Chapter 6: System Implementation
Systems implementation is the construction of the new system and the delivery of that
system into production (that is, the day-to-day business or organization operation).

The project team must construct the database, application programs, user and system
interfaces, and networks. Some of these elements may already exist in your project or
be subject to enhancement.

The systems implementation phase began with the application development in which
programs, code modules, and system functions were developed and tested.

At this point, the system is ready to go to work. The remaining tasks are to:

Prepare an operational environment,

Provide training,
Perform file conversion and changeover,
Install the new system,
Carry out a post-implementation evaluation, and
Present a final report to management.

The system can be implemented only after thorough testing is done and if it is found to
work according to the specification.

It involves careful planning, investigation of the current system and its

constraints on implementation, design of methods to achieve the change over
and an evaluation of change over methods a part from planning. Two major tasks
of preparing the implementation are education and training of the users and
testing of the system.

The more complex the system being implemented, the more involved will be the
systems analysis and design effort required just for implementation.

60
 The implementation phase comprises of several activities. The required hardware
and software acquisition is carried out. The system may require some software to be
developed. For this, programs are written and tested. The user then changes over to
his new fully tested system and the old system is discontinued.

TESTING:

The testing phase is an important part of software development. It is the

computerized system will help in automate process of finding errors and missing
operations and also a complete verification to determine whether the objectives are met
and the user requirements are satisfied.

System testing is carried out in three steps:

1. The first includes unit testing, where in each module is tested to

provide its correctness, validity and also determine any missing operations and to
verify whether the objectives have been met. Errors are noted down and
corrected immediately. Unit testing is the important and major part of the project.
So errors are rectified easily in particular module and program clarity is
increased. In this project entire system is divided into several modules and is
developed individually. So unit testing is conducted to individual modules.

2. The second step includes Integration testing. It need not be the case,
the software whose modules when run individually and showing perfect results, will also
show perfect results when run as a whole. The individual modules are clipped under this
major module and tested again and verified the results. This is due to poor interfacing,
which may results in data being lost across an interface. A module can have
inadvertent, adverse effect on any other or on the global data structures, causing
serious problems.

3. The final step involves validation and testing which determines which
the software functions as the user expected. Here also some modifications were. In the
completion of the project it is satisfied fully by the end user.

61
Maintenance:

AS the number of computer based systems, grieve libraries of computer software began
to expand. In house developed projects produced tones of thousand soft program
source statements. Software products purchased from the outside added hundreds of
thousands of new statements. A dark cloud appeared on the horizon. All of these
programs, all of those source statements-had to be corrected when false were detected,
modified as user requirements changed, or adapted to new hardware that was
purchased. These activities were collectively called software Maintenance.

The maintenance phase focuses on change that is associated with error correction,
adaptations required as the software's environment evolves, and changes due to
enhancements brought about by changing customer requirements. Four types of
changes are encountered during the maintenance phase.

62
 References

Books:
1. Software Engineering -K.K. Aggarwal and Yogesh Singh
2. Web Enabled Commercial Appplication Development -Ivan Bayross
3. Head First Servlets and JSP -Bryan Basham,Kathy Sierra and Bert Bates

Journals:

Gemino, A., Parker, D.(2009) "Use case diagrams in support of use case modeling:
Deriving understanding from the picture",Journal of Database Management, 20(1),
1-24.
Jacobson, I., Christerson M., Jonsson P., vergaard G., (1992). Object-Oriented
Software Engineering - A Use Case Driven Approach, Addison-Wesley.
Kawabata, R., Kasah, K. (2007). "Systems Analysis for Collaborative System by Use
Case Diagram", Journal of Integrated Design & Process Science, 11(1), 13-27.

Online Links:

http://www.codeproject.com/Tips/816904/Why-Use-ASP-NET-for-Web-Development

http://www.databasejournal.com/features/mssql/article.php/3769211/What-is-SQL-
Server.htm

63