Web Based Graduate Exit Examination System

Web Based Graduate Exit Examination System For
Ethiopian Higher Education and Institutes

PROJECT REPORT
Submitted By
Name ID
1. Memar Alemayehu---------------------TER/4677/07
2. Muluye Fentie---------------------------TER/4682/07
3. Nardos Enawgaw-----------------------TER/1495/08
4. Yitayal Mengiste------------------------TER/4700/07
IN PARTIAL FULFILMENT FOR THE AWARD OF THE DEGREE OF

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY
Under the guidance of
Lijalem Migbaru (MSC)
…………………….
SIGNATURE
DEPARTMENT OF INFORMATION TECHNOLOGY

INSTITUTE OF TECHNOLOGY
DEBRE MARKOS UNIVERSITY
DEBRE MARKOS, ETHIOPIA
January 2010 E.C
Web Based Graduate Exit Examination System
Abstract
Graduate exit examination is an examination, which is provided to graduate
students for the aims of determining the progress the student has made over the
years. The exam is taken by department in an international level and its content
covers the whole courses in the department .so WBEES is the proposed system and
this system solve the problem in the existing system. The system is a web-based
application and allows administrator users to add questions, view students’ results
and other functionalities. It also provides web-based exam to students and
automatically show their exam results. So that it will handle the overall
examination processes, from starting the exam up to showing final result.
i|Page
Acknowledgment
First of all we would to thank GOD for giving us strength to complete this
documentation. Because of without the will of GOD everything is impossible.
Then we would like to great thank our adviser Lijalem Migbaru that give important
information to us and provide excellence advice and supervision. Next we would to
thanks organizations which are provide services in Debre Markos University such
as school of law and health medical college for providing necessary information
and guidance about the system. Next our thanks extend to information technology
department head for providing support papers in order to do this project. Finally
thanks all classmate students, our family and all IT department staff members that
support to complete this documentation.
ii | P a g e
Acronyms and Abbreviations

 PHP: -Hyper Preprocessor Scripting Language
 HTML:-Hypertext Markup Language
 CSS:-Cascading Style Sheet
 MYSQL:- Structured Query Language
 JS:-Java Script
 UML:- Unified Modeling Language
 UI:-User Interface
 UC:-Use Case
 WAMP:- Windows Apache MySQL PHP
 WBEES:-Web Based Exit Examination System
 Info:-Information
 BR:-Business Rule
 IT:-Information Technology
 GUI:-Graphical User Interface
iii | P a g e
Table of Contents
Abstract .......................................................................................................................................................... i
Acknowledgment .......................................................................................................................................... ii
Acronyms and Abbreviations ...................................................................................................................... iii
Table of Contents ......................................................................................................................................... iv
List of figure ............................................................................................................................................... vii
List of table ................................................................................................................................................ viii
CHAPTER ONE ........................................................................................................................................... 1
1.1 Introduction ............................................................................................................................................. 1
1.2 Background of the Project ...................................................................................................................... 1
1.3 Problem Statement .................................................................................................................................. 2
1.4 Objective of the Project .......................................................................................................................... 3
1.4.1 General Objective ................................................................................................................................ 3
1.4.2 Specific Objective ................................................................................................................................ 3
1.5 Scope of the Project ................................................................................................................................ 4
1.6 Limitation of the Project ......................................................................................................................... 4
1.7 Significance of the Project ...................................................................................................................... 4
1.8 System Requirements.............................................................................................................................. 5
1.8.1 Hardware Requirement .................................................................................................................... 5
1.8.2 Software Requirement...................................................................................................................... 5
1.8.3 Programming Language ................................................................................................................... 6
1.9 Methodology ........................................................................................................................................... 7
1.9.1 Data Collection Approaches ............................................................................................................ 7
1.9.2 The System Analysis and Design Approaches................................................................................. 8
1.9.3 The System Development Model ..................................................................................................... 8
1.10 Feasibility Study ................................................................................................................................... 8
1.10.1 Technical Feasibility ...................................................................................................................... 9
1.10.2 Economical Feasibility................................................................................................................... 9
1.10.3 Operational Feasibility ................................................................................................................... 9
1.10.4 Legal Feasibility............................................................................................................................. 9
CHAPTER TWO ........................................................................................................................................ 10
2. SYSTEM ANALYSIS ............................................................................................................................ 10
iv | P a g e
2.1 Overview of the Existing System.......................................................................................................... 10

2.2 System Requirement Specification ....................................................................................................... 11
2.2.1 Functional Requirements ............................................................................................................... 11
2.2.2 Non Functional Requirements ....................................................................................................... 12
2.2.2.1 Technical Requirement ........................................................................................................... 13
2.2.3 Business Rules ............................................................................................................................... 13
2.3 System Requirement Analysis .............................................................................................................. 14
2.3.1 Actor and Use Case Identification ................................................................................................. 14
2.3.1.1 Use case diagram ...................................................................................................................... 2
2.3.1.2 Use Case Description ................................................................................................................ 3
2.3.2 Sequence Diagram ............................................................................................................................. 10
2.3.3 Activity Diagram ........................................................................................................................ 16
2.3.4 Analysis Class Diagram ..................................................................................................................... 19
CHAPTER THREE .................................................................................................................................... 20
3. SYSTEM DESIGN ............................................................................................................................. 20
3.1 Introduction ........................................................................................................................................... 20
3.2 Design Class Diagram........................................................................................................................... 20
3.2.1 Design Class Diagram Description ................................................................................................ 22
3.3 Database Design /Physical Data Model ................................................................................................ 22
3.4 User Interface Design...................................................................................................................... 27
3.5 System Architecture ........................................................................................................................ 34
3.3.1 Component Diagram ...................................................................................................................... 34
3.3.2 Deployment Diagram ..................................................................................................................... 35
Chapter Four ............................................................................................................................................... 37
4.1 Introduction ........................................................................................................................................... 37
4.2 Overview of the programming language used ................................................................................ 37
4.3 Algorithms Used ................................................................................................................................... 38
4.4 Sample Codes........................................................................................................................................ 38
Chapter Five ................................................................................................................................................ 50
5. Testing .................................................................................................................................................... 50
5.1 Introduction ........................................................................................................................................... 50
5.2 Sample Test........................................................................................................................................... 50
v|Page
Chapter six .................................................................................................................................................. 53

6. Conclusion and Recommendations ......................................................................................................... 53
6.1 Conclusion ...................................................................................................................................... 53
6.2 Recommendation ............................................................................................................................ 54
6.3 Future Enhancement ............................................................................................................................. 54
References ................................................................................................................................................... 55
vi | P a g e
List of figure
FIGURE 1: USE CASE DIAGRAM .............................................................................................................................................3

