FINAL PROJECT DOCUMENTATION (1) Done at Wollo University

WOLLO UNIVERSITY
KOMBOLCHA INSTITUTE OF TECHNOLOGY

COLLEGE OF INFORMATICS
DEPARTMENT OF INFORMATION TECHNOLOGY
Web based COC management system for Kombolcha TVET College
Prepared by:-
Student
Name……………………………………………………………………ID No
1. Znabu H/selasie------------------------------------------------------WOUR/2072/08
2. Mohammed Melash-------------------------------------------------WOUR/1985/08
3. Mohammed Yesuf---------------------------------------------------WOUR/1982/08
4. Mohammed Abdu----------------------------------------------------WOUR/1983/08
5. Melkamu Alemnew--------------------------------------------------WOUR/1966/08
Advisor: -Abraha G.
Kombolcha, Wollo, Ethiopia

February 2011
KOMBOLCHA TVET COLLEGE COC MANAGEMENT SYSTEM 2019
Approval
This is to certify that the project is original and has not submitted for partial fulfillment of
Bachelor of degree in Information Technology. Our project member name and signature.
Name Signature
Znabu H/selasie _________________________
Mohammed Melash _________________________
Mohammed Abdu _________________________
Mohammed Yesuf _________________________
Melkamu Alemnew _________________________
College: College of Informatics
Program: Bachelor of degree
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope
and quality, as a project for the degree of Bachelor of Science.
------------------------------------- -----------------------
Name of Advisor Signature
1. Chairman ____________ ____________ __________
2. Examiner1 ____________ ____________ __________
3. Examiner 2 ____________ ____________ __________
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY I

Acknowledgment
We have taken efforts in this project. However, it would not have been possible without the Kind
support and help of many individuals and organizations. We would like to extend our sincere
thanks to all of them. We are highly indebted to TVET College employees and our advisor
Abrha M, for his guidance and constant supervision as well as for providing necessary
information regarding the project & also for their support in completing the project.
We would like to express our gratitude towards team (G-3) for their kind co-operation and
Encouragement that help us in completion of this project. Our thanks and appreciations also go
to our collage in developing the project and people Who have willingly helped us out with their
abilities.
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY II

Table of Contents
Approval ......................................................................................................................................................... I
Acknowledgment .......................................................................................................................................... II
List of figures ................................................................................................................................................ VI
List of tables ............................................................................................................................................... VIII
Abstract ........................................................................................................................................................ IX
Acronym ........................................................................................................................................................ X
Chapter One ................................................................................................................................................. 1
1 Introduction .......................................................................................................................................... 1
1.2 Introduction of the project ..................................................................................................................... 1
1.3 Statement of the Problem ............................................................................................................ 1
1.4 Objective of the project ................................................................................................................ 2
1.4.1 General objective .................................................................................................................. 2
1.4.2 Specific objective .................................................................................................................. 2
1.5 Scope and limitation of the project .............................................................................................. 2
1.5.1 Scope of the project............................................................................................................... 2
1.5.2 Limitation of the project ....................................................................................................... 2
1.6 Significance of the Project ............................................................................................................ 2
1.7 Target beneficiaries of the system ................................................................................................ 3
1.8 Methodology ................................................................................................................................. 3
1.8.1 Data collection method......................................................................................................... 3
1.9 System Development methodology ............................................................................................. 4
1.9.1 Software tools ....................................................................................................................... 4
1.9.2 Hardware tools ...................................................................................................................... 4
1.10 Feasibility study............................................................................................................................. 4
1.10.1 Operational feasibility ........................................................................................................... 5
1.10.2 Technical feasibility .............................................................................................................. 5
1.10.3 Economic Feasibility............................................................................................................. 5
1.10.4 Cost estimation...................................................................................................................... 5
1.10.5 Schedule feasibility ............................................................................................................... 6
1.11 Team Composition ........................................................................................................................ 7
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY III

Chapter two .................................................................................................................................................. 8

2 Description of the Existing system ........................................................................................................ 8
2.1 Introduction of existing system .................................................................................................... 8
2.2 Player of the existing system ........................................................................................................ 8
2.3 Business Rule of the organization ................................................................................................. 9
2.4 Major activities of the existing system ......................................................................................... 9
2.4.1 Existing System Workflow Structure.................................................................................... 9
2.4.2 Report generation of the existing system ............................................................................ 10
2.4.3 Examination system ............................................................................................................ 10
2.5 Problem of Existing System ........................................................................................................ 11
2.6 Proposed system description ...................................................................................................... 12
2.7 Requirement of the proposed system ........................................................................................ 12
2.7.1 Functional requirement ....................................................................................................... 12
2.7.2 Nonfunctional requirement ................................................................................................. 13
2.8 Modeling the existing systems.................................................................................................... 14
2.8.1 Essential Use Case Modeling .............................................................................................. 14
2.8.2 Essential User Interface Prototyping................................................................................... 16
2.8.3 Domain modeling with class responsibility collaborator (CRC) ........................................ 17
Chapter Three ............................................................................................................................................. 20
3 System Analysis ................................................................................................................................... 20
3.1 System Analysis and Design Techniques ..................................................................................... 20
3.2 System models ............................................................................................................................ 20
3.2.1 System Use Case Modeling ................................................................................................ 20
3.2.2 Use case Description ........................................................................................................... 23
3.3 Sequence Diagrams..................................................................................................................... 34
3.4 Activity diagramming .................................................................................................................. 44
3.5 Analysis level class diagram ........................................................................................................ 50
3.6 User interface prototyping.......................................................................................................... 51
CHAPTER FOUR ........................................................................................................................................... 52
4 System design ..................................................................................................................................... 52
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY IV

4.1 Introduction ...................................................................................................................................... 52
4.2 Design Goals ................................................................................................................................ 52
4.3 Subsystem Decomposition.......................................................................................................... 53
4.4 Class modeling ............................................................................................................................ 55
4.5 State chart modeling ................................................................................................................... 56
4.6 Collaboration Modeling .............................................................................................................. 61
4.7 Component Modeling ................................................................................................................. 64
4.8 Deployment modeling ................................................................................................................ 65
4.9 Persistence modeling .................................................................................................................. 66
4.10 User Interface design .................................................................................................................. 70
Chapter Five ................................................................................................................................................ 74
5 Implementation and Testing ............................................................................................................... 74
5.1 Introduction ................................................................................................................................ 74
5.2 Final Testing of the system ......................................................................................................... 74
5.2.1 Unit test ............................................................................................................................... 74
5.3 Hardware software acquisitions ................................................................................................. 82
5.4 User manual preparation ............................................................................................................ 82
5.5 Training ....................................................................................................................................... 82
5.6 Installation .................................................................................................................................. 83
5.7 Start-up strategy ......................................................................................................................... 83
Chapter six: ................................................................................................................................................. 84
6 Conclusions and Recommendation..................................................................................................... 84
6.1 Conclusions ................................................................................................................................. 84
6.2 Recommendation........................................................................................................................ 85
Appendix A .............................................................................................................................................. 86
References .............................................................................................................................................. 87
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY V

