DEBRE TABOR UNIVERSITY

FACULITY OF TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY
WEB BASED CENTER OF COMPETENCE (COC) MANAGEMENT SYSTEM
FOR FEKEDE EGZI COLLAGE
In partial fulfillment of the requirement for the degree of B.SC.

In Information technology

By Group 9 members
Name Id number
Wassie Baye IT®057/08
Yilkal Kidie IT®081/08
Degisew Ademe IT® 080/08
Tilashwork Eshetie IT® 117/08

DTU ETHIOPIA
June 19/10/2011 E.C
 DEBRE TABOR UNIVERSITY
FACULITY OF TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY
Web based Center of Competence (CoC) Management System
Submitted
In partial fulfillment of the requirement for the degree of B.SC.
In Information technology

By Group 9 member
Name Id number
Wassie Baye IT®057/08
Yilkal Kidie IT®081/08
Degisew Ademe IT® 080/08
Tilashwork Eshetie IT® 117/08

DTU ETHIOPIA
June 19/10/2011 E.C
Declaration
We declare that this project is our original work has not been presented for degree in this or any
other university, and all the source of materials used for the project have been acknowledged.

Name ID No Signature

1 ------------------------------------ --------------------- ---------------

2 ------------------------------------ --------------------- ---------------

3 ------------------------------------ --------------------- ---------------

4 ------------------------------------ --------------------- ---------------

College: Technology Department: IT

This project has been submitted for examination with our approval as a project advisor.

Main advisor’s Name: -------------------------------- Signature: ----------------------------------

Co- advisor’s Name: -------------------------------- Signature: ----------------------------------

DTU ETHIOPIA

June 19/05/2011 E.C

i
 ACKNOWLEDG
MENTS
First of all, we would like to thank Our GOD for helping us from the beginning to the
end of the project. The team would like to give deepest thanks to those who helped us
for accomplishment of this project.

Secondly, we would like to say thanks with great respect to our advisors Mr. Nibretu Kebede
who gave us pertinent guidance and helps to throughout this project accomplishment.
Thirdly, we would like to thank the Information Technology department staff who gave us
different course throughout our university life.
Finally, we would like to thank our friends and classmates for their suggestion and
comments to the project.

ii
Executive summary
The center of competence Exam information Examination management system of Fekede Egzi
College is done manually, like Students registration for center of competence, exam
management, level management.

The institution has the following problem, like question management, Account Management and
center of competence examination management. Center of competence –information
management system, the proposed system solve the problem in the existing system and make it
simple. It is a web-based application, which host in the institute local area network and is
available to the students within the institute. It allows administrator users to add questions, view
students’ results and other functionalities. It provides web-based exam to students and
automatically show their exam results. As a result, we recommended Fekede institutions that
provide center of competence exams to introduce this new automated system. So that it handles
the overall examination processes from starting the exam up to showing final result.

iii
Contents

Declaration...................................................................................................................................................i
ACKNOWLEDGMENTS..............................................................................................................................ii
Executive summary....................................................................................................................................iii
Contents......................................................................................................................................................iv
List of Tables..............................................................................................................................................vi
List of Figures............................................................................................................................................vii
Acronyms and Abbreviations....................................................................................................................viii
Chapter one: Introduction............................................................................................................................1
1.1 Background of the Organization........................................................................................................1
1.2 Existing System Study (Article Review)...........................................................................................1
1.3 Statement of the problem...................................................................................................................2
1.4. Objective of the project....................................................................................................................3
1.4.1. General objective.......................................................................................................................3
1.4.2. Specific Objectives....................................................................................................................3
1.5. Scope and limitations of the project..................................................................................................3
1.6 Significance of the Project.................................................................................................................4
1.7 Feasibility of the Project....................................................................................................................4
1.7.1 Technical Feasibility...................................................................................................................5
1.7.2 Economic Feasibility..................................................................................................................5
1.7.3 Operational Feasibility................................................................................................................6
1.8 Methodology.....................................................................................................................................6
1.8.1 Data gathering techniques...........................................................................................................6
1.8.2 Design Methodology..................................................................................................................7
1.8.3 Implementation Methodology.....................................................................................................7
1.8.4 Testing Methodology..................................................................................................................8
CHAPTER TWO: REQUIREMENT ANALYSIS DESCRIPTION/SYSTEM FEATURES....................10
2.1 Overview of the Existing System.....................................................................................................10
2.1.1 Activities of the existing system...............................................................................................10
2.1.2 Problems of the existing/current system...................................................................................10

iv
 2.1.3 S (strength), W (weakness) analysis.........................................................................................12
2.2 Overview of the Proposed System...................................................................................................12
2.2.1 Functional Requirements..........................................................................................................12
2.2.2 Nonfunctional Requirements....................................................................................................13
2.2.3 System Requirement (Hardware and Software Requirement)...................................................13
2.2.4 User Requirement.....................................................................................................................14
2.2.5 Business Rule...........................................................................................................................14
CHAPTER THREE: SYSTEM MODELING...........................................................................................16
3.1 Use Case Model...............................................................................................................................16
3.1.1 Actor Specification...................................................................................................................16
3.1.2 Use case Diagram.....................................................................................................................16
3.1. 2 Use case description.................................................................................................................18
3.2 Sequence Diagram...........................................................................................................................24
3.3 Class diagram..................................................................................................................................30
3.4 Activity Diagram.............................................................................................................................32
CHAPTER FOUR: SYSTEM DESIGN....................................................................................................38
4.1 Design Goal.....................................................................................................................................38
4.2 System Decomposition....................................................................................................................38
4.3 System Architecture........................................................................................................................39
4.4 Deployment Diagram.......................................................................................................................40
4.5 Persistence Data Management.........................................................................................................41
4.6 Access Control and security Policy.................................................................................................42
CHAPTER FIVE: IMPLEMENTATION..................................................................................................44
Implementation and Testing......................................................................................................................44
5.1 Tools and environment....................................................................................................................44
5.1.1 Hard Ware tool.........................................................................................................................44
5.1.2 Software tool.............................................................................................................................44
5.1.3 Environments................................................................................................................................44
5.2 Algorithm (used).............................................................................................................................45
5.2.1 Algorithm for Login.................................................................................................................45
CHAPTER SIXS: TESTING.....................................................................................................................57
6.1 Unit testing......................................................................................................................................57
6.2 Integration testing............................................................................................................................58

v
 6.3 System testing..................................................................................................................................58
6.4 Acceptance testing...........................................................................................................................58
CHAPTER SIVEN: CONCLUSIONS AND RECOMMENDATIONS....................................................60
7.1 Conclusion.......................................................................................................................................60
7.2 Recommendation.............................................................................................................................61
Reference...................................................................................................................................................62
Appendix...................................................................................................................................................63

vi
List of Tables

Table 1. 1project budget..............................................................................................................................5

Table 1. 3 software requirements.................................................................................................................7
Table 1. 4 hardware requirements................................................................................................................8
Table 1. 5 login unit testing.......................................................................................................................9Y
Table 3. 1 use case table for login.............................................................................................................18
Table 3. 2 use case description for User Account......................................................................................19
Table 3. 3 Use case table for Manage exam..............................................................................................20
Table 3. 4 Use case table for report...........................................................................................................20
Table 3. 5 : use case table for send Feedback............................................................................................21
Table 3. 6 Use case table for view feedback..............................................................................................22
Table 3. 7 pay fees.....................................................................................................................................23
Table 3. 8 use case description for Log Out...............................................................................................24
YTable 4. 1 access control and security policy

