G 222

INTRODUCTION
On-line examinations contents providers to focus on

creating effective assessment questions and focusing on
exam’s feedback delivery to students. In the paper we
present techniques that are pertinent to the elements of
assessment process: answers submission, computerized
grading, and feedback after submission. The
administrators, instructor (examiner) and Students who
are attending for online examination can communicate
with the system
1
STATEMENT OF THE PROBLEM
 We recognized that there are many problems in terms of

examination giving process with required quality in the
university. Generally, we have noticed the following problems.
 There is high cost to buy copy machines, printers, papers for
hard copy as well as payment for duplicators and invigilators.
 High human power wastage.
 Wastage of time to print and to wait for copying in duplicate
office.
2
 It is wastage of time for instructors while correcting
exam papers and giving result back.
 Some pages of exam paper may be jumped by error
while duplicating.
 The result of students may be lost.
3
OBJECTIVE OF THE PROJECT
General Objectives of the Project

The general objectives of this project are to develop and
implement a web-based examination system for WSUOES
Sodo University.
4
SPECIFIC OBJECTIVES OF THE PROJECT
The specific objective of the Online Examination System is:-
 To enable admin create account to student, exam commitie,
instructor.
 To enable student to check the Result.
 To design and implement a database for the proposed system.
 To design and implement exam preparation module for the

proposed system.
 To develop the system that stores the student result in the
database and displays the result back to the students.
 To test and evaluate the performance of the proposed system
by inserting different data.
5
SIGNIFICANCE OF PROJECT
 To make the process time and cost effective and

efficient.
Time minimizing
Cost (resource) minimizing
 To enable student to use their time properly while taking
exam (timer will start automatically and show the
student how much time is left).
 To solve problems of students forgetting to write their 6
name and ID on the exam paper.

SCOPE OF THE PROJECT
The scopes of the project are the following:

 OES (Online Examination System) will be developed for WSUOES
Sodo University.
 The system handles all the operations, and generates reports as soon as
the test is finish, that includes name, mark, time spent to solve the exam.
 It can be used to solve many problems occurred in the university on
examination giving process.
 It can enable instructors to easily prepare exam papers and see the result
of students.
 It enables students to take exam properly and get fair correction and
result. 7
THE LIMITATIONS OF THE PROJECT
The Limitations of the project are the following:

 Only multiple choice, matching and true/false type of
questions are automated, subjective questions are checked
manually.
 If the time is finished student cannot read the questions again
and the answer is automatically submitted and the result is
displayed with the correct answer.
8
METHODOLOGY
1) Interview
The data gathering system in this project proposal is
interview method. That means by asking the manager or
the department head of the office.
2) Observation
Group members observe the work office of different
department, the examination style during exam and
identify its problem for our projects.
9
HARDWARE AND SOFTWARE REQUIREMENTS
 PHP to develop user interface prototypes (back end).

 My SQL to make the back end (database part)
 Microsoft Office Visio 2003 for UML Diagram
 Microsoft Office 2007 for documentation writing
One server computer with :-
 500MB of RAM,
 Flash disc 1-16 GB
 Two or more client computers 10
FEASIBILITY OF THE PROJECT
Economic feasibility: The newly being developed system will

improves the examination speed, and saves resources.
Technical feasibility: The proposed system is technically

feasible. Because it can generate outputs in a given time,
response time is minimum, easy to communicate and generally
it satisfies the end-user’s requirement.
Operational feasibility: The proposed system OES is

operationally feasible because it is simple to access and all
11
operations will be performed easily.
DESCRIPTION OF THE CURRENT SYSTEMS
The whole process of assigning exam and evaluating

scores of students after the exam, in the University was
done manually till date. Processing the exam paper i.e.
checking and distributing respective scores is used, and it
is time consuming and loose of effort.
12
PLAYERS IN THE EXISTING SYSTEM
 Instructor
 Student
 Department head
 Exam committees
13
FUNCTIONAL REQUIREMENTS
The user requirement for this system is to make the system

fast, flexible, less prone to error, reduce expenses and save
the time. Using the online examination system the
following functional requirements are performed by each
actors of the system.
 The system administrator should be able to manage

account of users,, departments, courses and exams by
logging into the system.
14
 Instructors should be able to manage questions by logging in
to the system by selecting department and courses.
 The Exam committees should be able to check the exam