FIGURE 2: SEQUENCE DIAGRAM FOR LOGIN............................................................................................................................11
FIGURE 3: SEQUENCE DIAGRAM FOR TAKE EXAM ....................................................................................................................12
FIGURE 4: SEQUENCE DIAGRAM FOR VIEW RESULT..................................................................................................................13
FIGURE 5: SEQUENCE DIAGRAM FOR VIEW REPORT .................................................................................................................14
FIGURE 6: SEQUENCE DIAGRAM FOR FEEDBACK ......................................................................................................................15
FIGURE 7: ACTIVITY DIAGRAM FOR LOGIN ..............................................................................................................................16
FIGURE 8: ACTIVITY DIAGRAM FOR TAKE EXAM .......................................................................................................................17
FIGURE 9: ACTIVITY DIAGRAM FOR VIEW RESULT .....................................................................................................................18
FIGURE 10: ACTIVITY DIAGRAM FOR FEEDBACK .......................................................................................................................18
FIGURE 11: ANALYSIS CLASS DIAGRAM .................................................................................................................................19
FIGURE 12: DESIGN CLASS DIAGRAM ....................................................................................................................................21
FIGURE 13: GRAPHICAL USER INTERFACE FOR HOME PAGE .......................................................................................................28
FIGURE 14: GRAPHICAL USER INTERFACE ADMIN PAGE ............................................................................................................29
FIGURE 15: EXAM EDITOR PAGE ..........................................................................................................................................30
FIGURE 16: SET EXAM QUESTION PAGE.................................................................................................................................31
FIGURE 17: CANDIDATE PAGE .............................................................................................................................................32
FIGURE 18: EXAM TAKEN PAGE ..........................................................................................................................................33
FIGURE 19:COMPONENT OF THE SYSTEM ..............................................................................................................................34
FIGURE 20:COMPONENT DIAGRAM .....................................................................................................................................34
FIGURE 21: DEPLOYMENT DIAGRAM ....................................................................................................................................36
FIGURE 22: SAMPLE SECURITY TESTING ................................................................................................................................52
vii | P a g e
List of table
TABLE 1: USE CASE IDENTIFICATION .......................................................................................................................................1
TABLE 2: USE CASE DESCRIPTION FOR LOGIN ...........................................................................................................................4
TABLE 3: USE CASE DESCRIPTION FOR TAKE EXAM ....................................................................................................................5
TABLE 4: USE CASE DESCRIPTION FOR VIEW RESULT .................................................................................................................6
TABLE 5: USE CASE DESCRIPTION FOR SEND COMMENT .............................................................................................................7
TABLE 6: USE CASE DESCRIPTION FOR VIEW COMMENT .............................................................................................................8
TABLE 7: USE CASE DESCRIPTION FOR VIEW REPORT .................................................................................................................9
TABLE 8: USE CASE DESCRIPTION FOR CREATE ACCOUNT FOR CANDIDATE....................................................................................10
TABLE 9: DESIGN CLASS DESCRIPTION FOR ADMIN CLASS .........................................................................................................22
TABLE 10: DESIGN CLASS DESCRIPTION FOR RESULT ..............................................................................................................22
TABLE 11: RESULT TABLE ...................................................................................................................................................23
TABLE 12: FEEDBACK TABLE ...............................................................................................................................................23
TABLE 13: QUESTION TABLE ...............................................................................................................................................24
TABLE 14 :NOTICE TABLE ...................................................................................................................................................24
TABLE 15: TIMER TABLE.....................................................................................................................................................25
TABLE 16: EXAM DATE TABLE..............................................................................................................................................26
TABLE 17: ACCOUNT TABLE ................................................................................................................................................26
TABLE 18: USER TABLE ......................................................................................................................................................27
viii | P a g e
CHAPTER ONE
1. INTRODUCTION
1.1 Introduction
A web-based system provides access to a software system using a computer and internet
connection. Web based graduates exit examination system is one of the systems which provide
web based test exam services through internet connection or network and it is control by
Centralized administrator. The system also helpful for conducting different examination question
which can be conducted regularly. It can also be used for provide immediate results and save
precious time of to check student’s copy and prepare mark sheets, so it is very important for that
graduates students to handle the web based examinations system and evaluate their results
online. But the purpose The exam is to facilitate the effort of student to revise the core of
learning outcome of the course covered also make ensure the student to be competent and
monitor the level of achievement in learning outcomes of course.so the system solve the
problem which are occur during exam time taken through manual system. Therefore the
document describes all features and procedures to develop graduate exit examination system for
Ethiopia higher education institute graduate students. Because of it is very useful for any
Institute or Department to test their students continuously for their mutual development and
know about their progress. The system allows exam agency to create their own exam on online.
It would enable the institutes to perform exit exam.
1.2 Background of the Project
Today many organizations are conducting web based examinations system in worldwide
successfully and issue results online. Web based exit examination system is the system that
examinations is conducted through the extranet or in an intranet (if within the Organization) for a
remote candidate(s). Most of the examinations issue results as the candidate finish the
examination, when there is an answer processing module also included within the system.
Candidate is given a limited time to answer the questions and after the time expiry the answer
1|Page
place is disabled automatically and answers is sent to the database. Because all question and
answer is placed in the database of the system. Therefore the system will evaluate answers,
through automated process and the results will be sent to the candidate through candidate identity
on candidate pages in the available in the web site. But up to this time the examination process is
given by through manual process. That means every student takes an exam in a classroom,
because they are to sit there and have the examiners during the exam. This web based
Examination System is to efficiently evaluate the exam through a fully automated system that not
only saves lot of time but also give fast results. It will solve all the paper works in the
examination process usually spent by the teacher or instructor in reading and checking the
answer one after the other. The college or institute which provide exit exam through manually
process in Ethiopian higher education institute are school of law and medical health college
started around in 2003 E.C. but but in next year will be started in all college and schools in 2011
E,C so this project will start ,any graduate student take exit exam before it graduate.
1.3 Problem Statement

In higher education institute examination process performs by examiners that give the exam
papers to students manually. Therefore we recognized that there are many problems in terms of
examination giving process in higher education institute or university. Some of the problems are
which are occur in the exam process through manual system are:
 There is high cost to buy copy machines, printers, papers for hard copy as well as payment
for duplicators and supervisors.
 High human power wastage that means it needs examiners, Supervisor and others that
participate in the examination place.
 Wastage of time to print and to wait for copying in duplicate office.
 It is wastage of time for examiners while correcting exam papers and giving result back to
the student.
 Some pages of exam paper may be jumped by error while duplicating.
 The result of students may be lost.
 Takes time to test the exam, to evaluate the answer or exam, to announce the exam date to
the candidate.
2|Page
 Even candidates or students may lose where and when the exam is performed.
 It is difficult to show the result of students
 The exam may be stolen during posted to exam place.
 It is difficult to keep exam information consistency ,update and generality
 The consistency or generality of the exam process may be different from one institute to other.
 The candidate cannot see the result immediately after taken exam.
1.4 Objective of the Project
1.4.1 General Objective

The main objective of this project is change the manual Exit Examination system to
computerized system which is Web Based Graduate Exit Examination System for Ethiopian
higher education institutes.
1.4.2 Specific Objective

In order to achieve the main objective, the specific objective is designed to do the following
activity.
 To investigate and identify the problems in the existing manual system exam handling.
 To model and implement for using object oriented system and analysis approach.
 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 candidate result in the database and displays the
result back to the candidate.
 To test and evaluate the performance of the proposed system by inserting different data.
 Enabling candidates to see the exam date online.
3|Page
1.5 Scope of the Project

In this project supposed to do the following points.
 The system includes choose type of questions only (either multiple choice or true-false
question). It does not include essay type of questions or short answer questions. Because it
is difficult to develop a system that checks the essay question answer word by word. The
system also Retrieve any information from a database on the designed interface as per the
requirements of the user.
1.6 Limitation of the Project

Even if we have done many functionalities about Exit Exam, we also not able to include the
following activities
 Online payment system when candidate take Rexam

 Digital signature
 Cannot handle descriptive or subjective questions (essay)
 The system provide service only non-blind candidates
1.7 Significance of the Project

Developing this project has much significance for the university or institutes and the students
which are take exit exam before graduate. The system is centralized administrator controls and
saves the efforts and time of both the university and the students.
For university:
 Reduce economy spend for buying papers and printers.
 Reduce Time consumption
 Reduce man power like examainer,superviser and other that participate in exam
 Avoid document missing about candidate information.
4|Page
 Avoid tiredness to analysis the student result, because the student file will stored in
the database instead of cabinet so, it is easy to search student file from database.
 It ensuring the availability of documents in their proper place in the database.
For students:
 Making students aware about the examination because student can see all
information about exam detail from the system.
 View their exam result online immediately without came to the Department or class
room.
 It reduces time consumption when we see the results and economy wastage like pen
and paper.
 Generally the system Create suitable condition for candidates (students) to view their
result online and detail information.
1.8 System Requirements
1.8.1 Hardware Requirement

 Flash disk: For storing data what we have done.
 Personal Computer: For performing every activities about the project
 Stationeries (pen, paper): for writing all necessary documentations associated with the
project
 Note book: to take notes during data collection and for other documentations
1.8.2 Software Requirement

The tools that the we will use in this project are:
 Microsoft word 2010-for writing documentation sections.
 Wamp server: to provide MySQL for creating and manipulating databases and
PHP to design user interface from the front end of software. That is develop code
 Notepad++, Notepad, Dreamweaver , Code Lobster PHP Edition is a free portable
handy and easy-in-use code editor that is primarily intended for quick and easy
creation and editing of PHP, HTML, CSS, JavaScript files.
5|Page
 Browsers for running the code like Microsoft Internet Explorer, Mozilla Firefox,