Y
Table 6. 1 unit testing................................................................................................................................57

vii
List of Figures
YFigure 3. 1 Use case Diagram for proposed system....................................................................................
figure 3. 2 sequence diagram for login......................................................................................................25
figure 3. 3 create account...........................................................................................................................26
Figure 3. 4 sequence diagram for pay fees.................................................................................................27
figure 3. 5 sequence diagram for candidate registration.............................................................................28
figure 3. 6 sequence diagram for add question.........................................................................................29
figure 3. 7 sequence diagram for generate report.......................................................................................30
figure 3. 8 Class diagram for proposed system..........................................................................................31
figure 3. 9 activity diagram for login........................................................................................................32
figure 3. 10 activity diagram for create account........................................................................................33
figure 3. 11 activity diagram for registration............................................................................................34
figure 3. 12 Activity diagram for evaluating exams..................................................................................35
figure 3. 13 activity diagram for send comment.......................................................................................36
figure 3. 14 Activity diagram for COC exam preparation 37

Y
figure 4. 2 system decomposition..............................................................................................................39
figure 4. 3 system architecture...................................................................................................................40
figure 4. 4 deployment diagram.................................................................................................................41
Figure 4. 5 persistance diagram.................................................................................................................42
figure 5. 1 create account form.................................................................................................................56
figure 5. 2 student certificate.....................................................................................................................56

viii
Acronyms and Abbreviations
COC Center of Competence
COC-IMS Center of Competence information Management System
CSS Cascading Style Sheet
DB Database
DBMS Database Management system
EPS exam preparation section
GB Giga Byte
Info Information
Js JavaScript
MS Microsoft
PHP Hyper preprocessor Scripting language
SQL structural query language
UML Unified Modeling Language

ix
Chapter one: Introduction
The COC Exam information management system of Fekede Egzi College is manual, like
Students registration for COC, exam management, level management. The college has the
following problem, like question management, account management and COC examination
management. COC examination is an exam content which covers all courses in the level within
the institution. It provide for each student of the collages in their levels. Web-based examinations
content to focus on creating effective assessment questions and focusing on exam’s feedback
delivery to candidate. As the modern organizations are automated and computers are working as
per the instructions, it becomes essential for the coordination of human beings commodity and
computers in an organization.
1.1 Background of the Organization
Fekede Egzi College is an organizations in Amhara region at Debre Tabor city. It established in
1997 E.C by teacher association training cycle and continues its work . The organization gives
certificate for candidates after take the exam. This organization gives different level in different
departments these are level one, level two, level three and level four. The COC Exam in Fekede
College is given in four level and in different ways like oral exam, practical exam, and written
exam.
Objective of the organization
Fekede Egzi College is ultimately devoted to push the nation developmental thrive a step
forward through building citizens technical, theoretical, and attitudinal competence through
education.
Vision
By 2020 Fekede Egzi College will be a center of excellence and the institution of choice for
highly qualified students in Amhara region.
Mission
Fekede Egzi College strive to become leading college creating conducive modern teaching
learning environment and dedicated the advancement of the academic excellence in the
diversified programs of higher education.
.

1
1.2 Existing System Study (Article Review)
The existing/current system is very tedious and time consuming because everything is
Performed manually. The COC examination is given for candidates by the assessors who come
from the COC center of Amhara region. In the existing system of COCIMS the supervisor
Controls/manages all activities during and after the COC examination takes place. The COC
Exam information Examination management system of Fekede collage is doing manually, like
Students registration for COC, exam management, level management, question, COC
examination is a final assessment mechanism for the sake of educational quality assurance. The
previous exam papers are simply stored in the exam storage place and after evaluations, it is
burned, and then any candidate cannot get any information about the COC examination question
paper.
1.3 Statement of the problem
Certificate of COC –pass and fail are managed manually. This means using papers and/or
general purpose application software like MS - word, MS-Excel simply by hands. It is not stored
in centralized database. So, searching and retrieving information for each candidate is tedious
and time consuming. These are:-
Manual student registration for COC exam. This means that the director must fill all
information on the paper in Fekede College the center of competence then he/she can get id
number from the center. It may be leads loss of relevant information and take more time.
Print based exam. It is more tedious and it may be stole the examination by someone and also
occurs wastage of resources since it need extra paper.
Report structure (pass or fail) is manually worked. Pass or fail of candidates in the exam is
managed manually. It may be a corruption.
Delay of exam marking and result report viewing. When the delay of examination mark and
result the candidate get bored and also the director get confuse.
Time wastage. When the candidate come to see their result there is time wastage because of all
works are manual.
Many exam marking related mistakes. May be the teacher or the student make a mistake
because of their known or unknown mistake.
It needs large number of examiner. This also obvious it takes a many number of examiner as
well as supervisor and when it needs large amount of human resource the wastage also increases.

2
Exam distribution process problem. This examination distribution process is not equal time
interval for all candidates.
Wastage of resources. It needs too much amount of paper and cost.
Generally, the COC Exam information management system of Fekede College is not
computerized. Rather most of the works are done on paper based. Like:-
 Candidate’s registration process.
 Exam distribution process.
 Result report structure.
 Security mechanism regarding to data processing.
1.4. Objective of the project
1.4.1. General objective
The main objective of this project is to develop web based COC information management system
For Fekede Egzi College.
1.4.2. Specific Objectives
The specific objective of our project is used:
 To gather required information for proposed system.
 To analyses the existing system and find out the problem.
 To design interactive and user friendly interfaces
 To design and implement a database for the proposed system.
 To design and implement exam for the proposed system.
 To Test and deploy the proposed system.
1.5. Scope and limitations of the project
The scope of the project is to develop web based COC Exam for Fekede College. The project
focus on:-
 Student registration for COC
 Create account for users
 Level management such as level 1,level 2,level 3 and level 4
 Exam paper generation
 Upload exam and exam result
 Time management

3
Limitation of the project
This project does not cover the following activities:-
 It is not used by night blind candidates
 It cannot give all practical exams.
 It cannot recover when Power dawn off.
1.6 Significance of the Project
The proposed project is useful for the Fekede College to perform works in a simplified way.
Since the Fekede College is using the manual system it takes time and much human power, so
developing an automated system for Fekede College to perform its work in a short Period of time
and little human power with little resource consumption. So the project is crucial for the Fekede
College.
The proposed system has the following significances for the institution.
Reduce processing errors
Manpower reduction
Can reduce the amount of paperwork involved
Save registration time
It avoids data redundancy or Error reduction.
Provide higher data backup
Reduce resource requirements or unnecessary wastage of resource.
Increase system performance
Improve candidate satisfaction
Better decision making
Better service to the candidate.
Improved candidate’ motivation by avoiding paperwork.
1.7 Feasibility of the Project
Feasibility study is essential to evaluate the cost and benefits of the new system.
Need of the feasibility study:
 It determines the potential of the existing system.
 It used to determine/finds out the problem of the existing system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing system.

4
 To identify the weakness and strength of the new system.