List of figures
Figure 2. 1 Existing System Workflow ........................................................................................................ 10
Figure 2. 2: Essential use case diagram...................................................................................................... 15
Figure 3. 1: System use case diagram…………………………………………………………………………………………………….22
Figure 3. 2: Sequence diagram for login .................................................................................................... 34
Figure 3. 3: Sequence diagram for registration. ......................................................................................... 35
Figure 3. 4: Sequence diagram for evaluate exam ...................................................................................... 36
Figure 3. 5: Sequence diagram for view report ........................................................................................... 37
Figure 3. 6: Sequence diagram for view result............................................................................................ 38
Figure 3. 7: Sequence diagram for send receipt number. ........................................................................... 39
Figure 3. 8: Sequence diagram for add questions. ...................................................................................... 40
Figure 3. 9: Sequence diagram for add schedule. ....................................................................................... 41
Figure 3. 10: Sequence diagram for add user.. ........................................................................................... 42
Figure 3. 11: Sequence diagram for change password. .............................................................................. 43
Figure 3. 12: Activity diagram for login ...................................................................................................... 44
Figure 3. 13: Activity diagram for user registration inthe system............................................................... 45
Figure 3. 14: Activity diagram for add account. ......................................................................................... 46
Figure 3. 15: Activity diagram for Evaluate exam ...................................................................................... 47
Figure 3. 16: Activity diagram for view report........................................................................................... 48
Figure 3. 17: Activity diagram for change password .................................................................................. 49
Figure 3. 18: Class diagram ........................................................................................................................ 50
Figure 3. 19: User interface prototyping for login ...................................................................................... 51
Figure 4. 1 Subsystem diagram……………………………………………………………………………………………………………….54
Figure 4. 2 Class diagram........................................................................................................................... 55
Figure 4. 3 State chart diagram for login ................................................................................................... 56
Figure 4. 4 State chart diagram for evaluate exam .................................................................................... 57
Figure 4. 5 State chart diagram for generate report .................................................................................. 58
Figure 4. 6 State chart diagram for register schedule ................................................................................ 59
Figure 4. 7 State chart diagram for register exam ...................................................................................... 60
Figure 4. 8 Collaboration diagram for registering in the system ............................................................... 61
Figure 4. 9 Collaboration diagram for add schedule ................................................................................. 62
Figure 4. 10 Collaboration diagram for login ........................................................................................... 62
Figure 4. 11 Collaboration diagram for change password ......................................................................... 63
Figure 4. 12 Collaboration diagram for register question .......................................................................... 63
Figure 4. 13 Component diagram .............................................................................................................. 64
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY VI

Figure 4. 14. Deployment diagram ............................................................................................................. 65
Figure 4. 15 Mapping Generalization relationship into Single Table ......................................................... 66
Figure 4. 16 Mapping From Many-Many Relation Ship ........................................................................... 67
Figure 4. 17 Mapping from Many-Many Relation Ship .............................................................................. 67
Figure 4. 18 Mapping from Many-1 Relation Ship .................................................................................... 68
Figure 4. 19 Mapping from One-One Relation Ship .................................................................................. 68
Figure 4. 20 Diagram for database design ................................................................................................ 69
Figure 4. 21: Home page interface .............................................................................................................. 70
Figure 4. 22: User login interface ............................................................................................................... 71
Figure 4. 23: Candidate registration interface ............................................................................................. 72
Figure 4. 24: Adding question interface...................................................................................................... 73
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY VII

List of tables
Table 1.1: Cost needed to develop this project ............................................................................................. 5
Table 1. 2: Time schedule to complete this project ....................................................................................... 6
Table 1. 3: Team composition table .............................................................................................................. 7
Table 2. 1: Essential use case description………………………………………………………………………………………………14
Table 2. 2: Candidate registration form. .................................................................................................... 16
Table 2. 3: Class Responsibility and Collaboration table for manager. ..................................................... 17
Table 2. 4: Class Responsibility and Collaboration table for candidate. ................................................... 17
Table 2. 5: Class Responsibility and Collaboration table for EP ............................................................... 18
Table 2. 6: Class Responsibility and Collaboration table for EEC. ........................................................... 18
Table 2. 7: Class Responsibility and Collaboration table for CRC ............................................................ 18
Table 2. 8: Class Responsibility and Collaboration table for Examiner ..................................................... 18
Table 2. 9: Class Responsibility and Collaboration table for cashier ........................................................ 19
Table 2. 10: Class Responsibility and Collaboration table for exam ......................................................... 19
Table 3. 1: Use case table for login………………………………………………………………………………………………………..23
Table 3. 2: Use case table for registration request ..................................................................................... 24
Table 3. 3: Use case table for evaluate exam.............................................................................................. 25
Table 3. 4: Use case table for view report .................................................................................................. 26
Table 3. 5: Use case table for assign privilege ........................................................................................... 26
Table 3. 6: View rejected question. ............................................................................................................. 27
Table 3. 7: Use case table for view schedule .............................................................................................. 27
Table 3. 8: Use case table for manage account .......................................................................................... 28
Table 3. 9: Use case table for manage exam question ................................................................................ 29
Table 3. 10: Use case table for take exam. ................................................................................................. 29
Table 3. 11: Use case table for view result ................................................................................................. 30
Table 3. 12: Use case table for register exam ............................................................................................. 30
Table 3. 13: Use case table for register schedule. ...................................................................................... 31
Table 3. 14: Use case table for add user. .................................................................................................... 31
Table 3. 15: Use case table for change password. ...................................................................................... 32
Table 3. 16: Use case table for prepare report. .......................................................................................... 32
Table 3. 17: Use case table for print certificate.......................................................................................... 33
Table 3. 18: Use case table for send receipt number. ................................................................................. 33
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY VIII

Abstract
COC examination is an examination, which is provided to college/TVET graduating students as
a final assessment mechanism for the seek of quality assurance. It is an exam content which
covers the whole life courses in the level within the institution.
COCMS, the proposed system will solve the problem in the existing system and make it simple.
It is a web-based application, which will 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 want to recommend TVET institutions that provide COC
exams to introduce this new automated system. So that it will handle the overall examination
processes, from starting the exam up to showing final result
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY IX

Acronym
BR Business Rule
COC Center of Competence
COCMS COC Management System.
CRC Candidates registration committee
CS Cascading Style Sheet
DB Database
DBMS Database Management system
EEC Exam evaluation committee.
EP Exam provider
Js JavaScript
KTC Kombolcha TVET Collage
MS Microsoft
PHP Hyper preprocessor Scripting language..
TVET Technical and Vocational Education and training
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY X

Chapter One
1 Introduction
1.1 Background about the Organization
TVET is one of the known Organizations in Ethiopia. Kombolcha TVET College is one of the
numerous TVET institutions, probably eighty-nine Technical and Vocational Education Training
colleges currently under the jurisdiction of the Amhara National Regional State (ANRS) TVET
bureau.
The brief historical background of Kombolcha TVET College was started in 1994 E.C. with
institution status, having the name entitled Kombolcha Technical & Vocational Education
&Training Institute and Vocational Education and Training College. Since in 2000 E.C. the
TVET College has been offering training service in two campuses. Kombolcha TVET collage
starts COC examination in 2004 E.C [2]. This organization gives different level in different
departments those are level one, level two, level three, and level four. The COC Exam in TVET
College is a given in different level and in different ways like, practical exam, and real exam.
1.2 Introduction of the project

Web based COC management system is, a system which reduce manual work and time wasting
activity. It provides online examination using a different platform for the examinee to give their
examination at their own place. This system will reduce the complexity and consumption of
time. The examinees will get their results in their short time in comparison to those in other
system.
Kombolcha TVET collage provides COC exam for candidates in a different label. In fact, this
organization uses manual system, like Students registration for COC, exam management, level
management, question management, Account Management system, which need to be automating
to solve problem that faces the manual system.
1.3 Statement of the Problem

Kombolcha TVET collage uses manual system for COC management system. This means using
pen and paper. As a result, the current system faces several problems. Such as:-
 Delay of exam marking and result report viewing.
WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 1

 Resource wastage during registration and examination.
 Many exam marking related mistakes and corruptions.
 It needs large number of examiner.
 Time wastage during exam distribution process.
1.4 Objective of the project