Google Chrome
 Microsoft Office Visio 2007: to design Sequence Diagram, Class Diagram Activity
diagram and Use case Diagram of our system.
 Adobe Photoshop: for editing images.
 GUI Design Studio Pro Software for drawing graphical user interface.
1.8.3 Programming Language

Now a day’s many programming languages are used to develop many projects .The Project
include both back-end programming Languages and front-end programming Languages. [4]
I. Back-End Programming Languages: are programming Languages that run on browser

the user doesn’t see it or directly interact with it as with client-side technology. For
Example PHP ,Perl, Python, MYSQL Etc. but we are used PHP language because
 Increased efficiency & usability - PHP provides incomparable efficiency and
usability when it is used for the development of websites.
 Compatible- PHP is compatible on all operating systems including Windows and
UNIX- among other systems.
 Data processing - A website that has been developed using the PHP functions has
fast features of data processing.
 Easy to understand - When compared with other scripting languages, PHP can be
understood easily because it has simple techniques and features.
 Integration - it is easy to integrate popular web applications using this scripting
language.
 Cost advantages - PHP based websites are affordable to develop, design, modify
and customize. There are many website development companies which provide
professional services within the area of PHP, including websites designing,
developing web application and so forth.
 We are familiar with PHP language, so we select it to develop the proposed system.
6|Page
II. Front-end programming Languages: are programming Languages that run on

browser the user see or directly interact with it as with client-side technology. For
example html, css,javasript
Also the project includes database tool like MYSQL. Most of the time MYSQL is compatible
with PHP programming language and MYSQL portable. We are familiar with MYSQL so we
select it to manage database system. MYSQL is a relational database management system which
is an open source database.
1.9 Methodology
1.9.1 Data Collection Approaches

Different fact finding techniques or approaches were used to gather information about the current
system. It is the fundamental activity for the development of the system. Without them data
modeling cannot be constructed. In order to know how the existing system work and what
problem are there we have been using the following fact-finding techniques.
 Observation: Observation is one of the most important methodologies to gathering
information by physical going to the place and looks how the current system works. It can
be very difficult for humans to explain what they do or to even describe accurately how they
achieve a task, so observation very crucial to gathering information.
 Interview: Interview is another important methodology to gathering information by asking
someone a set of questions. It helps us to get critical and important information about the
overall view of the current system.
 Document analysis: This is also another information gathering methodology by referring
the document of the existing system. The project team tried to discover written documents
about the organization relevant to the project.
7|Page
1.9.2 The System Analysis and Design Approaches

The goal of this section is to provide the basic overview of the system that we are going to
develop. The system analysis and design approaches for this project we used the object oriented
system analysis & design. Because
 It provides code and function reuse through the concepts of inheritance, polymorphism,
encapsulation, modularity, coupling and cohesion.
 To design the system the project team has choose Object Oriented Modeling techniques
and Unified modeling language tools.
 Understanding of the structure is easy because object oriented modeling and tools used to
represent real world entities.
 It enables us to comprehensively model a system before we develop it.
 Modification of the object implementation is easy because objects are loosely coupled.
1.9.3 The System Development Model

There are various software development life cycle models defined and designed which are
followed during the software development process. These models are also referred as “Software
Development Process Models". Each process model follows a Series of steps unique to its type
to ensure success in the process of software development. But the proposed system follows
Incremental model. Because In this model, each module passes through the requirements, design,
implementation and testing phases. A working version of software is produced during the first
module, so you have working software early on during the software life cycle. Each subsequent
release of the module adds function to the previous release. The process continues still the
complete system is achieved [1].
1.10 Feasibility Study

Feasibility is the measure of how beneficial or practical the development of an information
system will be an organization. To start with our project first we should have to clearly notify the
feasibility of the system that we are going to do.
8|Page
1.10.1 Technical Feasibility

The system developed by following the Object Oriented System Development technique and initiate
to develop the system without any difficulty Using PHP, Java script, CSS, html and MySQL database
without any problems, so the system technically provide easier and fast work of activities and
technical support for users how to operate their tasks. The system gives powerful to be applied by
low skilled users as much as possible. Our system will provide an easy access to the users. The work
for the project is done with the current equipment and existing software and hardware technology.
1.10.2 Economical Feasibility

The proposed system is economically feasible because The proposed system will provide many
benefits for the university and students. Some of benefits are
 There is no cost for copy machines, printers and papers to prepare the exit examination.
 A problem that was occurring on exam paper correction is strictly avoided.
 There is no cost wastage for duplicators, examiners and coordinators.
The cost required in the proposed system is comparatively less to the existing system. For
example the following points must be feasible when we proposed the system.
 The cost to buy server computer.
 The cost to buy client computers and network connection devices.
 The cost paid for system designers and system analysts.
 The cost of the software to be acquired to build and run the system.
 The cost to train students and examiner show to use the system.
 The cost to maintain computers if there is problem with computers.
1.10.3 Operational Feasibility

The proposed system is operationally feasible because it is simple to access and all operations
will be performed easily.
1.10.4 Legal Feasibility

Legal feasibility determines whether the proposed system conflicts with the legal requirement or
not. The proposed system is legally feasible because The project team members built the system
without violating rules and regulations of the governments as well as the organization. The
system being built is for the sake of productivity of the organization.
9|Page
CHAPTER TWO
2. SYSTEM ANALYSIS
2.1 Overview of the Existing System

This project emphasizes on Graduate Exit examination system for graduate student higher
education institutes of Ethiopia. The existing system of conducting examination process is
through manual system. Due to these users of the existing system wastes much amount of
resources. For instance it takes time to test the exam and evaluate the answer of the exam as well
as to announce the exam date to the candidate. It takes also large numbers of paper and even
candidates may lose where and when the exam is performed. In general, almost all activities in
the system are done manually, so it has many problems.so we introduce new system which is
fully computerized. Therefore the entities that interact with the existing system are user of the
system and have its own role. The current system users relating to exit exam are: [3]
1. Exam board editor: the exam board editor responsible for Prepare proposals that shows the
cost of the exam and Ensure that exam question are prepared and printed timely. Also ensure
that the exam question and results are posted to the university with in sufficient time. The
exam editor Handle any complaints that occur relating to marking the examination and
responsibility to ensure the proper administration, transportation and correction of the
examination. Generally exam board editor coordinate how the exam to be performed and
select exam setter who set or prepare exit exam and exam evaluator.
2. Exam setter: responsibility to prepare or set the exam in line with the scope of the learning
domain to be assessed. During preparing the exam the exam setter Prepare exam with in a
given time and Responsible for providing answer key and making corrections where some
error are detected in the questions. also responsibility to check question are not repeated and
include the answer in the listed choice.
3. Candidates: are student who take the exit exam.
4. Examiners: responsibility to tests or examine candidates or students and shall be assigned
from other department.
10 | P a g e
5. Department Head: responsibility to Specifies places for exam and generally he manages all
activities in his perspective departments.
6. Exam evaluator: Evaluates the exam that is drafted/prepared by exam setter.
7. Registrar: responsibility to capture candidate information or profile and checks candidates
take all department course before take exam.
8. Supervisor: responsibility to controls the overall exam (candidates and examiner) and take
and bring the exam paper to Exam Board Editor.
2.2 System Requirement Specification

A System Requirements Specification also known as a Software Requirements Specification .it
is a document or set of documentation that describes the features and behavior of a system or
software application. a Requirement is any function, constraint, or property that the system must
provide, meet, or satisfy in order to fulfill its purpose. So we need to identify and understands the
problem of the existing system to develop the new system. We decide the following functional
and non-functional requirements of the system. [6]
2.2.1 Functional Requirements

Functional requirement is the requirement describing the behavior of the system as it relates to
the system's functionality that is describes what the system does. This behavior may be expressed
as services, tasks or functions that the system is required to perform. Therefore the functional
requirements for the new proposed system includes the following section.
 Exam management section: these section includes

 Exam Setter: Exit Exam preparation section can add questions, edit questions, manage
and view all questions of a given department.
 Exam Editor: check or ensure that exam question is prepared correctly and timely.
 Registrar: send candidate profile or information to Editor that take exit exam.
 Candidate section: includes students who take exit exam and select answer within given