1.7.1 Technical Feasibility
The proposed system doesn’t require much technical expertise person. The system is developed
by using Technological system development techniques such as PHP, Java script, CSS and
MySQL Database without any problems and the group members have enough capability to
develop the Project so the system is technically feasible.
1.7.2 Economic Feasibility
The system which we are going to develop would have economic benefit. Those economic
benefits may be tangible or intangible.
Tangible benefit: This means the concrete benefit that can be expressed in terms of dollars or
birr. So the system proposed to develop would decrease a lot of birr that was expensive to buy
the hard copy document material such as paper, pencil, rubber, and so on. Also reduce the loss of
data that means if it reduces the loss of data it also reduces the cost of replacing the lost data.
Some of the tangible benefits are.
Less human power: it reduce human work load.
Cost reduction: the system reduce cost of buying paper.
Intangible benefit: the benefits that cannot be expressed in terms of birr or dollar.
Table 1. 1project budget

No Items Quantity Unit price Total price

1 Paper 75 0.5 birr 32.3 birr
2 Pen 6 5 30 birr
3 Flash disk(8GB) 2 220 440 birr
4 Laptop 1 12,000 12,0000 birr
5 Mobile card 14 10 140 birr
6 Transport 16 3 48 birr
7 Print 65 page 1.5 birr 92.5 birr
8 Binding 2 15 30 birr
TOTAL 12,802.8 birr

1.7.3 Operational Feasibility

The system is developed to provide accurate, active, secured service and decreases labor of
Workers and also it is not limited to particular groups or body. And also it is plat form
independent i.e. it runs in all operating system, and devices.

5
1.8 Methodology
1.8.1 Data gathering techniques
Different fact finding techniques used to gather information about the current system. It is the
fundamental activity for the development of the system. In order to collect information for the
proposed project, the team members use the following methods.
Observation: Observation is one of the most important methodologies to gathering information
by physically going to the place and looks how the current system works. It is very difficult for
humans to explain what they do or to describe accurately how they achieve a task, so observation
is very crucial to gather information.
we have seen some paper forms used for registering candidates, transcript forms filled with
candidate mark, other manual works, for example how they prepare College weekly schedule,
some notification boards, how Candidates fill COC exam forms and College resources needed to
implement our project, like Internet connections, computers and how much they are satisfied
after successful completion of the project.
Interview: Interview is another important methodology to gathering information by unstructured
method. It helps us to get crucial and important information about the overall view of the current
system.
Generally, we have grasp different information’s about the current scenario of Fekede College
center of competence, from these we have understand the current system of Fekede College is
Manual, because they have used paper in order to generate report, registration, giving exam,
Evaluation of exam result. We have seen different activities related with COCIMS for Fekede
College by direct visiting the Fekede College. As we have seen from most of the COCIMS are
done by manual, and this leads to loss of data, redundancy of information/ data, corruption, error
prone generation of report, time wastage for registration, and viewing result, missing information
about COCIMS. We also have analyzed more information’s by making an interview to Fekede
College workers. They told us the COCIMS of Fekede College is manual because they used
papers to generate reports, preparing grade report, evaluate exam, status report, and summary of
reports, certificates, and taking examination. So our team is going to plan to automate this system
to solve the problems of COCIMS of Fekede College.

6
1.8.2 Design Methodology
To design the system the project team has choose Object Oriented Modeling techniques and
unified modeling language tools. Reason for choosing:
 It enables us to comprehensively model a system to be developed.
 Modification of the object implementation is easy because objects are loosely coupled.
 Understanding of the structure is easy because object oriented modelling and tools used to
represent real world entities.
In the system analysis and design phase of a project we use the web design approach that
examines requirements from the perspective of the web pages and web servers found in the
problem domain.
1.8.3 Implementation Methodology
The implementation is the final and important phase, once the design phase has already finished,
the next task is the issue of implementation. The implementations have been performed by
software called notepad++ or sublime text. Therefore the validation activity has been performed
by a java script.

Software tools and Hardware tools

Table 1. 2 software requirements

Software tools Description

Php Server side scripting language.
Java script Client side scripting language.
Notepad++ Free text editor and source code editor that can be used for
HTML, PHP, CSS and JAVA SCRIPT.

HTML Client side coding.

MS-word For preparing documents.
MS-Power Point For preparing the slides for presentation.

Micro soft Visio 2013 For designing UML diagrams associated with the project.
Axure RP 8: For design user interface.
Visual paradigm 14.2: For design persistance diagram.
Web browser Used as main tool for accessing data online.
MySQL Used for storing and querying data.

7
 WAMP Implementation application.
Front end: - css, html, JavaScript
Back end:- php, wampserver, xampp

Table 1. 3 hardware requirements

Hardware tools Description

Printer: For printing document we are developing.
Paper, pen, etc. For writing the requirement.
USB flash: For transferring data from one pc to another
pc.
RAM: For data storage.
Personal Computer: for doing the entire application
(documentation and code).

1.8.4 Testing Methodology

Testing is a process of evaluating the developed system whether it is functional or not and is it
fulfill all the requirements or not .we are o develop a system, so we should predict the type of
testing that is important for our system. There are many testing techniques including:-
Unit testing:-testing each component one by one. Each component of the system would be
tested by the team members while doing the implementation of the system.

Table 1. 4 login unit testing

Unit to Test = Authentication of login users
Assumptions = Login into appropriate page
Test Data = User Name(empty , invalid user name, valid username)
Password (empty ,invalid password, valid password)
Steps to be Executed Data Expected Results (display message)
Empty Username and Any invalid data for Please check User name and password
password and Click Login the other fields
button
Enter invalid User name, Any invalid data for Please check User name and password

8
 password and Click Login the other fields
button
Enter valid username ,empty Any valid data for Please check User name and password
Password and Click Login the other fields
button
Enter valid password ,empty Please check User name and password
Any invalid data for
user name and Click Login
the other fields
button
Enter valid Username and All fields Fulfill with Login in to approprate page
Password then Click Login valid data
button

Integrating testing:-testing the whole component once and testing how they perform tasks
when they are integrated. This is a testing technique that tests the whole system once.
Acceptance testing:-is a testing technique performed to determine whether or not the software
system has met the requirement specifications. It is formal testing with respect to user needs,
requirements, and business processes conducted to determine whether or not a system satisfies
the acceptance criteria and to enable the user authorized entity to determine whether or not to
accept the system. The client satisfying all the requirements specified by them has also
developed the software within the time limitation specified.

9
CHAPTER TWO: REQUIREMENT ANALYSIS DESCRIPTION/SYSTEM
FEATURES
2.1 Overview of the Existing System
The COC Exam given in Fekede College in different ways like oral exam, practical exam, and
written exam. The existing/current system is very tedious and time consuming because
everything is performed manually. The COC examination is given for candidates by the
assessors who come from the COC center of Amhara region. The COC Exam information
management system for Fekede College is doing manually, like Students registration for COC,
exam management, level management, question management, COC examination is an
examination, which is provided to college students as a final assessment mechanism for the sake
of educational quality assurance. The previous exam papers are simply stored in the exam
storage place and after evaluations, it is burned, and then any candidate cannot get any
information about the COC examination question paper.
2.1.1 Activities of the existing system
The major functions in the current/ existing system are:-
 student registration for COC
 Report generation
 Prepare examination and give examination for students
 Submission of candidate result
 Giving certificate for students
 Generate status report
 Give the certificate to the students
2.1.2 Problems of the existing/current system
As we have seen from the existing system by some methodologies such as unstructured
interview. It is not preferable for the students since everything is manual. The major problems
found in the existing system are: -
Performance Related Problem
The problem which is resided in the current system is performance. We are measuring the
Performance of the current system in terms of time. The times takes by the current system for
Providing information about the service provider to user is so slow.
 The work procedure is error prone.