1.4.1 General objective
The main objective of this project is to develop web based COC management system for
Kombolcha TVET collage.
1.4.2 Specific objective
In order to achieve the main objective, we have developed the following specific objectives:
 Design and implement a database for the proposed system.
 Design and implement a web based system.
 Test and deploy the developed system.
 Create a system that provide a database backup and recovery.
1.5 Scope and limitation of the project

1.5.1 Scope of the project
The project aims to develop web based COC management system for Kombolcha TVET collage.
It includes only wed based COC exam management, candidate’s registration, and Exam
Evaluation activities.
1.5.2 Limitation of the project

This project does not cover the following activities: -
 It does not include online Payment system.
 The system does not include Oral and Practical exams.
 It does not use face detection as authentication.
1.6 Significance of the Project

The proposed project is useful for the TVET College to perform its activity in a short period of
time and little human power with little resource consumption.
The proposed project is the right software to be incorporate into the Automation of COC exam
management system Software for helping the organization needs with respect to skillful labor.
The proposed system will be more user-friendly and easy to adapt.

We categorize the benefits of the system into tangible and intangible.
Tangible benefits:
 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
Intangible benefits:
 Improve candidate satisfaction
 Improve COC exam process.
 Better decision making
 Better service to the candidate
 Improved candidate’ motivation by avoiding paperwork
1.7 Target beneficiaries of the system

The beneficiaries of the COCMS for:-
 Candidate:- to take COC exam, to view total exam result statistics (passed or failed) and
to registered for COC exam in order to save time and resources.
 Administrator:- to manage the overall activity of the system.
 TVET Collage:- to minimize cost for printing exam paper.
 EP:- to send exam easily to the EEC.
 EEC:- easily to send the exam after evaluated the exam.
1.8 Methodology
1.8.1 Data collection method
Our team uses different techniques to gather information about the current system. It is the
fundamental activity for the development of the system. Without them, the data modeling
can’t be construct. In order to know how the existing system work and what problem are
there we have been using the following fact-finding techniques.
 Interview:- to get the basic information and background information about the existing
system. The services given by the collage and the processes used by the TVET collage to
provide COC exam, the team members has interviewed the collage manager, human
interaction officer, examiners and some examinee/candidates about the services that are
given to them, and the problems associated with that environment.


 Observation: direct observation is simple, because it observes information that cannot
maintain from the interview or others and it is important if they are unable to
communicate with others because of the difficulties they have to the language. Then our
project team members physically observe how the activity done and how the services
were provided.

 Document analysis: This is also another information gathering methodology by referring
the document of the existing system, then our team observes some documents related
service delivery and information management techniques.
1.9 System Development methodology

1.9.1 Software tools
 PHP :- it’s one of the best programming language for our project which is used for
writing a code
 WAMP Server: -
 Manage your Apache and MySQL services.
 Create a subdirectory in “www” and put your PHP files inside.
 E draw max:-For designing UML diagrams associated with the project.
 Microsoft Office 2007:- for writing documentation.
 Sublime and notepad++:- for writing code.
 MySQL: - used to connect database server.
1.9.2 Hardware tools
 Flash disk
 Desktop computer
 Personal Computer
1.10 Feasibility study
Feasibility is the analysis of risks, costs & benefits relating to economics, technology & user
operation. When we are developing the system (software), we must know the proposed system
will be feasible i.e. practically implemented or not. It may be possible that the proposed system
will not be implement due to many reasons as it may take long time in development than the
specified time limit, cost may increase than proposed one etc. Therefore, we must analyze the
feasibility of the system. There are several type of feasibility depending on the aspect of they
cover. Some important feasibilities are as follows: -

1.10.1 Operational feasibility
The system to be develops will provide accurate, active, secured service and decreases labor of
workers and it is not limited to particular groups or body. In addition, it is platform independent,
i.e. it run is in all operating system.
1.10.2 Technical feasibility
Technical feasibility centers on the existing manual system of the test management process and
to what extent it can support the system. According to feasibility analysis, procedure the
technical feasibility of the system is analyze and the technical requirements such as software
facilities, procedure, inputs are identifying. It is also one of the important phases of the system
development activities. The system offers greater levels of user friendliness combined with
greater processing speed. Therefore, the cost of maintenance can be reducing. Since, processing
speed is very high and the work is reduced in the maintenance point of view management
convince that the project is operationally.
1.10.3 Economic Feasibility
Economic analysis is the most frequently used for evaluation of the effectiveness of the system.
More commonly known as cost/benefit analysis the procedure is to determine the benefit and
saving that are expected from system and compare them with costs, decisions is made to design
and implement the system
1.10.4 Cost estimation
Cost estimation has a great impact for the successful accomplishment of the project. The costs
associated with each items required has estimated. This will help us to limit the constraints
related to cost while the project is conduct. From the beginning up to the end of this project is
planned the following cost list.
Table 1.1: Cost needed to develop this project
Type Item Quantity Price per Item Total Item

Hardware Flash 3 180birr 540 birr
Print 2 30birr 90 birr
Stationary
Paper 10 1birr 10birr
Transportation Transport - 16 48
Miscellaneous Mobile card 5 10 50
Total 7 24 243 birr 750 birr

1.10.5 Schedule feasibility
Since schedule feasibility is a process of assigning the degree to which the potential time frame
and computation date for all major activities within a project meet organizational deadlines, so
our project will be continued next.
Table 1. 2: Time schedule to complete this project
20011 EC
No Task Name Nov16- Dec25 Dec26- jan20 Jan 23- Mar25 Apr27- May10 May11-jun5
.
1 Requirement
gathering
2 System
requirement
specification
3 System
designing
4 System
implementatio
n
5 Operation
&testing

1.11 Team Composition
The team that will develop the project consists of five members. The team members meet in
daily bases to discuss about the project, and to asses where each member is on his prospective
task in reference to the schedule. The team composition or work breakdown is shown in the
following table.
Table 1. 3: Team composition table
No Team members ID Number Role on group Role on the project work
1 Zinabu H/slassie WOUR/2072/08 Coordinator System Analyst
2 Mohammed Melash WOUR/1985/08 v/coordinator Implementation
3 Mohammed Abdu WOUR/1983/08 Secretary Testing
4 Mohammed Yesuf WOUR/1982/07 Member Designer
5 Melkamu Alemnew WOUR/1966/08 Member Designer

Chapter two
2 Description of the Existing system
2.1 Introduction of existing system
COC-Exam is mandatory on TVET College and other diploma-certification institutes. This is
currently provide manually. Certificate of COC-Pass is manage and produced manually. This
means using papers and pens. TVET is one of the known Organizations in Ethiopia. This
Organization gives different level in different departments those are level one, level two, level
three and level four. The COC Exam in TVET College given in different level and in different
ways like oral exam, practical exam, and real exam.
2.2 Player of the existing system

This illustrates the actors involved in the current system. Those actors in the existing system are:
 Manager comes with the following activities.
 Manage the employees of the collage.
 Unfold individual and overall reports.
 Give orientation to candidates.
 Prepare and give certificate for candidates.
 Examiner comes with the following activities.
 Examine candidate.
 Mark exam.
 Exam provider comes with the following activities.
 Prepare question.
 Set time schedule for exam.
 Give the exam paper to examiner.
 Candidates come with the following activities.
 Registered in the collage.
 Give payment to cashier.
 Take the exam.
 View result of their exam.
 Take certificate
 Cashier comes with the following activities.
 Receive payment.
 Give receipt to candidates.
 EEC comes with the following activities
 Evaluate exam
 Prepare exam schedule

 CRC comes with the following activities
 Register candidates
2.3 Business Rule of the organization