question by its page of the system and finally view its result.
 Report generate management section includes
 The candidate can view his/her result after exam completed.
11 | P a g e
 The system reports the exam result to individual candidate after candidate take exam.
For example:-
Full Name: Muluye Fentie Admas
User Id:TER/4682/07
Department: IT
Institute: Technology
Address:DMU
Result: Competent
 The system admin views all candidates’ results and any other reports.
 The system should validate the data entry. That is the system shall validate and
authenticate the users’ username and password.
 The system shall allow all eligible users to update their accounts.
 User account management section :The system has different account types and the system
adimin for all system user account
2.2.2 Non Functional Requirements

Functional requirement describes what a software system should do, while Non-functional
requirement is any requirement which specifies how the system performs a certain function.it
will describe how a system should work and what limits there are on its functionality.
Nonfunctional requirements generally specify the system’s quality attributes or characteristics.
Therefore some of the non-functional requirement that needs to be met in order for the proposed
system to operate or done correctly can be:
 Control and Security: This system uses different security systems to protect its data. Among
this: Password and user name. The system users are allowed to perform activities or make a
modification to the data if and only if they are authorized which will be checked by their
username, password, and account type.
 Performance : The amount of time needed to get the response for a transaction or request is
minimized and also The system has fast response time because of a light weighted code in
HTML, PHP, CSS and JavaScript.
 Portability: This system is portable, since it runs on different desktop platforms. Running on
different platforms in desktop computer browser makes the system accessible by users.
12 | P a g e
 Availability: The system is available in the presence of Extranet connection. So, the users of
system can access the system successfully for provide different services but the exam is taken
periodically.
 Reliability: The system should handle invalid inputs and displays error message to users.
Reliability is one feature of the system significantly validates user inputs.
 Backups: In addition to authorizing access to users, the system could have problems in such
areas of data crime, disaster, and human errors. For this purpose, incremental backup copies
(copies of only the challenge to files) and full backup copies (copies of all files) will be made
and stored in a secured location.
 Usability: The system has an interactive and attractive GUI which eases users’ usage
problem. It needs simple training. Because it is easy to use and adapt.
2.2.2.1 Technical Requirement

Technical requirement concerns or pertains to the technical aspects that our system must fulfill.
The followings are technical requirement of the project:-
 The system should have good user interface for users for simplicity and easy to use.
 The system should be attractive.
 The system should be platform independent.
 The interface should display error message if it detects invalid input.
 The system should deny unauthorized accesses to the system domain.
 The system should provide help for the user.
 Requires an expert to use the system.
 Training the users to access the system.
2.2.3 Business Rules

Business rules are statements that describe a business policy or procedure and they reflect
business policies. organization have policies in order to satisfy the business objective, make good
use of resources, and conform to laws or general business conversions. Business rule become
requirements that is they may be implemented in software as a means of requirements of this
software system. Identifying the business rule of the proposed system will help us to specify and
13 | P a g e
describe each use case in effective way. The business rules of the exit exam system are listed as
following: [3]
BR1: The registrar must send graduated students list with full information to Exam Editor.
BR2: The candidate’s should be legible.
BR3: The system administrator and candidates must have user account for managing the
activity specified and limited to their privilege or generally the system user must have an
account to access the services in the system and managed by system administrator.
BR4: They should have a take along unique ID that expresses his/her identity.
BR5: The candidates should have to take the exam within the given time of period.
BR6: The exam should be deactivating after the exam is taken or exam time is expired.
BR7: The exam question should not be duplicated or there is no redundancy of question.
BR8: The candidate should take all department courses before take exam.
BR9: Candidates can take another exam more than once, when candidate cannot pass the first
time, but candidate pay fee before taking re-exam.
BR10:The entire examinations question are objective.
BR11:the candidates should fill the form and the requirements properly and carefully.
BR12:all candidates must take the same exam according to their department.
2.3 System Requirement Analysis

System Requirements Analysis gives the professional systems engineer the tools to set up a
proper and effective analysis of the resources, schedules and parts needed to successfully
undertake and complete any large, complex project.
2.3.1 Actor and Use Case Identification

i. Actor: It represents a type of users of the system or external systems that the system interacts
with an actor is a user of the system playing a particular role. The actors of the new system
are:
 Candidate  Exam setter
 Department head  Exam Editor
 Registrar  System admin
14 | P a g e
ii. Use case: describes the sequence of events of some types of users, called Actors, using some
part of the system functionality to complete a process. The possible use case of the new
system are:
Table 1: Use Case Identification
Use Case ID Use Case Name Include
UC01 login
UC02 View exam date UC01
UC03 View result UC01

UC04 View exam question UC01
UC05 View notification UC01
UC06 View report UC01

UC07 View system user UC01
UC08 View exam question time UC01

UC09 View candidate UC01
UC10 View comment UC01
UC11 Send comment UC01

UC12 Take exam UC01
UC13 Manage account UC01

UC14 Send request UC01
UC15 Prepare questions UC01
UC16 Update user info UC01

UC17 Change password UC01
UC18 Specify exam date UC01

UC19 Specify exam time UC01
UC20 Post notice UC01
UC21 Send candidate info UC01
1|Page
UC22 Specify exam passing score UC01
UC23 Logout UC01
2.3.1.1 Use case diagram

A use case diagram is a graphic depiction of the interactions among the elements of a system.
Use case diagram shows use cases, actors, and their interrelationships. A use case is a
methodology used in system analysis to identify, clarify, and organize system requirements. Use
Case Model describes the proposed functionality of a new system. use case diagram contains
four components. [6]
 The boundary, which defines the system of interest in relation to the world around it.
 The actors, usually individuals involved with the system defined according to their
roles.
 The use cases, which the specific roles are played by the actors within and around the
system.
 The relationships between and among the actors and the use cases.
The use case diagram of the system can see below.
2|Page
Take exam
Manage user account
View result
Take backup
View notification include Include

include View system user
Include
Candidate include Admin
include
send request
View report
include
include
include
include view request
Send comment
Login include
include
view report include include post notice

Dep't Head
include
include
include set passing score
view candidate
Include
include
register user
Extend include
view exam date
include Exam Editor
View candidate
include
Registrar
include
Send candidate
Specify exam date
information include
Logout view comment
Specify exam time
Edit questions
Exam Setter
Prepare questions
send comment
Figure 1: Use Case Diagram
2.3.1.2 Use Case Description

Use case description is documents that contain brief information about use case .use case
description contain the components like use case name, use case ID, participate
3|Page
actor,description,basic course of action, alternative course of action,pre-condition and post-

condition.
Table 2: Use Case Description for Login
Use case name Login

Use case ID UC01
actors System users
description Describes how the system users login into the system
basic course of action 1. Open web site

2. User enter username and password
3. Click login button
4. System checks username and Password.
5. If username and password is valid
6. User authenticated and gets access to the system.
7. End of use case
alternative course of action I. User is not authenticated and is denied access to the system.
II. System displays an incorrect username and password message.
III. System enables user to try again.
IV. Use case returns to step 2 to fill or enter the correct username and
password.
pre-condition Users must have user name and password
post-condition login to the system successfully and gets access to the system according to
their predefined system privileges.
4|Page
Table 3: Use Case Description for Take Exam
Use case name Take Exam

Use case ID UC12
actor Candidate
description Describes how the candidate to login into the System to take exam.
basic course of action 1. Open the web site

2. Candidate enter username and password
3. Click login button
4. System checks username and user Password
5. Candidate authenticated and takes exam on the system.
6. End of use case
alternative course of I. Candidate is not authenticated and is denied access to the
action system.
II. System displays an incorrect message.
III. System enables user to try again.
IV. Use case returns to step 2 to fill correct Username and PW
pre-condition Must complete all department courses
post-condition Can take exam and finally view result
5|Page
Table 4: Use Case Description for View Result
Use case name View Result

Use case ID UC06
actor Candidate
description System generates result based the candidate ID individually.
basic course of action 1. Candidates Open website

2. Candidates Logged to website
3. Candidates Click View Result link.
4. System Display their result
5. Candidates view their exam result
6. End of use case
alternative course of If the Candidates doesn’t have access privilege to use the system,
action then the Candidates is not authenticated and is denied access to the
system.
pre-condition Candidate Must be take exam
post-condition Result will be generate and see the Result
6|Page
Table 5: Use Case Description for Send comment
Use case name Send Comment