prepared by instructors and approve the exam.
 The student should be able to view his/her own result that
displayed by system. The System should be able to show the
schedule of the exam before the exam time.
15
NON FUNCTIONAL REQUIREMENT
 Performance: The system is very fast since it is

automated.
 Error Handling: The system should display error
message if the user input invalid information.
 Security: Authenticated user with predefined access right
will only enter to the information related to database.
 Availability: The server should be always on to be
available.
 User-Friendly: The Online Examination System has a
very user-friendly interface. Thus the users will feel 16
happy since it is easy to work on it.

USE CASE DIAGRAM
Use Case Diagram represents user requirements gathered during

requirement elicitation, contains use case, actors, system
boundary and their relationships.
17
DIAGRAM OF USE CASE OF OES
18
SEQUENCE DIAGRAM
Sequence diagrams show a succession of interactions between
classes or object instances over time.
19
ACTIVITY DIAGRAM
Activity diagram used to emphasize the flow of control from

activity to activity or to model the flow of an object as it moves
from state at different points in the flow of control.
20
DESIGN MODELING CLASS DIAGRAM
 In object oriented system Analysis, Real world concepts

are modeled into objects.
 A class is a set of objects that share a common structure
and a common behavior (the same attributes, operations,
relationships).A class is an abstraction of real world
items.
21
22
ARCHITECTURE OF THE SYSTEM
It displays data to the user. The client layer interacts with the
web/application Server to make requests and to retrieve data
from the database. It then displays to the user the Data retrieved
from the server.
23
COMPONENT DIAGRAM
The component diagram illustrates the software components to
build the system. Describes how a software system is split-up
into components and shows the dependencies among these
components.
24
DEPLOYMENT DIAGRAM
 UML deployment diagram show physical view of system,
taking software into real world by showing how software gets
assigned to hardware and how communicates.
25
PERSISTENCE MODELING
 Persistence of our object can be achieved by relational
database since it used as machine to make object persistent. It
describes the persistent data aspect of software system.
26
PART 2
 System design and User interfaces
 User interface design is the specification of the interaction between the
system users and a system. The process involves input mechanism design,
output mechanism design, and navigation mechanism.
27
DATABASE DESIGN
 Database design is the process of producing a detailed data model of a
database. This logical 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. A fully attributed data model contains detailed
attributes for each entity.
28
ACCOUNT TABLE
29
FEEDBACK TABLE
30
USER INTERFACES
User interface design is the specification of the interaction between

the system users and a system.
 Navigation mechanism is part of user interface that takes the
user form one part of the system to the other user system.
 Input design is about designing a form and its controls for
GUI system.
 Output design is about designing reports like detailed,
summarized,and etc.
31
HOME PAGE FOR ONLINE EXAM
32
HOME PAGE FOR ADMIN
33
HOME PAGE FOR INSTRUCTOR
34
TESTING USER INTERFACE
 Testing is the process of finding the difference between expected
behaviors specified by the system model and observed behavior of
the implemented system.
 Login to the System Testing (Null value)
35
LOGIN TO THE SYSTEM TESTING (INCORRECT USER NAME
OR PASSWORD)
36
ERROR MESSAGE WHEN TO BE ENTERED TO THE SYSTEM IS
NOT FILLED
37
ADMIN ADD USER TO THE SYSTEM (CORRECT VALUE)
38
The end
39

G 222

Uploaded by

Copyright:

Available Formats

G 222

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

G 222

Uploaded by

Copyright:

Available Formats

INTRODUCTION

On-line examinations contents providers to focus on

 We recognized that there are many problems in terms of

General Objectives of the Project

 To design and implement a database for the proposed system.

 To design and implement exam preparation module for the

 To make the process time and cost effective and

name and ID on the exam paper.

The scopes of the project are the following:

The Limitations of the project are the following:

 PHP to develop user interface prototypes (back end).

Economic feasibility: The newly being developed system will

Technical feasibility: The proposed system is technically

Operational feasibility: The proposed system OES is

The whole process of assigning exam and evaluating

The user requirement for this system is to make the system

 The system administrator should be able to manage

 Performance: The system is very fast since it is

happy since it is easy to work on it.

Use Case Diagram represents user requirements gathered during

Activity diagram used to emphasize the flow of control from

 In object oriented system Analysis, Real world concepts

User interface design is the specification of the interaction between

You might also like