Identifying the business rule of the existing system will help us to specify and describe each use
case in effective way. The business rules of the COC information management system listed as
following: -
BR1: The candidates should register.
BR2: - They should have a take along unique ID that expresses his/her IDENTITY.
BR3: - The candidates should have to take the exam within the given time of period.
BR4: - The exam should be de activate after the exam has taken, i.e. the exam paper should be
return to the office after the exam had taken.
BR5: -The exam should not be duplicate.
BR6: - No candidates can take a particular exam more than once.
BR7: - the candidates should fill the form properly, i.e. the form needed to be fill by candidates
to take the exam.
BR8: all candidates must take the same exam according to level and department.
2.4 Major activities of the existing system

2.4.1 Existing System Workflow Structure
The task that accomplished in this COCMS is the candidates register manually by going to the
collage. The COC exam preparation section will prepare question and the EEC will evaluate the
question based on rules, which is prepared by the COC exam preparation section. After that, the
exam will goes to the examiner. The candidates take the exam. The examiner examines the
candidate and marks the exam, and then gives the result to the manager. Finally, the manager
prepares and gives certificate to the candidates.

COCMS
Manager
Assign Assign
Assign Assign Assign

EEC
ERC Cashier
Exam
Give Evaluate exam
Examiner provider
Register exam
Examinee
Candidates
Take exam
Figure 2. 1 Existing System Workflow
2.4.2 Report generation of the existing system

The collage manager communicates with the exam preparation section to check the exam is
prepared, and the exam is ready to be provide to the examinee. Then the candidates take the
exam and the manager report the number of passed and failed candidates to the collage. Allow
the candidate to see their individual exam result.
2.4.3 Examination system
The examination system in the collage is work manually by using paper and general purposed
applications to the candidate. After candidate’s full fill, the requirement needed to take COC
exam by going to the collage. They gone to the collage, then take some training and orientation
related to the exam. After that, the candidates take the exam.

2.5 Problem of Existing System
As we have seen from the existing system by some methodologies listed in chapter one (1.7.1), it
is not preferable for the candidates since everything is manual. The major problems, which was
founds in the existing system, listed as follows:
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 time took by the current
system for providing information about the service provider to user is so slow.
 The work procedure is error prone.
 The throughput (output) of the organization is not effective. Since it is paper based lead
to different error during marking the exam.
Information related problem
 Miss handling of candidate information occurs.
 Data is difficult to correct and maintain.
 Data is stored redundantly in multiple files (paper).
 Data is not easily accessible.
 Data is not well organized.
Efficiency related problem
 Since the work is performs 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 will
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: -since human marks the exam, then many exam marking related
mistakes and corruptions would be occur.

Economic related problem
 Manual handling of data is expensive.
 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 student’s increase.
Service related problem
 The candidates do not get better service as they need,
 Then candidates do not satisfy with service.
Time consuming
 User has to wait for register i.e. -The candidates go to the organization to register using
the document and the registrar registers the candidates and gives them their individual
unique ID for COC exam.
 Less communication between exam agency with administrator and takes time.
 The way from home to organization takes time.
 COC exam process: - the candidates take orientation from the instructor and then take the
exam using manually way since the system is paper based.
2.6 Proposed system description

After we observe the existing system, we propose a web based COCMS. The proposed system
has the following purpose.
 Increased efficiency of COC exam process.
 Allows neat handling of data rather than error prone records.
 Avoiding Mistakes Due to Human Error (Accurate).
 Will Increase Efficiency and Save Time for exam processing.
 Saving the extra time to register for COC exam.
 Saving the extra time for take COC exam.
 Candidates need not wait for see their results.
2.7 Requirement of the proposed system
2.7.1 Functional requirement
The new system has the following main functionalities (functional requirements).
Exam Management:

 Exam Registration: a COC EP can add questions, delete questions, view all questions of a
given level, occupation, and sector. Since upload questions. The COC exam provider
manages question.
 Exam Evaluation: - the EEC will evaluate the exam, which is prepare by EP and accept
or reject the evaluated exam.
 Online Examination: - The candidates take exam online and the system marks exam.
Report generation management
Candidate should be view his/her result immediately after exam completed. Then the system
reports the exam result to individual candidate after candidate take exam with some important
information about the candidate, i.e. name of candidate, candidate id, sector and related
information. In addition, the manager posts the pass/fail report and by printing certificate upload
it for passed candidates and he reports how many candidates take or not the exam. The cashier
reports how many candidate pay their payment for the registration.
The admin views all candidates’ results and could modify or delete.
User account Management:
 Account registration: the system register all accounts needed to function this system.
Candidate account, EP account and EEC account will be register in the system, and
allow Candidates to be register with their detailed information for taking COC exam.
 Account control: The administrator control all accounts in the system. Then online
admin manages user account for Exam registration section, Exam evaluation section.
2.7.2 Nonfunctional requirement
This requirement is relating to the advantages of the new system, which is develop 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) on
functional requirement describes user visible aspects of the system that are not designed to the
functional behavior of the system. Some of the nonfunctional requirements are:
Performance:
The amount of time needed to get the response for a transaction or request minimized.
The system has fast response time because of a light weighted code in HTML, PHP, CSS and
JavaScript.

Control and Security:
This system uses different authentication. The system users are allowing performing activities or
making a modification to the data if and only if they are authorizing which will be check by their
username, password, and account type.
Usability:
The system has an interactive and attractive GUI, which eases users’ usage problem.
2.8 Modeling the existing systems

2.8.1 Essential Use Case Modeling
A use case represents a description of existing system functionality from a particular point of
view. Use cases describe an interaction between an actor and the system. The main actors in this
system listed in table four below.
Table 2. 1: Essential use case description
Actor Use case Description

Candidate Take exam A person that can full fill the
View result requirement by the
Pay money to register organization can be register to
take exam.
EP Create exam This actor provides exam to
Set time schedule for exam the organization.
Examiner Examine candidates Examine candidates mark
Mark exam exam as needed.
Manager Assign privilege The manager of the collage
View report that manage the overall
Prepare report activities.
Cashier Receive money from Candidates pay the money by
candidate going to the collage.
Give receipt for candidate
EEC Evaluate exam EEC evaluates the exam
prepared by EP.
CRC Register candidates CRC register candidates

Figure 2. 2: Essential use case diagram.

2.8.2 Essential User Interface Prototyping
The Kombolcha TVET collage uses the following registration form. The candidates should fulfill
the form to register and take the exam.
Table 2. 2: Candidate registration form.
Institution Name :- Document Number:-

Kombolcha TVET Collage KTC/OF/R/36
Title:-Format Together Detailed Data of Trainers and Candidates form Issue No Page No
1 1 of 1
Form-A category of candidates
registered
Format together detailed Data of candid for the first time
For
reassessment
Assessment Center:-Kombolcha TVET Collage Occupation:-IT Level: 1
n I Candi Training institute Training program Purpose of assessment Assessme
Sex
o d date Na Ownership nt
n Full me
o Name
Not
yet
Level to level promotion
sati
fact
Competent in both
NGO
Knowledge only
Other(Specifly)
Practical only
Government
Graduation
Extension
Distance
Informal
Informal
Summer
Regular
Private
Total

2.8.3 Domain modeling with class responsibility collaborator (CRC)
CRC modeling techniques used to model the existing system that helps to build the proposed
class diagram by observing how the existing system is collaborate with each activity. A class
represents a collection of similar objects, a responsibility is something that a class knows or
does, and a collaborator is another class that a class interacts with to fulfill its responsibilities.
Table 2. 3:Class Responsibility and Collaboration table for manager.
Manager<<actor>>
Manager name
Age
Address Examiner
Sex
Assign examiner EP
Assign EP
View report
Prepare report
Table 2. 4: Class Responsibility and Collaboration table for candidate.
Candidate<<actor>>
Candidate ID cashier
Candidate name
Examiner
sex
level Exam
Take exam CRC
Register
View result
Pay money