Use case ID UC11
participate actor  Admin

 Exam setter
 Dep’t head
 Registrar
 candidate
description Describe system user can give comment or feedback about system
tasks or may any suggestion’s.
basic course of action 1. The user opens the of the system.
2. Login to the system
3. After logged to system according to its page
4. Can feedback/comment
5. End of use case
alternative course of I. User reenter correct username and password
action II. After enter correct username and password can login to
system.
pre-condition Must have username and password.
post-condition Can give comment or feedback
7|Page
Table 6: Use Case Description for View comment
Use case name View Comment

Use case ID UC10
participate actor Exam editor
description Describe exam editor can view different feedback which are sent
form other system user
basic course of action 1. Exam editor login to system
2. After logged go to comment link
3. System Display comment.
4. Exam editor view and delete comment
5. End of use case
8|Page
Table 7: Use Case Description for View Report
Use case name View Report

Use case ID UC6
participate actor Admin,Dep’t head, Exam editor
description The System allows to generate report for candidates about exam
Information.
basic course of action 1. Open website

2. Logged to website
3. Click on view report link.
4. System Display report
5. view exam result report
6. End of use case
alternative course of If the user doesn’t have access privilege to use the system; user is
action not authenticated and is denied access to the system.
pre-condition All candidate must take the exam
post-condition Report will be generate
9|Page
Table 8: Use Case Description for Create account for candidate
Use case name Create account

Use case ID UC24
actors System Admin
description Describe how Admin create account to system user
basic course of action 1. Admin open website

2. Admin logged to website
3. Admin View users
4. Admin create account automatically for all candidate of the
system
5. End of use case
pre-condition User must be the member of the system and haven’t an account
before.
post-condition User create account
2.3.2 Sequence Diagram

A sequence diagram is a Unified Modeling Language (UML) that showing the sequence of
interactions among objects and used to represent or model the flow of messages, events and
actions between the objects or components a system. A sequence diagram represents the scenario
10 | P a g e
or flow of events in one single use case. The message flow of the sequence diagram is based on
the narrative of the particular use case. The Diagrams are also used primarily to design,
document and validate the architecture and interfaces of the system by describing the sequence
of actions that need to be performed to complete a task or scenario. The following describes the
sequence diagrams of the property administration system. A sequence diagram consists of a
group of objects that are represented by lifelines, and the messages that they exchange over time
during the interaction. Some of use case sequence diagram for the system are:- [6]
Home Page Login Page User Page Database

System User
Open() Enter UN and PW

Press Login Button
ValidateForm()
Check()
Display() Valid()
Invalid input() Else()
Figure 2: Sequence diagram for login
11 | P a g e
Home Page Login Page Candidate Page Exam link Exam Page Database
Candidate
Open() Enter UN and PW()
Login()
Validate() Check()
Invalid()
Invalid input()
Display()
Else()
Click Exam link()
alert message display()

Confrim()
Display()
Take exam
Submit answer
answer successfully sent
Cancel
Figure 3: Sequence diagram for Take Exam
12 | P a g e
Home Page Login Page Canidate Page View Result Database
Open()
Candidate Enter UN and PW()
ValidateForm()Check()
Invalid UN and PW() Invalid()
Display()
Valid()
Click View link()
View Result
Figure 4: Sequence diagram for View Result
13 | P a g e
Home Page Login Page Admin Page View Report Database
Open()
Enter UN and PW()
Admin
ValidateForm()
Check()
Invalid()
Invalid UN and PW()
Display() Else()
Click View Link()

View Report
Figure 5: Sequence diagram for View Report
14 | P a g e
Home Page Login Page User Page Feedback Database
System User
Open()
Enter UN and PW()
validateForm()
Check()
Invalid()
Invalid UN and PW()
Display()
Else()
Click Link()
Write Comment
Send()
Comment sent successfully
Figure 6: Sequence diagram for feedback
15 | P a g e
2.3.3 Activity Diagram
Activity diagram is another diagram in UML diagram that describe dynamic aspects of the
system. Activity Diagrams also describe how activities are coordinated to provide a service
which can be at different levels of abstraction. Typically, an event needs to be achieved by some
operations, particularly where the operation is intended to achieve a number of different things
that require coordination, or how the events in a single use case relate to one another, in
particular, use cases where activities may overlap and require coordination. It is also suitable for
modeling how a collection of use cases coordinate to represent business workflows. Generally
the purpose of an activity diagram describe to:- [6]
 Draw the activity flow of a system.

 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.
Some of the activity diagrams of the system use case are:-
User Open the system

User
Login
Enter UserName and Password
Invalid
Incorrect UserName and Password
Valid
Login into the System
Figure 7: Activity diagram for login

16 | P a g e
Candidate Candidate open system

Return
Candidate click login button
Return Invalid
Incorrect UserName and Password
Candidate dircts into its page Canidate click to Take Exam link
the system display alert message,"Are you ready to take exam"
Candidate Cancel Alert Message
Candidate confrim alert message
Exam question display
Submit Answer Take exam
Figure 8: Activity diagram for take exam
17 | P a g e
Candidate Candidate Open the System
Invalid Valid
Incorrect UserName and Password Canidate Page
Canidate Result View Result
Figure 9: Activity diagram for view result
User Open the system

User
Enter UserName and Pasword
Invalid Valid
Incorrect UserName and Password User Page
Send comment Write Comment Feedback
Figure 10: Activity diagram for feedback
18 | P a g e
2.3.4 Analysis Class Diagram
Class diagram is a static diagram that represents the static view of the system. The class
diagrams are widely used in the modeling of object oriented systems because they are the only
UML diagrams, which can be mapped directly with object-oriented languages. Class diagram
shows a collection of classes, interfaces, associations, collaborations, and constraints. Generally
the purpose of the class diagram can be summarized as: [6]
 Describing or modeling the static view of the system.

 Showing the collaboration among the elements of the static view.
 Describing the functionalities performed by the system.
 Construction of software applications using object oriented languages.
 Shows relationships between classes, objects, attributes, and operations.
Analysis Class Diagram
Admin Result
user
inherit all attribute view
-user_ID Candidate 1
+create account() +view result()
-Fname 1 +block account() -Dep't
-Mname 1
-Lname 1 -College
1
-Sex create1 and manage has 1 -University
-Mobile has -year
* +set candidate info() Question
-Email inherit 1 1
-Photo -Qid
-Role Account take -year
- -Dep't
+View user()
- 1 -question
1 * -choices
* +create account() 1
+block account() -answer
comment
+set question()
1 1
* has *
has has
Comment has
+Send ()
1 set
+view() 1 1 1
Departement Head Exam editor Exam setter

Registrar
-university -Dept 1
-University name
-dept +set exam date() +set exam()
+Register candidate()
+view report() +post notice() +set exam time()
+view report()
+view exam date() +view report()
Figure 11: Analysis Class Diagram
19 | P a g e
CHAPTER THREE
3. SYSTEM DESIGN
3.1 Introduction
System design is the transformation of the analysis model into a system design model. Up to now
we were in the problem domain. System design is the first part to get into the solution domain in
a software development. This chapter focuses on transforming the analysis model into the design
model that takes into account the non-functional requirements and constraints described in the
problem statement and requirement analysis sections discussed earlier in analysis. The purpose
of designing is to show the direction how the system is built and to obtain clear and enough
information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of design
created by the designer. If one wants to change to the system after it has been put in to operation
depends on the quality of the system design.
3.2 Design Class Diagram