10
 Poor performance. Information related problem
 Miss handling of candidate information occurs.
 Data is stored redundantly in multiple files (paper).
 Data is not easily accessible.
 Data is not well organized.
 Data is not secure from accident (damage).
Efficiency Related Problem
 Since the work is performed manually the efficiency of the working system is poor.
 The data is stored in redundant manner; the information generated also is redundant.
 As the number of the students increase the resources wasted for printing exam paper also
increase.
Control Related Problem
 Since the current system use manual system it is easily expose to security problem. The
existing system use hard copy document to store data and it may be stole by unauthorized
user easily and it causes a serious problem.
 Security is another big issue concerning manual based system since The files stored
physically if they damaged there is no back up
 Exam management:-Many exam marking related mistakes and corruptions since the exam is
marked by humans.
Cost in terms of time is high.
In addition to that it needs more stationary materials due to data duplication, errors, and storage
as number of students increase.
Service related problem
 The candidates do not get better service as they need,
 Then candidates do not satisfy with service.
Time Consuming
 COC exam process.
 View own exam results.

11
2.1.3 S (strength), W (weakness) analysis
 Strength: - The institution works 12 hours per a day therefore the candidate can gate free
access, they try to deliver the right item to the right user even in manual case, managing lots
of data on paper even data loss occurs some time.
 Weakness: - The current manual system exposes to lose important documents on the director
like student exam result, registration list, etc. farther more the weakness is listed above.
2.2 Overview of the Proposed System
The overview of the proposed system is designed to address the problems of the existing manual
system of CoC management system. The proposed system solves the entire problems in the
existing system. Controls all the data input and error which happen during CoC management
system. The new system would be able to access and retrieve different data effectively and
efficiently. The proposed system would be able to:
 Secured data , operational efficiency and effective manner
 Increase response time.
 Reduce time wastage.
 Give data availability and confidentiality.
 Achieve quality service delivery.
 Generate report.
 Retrieve the data from the database.
 Update and manipulate the database.
 It is easy to use (user friendly).
 Reduce wastage of human power.
2.2.1 Functional Requirements
The new system has the following main functionalities (functional requirements).
Exam preparation: A COC Exam preparation section can add questions, remove questions and
view all questions of a given level. The COC exam preparation section manages question.
Result generation: the students view his/her result after exam completed.
User Account Management:
The system has different account types.
 admin account
 Director Account

12
 student account
 Exam preparation section account
 Exam evaluation section account
 Candidates are allowed to be registered with their detailed information for taking COC exam
by director of the organization.
Examination Module: The examination module is including the examination question of the
COC exam, and it contains all items of the question. Such as:- Choice question, blank space
questions and true or false questions. The modules are prepared by the EPS.
Repository Module: The Repository module contains the previous exam question modules,
work sheets, working procedure modules, and exam guidelines which uploaded by the
organization director.
Registration
The system shows appropriate message if the item written to search box doesn’t much with the
items registered previously. The candidates don’t register without payment.
Candidates can print certificates after take the CoC exam.
2.2.2 Nonfunctional Requirements
This requirement is related with advantages of the new system which is developed up on the
existing manual system. It is a requirement related with quality of the system and its usability. It
also related with system security, ease of training, ease of maintaining (documenting works).
Some of the nonfunctional requirements are:
Performance: The amount of time needed to get the response for a transaction or request is
minimized. The system has fast response time because of a light weighted code in HTML, PHP,
CSS and JavaScript.
Portability: The system is accessible both in computer and mobile devices. Which means the
system is compatible in every platform (any windows operating system and mobile devices).
Thus it is portable for user.
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.3 System Requirement (Hardware and Software Requirement)
Software requirements: are requirements that are used to implement the system we are using,
Html: To create web applications forms.

13
Micro soft Visio 2013: To design (for drawing diagrams).
Axure RP 8: for design user interface
Visual paradigm 14.2: for design persistance diagram.
MS word 2007: for writing documentation.
Paint: for editing.
Window 7 & 10 Operating system: to implement the documentation and the code.
Wampserver and Xampp: for creating database and tables.
Front end is:- css, html, JavaScript
Back end is:- MySQL, php, wampserver, Xampp
Hardware requirements: -
 Printer: for printing document.
 Paper, pencil, pen, etc. for writing the requirement.
 Hard drive (USB flash): For transferring data from one pc to another pc.
 RAM: for data storage.
 Personal Computer: for doing the entire application (documentation and code).
2.2.4 User Requirement
They are the basic requirements that the user needs to operate with the new system; the following
are some of the user requirement that our system needs to communicate with user.
 User should have basic computer skill.
 User should know English language.
 User should have electronic device pc.
 User should have their own privilege (account).
2.2.5 Business Rule
Identifying the business rule of the proposed system help us to specify and describe each use
case in effective way. The business rules of the COC information management system are listed
as following:-
BR1: The students should be legible.
BR2: The students must pay the fee in order to register.
BR3: The students should be register.
BR4:- They should have a take along unique ID that expresses his/her IDENTITY.
BR5:- The students should have to take the exam within the given time.

14
BR6:-The exam should not be duplicated.
BR7:- No students can take a particular exam more than once.
BR8:- The examinations are all objective. Students can take each Exam just once.
BR9:- the students should fills the requirements care fully
BR10: all students must take the same exam according to level and department.

15
CHAPTER THREE: SYSTEM MODELING

3.1 Use Case Model

A use case is an interaction between users and a system. It captures the goal of the users and the
responsibility of system to its users. It is the functionality of the system or the service provided
by the system.
3.1.1 Actor Specification
Actors are users of the system or external entities in which they interact with the system. An
actor reprsesents a coherent set of roles that are entities external to the system can play in using
the system, rather than representing a particular individual. Our proposed system has (include)
the following Actors with different role.
 System admin
 Director
 Candidate
 Exam preparation section
 Examiner
3.1.2 Use case Diagram
A system use case model, also known as concrete use case model or detailed use case model,
depicted below models our analysis of behavioral requirements, describing in detail how users
work with our system. Specifies what the system does for the actors or it is a sequence of action
that provides a measurable value to an actor.
 Plays a key role in modelling the behaviour of a system or subsystem.
 Consists of a set of use cases, actors and their relationships.
 Describes a way a real world interacts with the system.
 Documents the functional requirement of a system.

16
 CoC management system for Fekede Egzi collage

Approve exam
create account
Disapprove exam
Admin EES
Add course
Logout

Add deparment

view feedback upload exam

<<include>>
<<include>>
<<include>>
Remove exam
EPS
change password <<include>>
<<extend>>

<<include>>
view student result
<<include>> <<include>>

Approve transfer
<<include>> view feedback
<<include>>

<<include>>

<<include>>
Disapprove transfer <<include>> Manage time
<<include>> <<include>>
Director
Login Student
<<include>> <<include>>
Add practical exam value take exam
<<include>> <<include>>

view student result <<include>> <<include>> request transfer

<<include>>

<<include>>
Upload file send feedback
<<include>>

Register student View result

fee payment

Print certeficate

Figure 3. 1 Use case Diagram for proposed system

17
3.1. 2 Use case description
Table 3. 1 use case table for login

Use case name Login

Use case ID Uc1
Participating actor Administrator, Director, Candidate, Exam preparation section,
Examiner
Pre-condition The user must have valid user name and password
Description System user must login using user name and password to use the
System.
Basic course of action 1. Display login page
2. enter username and password
3. Click login button
4. System verifies username and Password.
5. User authenticated and gets access to the system.
6. Use case ends.
Alternative course of A1. User is not authenticated and is denied access to the system.
Action A2. System displays an incorrect username and password message.
A3. System enables user to try again.
A4. Use case returns to step 2 to fill the correct username and
password.
Post condition User gets access to the system according to their predefined
System privileges.