Table 2. 5: Class Responsibility and Collaboration table for EP
EP<<actor>>
EP ID Manager
EP name
EEC
Sex
Exam
Prepare exam
Set exam schedule
Table 2. 6: Class Responsibility and Collaboration table for EEC.
EEC<<actor>>
EEC ID Manager
EEC name
EP
Sex
exam
Evaluate exam
Table 2. 7: Class Responsibility and Collaboration table for CRC
CRC<<actor>>
CRC ID Candidates
CRC name
Sex
Register candidates
Table 2. 8: Class Responsibility and Collaboration table for Examiner
Examiner<<actor>>
Examiner ID
Examiner name Manager
Sex Candidates
Examine candidate exam
Mark exam

Table 2. 9: Class Responsibility and Collaboration table for cashier
Cashier<<actor>>
Cashier ID
Cashier name
Manager
Sex
Candidates
Receive money
Give receipt
Table 2. 10: Class Responsibility and Collaboration table for exam
Exam<<entity>>
Exam ID candidates
Exam type
EEC
Questions
alternatives EP
answers

Chapter Three
3 System Analysis
3.1 System Analysis and Design Techniques
The team chooses object oriented system analysis and design to analyze and design the system,
based on our preliminary analysis of the old system.
Because it has the following advantages: -
 Increase reusability: - the object oriented provides opportunities for reuse through the
concepts of inheritance, polymorphism, encapsulation and modularity.
 Increased extensibility: - when there is a need to add new feature to the system you only
need to make changes.
Improved quality: - quality of our system must be on time and meet our exceeded the expectation
of the users of our system, improved quality comes from increased participation of users in the
system development.
3.2 System models

A system model is the conceptual model that describes and represents a system.
3.2.1 System Use Case Modeling

A system uses case model is composed of use cases diagram association.
 Use case diagram
Use Case represents interaction between a user (human or machine) and the system.
 Actor identification
In the use, cases an actor interact with the system. Actors in this system are the following:
 Manager
 Administrator
 Candidate
 Exam provider
 Exam evaluation committee
 cashier
 Use case identification

The most important and basic use cases of this system are the following:-
 Login
 Change password
 Logout
 Manager
 Change role
 View report
 Prepare report
 Print certificate
 Administrator
 Add user
 Manage user (delete, update)
 Exam provider
 Register exam
 View exam evaluate comment
 Manage exam
 Exam evaluation committee
 View exam
 Evaluate exam
 Register schedule
 Manage schedule
 Candidates
 Registration request
 Take exam
 View schedule
 View result
 Cashier
 Send receipt number

Figure 3. 1: System use case diagram

3.2.2 Use case Description
Table 3. 1: Use case table for login
Use case name Login
Use case ID Uc01
Participating actor administrator, manager, candidate, Exam evaluator section, exam

provider, cashier
Description To register user for join to the system.
Pre-condition User must have to fulfill all necessary information.
Post condition User gets access to the system according to their predefined system
privileges.
Basic course of action 1. user open web site

2. System display login page.
3. User enter username and password
4. User Click login button
5. System verifies username and Password.
6. If username and password is valid
7. The system displays the user page.
8. Use case ends.
Alternative course of 5.1. User not authenticate and deny access to the system.
action 5.2. System displays an incorrect username and password message.
5.3. System redirects into step 3.

Table 3. 2: Use case table for registration request
Use case name Registration request
Use case ID Uc02
Participating actor Candidate
Description Describe how the candidate registered intoweb-based

Examination System.
Pre-condition The candidate must have payment receipt.
Post condition Candidate information should be register in system database.
Basic course of action 1. The candidate click on registration link

2. System display candidates registration form
3. Candidate fulfills the required information and click
register button.
4. System validate the request.
5. Candidates information record in to database
6. Use case ends.
Alternative courses of 4.1. When candidate fills incorrect information. The system
action redirect in to step 3.

Table 3. 3: Use case table for evaluate exam
Use case name evaluate Exam
Use case ID Uc03
Participating actor EEC
Description Describe how the EEC evaluates questions in web-based

Examination System such as valid or not.
Pre-condition The EEC must login to the system.
Post condition EEC evaluates questions and display successfully evaluated
message to the COC exam provider.
Entry condition The user opens the home page of the system.
Basic course of action 1. the EEC evaluate exam link

2. The System display questions.
3. EEC evaluates questions.
4. If EEC agreed with the question click on accept button.
5. The question saved to the system.
6. Use case ends.
Alternative course of 4.1. If EEC does not agreed with the question EEC clicks reject
action button.

Table 3. 4: Use case table for view report
Use case name View report.
Use case ID Uc04

Participating actor Manager
Description System shall allow generate report for candidate exam

Information.
Pre-condition Manager must logged in to the system.
Post condition Report will be generate

Basic course of action 1. Manager clicks view report link.
2. System Displays the whole report.
3. Manager views the report.
4. Manager log out.
5. Use case ends.
Table 3. 5: Use case table for assign privilege
Use case name Change role
Use case ID Uc05

Participating actor Manager
Description This use case describes how the manager give employee user as
their skills.
Pre-condition All require fields of form are correctly fill by the manager.
Post condition The manager assign employee correctly
Entry condition The user opens the home page of the system.
Basic course of action 1. The manager clicks change role link.

2. System display list of change role form.
3. Manager inserts role type.
4. Manager changes role of user.
5. Manager click change role button.
6. Employee role change successfully.
7. Use case ends.

Table 3. 6: View rejected question.
Use case name View rejected question
Use case ID Uc06
Participating actor EP
Description This use case initiated by EP. This use case describes how EP
view exam evaluation result.
Pre-condition The EP must have evaluated exam
Post condition The EP sends notification to ERS and ERS save exams.
Basic course of action 1. EP clicks approved questions link.

2. System Displays rejected question.
3. EP view the rejected questions
4. Use case ends.
Table 3. 7: Use case table for view schedule
Use case name View schedule
Identifier Uc07
Actor Candidates
Description To view exam schedules.
Precondition Candidates must be login to perform those activities

Post condition System shows schedule information to the candidates.
Basic course of action 1. Candidates click view schedule link.
2. If schedules was registers system displays schedule
information.
3. Candidates view schedule.
4. Use case ends.
Alternative course of 2.1 If schedule not found, system display unsuccessful message.
action

Table 3. 8: Use case table for manage account
Use case name Manage user

Use case ID Uc08
Actor Administrator
Description Use case to delete/update.
Precondition The Administrator must be login to perform those activities
Post condition System has successfully delete/update/
Basic course of action 1. Administrator clicks delete/update account link.
2. The system displays account information form (delete, and
update).
3. Administrator or fills account information delete/update.
4. Administrator clicks delete/update button.
5. The account is delete from the database or update in the
database.
6. Use case ends
Alternative course of 4.1. When there is not filled the account information correctly
action “please fill account data
Correctly” message will be display.

Table 3. 9: Use case table for manage exam question
Use case name Manage exam

Use case ID Uc09
Actor EP
Description Use case to delete/update exam questions from/ to the system.
Precondition The EP must be login to perform those activities
Post condition System has successfully delete and update exam from/ to the system.
Basic course of action 1. The EP clicks delete/update question link.
2. The system displays the question information form (delete, and
update).
3. The EP select question to delete and update question.
4. ERS clicks delete/update button.
5. The questions delete from the system or update to the system.
6. Use case ends
.
Table 3. 10: Use case table for take exam.
Use case name Take exam

Use case ID Uc10
Actor Candidate
Description Use case to take exam.
Precondition The candidate must be login to the system.
Post condition System should provide exam to candidates.
Basic course of action 1. Candidates click take exam link.
2. The system displays exam.
3. Candidates start to work exam.
4. The candidates click send button.
5. Use case ends.
Alternative course of 3.1. When there is no question “on more question display”
action message will be display.