A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.
20 | P a g e
Design Class Diagram
Admin Result
user
view
-user_ID:varchar(50) +create account() Candidate 1
-Fname:varchar(50) +view result()
+block account() -Dep't:varchar(50)
-Mname:varchar(50)
1 -College:varchar(50)
-Lname:varchar(50) 1
1 1 -University:varchar(50)
-Sex:varchar(50) create and manage has Question
-year:int
-Mobile:varchar(50) has
+set candidate info() -Qid:int
-Email:varchar(50) 1
inherit attribute -year:int
-Photo:varchar(50) * 1 take -Dep't:varchar(50)
-Role:varchar(50) timer -question:varchar(2000)
+View user() Account -tid:int -txtA:varchar(100)
-status:varchar(20) -hour:int -txtB:varchar(100)
1 1
* +create account() -min:int -txtC:varchar(100)
comment inherit 1 +set examtime() * -txtD:varchar(100)
+block account()
+update() -Answer:varchar(10)
+view() set -status:varchar(50)
has 1 1
* -type:varchar(50)
has +set question()
has has
Comment +update()
+view()
-co_id:int
-date:date
-content:varchar(1000) 1 1 1 *
+Send () Exam editor
+view() 1 Departement Head
Exam setter set
-university:varchar(50) +set exam date() -Dept:varchar(50) 1
-dept:varchar(50) +post notice()
Registrar +set exam()
+view report() +view report()
-University name:varchar(50) +set exam time()
+view exam date() +Register()
+Register candidate() +update()
+view report() exam_date
-did:int
set -sdate:date
-edate:date
-stime:time
-etime:time
-year:int
+set()
+update()
+view()
Figure 12: Design class diagram
21 | P a g e
3.2.1 Design Class Diagram Description
Table 9: Design Class Description for Admin Class
Attribute Description Type

Method Description
Create account() This methods used for create account for users
View user account() Represent View user account
Block user account() Represent Block user account
View report() Represent View report
Table 10: Design Class Description for Result
Attribute Description Type

Empty space Candidate attribute who are inherits from user varChar(50)
and candidate class
Method Description
View This methods used for view or display candidate result after taken exit exam
result()
3.3 Database Design /Physical Data Model

Physical database model shows all table structures, including column name, column data type,
column constraints, primary key, foreign key, and relationships between tables. Features of a
22 | P a g e
physical data model include: Specification all tables and columns. Foreign keys are used to
identify relationships between tables.
Table 11: Result Table
Table 12: Feedback Table
23 | P a g e
Table 13: Question Table
Table 14 :Notice table
24 | P a g e
Table 15: Timer table
25 | P a g e
Table 16: Exam date table
Table 17: account table
26 | P a g e
Table 18: User Table
3.4 User Interface Design

User interface design is the design of computers, appliances, machines, mobile communication
devices, software applications, and websites with the focus on the user's experience and
interaction. User interface design is the specification of the interaction between the system users
and a system. The goal of user interface design is to make the user's interaction simple and
efficient as possible, in terms of accomplishing user goals—what is often called user-centered
design. Good user interface design facilitates finishing the task at hand without drawing
unnecessary attention to it.
27 | P a g e
Figure 13: Graphical user interface for Home page
28 | P a g e
Figure 14: Graphical user interface Admin page
29 | P a g e
Figure 15: Exam editor page
30 | P a g e
Figure 16: Set Exam question page
31 | P a g e
Figure 17: Candidate Page
32 | P a g e
Figure 18: Exam Taken Page
33 | P a g e
3.5 System Architecture
3.3.1 Component Diagram

Component diagrams are integral to building your software system. They help your team
understand the structure of existing systems and then build new ones. The purpose of a
component diagram is to show the relationship between different components in a system. The
component diagram shows the relationship between software components, their dependencies,
communication, location and other conditions [6] .The components the systems are:
Component of the system

-HTML
-CSS
PHP Web pages
SQL Web servers

PhpMyAdmin
Figure 19:Component of the system
Main server
clients/workstations
Business logic
PHP
<<TCP/IP>> Web browsers
SQL
Web server
Figure 20:Component Diagram
34 | P a g e
3.3.2 Deployment Diagram

In UML, deployment diagrams model the physical architecture of a system. Deployment
diagrams show the relationships between the software and hardware components in the system
and the physical distribution of the processing. Deployment diagrams consist of nodes and their
relationships. Deployment diagrams are used for describing the hardware components where
software components are deployed. Deployment diagrams are mainly used by system engineers.
These diagrams are used to describe the physical components (hardware), their distribution and
association. To clarify it in details we can visualize deployment diagrams as the hardware
components/nodes on which software components reside [6]. So the usage of deployment
diagrams can be described as follows:
 To model the hardware topology of a system.
 To model embedded system.
 To model hardware details for a client/server system.
 To model hardware details of a distributed application.
 To design the hardware components efficiently
35 | P a g e
Their is Web browser Web Application Server Database server

-Opera
-Firefox,.....
prepare exam
Client/User
specify exam time

Security
Exam setter
take exam
Candidate
view result
Database
manage account
Admin
view report
view dep't info
view exam date
Dep't Head
view comment
Exam editor
specify exam date
Registrar
View candidate list
hold candidate profile
send candidate list
Figure 21: Deployment Diagram
36 | P a g e
Chapter Four
4. Implementation
4.1 Introduction
Implementation is defined as a specified set of activities designed to put into practice an activity
or program of known dimensions. It is the carrying out, execution, or practice of a plan, a
method, or any design, idea, model, specification, standard or policy for doing something. It is
also a realization of a technical specification or algorithm as a program, software component, or
other computer system through computer programing and deployment. It is the most crucial
phase in which it transform the design and analysis of the system into a tangible system by
writing the code to the system to be developed and make it operational and applicable by testing
and debugging the functionalities that are done. This makes the implementation stage more
essential step to develop the required system. So, it is the most vital and necessary stage in
achieving a successful system and in giving the users confidence that the new system will work
and be effective by testing the system that is already implemented. First phase of implementation
is coding. Coding is the process whereby the physical design specification created by the
designers is turned in to working computer code by the programmer. The code is made simple in
such a way that another programmer can easily understand and work on that in future. In our
project we use PHP programming language with MYSQL database. Interface implementation:
this part of implementation stage which includes interface page of the project includes home
page with applicant registration, manager page interface, system admin page and storekeeper
interface pages.
4.2 Overview of the programming language used

This project used PHP, HTML, JavaScript, CSS, server side programming technology integrated
with MySQL database. PHP is a widely-used open source general-purpose scripting language that is
especially suited for web development and can be embedded into HTML.Hypertext Preprocessor
(PHP) is a server-side scripting language designed for web development. It is used to manage
dynamic content, databases, session tracking, even build entire e-commerce sites. The code and its
syntax is simple to understand as well as It's is quick to develop and it is flexible, available for
37 | P a g e
free ,runs on many different operating system and easy to access other web-based tools through
PHP.
4.3 Algorithms Used

The project used Random algorithm and we use MD5 technique for encryption purpose.
 MD5: Stand for Message-Digest Algorithm and it is a cryptographic hash function whose main
purpose is to verify that a file has been unaltered which is encrypted. MD5 has certain flaws and
so it isn't useful for advanced encryption applications, but it's perfectly acceptable to use it for
standard file verifications.
 Random algorithm: This algorithm is used when the candidate take exit exam, then it makes
exam question order or ranked randomlly.the algorithm randomly order exam question is one
way of code of exam and control cheating because the question order is randomly ranked for
each candidate and the order of exam question is different from other candidate.
4.4 Sample Codes

 Login