Table 3. 2 use case description for User Account

Use case name Manage user account

18
 Use case ID Uc2
Participating actor Admin
Pre-condition Admin must have privilege to access site.
Description 1.This use case should allow an admin to create and manage user account on the
privileges of the user.
2.By using this user account, users would be able to login to the system or into any
specific system directly.
initial condition The admin opens the system login with his/her page..
Basic course of action 1.Admin selects the user type i.e. whether he/she wishes to create
‘a user’ or ‘an administrator’.
2. System prompts to fill the user detail information.
3. Admin fills all mandatory fields.
4. Click create button to create the data
5. If the new user name, password,first name and last name is not
found in user account database,
The new user account created Successfully.
6. Use case ends.
Alternative course of A1. If the user is already registered, the system show success message to admin.
action.
Post condition The user use their account based on the privilege.

Table 3. 3 Use case table for Manage exam

Use case name evaluate Exam

Use case ID Uc3
Participating actor Examiner
Pre-condition The user must login to the system.

19
 Description This use case is initiated by the Examiner. This use case describes
how the Examiner evaluates questions in web-based Examination
System such as valid or not.
initial condition The user opens the home page of the system.
Basic course of 1. The user enters username and password.
action 2. System displays the Exams.
3. Then users see and evaluate questions based on the question rules.
4. Use case ends.
Alternative course of A1. User is not authenticated and is denied access to the system.
action. A2.Exam is not display tray again upload.
A3.the question is not fulfilling the required criteria tray again fill it.
Post condition Examiner evaluates exam questions and display successfully evaluated
message to the COC exam preparation section.

Table 3. 4 Use case table for report

Use case name View report

Use case ID Uc4
Participating actor Director.

Pre-condition Student must fulfill the required information and rules.

Description System shall allow generate report for candidate exam
Information.
initial condition The user opens the home page of the system.
Basic course of action 1. Director Open home page.
2. Director Logged to home page.
3. Director Click report link.
4. System Display report.
5. Director view exam result report.
6. Use case ends.
Alternative course of A1: If the user doesn’t have access privilege to use the system;
Action User is not authenticated and is denied access to the system.
Post condition Report be generate

20
Table 3. 5 : use case table for send Feedback
Use case name Send comment.
Use case ID Uc5
Participating actor Examiner.
Pre-condition All require fields of form are correctly fill by the Examiner
Description This use case is initiated by EPS. This use case describes how
Examiner sends feedback to EPS.
initial condition The user opens the home page of the system.
Basic course of 1. The Examiner login to the system.
action 2. The Examiner writes comment.
3 Examiner click send button.
4.use case ends
Alternative course of A1.If the form is not fulfilled, the system displays error message.
Action A2. System enables user to try again.
A3.The user fills the correct input.
A4.use case end.
Post condition The Examiner successfully send comment.

Table 3. 6 Use case table for view feedback

Use case name View comment

Use case ID Uc6
Participating actor EPS.
Pre-condition The Examiner must look the exam and write comment
Description This use case is initiated by EPS. This use case describes how
EPS view comment.
initial condition The user opens the home page of the system.
Basic course of 1. EPS open Home page
action 2 .EPS click comment link.
3. System Display comment.
4. EPS delete comment
5. Use case ends.
Alternative course of If there is no comment, return error message that inform Examiner
action
Post condition The Examiner sends notification to EPS and EPS save exams

21
Table 3. 7 pay fees
Use case name Pay fee
Use case ID UC 7
Participating candidate
actor
Pre-condition Candidate must have a bank account

Description Candidate must be pay money for register and to take the CoC exam.

initial condition Candidate account should have a deposited balance.

Basic course of 1 Candidate click pay button
action 2 system displays the payment form
3 Candidate enter their bank account information
4 system validate whether the Candidate have a bank account and a
deposited balance for the specified account number
5 Candidate click finish button
6 use case end

22
 Alternative A1: If the Candidate did not have an account or a deposited balance the system
course of action display the error message
Post condition Successfully message display and candidate register.

Table 3. 8 use case description for Log Out

Use case name Logout
Use case ID Uc8
Participating actor Administrator, Director, Candidate, Exam preparation section,
Examiner.
Pre-condition The user should have to login first and finish the task.
Description The user wants to logout from the system when he/she has finished
his/her tasks.
initial condition The user opens the home page of the system.
Basic course of 1. Click on logout button
action 2. The system displays the message ‘Are you sure you want to
logout?’
3. Click on ‘No’ button to stay with the system.
4. Click on yes to logout from the system.
5. Finally the system get out of the logged page.
6. Use case ends.
Alternative course of A1.If not needed to logout from the logged page or logout item is
action clicked un intentionally, simply Click on ‘No’ button.
Post condition User logout(remove) from the system

3.2 Sequence Diagram

Sequence diagrams describe interactions among classes in terms of an exchange of messages

23
over time. They're also called event diagrams. A sequence diagram is a good way to visualize
and validate various runtime scenarios. it helps to predict how a system behaves and
to discover responsibilities a class may need to have in the process of modeling a new system.

users home page login link login form controler

data base
<<actor>> <<ui>> <<link>> <<form>> <<validate>

Initiate the system

Select login sin up link
Click login link

Login form display

Fill user name and password

Click login button

Check validation

Try again display

sucess

figure 3. 2 sequence diagram for login

24
25
figure 3. 3 create account

director director page payment form controler

data base
<<actor>> <<ui>> <<form>> <<validate>

Go to director page
Select payment/ registration link
Fill and send data
Check validation

Try again

Data insert in to data base

Check

payment successfully

Error message display

Figure 3. 4 sequence diagram for pay fees

26
 director director page registration form controler
data base
<<actor>> <<ui>> <<form>> <<validate>

Go to director page
Select registration link
Fill and send data
Fee payment Check validation

Try again

Data insert in to data base

Check

successfully Registered

Error message display

figure 3. 5 sequence diagram for candidate registration

27
 add question
EPS page controler
EPS form
<<ui>> <<validate> data base
<<actor>> <<form>>

Go to eps page
Click add question link

Question detail form is display

Fill question detail

Fill question form display

Fill question

Click submit button

Check validation

Try again
Question add successfully

figure 3. 6 sequence diagram for add question

28
 Examiner Examiner page Report form Validation
Database
<<Actotr>> <UI> <form> <controler>

Go to examiner page

Select report link

Fill report criteria

Check validation

report Check
invalid

Successfully reported

X X X X X

figure 3. 7 sequence diagram for generate report

3.3 Class diagram

Class diagram describes the structure of the system. Objects are instances of classes that are
created, modified, and destroyed during the execution of the system. An object has state that
includes the values of its attributes and its link with other objects. Class diagram describes the
system in terms of objects, attributes, operations, and their associations.

29
 1
System admin Account
Candidate
admin_id varchar()
Firstname varchar() user_id int(25)
lastname varchar() username varchar(25) has user_id int(25)
sex varchar() password varchar(30) fname varchar(24)
lfname varchar(24)
+login() phone_num int(24)
-memberName +logout() sex varchar(25)
-memberName 1 address varchar(33)
hashas
+add account() has age int()
+delete account() ∞ email varchr(34)
+update account() manage
institute varchar(23)
+view report()
level varchar(10)
1 username varchar(26)
1 password varchar(30)
Examiner +payment()
EPS
+register()
take exam()
+create question () user_id int(25) view result()
+view comment() username varchar(25)
1 send comment()
password varchar(30) view comment()
∞ has
+evalute question()
∞ +send coment() 1 1
take
Comment