Table 3. 11: Use case table for view result
Use case name View exam result
Use case ID Uc11
Participating actor Candidate
Description This use case describes how candidates view their result.
Pre-condition The administrator must release the result
Post condition Candidates see their result.
Basic course of action 1. candidate click view exam link

2. System display exam result.
3. Use case ends.
Table 3. 12: Use case table for register exam
Use case name Register exam

Use case ID Uc13
Actor EP
Description Use case to register exam.
Precondition The EP must be login to the system.
Post condition EP should register exam to system.
Basic course of action 1. EP clicks add question link.
2. The system display exam registration form.
3. EP write question to the form.
4. The EP click add button.
5. Use case ends.

Table 3. 13: Use case table for register schedule.
Use case name Register schedule

Use case ID Uc14
Actor EEC
Description Use case to register schedule.
Precondition The EEC must be login to the system.
Post condition EEC should register schedule to system.
Basic course of action 1. EEC clicks add schedule link.
2. The system displays schedule registration form.
3. EEC fills the schedule information.
4. The EEC click add schedule button.
5. Use case ends.
Table 3. 14: Use case table for add user.
Use case name Add user

Use case ID Uc15
Actor Administrator
Description Use case to add new user.
Precondition The Administrator must be login to the system.
Post condition Administrator should add user to database.
Basic course of action 1. Administrator clicks add user link.
2. The system displays add user form.
3. Administrator fills user information.
4. The Administrator click add button.
5. The user added to the database.
6. Use case ends.

Table 3. 15: Use case table for change password.
Use case name Change password

Use case ID Uc16
Actor Administrator, Candidates, Manager, EEC, and EP
Description Use case to change account password.
Precondition User must be login to the system.
Post condition User should change their account to database.
Basic course of 1. User clicks change password link.
action 2. The system displays change user password form.
3. User fills required information.
4. The user clicks change button.
5 The system verifies the information.
6. The account change confirm to the database.
7. Use case ends.
Alternative course of 4.1 If the user fills invalid information the system return to step 3.
action
Table 3. 16: Use case table for prepare report.
Use case name Prepare report

Use case ID Uc17
Actor Manager
Description Use case to prepare report.
Precondition Manager must be login to the system.
Post condition Manager should generate report.
Basic course of 1. Manager clicks view report link.
action 2. The system displays report information.
3. Manager prepares report.
4. The user clicks save button.
5. Use case ends.

Table 3. 17: Use case table for print certificate.
Use case name Print certificate

Use case ID Uc19
Actor Manager
Description Use case to print certificate.
Precondition Manager must be logged to the system.
Post condition Manager should print certificate.
Basic course of action 1. Manager clicks prepare report link.
2. The system displays candidate information.
3. Manager click print button.
4. Use case ends.
Table 3. 18: Use case table for send receipt number.
Use case name send receipt number

Use case ID Uc20
Actor cashier
Description Use case to send receipt number.
Precondition Cashier must be logged to the system.
Post condition Cashier should send receipt number.
Basic course of action 1. Cashier clicks on receipt form.
2. The system displays receipt form.
3.Cashierfills receipt number.
4. Cashier click send button.
4. Use case ends.

3.3 Sequence Diagrams
A sequence diagram in a unified modeling language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. A sequence diagram shows object interactions arranged in times
sequence.
sd Sequence model
Home Page LoginForm Page User Page DB
User
Controller
Login
SD#1
1 Open web site. open ()
2. System display login

form
Create login form()
3. enter username and
password
4. click login button.

enter username and password()
5. system verify login
password and
username click login button()
6. System display user

page data()
verify()
enter correct username and password()
Display user page()
Figure 3. 2: Sequence diagram for login

Figure 3. 3: Sequence diagram for registration.

Figure 3. 4: Sequence diagram for evaluate exam

Figure 3. 5: Sequence diagram for view report

Figure 3. 6: Sequence diagram for view result.

Figure 3. 7: Sequence diagram for send receipt number.

Figure 3. 8: Sequence diagram for add questions.

Figure 3. 9: Sequence diagram for add schedule.

Figure 3. 10: Sequence diagram for add user..

Figure 3. 11: Sequence diagram for change password.

3.4 Activity diagramming
An Activity diagram is similar to a flowchart to represent the flow from one activity to another
activity. Activity diagrams and State chart diagrams are related. While a State chart diagram
focuses attention on an object undergoing a process (or on a process as an object), an Activity
diagram focuses on the flow of activities involved in a single process. The Activity diagram
shows how these single-process activities depend on one another.
Figure 3. 12: Activity diagram for login

Figure 3. 13: Activity diagram for user registration in the system

Figure 3. 14: Activity diagram for add account.

Figure 3. 15: Activity diagram for Evaluate exam

Figure 3. 16: Activity diagram for view report

Figure 3. 17: Activity diagram for change password

3.5 Analysis level class diagram
Class diagrams 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 the classes. The class diagram with its
corresponding objects will be present in the following diagram.
Figure 3. 18: Class diagram

3.6 User interface prototyping
Figure 3. 19: User interface prototyping for login

Chapter Four
4 System design
4.1 Introduction
This system design document is develop for describing the system design activities carried out
during the design phase for COC management system.
First, it describes the primary design goals set for the project (section 4.1). Next, the document
describes the system under development in terms of subsystem decomposition (section 4.2), class
modeling (section 4.3), State chart modeling (section 4.4), Collaboration Modeling(section 4.5),
Component Modeling (section 4.6), Deployment modeling (section 4.7), and Persistence
modeling(section 4.8). This Chapter is also uses to define the interfaces between teams of
developers and as a reference when architecture level definitions need to be revisited. Generally
the purpose of this chapter is to determine how we are going to build our system and to obtain
the information needed to derive the actual implementations of our system.
4.2 Design Goals

The design goals derived from the non-functional requirements of the system. They describe the
desired qualities that the system should have and provide a consistent set of criteria that should
be take into consideration when making design decisions. These goals consider the following
criteria of Patient Management System development.
 Reliability: the system shall be more reliable to accomplish each and every activity.
And this is the number one requirement of the system through the reason of:-
 The system will expected to perform all tasks consistency.
 Availability: The system should be available for twenty four hours of a day so that
the users can have access to it at any time. The system should also be designed to
prompt the user with password and user name. This provides security in such a way
that unauthorized users can not have access to the system’s resources. Moreover, the
system should be designed to reject invalid user inputs to ensure the system’s
robustness and reliability for all interacting users.
 Security: the system provides the service to the user based on their given privilege
The security tasks that are performed by the system are:-
 Password is hidden from the user

 Sensitive data’s are encrypted (like payment amount, password and patient
Laboratory result) to hide from the database user
 Performance: Performance considers different factors and these are :-
 Complexity: The system should need a very small amount of time the memory
space used by the system should be less except for the databases and files to be
stored related to the system.
 Responsive time: The response time to users request should be tolerable.
 End user: The system should provide user friendly and self-explanatory graphical
user interface that eases the interaction of the user with the system. In addition, the
system should have user manuals and help files.
 Usability: the system should be designed in such a way that users should find
convenient to interact with it.
4.3 Subsystem Decomposition

Our system provides several services. To effectively providing these services as per the goals
specified, the system would decompose into different subsystems. The subsystems would
describe below and followed by a diagram showing the dependencies among subsystems.
A. User account Management subsystem:
The subsystem responsible for manage user account of the system by taking care of login
information of different users. It manages user name and password of all user of system
for security purpose.
Operation provided by subsystem is:
Manage user account
 Create account()
 Delete account()
 Update account()
 Change Password()
B. Management questions preparation subsystem
 add question()
 delete question()
 Update Questions()
C. Management report subsystem
 Report candidate result()
 Exam result()

COC management system
Report management Subsystem
User account management Subsystem