<?php
session_start();
?>
<html>
<head>
<link rel="stylesheet" type="text/css" href="css/style.css" />
<script type="text/javascript" src="css/javasscript.js"></script>
<style type="text/css">
input[type="text"],input[type="password"],input[type="Submit"],input[type="reset"]
{
width: 180px;
height: 30px;
38 | P a g e
input[type="submit"],input[type="reset"]
{
background:#170b62;
color: #fdfdfd;
box-sizing: border-box;
font-size: 20px;
height: 40px;
}
</style>
</head>
<body>
<div class="login">
<form action=" " method="post" name="myForm" onsubmit="return

validateuser()">
<h1><br>   Enter UserName</h1><input type="text" name

="un" placeholder="Enter UserName...." >
<h1>   Enter Password</h1> <input type="password" name
="pass" placeholder="Enter Password...." >
<input type="Submit" name="login" value ="Login" >
<input type="reset" name="reset" value ="Reset" >
     <a href="forgot password.php">Forgot
Passsword</a>
</form>
<?php
if(isset($_POST["login"]))
{
include("connection.php");
function encryptpassword($password )
39 | P a g e
{
$cryptKey='qJB0rGtIn5UB1xG03efyCp';
$passwordEncoded= base64_encode( mcrypt_encrypt( MCRYPT_RIJNDAEL_256, md5(
$cryptKey ), $password, MCRYPT_MODE_CBC, md5( md5( $cryptKey ) ) ) );
return( $passwordEncoded );
}
$uname=$_POST["un"];
$pass=$_POST["pass"];
$plaintext_password=$pass;
$password=encryptpassword($plaintext_password);
if($con)
{
//account
$sql="select * from account where username='$uname' and password='$password'";
$matchfound=mysql_query($sql,$con);
$userexist=mysql_num_rows($matchfound);
if($userexist>0)
{
$sql=mysql_query("delete from attempt");
while($row=mysql_fetch_assoc($matchfound))
{
$id=$row["uid"];
$un=$row["username"];
$pw=$row["password"];
$status=$row["status"];
$pw_status=$row["password_status"];
}
if($pw_status=="unchanged")
{
$_SESSION['userid']=$id;
$_SESSION['oldpassword']=$pass;
header("location:change_password.php");
}
40 | P a g e
else
{
$sqll="select * from user where uid='$id'";
$matchfound1=mysql_query($sqll,$con);
while($user=mysql_fetch_assoc($matchfound1))
{
$fname=$user["ufname"];
$mname=$user["umname"];
$lname=$user["ulname"];
$role=$user["role"];
$photo=$user["photo"];
}
//store value in session
$fullname=$fname." ".$mname." ".$lname;
$_SESSION['fullname']=$fullname;
$_SESSION['sun']=$un;
$_SESSION['spw']=$pw;
$_SESSION['role']=$role;
$_SESSION['$uid']=$id;
$_SESSION['sphoto']=$photo;
// variable declaration for log file registration

$login_time = date("h:i:s");
$_SESSION['login_time']=$login_time;
//end log record

//Go to Page
if($role=="Admin" && $status=="active")
header("location:Admin/adminpage.php");
else if($role=="Candidate" && $status=="active")
header("location:candidate/candidatepage.php");
41 | P a g e
else if($role=="Exam setter" && $status=="active")

header("location:setter/examsetterpage.php");
else if($role=="Exam Editor" && $status=="active")

header("location:editor/exameditorpage.php");
else if($role=="Registrar" && $status=="active")

header("location:Registrar/Registrar.php");
else if($role=="Department Head" && $status=="active")

header("location:dept/deptheadpage.php");
else
{
if($status=="inactive")
echo"<font color='red' size=4><b><i>Sorry Your Account Is Bolcked!!!</i></b></font>";
else
{
echo "<h1>Invalid username/passwords<h1>";
header("location:index.php");
}
}
}
}
else
{
$count="insert";
$sql=mysql_query("select*from attempt");
$total=mysql_num_rows($sql);
$total++;
if($total>3)
{
42 | P a g e
//$sql=mysql_query("delete from attempt");

header("location:index1.php");
}
else
{
echo "<h1>Invalid username/password<h1>";
echo "<br>you are tries $total times,but allowed 4 times<h1>";
$insert=mysql_query("insert into attempt values(' ','$count')");
}
}
}
else
echo"Connection fail".mysql_error();
}
?>
</div></body>
</html>
 Set Exam Question

<?php
if(isset($_POST['savequestion']))
{
$dname=$_POST["departmentname"];
$txtquest=$_POST["txtquest"];
$txta=$_POST["txta"];
$txtb=$_POST["txtb"];
$txtc=$_POST["txtc"];
$txtd=$_POST["txtd"];
$txtansw=$_POST["txtansw"];
$qstatus="active";
43 | P a g e
$sid=$_POST["sid"];
$qtype1=$_POST["qtype"];
if($con)
{
$sql="insert into question values('

','$year','$dname','$txtquest','$txta','$txtb','$txtc','$txtd','$txtansw','$qtype','$qstatus','$sid')";
$insert=mysql_query($sql,$con);
if($insert)
echo" Question is inserted sucessfully";
else
echo" NO Question inserted inserted !!!".mysql_error($con);
}
else
echo"Connection Failed:".mysql_error($con);
}
?>
 Take Exam
<?php
if(isset($_SESSION['sun'])&&isset($_SESSION['spw']))
{
$uid=$_SESSION['$uid'];
$username=$_SESSION['sun'];
$role=$_SESSION['role'];
$login_time=$_SESSION['login_time'];
$logout_time="empty";
$count=0;//check take exam before this or not
$number=0;//role number question
44 | P a g e
//check department
$sql="select * from candidate where cid='$uid'";
$recordfound=mysql_query($sql,$con);
while($row=mysql_fetch_assoc($recordfound))
{
$dept=$row["dept"];
$univesity=$row["unversity"];
$year=$row["year"];
$_SESSION['dept']=$dept;
$_SESSION['univesity']=$univesity;
$_SESSION['year']=$year;
}
?>
<div id="header">
<div id="banner">

<?php
require("dmu.php");
?>

</div>
</div>
<div id="navigation">
<?php
require("candmenu.php");
?>
</div>
45 | P a g e
<div id="site_content"></div>
<div id="site_content">
<div class="sidebar_container">
</div>
<div id="content">
<fieldset class="fieldset">
<br><br>
<?php
$fullname=$_SESSION['fullname'];
$uname=$_SESSION['sun'];
$role=$_SESSION['role'];
$photo=$_SESSION['sphoto'];
?>
<div style="margin: 10px;float: right;border:1px Solid #dadcdc;
box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px
0 rgba(0, 0, 0, 0.19);margin-top: -15px;">
<table cellspacing="0" height="70">
<tr><td colspan="2"><center><?php echo "<img

src='../editor/$photo' height=150 width=150>"?></center></td></tr>
<tr><td><b>User Name:</b></td><td><font
color="#e9163c"><?php echo $uname;?></font></td></tr>
<tr><td><b>          &n
bsp;Role:</b></td><td><font color="#e9163c"> <?php echo
$role;?></font></td></tr>
<tr><td>Time Allowed  </td> <td
style="font-weight: bold;font-size: 20px;"><div id="showtime" ></div></td> </tr>
</table>
</div>
<div class="style1">
46 | P a g e
<?php
// Retrive time According to Department
$sq="select * from timer where dept='$dept' and question_type='Regular' and year='$year'";
$t=mysql_query($sq,$con);
while($row=mysql_fetch_array($t))
{
$h=$row["hour"];
$m=$row["min"];
}
?>
<script language ="javascript" >
var tim;
var hour=<?php echo $h;?>;
var min =<?php echo $m+1;?>;
var sec =0;
var f = new Date();
function f1()
{
f2();
document.getElementById("starttime").innerHTML = "Your started Exam at " + f.getHours() +
":" + f.getMinutes();
}
function f2()
{
if (parseInt(sec) > 0){
sec = parseInt(sec) - 1;
document.getElementById("showtime").innerHTML = hour+" :"+min+" :" + sec;
tim = setTimeout("f2()", 1000);
}
else {
if (parseInt(sec) == 0) {
min = parseInt(min) - 1;
47 | P a g e
if (parseInt(min) == 0) {
var m=document.getElementById('Exam');
m.submit();
clearTimeout(tim);}
else {
sec = 60;
document.getElementById("showtime").innerHTML = "Your Left Time is " +
min + " Min " + sec + " Sec";
tim = setTimeout("f2()", 1000);
}}}}
</script>
<?php
$query="select *from question";
$rand=mysql_num_rows(mysql_query($query,$con));
//set question
$sq="select *from question WHERE dept='$dept' and status='active' and year='$year' and
question_type='Regular' ORDER BY RAND()
LIMIT $rand ";
$result = mysql_query($sq,$con);
// Loop through each records
?>
<?php
while($row = mysql_fetch_array($result))
{
$qid=$row["qid"];
$question=$row["question"];
$option1=$row["optiona"];
$option2=$row["optionb"];
$option3=$row["optionc"];
$option4=$row["optiond"];
$number++;
?>
48 | P a g e
<div id="radio_button">
<table id="question">
<form id="Exam" action="display.php" method="post" >
<hr>
<tr ><td colspan="2"><?php echo $number;?>.   <?php echo $question;?></td> </tr>
<tr><td width="1"><input type="radio" name="<?php echo $qid;?>" value="A"/></td>
<td>A)  <?php echo $option1;?> </td></tr>
<tr><td width="1"><input type="radio" name="<?php echo $qid;?>" value="B"/></td>
<td>B)  <?php echo $option2;?> </td></tr>
<tr><td width="1"><input type="radio" name="<?php echo $qid;?>" value="C"/></td>
<td>C)  <?php echo $option3;?> </td></tr>
<tr><td width="1"><input type="radio" name="<?php echo $qid;?>" value="D"/></td>
<td>D)  <?php echo $option4;?> </td></tr>
<?php
}
?>
49 | P a g e
Chapter Five
5. Testing
5.1 Introduction
Developing software is a complex process. No matter how hard we try to eliminate
all faults simply by going through the development phases which is requirements
elicitation, requirement analysis, system design, and implementation, however
through good practice we can make sure that the most series fault does not occur in
the first place. In addition we need a separate testing phase, with the goal of
elimination all remaining faults before release the system.
Testing is the final phase of implementation. Testing is a process to show the
correctness of the program. Testing is checking of the system workability in an
attempt to discover errors and avoiding such errors from the system. In this the
team members tested the entire system as a whole with all forms and code. In this
we tested all the functionalities in the System. All errors in the forms, functions,
modules have been tested.
5.2 Sample Test