manage
-comment varchar() 1
Result view
+view()
+send()
cadid varchar() ∞
1 date date()
view
1 fullname varchar ()
level vachar() Question
director institution varchar()
+view result() level question()
user_id int(25) question id()
username varchar(25) timer
question type()
password varchar(30) answer id()
answer type()
+upload module()
+send comment() hr int() ∞
+view comment() min int()
second ()
+set time()
∞ set

figure 3. 8 Class diagram for proposed system

30
3.4 Activity Diagram
Activity diagrams are graphical representations of work flow of activities and actions with
support for choice, iteration and concurrency. We depict activity diagrams of this project as
follows.

open web page

go to login page

enter username &

password

Data is not match fill again

go to login page?

check the db
macth

successfully
login

figure 3. 9 activity diagram for login

31
 check user acc link

dissplay create account

form

enter the required

information

Check the correct Data is not match fill again

intput?

yes no

check
database

account create
successfully

figure 3. 10 activity diagram for create account

32
 login

registration form

pay fees

Required is not success

Is correct?

Yes no

check the db macth

successfully register

figure 3. 11 activity diagram for registration

33
 login

View question

Evalute question

Is it valid? Ni Reject

Yes

Accept

figure 3. 12 Activity diagram for evaluating exams

34
 select requiest

check type of user

Transfer? Ni exit

Yes

system display form

Send

figure 3. 13 activity diagram for send comment

35
 sta rt

Create questions

Se t test type

Add questions

inva lid

correct

Se t test option

Se t test time

Se t total ma rk

figure 3. 14 Activity diagram for COC exam preparation

36
CHAPTER FOUR: SYSTEM DESIGN
4.1 Design Goal
Design goal primarily emerged from nonfunctional requirement of the system and the objectives
of the design goal are to model a system with high quality.
The nature of the design is created by the designer and it is more important for the programmer
to implement a high quality and error free system. The design goal of the system may include
with angle of performance, dependability, and end user criteria.
Generally for the performance criteria the system response time should be fast and reliable and
also should not take up too much disk space. The system must be robust and failure free (fault
tolerant) for supporting the dependability issue. And finally efficiency and satisfaction must be
specified with interactive and easily system usability. To the strict it should consider:
Low operating cost: in performing tasks by using the new proposed integrated system cost
expenditure minimized .For example we need not to have paper, pen and other like the manual
because forms are found in the proposed system we can simply use those.
Easy to use: Because the web application is developed by easy user interactive pages the user of
the web application is feels easy to use.
Easy maintenance: when sometimes failure comes to the new proposed system it maintained
easily.
Security: Management of Fekede College web based CoC exam system should be secured
because on one can’t access the system without the use of his/her privilege code.

Good response time: to make the developed system manage actor’s request in short period of
time.
Portability: In this case the developed system is plat form independent; user can use the system
on every computer
Minimize error: By using the new proposed system the error which happens during in manual
case reduced and makes the process of handling data and records more simple.
4.2 System Decomposition
The importance of decomposing the system in to subsystems in any software development side is
developing and identifying the sub-system from the functional requirements.

38
Admin: - the Admin to manage user account to be add, delete, activate, deactivate the user
account.
Director:-the director prepare module for candidate, generate report; change his/her own
password.
Candidate:- candidate pay fees, register, take exam ,view result and download exam certificate.
Examiner:-evaluate candidate’s exam and generate report.
EPS:-the exam preparation section prepare exam question, manage time and upload question.

create user delete user update user

acc acc acc

upload exam generate

prepare exam time mange
question report
change
evalute exam
password
Admin
<<subsystem>>
generate
report

Examiner CoC Mgt System for EPS

<<subsystem>> Fekede Egzi Collage <<subsystem>>
dawonloade
certificate

pay fee
Director candidate
<<subsystem>> <<subsystem>>

register

take exam

generate change prepare

view result
report password module

chnage
password

figure 4. 1 system decomposition

4.3 System Architecture

In this project the team uses a three tier architecture which has three layers. These three layers
are the Application or Presentation layer, the business layer and the data access layer.

39
Application or presentation layer: is the form which provides the user interface to either
programmer or end user.
The business layer: is the class which the team uses to write the function which works as a
mediator to transfer data from application layer or presentation layer to data layer.
The data access layer: is also a class to get or set data to the database queries back and forth.
This layer only interacts with the database. The database queries or stored procedures would be
written here to access the data from the database or to perform any operation to the database.

CoC management system for Fekede Egzi collage

figure 4. 2 system architecture

40
4.4 Deployment Diagram
Deployment diagram is a structure diagram which shows architecture of the system as
deployment (distribution) of software artifacts to deployment targets. The name Deployment
itself describes the purpose of the diagram. Deployment diagrams are used for describing the
hardware components where software components are deployed. Component diagrams and
deployment diagrams are closely related but Deployment diagrams shows how they are deployed
in hardware. It also used to show the hardware of the system, the software that is installed in the
hardware and also shows how the software and the hardware components work together.

Client browser Application server Database server

TCP/IP PHP/mysql

manage account

Admin generate report

Security

prepare exam

upload exam
Director
time man age

EPS upload exam

view result

Examiner
register

pay fee

Candidate take exam

dawonload certf Database

HTTP

figure 4. 3 deployment diagram

41
4.5 Persistence Data Management
Persistence Diagram shows the relationship between one entities to another entity of objects. The
persistence Diagram increases the maintainability, extensibility and portability of your
application. Persistence Diagram also called data model or Entity relationship (ER) models, are
used to communicate the design of a database, usually a relational database, to both users and
other developers. Persistence are used the schema of database.

Figure 4. 4 persistance diagram

4.6 Access Control and security Policy

Access control is way of limiting access to a system or to physical or virtual resources. In
computing, access control is a process by which users are granted access and certain
privileges to systems, resources or information. In access control systems, users must present
credentials before they can be granted access. In physical systems, these credentials may
come in many forms, but credentials that can't be transferred provide the most security.

42
Table 4. 1 access control and security policy

Function
Actors
Admin Director Candidate EPS Examiner
Login     
Manage user account 
Generate report   
Prepare exam 
View result 
Pay fees 
Manage time 
Evaluate exam 
Change password     
Register 
Take exam 
download certificate 
Logout     

43
CHAPTER FIVE: IMPLEMENTATION
Implementation and Testing
The implementation document helps users on how to work with the system. It acts as a user
manual and it helps users not to be the system confused with. It includes sample forms and some
selected fragment code. It gives the users a brief over view of the system.

This document describes the project implementation for developing the COC-information
management system. The project implements PHP, MySQL and standard HTML. This project is
running on standard internet web browsers. The interface for the project is provide a good
navigation to user of the system with nice look and feel.

5.1 Tools and environment

To develop the system we are going to use different hardware and software tools.
5.1.1 Hard Ware tool
 RAM (Random access memory).
 Laptop Core i3 processor.
 USB flash disk.
 Printer.
5.1.2 Software tool
 Sublime text and Notepad++ tool to design the web pages.
 MySQL database system.
 Wampp server, Xampp server.
 Google chrome, UC Browse, Mozilla Firefox.
 Operating system: Window7.
 Programming languages: - PHP, MSQL, JavaScript, CSS, and HTML.