Patient treatment System Manager
User account
Question Management subsystem

Register Schedule
Candidate Question
Registration Exam evaluator
Candidate
Approve Exam provider

Cashier
Report
Print
View report
Exam result
Figure 4. 1Subsystem diagram

4.4 Class modeling
Class diagrams are the most common diagram found in modeling object-oriented systems. The
classes used in this system are in the diagram below.
Figure 4. 2 Class diagram

4.5 State chart modeling
In this part the team used to model the behaviors of the objects by drawing the state diagram.
The state diagram depicts the state of objects as their attributes change from state to the other
state. State chart modeling is used to show the sequence of states that an object goes through, the
cause the transition from one state to other and the action that result from a state change.
Figure 4. 3 State chart diagram for login

Figure 4. 4State chart diagram for evaluate exam

Figure 4. 5State chart diagram for generate report

Figure 4. 6 State chart diagram for register schedule

Figure 4. 7 State chart diagram for register exam

4.6 Collaboration Modeling
We are derived Collaboration diagram from sequence diagram it describes interactions among
objects in terms of sequenced messages for our system.
Figure 4. 8 Collaboration
ollaboration diagram for registering in the system

Figure 4. 9 Collaboration diagram for add schedule
Figure 4. 10 Collaboration diagram for login

Figure 4. 11Collaboration
ollaboration diagram for change password
Figure 4. 12Collaboration diagram for register question

4.7 Component Modeling
Component diagram is a special kind of diagram in UML. The purpose is also different from all
other diagrams discussed so far. It does not describe the functionality of the system but it
describes the components used to make those functionalities.
Purpose of the component diagram can be summarizing as:
 Visualize the components of a system.
 Construct executables by using forward and reverse engineering.
 Describe the organization and relationships of the components.
Figure 4. 13 Component diagram

4.8 Deployment modeling
Deployment diagram shows static view of the run time configuration of processing nodes
(Actors) and the components (use cases) that run on those nodes. In other words,
deployment diagram shows the hardware of our system, and the software that to be
installed in that hardware and the middleware used to connect the disparate machines to
one another. It also shows how hard ware and software components work together.
Figure 4. 14 Deployment diagram

4.9 Persistence modeling
Persistence modeling needs to use to communicate each other the design of the database in our
system, it is usually the database to both the users of C
COC-MS
MS and for the developers. It is also
used to describe the persistence data aspect of CCOC-MS system.
The following diagram indicates the persistence diagram of the C

COC-MS:
Figure 4. 15 Mapping Generalization relationship into Single Table

Figure 4. 16 Mapping From Many-Many Relation Ship
Figure 4. 17 Mapping from Many-Many Relation Ship

Figure 4. 18Mapping from Many-1 Relation Ship
Figure 4. 19Mapping from One-One Relation Ship

The data storage schema and data management of COCMS is the diagram below.
Figure 4. 20Diagram for database design

4.10 User Interface design

The goal of user interface design is to make the user's interaction as simple and efficient as
possible, in terms of accomplishing user goals what often called user-centered design. Good
user interface design facilitates finishing the task without drawing unnecessary attention to it.
The following interface design pictures describe the logical characteristics of some interfaces
between the system and the users. So the sample interface shown below:
Figure 4. 211: Home page interface

Figure 4. 222: User login interface

Figure 4. 233: Candidate registration interface

Figure 4. 244: Adding question interface

Chapter Five
5 Implementation and Testing
5.1 Introduction
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-management
system. The project implements PHP, MySQL and standard HTML. The project will be capable
of running on standard internet web browsers. The interface for the project will provide a good
navigation to user of the system with nice look and feel.
5.2 Final Testing of the system

Testing is the final phase of implementation. Testing is a process to show the correctness of the
program. We have seen the following different testing strategies
5.2.1 Unit test