To simplify the testing process, the project team followed the different types of tests that break
the testing process up into the distinct levels. These types testing are functional testing (unit
testing, integration testing, acceptance testing and system testing) and non-functional testing
(Security testing).
50 | P a g e
 Unit testing: Unit testing is a validation method in which a programmer tests if

individual units of source code are fit for use. The system units are tested one by one by
inserting invalid data.
 Integration testing: In this testing part, all the modules combined together and tested for
fitness with each other and with the systems functionality. If error occurs in combining
them, the module with problem will be identified and re combined.
 Acceptance testing: Acceptance testing is the process of testing system prior to its
delivery. A system is mainly developed for an end user normally a customer of the
organization. A system is said to be accepted if and only if the user of the system is
satisfied. In this perspective acceptance testing is widely used to prove that system
performs as per the requirements. In acceptance testing the customers provides the input
data to validate the system operation. It is also known as functional testing, black-box
testing, release acceptance, application testing, confidence testing, final testing and
validation testing.
 System testing: It is the final step of testing. In this the team members tests the entire
system as a whole with all forms, code, modules. This form of testing is popularly known
as Black Box testing or System tests. In this the team members tests all the functionalities
in the System. All errors in the forms, functions, modules are tested.
 Security testing: Security testing was done by trying to access the system that is not
authorized. For example without the valid user name and password tester will try to
access the system.
51 | P a g e
Incorrect account that we enter
Figure 22: Sample Security Testing
52 | P a g e
Chapter six
6. Conclusion and Recommendations
6.1 Conclusion
An effort has been made to study web based Gradate Exit Examination system for Ethiopian
higher education institutes as partial fulfillment in Information technology. Web based Gradate
Exit Examination system is computerized Exam taking system, exam marking and view exam
result system automatically. The system solve the problems which occur manually such as un-
readability of candidate answer or question, manual correction error, view results to candidate
after finish exam immediately and other problems which are occur in manual system. The system
is web-based application, which will host in the institute extranet network and is available to the
candidate within the institute as well as the exam setter set or prepare exam question according to
their department and academic year in the system. The exam setter not only prepare exam but
also can update or modify question for own departments. The exam taken to graduate student at
higher education institutes and automatically show the result status of each candidate according
to their identity. This is a very modern and qualified way of candidate assessment technique.
Because it is free from human intervention except adding questions and the software
management.
This project has been prepared with the objective of developing a new web based graduate exit
examination system for different higher educational institutions in Ethiopia The main objectives
of this project are to simplify and qualify the candidate evaluation/assessment mechanism by
providing automatic exam process and exam marking techniques. It provides on time exam
result, with no postpone unless technical problem on computers, electricity happens. The new
system will solve the current system drawbacks by making each Exit Exam questions available
digitally and usable anywhere within the institute network.
53 | P a g e
6.2 Recommendation
To use the system properly the all candidate must take computer training. The extranet network
connection must also available in all places. In addition to these the electricity must available in
all place and the users must be familiar to the system.
6.3 Future Enhancement

According to scope of our project the team develops web based application. Because of the time
constraint we may have limitation which should be consideration in, but in the feature the team
believes that this system should be fully operationally by adding some functionality that are not
included in the proposed system. We also want to recommend this project can be expanded and
more automated with additional functionalities by integrating with many new technologies. We
recommend being included the following functionality:
 Online Payment system when candidate take Rexam
 subjective questions
 Digital signature that identifies the correct candidate
 Make the exam fully automated
 Develop better security mechanism
Generally the project will be better for the future, when we add the above future enhancement
that the candidate can take any type of question as well as make payment during take
reexam.therefore in the future will including these future enhancement by integrating with many
new technologies is the better way of developing the system.
54 | P a g e
References
[1] "System Develpment model," [Online]. Available: http://www.google.com. [Accessed 16 November

2010].
[2] "LAW School and Health medical college Interview," Debre Markos univesity, 01 Sep, 2003.
[Online]. [Accessed 05 Nov 2010].
[3] "Revised LL.B Exit Examination Guidlines Education Strategy center and Consortium of Ethiopian
Law School," [Online]. [Accessed 15 Nov 2010].
[4] "What are front-end and back-end programing language," [Online]. Available:
http://www.google.com. [Accessed 15 November 2010].
[5] "Software requirnment specification," [Online]. Available: http://www.google.com. [Accessed 20

November 2010].
[6] "UML Modelling Diagram," [Online]. Available: http://www.google.com. [Accessed 02 December

2010].
55 | P a g e

Web Based Graduate Exit Examination System

Uploaded by

Document Information

Original Description:

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

Web Based Graduate Exit Examination System

Uploaded by

Copyright:

Available Formats

Web Based Graduate Exit Examination System For

Ethiopian Higher Education and Institutes

IN PARTIAL FULFILMENT FOR THE AWARD OF THE DEGREE OF

DEPARTMENT OF INFORMATION TECHNOLOGY

Acronyms and Abbreviations

2.1 Overview of the Existing System.......................................................................................................... 10

Chapter six .................................................................................................................................................. 53

FIGURE 1: USE CASE DIAGRAM .............................................................................................................................................3

1.2 Background of the Project

1.3 Problem Statement

1.4 Objective of the Project

1.4.1 General Objective

1.4.2 Specific Objective

1.5 Scope of the Project

1.6 Limitation of the Project

 Online payment system when candidate take Rexam

1.7 Significance of the Project

1.8 System Requirements

1.8.1 Hardware Requirement

1.8.2 Software Requirement

1.8.3 Programming Language

I. Back-End Programming Languages: are programming Languages that run on browser

II. Front-end programming Languages: are programming Languages that run on

1.9.1 Data Collection Approaches

1.9.2 The System Analysis and Design Approaches

1.9.3 The System Development Model

1.10 Feasibility Study

1.10.1 Technical Feasibility

1.10.2 Economical Feasibility

1.10.3 Operational Feasibility

1.10.4 Legal Feasibility

2.1 Overview of the Existing System

2.2 System Requirement Specification

2.2.1 Functional Requirements

 Exam management section: these section includes

2.2.2 Non Functional Requirements

2.2.2.1 Technical Requirement

2.2.3 Business Rules

2.3 System Requirement Analysis

2.3.1 Actor and Use Case Identification

Table 1: Use Case Identification

Use Case ID Use Case Name Include

UC03 View result UC01

UC05 View notification UC01

UC06 View report UC01

UC08 View exam question time UC01

UC10 View comment UC01

UC11 Send comment UC01

UC13 Manage account UC01

UC15 Prepare questions UC01

UC16 Update user info UC01

UC18 Specify exam date UC01

UC21 Send candidate info UC01

UC22 Specify exam passing score UC01

UC23 Logout UC01

2.3.1.1 Use case diagram

The use case diagram of the system can see below.

View notification include Include

view report include include post notice

Logout view comment

Specify exam time

Figure 1: Use Case Diagram

2.3.1.2 Use Case Description