5.1.3 Environments
The environment is very restrictive for implementing this system as well using it. When we say
this it is impossible to access this system out of coverage of network access mean that it is
connection dependent. Since our system is web based; it is allowed on all operating system, and
all electronic devices that are capable to access web.
When we are develop our system we use the following tools in the development environment.
 Personal computer to be able to run the system.

44
 PHP MYSQL (xampp), software data base system would be used in developing and
managing the database.
 Web browser to run our system which is CoC management system for Fekede collage.
5.2 Algorithm (used)
Before writing any piece of computer code, the team members have to know what the program is
supposed to do. Going straight to coding can be very confusing. Before writing one line of code
in any language, it is a good idea to write algorithms in a simple.
5.2.1 Algorithm for Login
1. Function login (username, password)
2. If password length =0 and password length less than 6
3. Display error message “Please fill username and password “and “password is too short
message display”
4. Return
5. Username=Retrieve user name and Password=Retrieve Password
6. If username! =username and password! =password

7. Display error message “Please check username and password”

8. Return
9. Username= Retrieve username and password =Retrieve Password
10. If username ==username and password =password
11. Display page
12. //end of the function login
Coding

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.
Modern language that used is Hypertext Preprocessor (PHP). The code is made simple in such a
way that another programmer can easily understand and work on that in future.
Sample Code for Login
<div class="col-sm-offset-3 col-sm-6">

<div class="panel">

<form class="form-horizontal" action="login/login.php" method="POST">

45
<fieldset>

<h3 style="background: #005cc2;text-align: center;padding: 6px;font-family:

Georgia;color: #eeeeee"><span >Login</span></h3>

<!-- Text input-->

<div class="form-group">

<label class="col-md-2 control-label" for="email"></label>

<div class="col-md-8">

<input id="uname" name="uname" placeholder="Enter your username" class="form-

control input-md" type="text">

</div>

</div>

<!-- Password input-->

<div class="form-group">

<label class="col-md-2 control-label" for="password"></label>

<div class="col-md-8">

<input id="password" name="password" placeholder="Enter your Password"

class="form-control input-md" type="password">

</div>

</div>

<div class="form-group">

<div class="col-md-offset-2 col-md-8">

<select required class="form-control" name="accout_type">

<option value="">Account type</option>

46
<option value="Administrator">Administrator</option>

<option value="Director">Director</option>

<option value="Department">Exam evaluator</option>

<option value="Instructor">Exam Preparation</option>

<option value="Student">Student</option>

</select>

</div>

</div>

<div class="form-group">

<div class="col-md-offset-2 col-md-8">

<button type="submit" name="login" class="btn btn-primary">Log in</button>

</div>

</div>

</fieldset>

</form>

</div>

</div>

<div class="bg1">

<div
class="row">
</div>

2. Sample Code for Create Account

<?php include
"../connection/dbConnection.php"