Unit testing is every module of the System is separately tested.
Change role
This is a use case that an manager uses for changing the role of users. It has the following
structure that a user can navigate with.
Functioning: The system is working in such a way.
The manager can change their role by clicking in the change role button.
Sample Code: This use case has the following internal codes:
<?php
if(isset($_POST['submit'])){

$servername = "localhost";
$username = "root";
$password = "";
$dbname = "coc";
$role = mysql_real_escape_string($_POST['role']);
$idd = mysql_real_escape_string($_POST['user_id']);
$conn = mysqli_connect($servername, $username, $password, $dbname);
if (!$conn) {
die("Connection failed: " . mysqli_connect_error());
$sql = "SELECT * FROM users WHERE id = '$idd'";
$result = mysqli_query($conn, $sql);
if (mysqli_num_rows($result) > 0) {
// output data of each row
while($row = mysqli_fetch_assoc($result)) {
$selected_id = $row['id'];
$selected_role = $row['role'];
$sql = "UPDATE users SET role='$role' WHERE id='$selected_id'";
$query1 = mysqli_query($conn, $sql);
if ($query1) {
session_start();
if ($_SESSION['role'] == 'manager') {
echo "<script>alert('User Role Changed

Sucssesfuly!!!');window.location='change_role_manager.php';</script>";
}else{

echo "<script>alert('User Role Changed
Sucssesfuly!!!');window.location='change_role.php';</script>";
else {
echo "Error on Changing Role: " . mysqli_error($conn);
}
}
?>
Add Questions:
This is a use case that an exam provider uses for adding questions (for real exam).It has
the following structure that a user can navigate with.


 A user can add new question: by providing question details, fill the controls on the
right side of the form then click on “Add” button.
 This use case has the following sample PHP code:
<?php
include 'connection.php';
if(isset($_POST['submit'] )){
$question = mysql_real_escape_string($_POST['question']);
$choice_1= mysql_real_escape_string($_POST['choice_1']);
$choice_2 = mysql_real_escape_string($_POST['choice_2']);
$time = mysql_real_escape_string($_POST['time']);

$level = mysql_real_escape_string($_POST['level']);
$sector = mysql_real_escape_string($_POST['sector']);
$occupation = mysql_real_escape_string($_POST['occupation']);
$answer = mysql_real_escape_string($_POST['answer']);
$role = 'exam_provider';
$question_type = 1;
$comment = 'null';
$status = 3;
$user_id = $_SESSION['user_id'];
$username = "root";
$password = "";
$dbname = "coc";
$conn = new mysqli($servername, $username, $password, $dbname);
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}
$sql="INSERT INTO questions
(question_type,question,level,choice1,choice2,choice3,choice4,answer,comment,occupation,sect
or,status,user_id,timee) VALUES
('$question_type','$question','$level','$choice_1','$choice_2','$choice_3','$choice_4','$answer','$c
omment','$occupation','$sector','$status','$user_id','$time') ";
if ($conn->query($sql) === TRUE) {

echo
"<script>alert('succesfully_Added!!!')k;window.location='all_choices_by_provider.php';</script
>";
header('location:all_choices.php');
} else {

echo "Error: " . $sql . "<br>" . $conn->error;
}
$conn->close();
}
Take Exam:
This is a use case that a candidate is taking an exam. A candidate is supposed to take his/her
specific level. This is done after the student is assigned to a particular level at its registration
time.
 A candidate selects answer in the radio button.

 The timer counts down and if reach 00:00 it redirects the candidate to see his exam result.
Undone questions are assumed to be “X”.
Sample Code: This use case has the following internal codes:
<?php
$username = "root";
$password = "";
$dbname = "coc";
$level = $_SESSION['level'];
$occupation = $_SESSION['occupation'];

$sector = $_SESSION['sector'];
$conn = new mysqli($servername, $username, $password, $dbname);
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}
$sql = "SELECT * FROM result WHERE candidate_id = '$user_id'";
$result = $conn->query($sql);
$question_number = 0;
if ($result->num_rows > 0) {
echo "<h1 style='color: green;text-align:center;'> Dear ".$_SESSION['first_name']."
".$_SESSION['last_name']."</h1>";
echo "<h1 style='color: ;text-align:center;'>You have Taken the COC Examination
Already!</h1><hr>";
}else{
$sql2 = "SELECT * FROM Schedule WHERE occupation ='$occupation' AND level = '$level'
AND sector = '$sector'";
$query2 = $conn->query($sql2);
if($query2->num_rows <= 0){
echo "<h1 style='color: green;text-align:center;'> Dear ".$_SESSION['first_name']."
".$_SESSION['last_name']."</h1>";
echo "<h1 style='color: ;text-align:center;'>You have No Schedule!</h1><hr>";
}else{
echo "<h1 style='text-align: center;color: green;'>Your Exam Already Started!!! GooD
Luck!</h1>";
$level = $_SESSION['level'];
$occupation = $_SESSION['occupation'];
$sector = $_SESSION['sector'];

$sql = "SELECT * FROM questions WHERE occupation = '$occupation' AND level = '$level'
AND sector = '$sector'";
$result = $conn->query($sql);
$question_number = 0;
if ($result->num_rows > 0) {
// output data of each row
while($row = $result->fetch_assoc()) {
$question_number++;
if($row['status'] == 1){
if($row['question_type'] == 1){
echo"<h5style='color:green'>#".$question_number.",</h5><span><h1>".$row['question']."</h1>
</span>";
echo"<input required='true' type='radio' name='".$row['id']."'
value='1'>".$row['choice1']."<br/>";
echo "<input required='true' type='radio' name='".$row['id']."'
echo "<hr><br>";
}
elseif ($row['question_type'] == 2) {
echo "<h5 style='color:green'>#".$question_number.",</h5><h1>".$row['question']."</h1>";
echo "<input type='text' name='".$row['id']."' placeholder='Make sure your
spellings...' required='true' class='form-control form-control-user'/><br/>";
}
elseif ($row['question_type'] == 3) {

echo"<h5style='color:green'>#".$question_number.",</h5><span><h1>".$row['question']."</h1>
</span>";
echo "<input required='true' type='radio' name='".$row['id']."' >TRUE<br/>";
echo "<input required='true' type='radio' name='".$row['id']."' >FALSE<br/>";
echo "<hr><br>";
}
}
}
}
echo '<input type="submit" name="submit" value="Finished!">
}
5.3 Hardware software acquisitions

To implement (develop) this project we shall use HTML, JavaScript for front end (developing
Graphic user interface).
Tools we will use additional software to different tasks.
Microsoft word 2010/2013
Microsoft PowerPoint 2010/2013
Xamp Web Server
5.4 User manual preparation

User manual preparation since the system is computerized, everything important for the
user will be explained and implemented while preparation of short training document when the
system is deployed.
5.5 Training
Training manuals serve the important purpose of providing a consistent way to communicate
instructions to users about how to perform essential functions of their jobs by using the system.
They benefit ICT officer responsible for educating workers about the system as well as users
themselves, by providing content and structure necessary to train new users and to manage the
performance of incumbent users. To be effective, training manuals is based on functionalities
and instructional objectives. Information should be provided about the processes and procedures

users are required to follow as well as tasks that form the basis of the jobs they are charged with
performing.
5.6 Installation
Installation of our proposed system at minimum requires a computer to serve as a computer to
run the program. In addition, WAMP or XAMPP software needs to be installed and configured
so that the database and other interrelated functions can be process.
To do this project we used PHP, HTML, JAVASCRIPT, CSS as front end and WAMP Server as
back end database.
5.7 Start-up strategy

Once the system has start-up strategies:
the first start-up strategy is for the manager, EEC, exam provider and cashier who require the
username and password to access the system in all cases of users. The owner accessibility part is
restricted for the owner and the other are do as it. The users or candidates start-up strategy part is
the system home page, which does not require the username and password and it can be viewed
by anybody.

Chapter Six:
6 Conclusions and Recommendation
6.1 Conclusions
A COC-MS is a computer-based exam taking, exam marking and exam result viewing system. It
will solve most manually introduced problems such as un-readability of candidate answer,
cheating among candidate, manual correction error, etc. And make examination-related tasks
simple. It is a web-based application, which will host in the institute local area network and is
available to the candidate within the institute. It allows Exam provider to add questions, edit
questions, delete questions. It provides exam to candidate of the Kombolcha TVET institute and
automatically show their exam results.
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 COC-management system
for Kombolcha TVET collage.
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 COC-Exam questions
available digitally and usable anywhere within the institute network. This is achieved by
allowing Exam provider users to add questions according the level that will provided and
candidate to use them.

6.2 Recommendation
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 other coming students to make this project expanded and more
automated with additional functionalities and by integrating with many new technologies
We recommend to working the following functionality in the future:
 Online Payment system
 Includes practice and oral exam
 Online examination rather than web based exam

Appendix A
Questions asked during requirement gathering using interview

Q1. What are the objectives of your colleges?
Q2. How does your current system work?
A. Is it manual?
B. is it computerized.
C. is it semi-automated.
Q3. How to register candidate for take COC exam?
Q4. In what way exam taken ?
Q5. How candidate seen exam result after exam taken?

References
1. http://www.tvet.org
2. Kombolcha TVET collage background information
3. http://en.wikipedia.org/wiki/Object-oriented_design
4. http://www.tvet.org
5. http://www.google.com

FINAL PROJECT DOCUMENTATION (1) Done at Wollo University

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FINAL PROJECT DOCUMENTATION (1) Done at Wollo University

Uploaded by

Copyright:

Available Formats

WOLLO UNIVERSITY

KOMBOLCHA INSTITUTE OF TECHNOLOGY

Kombolcha, Wollo, Ethiopia

Znabu H/selasie _________________________

Mohammed Melash _________________________

Mohammed Abdu _________________________

Mohammed Yesuf _________________________

Melkamu Alemnew _________________________

College: College of Informatics

Program: Bachelor of degree

1. Chairman ____________ ____________ __________

2. Examiner1 ____________ ____________ __________

3. Examiner 2 ____________ ____________ __________

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY I

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY II

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY III

Chapter two .................................................................................................................................................. 8

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY IV

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY V

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY VI

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY VII

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY VIII

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY IX

COC Center of Competence

COCMS COC Management System.

CRC Candidates registration committee

CS Cascading Style Sheet

DBMS Database Management system

EEC Exam evaluation committee.

KTC Kombolcha TVET Collage

PHP Hyper preprocessor Scripting language..

TVET Technical and Vocational Education and training

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY X

1.2 Introduction of the project

1.3 Statement of the Problem

 Delay of exam marking and result report viewing.

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 1

1.4 Objective of the project

1.5 Scope and limitation of the project

1.5.2 Limitation of the project

1.6 Significance of the Project

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 2

1.7 Target beneficiaries of the system

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 3

1.9 System Development methodology

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 4

Type Item Quantity Price per Item Total Item

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 5

Table 1. 2: Time schedule to complete this project

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 6

Table 1. 3: Team composition table

No Team members ID Number Role on group Role on the project work

1 Zinabu H/slassie WOUR/2072/08 Coordinator System Analyst

2 Mohammed Melash WOUR/1985/08 v/coordinator Implementation

3 Mohammed Abdu WOUR/1983/08 Secretary Testing

4 Mohammed Yesuf WOUR/1982/07 Member Designer

5 Melkamu Alemnew WOUR/1966/08 Member Designer

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 7

2.2 Player of the existing system

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 8

2.3 Business Rule of the organization

2.4 Major activities of the existing system

WOLLO UNIVERSITY, KOMBOLCHA INISTITUTE of TECHNOLOGY Page 9

1. Chairman __

2. Examiner1 __

3. Examiner 2 __