47
; session_start();
if(isset($_POST["createaccount"]
))
{ if(isset($_POST["department
"])){
$dep = $_POST["department"];

$acc_type = $_POST["acc_type"];

$fullname = $_POST["fullname"];

$gender = $_POST["gender"];

$username = $_POST["user"];
$password = $_POST["pass"];
$confirm =
$_POST["confirm"]; $date =
date("Y-m-d");
if($fullname==""){
$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Please fill the full

name field"; header("location:index.php?q=1"); }
else if($acc_type==""){
$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Please choose

account type"; header("location:index.php?q=1");
}else if($gender==""){
$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Please choose

gender"; header("location:index.php?q=1");
}else if($username==""){

48
 $_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Please fill the

username field"; header("location:index.php?q=1");
}else if($password==""){
$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Please fill the

password field"; header("location:index.php?q=1");
}else if($confirm==""){
$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Please fill the confirmation field";

header("location:index.php?q=1");

}
else{ if($password==$confir
m)
{ if(strlen($password)>=6)
{ $password =
md5($password);
$unique_id = uniqid();
if(isset($_POST["department"])){
$query="insertintousers
(unique_id,full_name,gender,user_name,pwd,account_type,department,date,status)values
('$unique_id',''$fullname','$gender','$username','$password','$acc_type','$dep',$date,'1')";

}else{

$query="insertintousers
(unique_id,full_name,gender,user_name,pwd,account_type,date,status)values
('$unique_id','$fullname','$gender','$username','$password','$acc_type',$date,'1')";

49
 $create = mysqli_query($con, $query);
if($create){
$_SESSION["success"] = "success";

$_SESSION["success_msg"] = "Account created successfully";

header("location:index.php?q=1");
}else{
echo mysqli_error($con);
}

}else{

$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "Password too short";

header("location:index.php?q=1");
}

}else{

$_SESSION["error"] = "error";

$_SESSION["error_msg"] = "The confirmation and the password do not match";

header("location:index.php?q=1");

?>

3. Question Detail sample code <?php

if(@$_GET['q']==1 && (@$_GET['step'])==2 &&
isset($_GET['quiz_id'])) {
$quiz_id =
$_GET['quiz_id']; echo '

50
<div class="row">

<span class="title1" style="margin-left:40%;font-size:30px;"><b>Enter Question

Details</b></span><br /><br />

<div class="col-md-3"></div><div class="col-md-6">

<form class="form-horizontal title1" name="form"

action="update.php?q=addqns&n='.@$_GET['n'].'&quiz_id='.
$quiz_id.'&eid='.@$_GET['eid'].'& ch=4 " method="POST">

<fieldset>

';

for($i=1;$i<=@$_GET['n'];$i++)

echo '<b>Question number&nbsp;'.$i.'&nbsp;:</><br /><!-- Text input-->

<div class="form-group">

<label class="col-md-12 control-label" for="qns'.$i.' "></label>

<div class="col-md-12">

<select rows="3" cols="5" id="q_type'.$i.'" name="q_type'.$i.'"

onchange="change_question_type('.$i.')" class="form-control">

<option selected value="choice">Choice</option>

<option value="blank_space">Blank space</option>

<option value="true_false">True or False</option>

</select>

</div>

</div>

<script >

51
 $(document).ready(function () {

$("#blank_space'.$i.'").hide();

$("#true_false'.$i.'").hide();

})

</script>

<div id = "choice'.$i.'">

<div class="form-group">

<label class="col-md-12 control-label" for="qns'.$i.' "></label>

<div class="col-md-12">

<textarea rows="3" cols="5" name="choice_qns'.$i.'" class="form-control"

placeholder="Write question number '.$i.' here..."></textarea>

</div>

</div>

<!-- Text input-->

<div class="form-group">

<label class="col-md-12 control-label" for="'.$i.'1"></label>

<div class="col-md-12">

<input id="choice_'.$i.'1" name="choice_'.$i.'1" placeholder="Enter option a"

class="formcontrol input-md" type="text">

</div>

</div>

<!-- Text input-->

<div class="form-group">

52
<label class="col-md-12 control-label" for="'.$i.'2"></label>

<div class="col-md-12">

<input id="choice_'.$i.'2" name="choice_'.$i.'2" placeholder="Enter option b"

class="formcontrol input-md" type="text">

</div>

</div>

<!-- Text input-->

<div class="form-group">

<label class="col-md-12 control-label" for="'.$i.'3"></label>

<div class="col-md-12">

<input id="choice_'.$i.'3" name="choice_'.$i.'3" placeholder="Enter option c"

class="formcontrol input-md" type="text">

</div>

</div>

<!-- Text input-->

<div class="form-group">

<label class="col-md-12 control-label" for="'.$i.'4"></label>

<div class="col-md-12">

<input id="choice_'.$i.'4" name="choice_'.$i.'4" placeholder="Enter option d"

class="formcontrol input-md" type="text">

</div>

</div>

<br />

53
<b>Correct answer</b>:<br />

<select id="ans'.$i.'" name="choice_ans'.$i.'" placeholder="Choose correct answer "

class="formcontrol input-md">

<option value="a">Select answer for question '.$i.'</option>

<option value="a">option a</option>

<option value="b">option b</option>

<option value="c">option c</option>

<option value="d">option d</option></select><br /><br />

</div>

<div id = "blank_space'.$i.'">

<div class="form-group">

<label class="col-md-12 control-label" for="qns'.$i.' "></label>

<div class="col-md-12">

<textarea rows="3" cols="5" name="blank_space_qns'.$i.'"

class="form-control" placeholder="Write question number '.$i.' here..."></textarea>

</div>

</div>

<!-- Text input-->

<br />

<b>Correct answer</b>:<br />

<input id="ans'.$i.'" name="blank_space_ans'.$i.'" placeholder="Choose correct answer "

class="form-control input-md">
</input><br /><br />
</div>

54
<div id = "true_false'.$i.'">
<div class="form-group">

<label class="col-md-12 control-label" for="qns'.$i.' "></label>

<div class="col-md-12">

<textarea rows="3" cols="5" name="true_false_qns'.$i.'" class="form-

control" placeholder="Write question number '.$i.' here..."></textarea>

</div>

</div>

<b>Correct answer</b>:<br />

<select id="ans'.$i.'" name="true_false_ans'.$i.'" placeholder="Choose correct answer "

class="form-control input-md">

<option value="a">Select answer for question '.$i.'</option>

<option value="true">True</option>

<option value="false">False</option>

</select><br /><br />

</div>
'; }

echo '<div class="form-group">

<label class="col-md-12 control-label" for=""></label>

<div class="col-md-12">

<input type="submit" style="margin-left:45%" class="btn btn-primary" value="Submit"

</fieldset>
</form>

</div>';

}
55
figure 5. 1 create account form

figure 5. 2 student certificate

56
CHAPTER SIXS: TESTING

Final phase of implementation is testing. It is a used to check the functional and nonfunctional
requirements of the system that validates the workability of the system. Thus, the team members
have tested the entire system as a whole with all forms, code, and modules. In this way, the team
have tested all the functionalities and non-functionalities of the system by using unit testing,
integration testing, and system testing and user acceptance testing strategies.
6.1 Unit testing
Unit testing is the testing of an individual unit or group of related units. It falls under the class of
white box testing. It is often done by the programmer to test that the unit he/she has implemented
is producing expected output against given input.

Table 6. 1 unit testing

Unit to Test = Authentication of login users

Assumptions = Login into appropriate page
Test Data = User Name(empty , invalid user name, valid username)
Password (empty ,invalid password, valid password)
Steps to be Executed Data Expected Results (display message)
Empty Username and Any invalid data for Please check User name and password
password and Click Login the other fields
button
Enter invalid User name, Any invalid data for Please check User name and password
password and Click Login the other fields
button
Enter valid username ,empty Any valid data for Please check User name and password
Password and Click Login the other fields
button
Enter valid password ,empty Please check User name and password
Any invalid data for
user name and Click Login
the other fields
button
Enter valid Username and All fields Fulfill with Login in to approprate page
Password then Click Login valid data
button

6.2 Integration testing

Integration testing is testing in which a group of components are combined to produce output. It
may fall under both white box testing and black box testing.

57
Integration testing can be done in a variety of ways but the following are three common
strategies:

The top-down approach to integration testing requires the highest-level modules be test and
integrated first.

The bottom-up approach requires the lowest-level units be tested and integrated first.

The third approach, sometimes referred to as the umbrella approach, requires testing along
functional data and control-flow paths.

6.3 System testing

System test insures that the entire integrated software system meets requirements. It tests a
configuration to insure known and predictable results. System testing is based on process
description and flows, emphasizing pre-driven process links and integration points. In system
testing is not about checking the individual parts of design, but about checking the system as a
whole. In effect it is one giant component. System testing insures the features of functional and
non-functional requirements and the specifications.

6.4 Acceptance testing

Acceptance testing is a testing technique performed to determine whether or not the software
system has met the requirement specifications. It is formal testing with respect to user needs,
requirements, and business processes conducted to determine whether or not a system satisfies
the acceptance criteria and to enable the user authorized entity to determine whether or not to
accept the system. The client satisfying all the requirements specified by them has also
developed the software within the time limitation specified. A demonstration has been given to
the client and the end-user giving some of operational features. Where product being delivered to
customer and then customer execute the acceptance test see whether the expectation of the
functionality meet or fulfill user requirements. Here is the general diagram of Acceptance

58
figure 6. 1 acceptance testing

59
CHAPTER SIVEN: CONCLUSIONS AND RECOMMENDATIONS

7.1 Conclusion
A COC-IMS is a computer-based exam taking, exam marking and exam result viewing system. It solves
most manually occurred problems such as un-readability of student or candidate answer, cheating among
candidate, manual correction error, etc. it also make examination-related tasks simple. It is a web-based
application, which host in the institute local area network and is available to the candidate within the
institute. It allows EPS to add questions, edit questions, delete questions. It provides exam to students of
the institute and automatically show their exam results.

This is a very modern and qualified way of student 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 COC-information management
system for Fekede Egzi collage.
The main aim of this project is 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 solve the
current system drawbacks by making each COC-Exam questions available digitally and usable anywhere
within the institute network. This is achieved by allowing EPS users to add questions according to the
level that provided and candidate to use them.

60
7.2 Recommendation

According to the scope of our project the team develops web based application. Because of the time
constraint we have limitation, but in the future the team believes that this system should be fully
operational by adding some functionality that are not included in our work. We also want to recommend
other coming students to make this project expanded and more automated with additional functionalities
and by integrating with new technologies

We recommended the following tasks to be done by other interested students as a future work.
 Practice and oral exam should be included.
 Online Cheating control mechanism

61
Reference
1. Bruegge, B. (2000). Object oriented Software Engineering Conquering Complex
and Changing System. Upper Saddle River: Prentice Hall.
2. Hoffer, J. et.al.(2000). Modern Systems and Design, Person Education (Singapore)
ptc.Ltd, India Brench, 482 F.I.E Patperegieng, Delhi 110092, India.
3. Jim A.(2013), OO Analysis and Design with UML .
4. Object-oriented design, http://en.wikipedia.org/wiki/Object-oriented_design,
5. https://www.scribd.com/doc/22746893

62
Appendix
Questions to be asked during requirement gathering using interview are:-
1. What are the objectives of your colleges?

______________________________________________________________________________
______________________________________________________________________________
__________________________________________________________

2. How does your current system working?

A. Is it manual?

B. Is it computerized?

C. Is it semi-automated?
3. How to register candidate for take COC exam?

_____________________________________________________________________________
_____________________________________________________________________________
___________________________________________________________

4. In what way the student can take the exam?

______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________
5. How student seen exam result after exam taken?
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
____________________________________________________________

6. What other solutions we are using to change the manual activity to minimize the work load of
the employers in your Colleges?

_____________________________________________________________________________
_____________________________________________________________________________

63