Bahir Dar University

Bahir Dar Institute of Technology

Faculty of computing
Computer Science and Engineering (Software Stream)

Project on

GRADUATE VERIFICATION SYSTEM

For higher educational institutes in Ethiopia

June, 2016
Bahir Dar, Ethiopia
Graduate Verification System

Graduate Verification System

For higher educational institutes in Ethiopia

By Gebremedihn Mekonen
Samson Endale

Advisor Desta Berihu

A project submitted to Faculty of Computing of Bahir Dar

University in fulfillment of the course project thesis.

June, 2016 P a g e 1 | 57

Bahir Dar, Ethiopia

Graduate Verification System

Declaration
The Project is our own and has not been presented for a degree and/or course project in
Bahir Dar University and/or in any other university and all the sources of material used
for the project have been duly acknowledged.

Gebremedihn Mekonen
Name Signature

Samson Endale
Name Signature

Faculty Computing
Program Computer Science and Engineering(Software Stream)
Project Subject Ministry of Education Graduate Verification System
for higher educational institutes in Ethiopia

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 Bachelor Thesis.

Desta Berihu
Name Signature

Examining committee member’s signature Date

1. Examiner 1 ____________________________________
2. Examiner 2 _____________________________________
It is approved that this project has been written in compliance with the formatting rules
laid down by the school of the university.

P a g e 2 | 57
Graduate Verification System

Acknowledgment
First of all we would like to thank God the almighty for everything that ever happened.
Secondly we would like to give our deep sense of gratitude to Instructor Desta Berihu
for his advice and support from the beginning of this wonderful project. Then we would
like to thank Seffi Gebeyehu who is the dean of computing faculty at Bahir Dar
University and all of the faculty instructors for their fruitful support and
acknowledgement.
We also want to thank Dr. Kaba Urgessa who is State Minister for Higher Education, Mr.
Zalalem Asefa who is the CEO of Ethiopian Education Research Network and his ICT staff
members, Dr. Baylie Damtie who is the president of Bahir Dar University, Dr. Mulunesh
Abebe who is Vice President of research and community service at Bahir Dar University,
Mr. Atnafu who is the ICT director of Bahir Dar University and his ICT team members,
Instructor Getenet Mamo at Computing Faculty for their kindly response to all our
questions and who give as a lot of feedback and appreciation.
We sensory want to thank everyone who are helping us to successfully accomplish this
project.
Lastly we would like to thank our family for their support throughout the years.

P a g e 3 | 57
Graduate Verification System

P a g e 4 | 57
Graduate Verification System

Table of content
Acknowledgment ............................................................................................................................ 3
Table of content .............................................................................................................................. 5
List of Figures .................................................................................................................................. 6
List of Tables ................................................................................................................................... 7
List of Acronyms .............................................................................................................................. 8
Chapter one .................................................................................................................................... 9
1. Introduction ........................................................................................................................ 9
1.1 Background ....................................................................................................................... 9
1.2 Existing System Study ................................................................................................. 10
1.3 Proposed System ........................................................................................................ 11
1.4 Objective of the project .............................................................................................. 11
1.5 Scope and limitation of the project ............................................................................ 11
1.6 Methodology for the project ...................................................................................... 12
1.7 Significance of the project .......................................................................................... 15
1.8 Organization of the project ........................................................................................ 15
Chapter two .................................................................................................................................. 16
2 System Features ................................................................................................................ 16
2.1 Existing system description ........................................................................................ 16
2.2 Proposed system description ..................................................................................... 16
2.3 User requirement ....................................................................................................... 16
2.4 System requirement ................................................................................................... 19
2.5 Analysis Model............................................................................................................ 30
Chapter three ................................................................................................................................ 40
3 System design ................................................................................................................... 40
3.1 Deployment diagram .................................................................................................. 40
3.2 Architectural design .................................................................................................... 41
3.3 User interface design .................................................................................................. 44
3.4 Data structure design ................................................................................................. 54
Bibliography .................................................................................................................................. 56

P a g e 5 | 57
Graduate Verification System

List of Figures
Figure 1: Use case 1 ...................................................................................................................... 20
Figure 2: Use case 2 ...................................................................................................................... 21
Figure 3: Use Case 3 ...................................................................................................................... 21
Figure 4: Login activity for minister administrator: ...................................................................... 30
Figure 5: Register graduate process for graduate administrator ................................................. 31
Figure 6: API graduate registration process ................................................................................. 32
Figure 7: Administrator Password Reset ...................................................................................... 33
Figure 8: Graduate Verify Process ................................................................................................ 34
Figure 9: Minister Administrator Login Sequence Diagram ......................................................... 35
Figure 10: Graduate Administrator Registering Graduate Sequence Diagram ............................ 36
Figure 11: Anonymous User Verifying Graduate Sequence Diagram ........................................... 37
Figure 12: Integrated Application Registe0ring Graduate Sequence Diagram ............................ 38
Figure 13: Deployment diagram ................................................................................................... 40
Figure 14: Models Class Diagram .................................................................................................. 41
Figure 15: Requests Class Diagram ............................................................................................... 42
Figure 16: Controllers Class Diagram ............................................................................................ 43
Figure 17: Login Page .................................................................................................................... 44
Figure 18: Password reset page .................................................................................................... 45
Figure 19: Graduate verify page ................................................................................................... 46
Figure 20: Graduate Verified page ................................................................................................ 47
Figure 21: Two Factor Authentication .......................................................................................... 48
Figure 22: Minister Administrator Dashboard .............................................................................. 49
Figure 23: Programs page ............................................................................................................. 50
Figure 24: Fields page ................................................................................................................... 51
Figure 25: Change password page ................................................................................................ 52
Figure 26: Institute view page ...................................................................................................... 52
Figure 27: Upload institute logo ................................................................................................... 53
Figure 28: Applications page ......................................................................................................... 53
Figure 29: Graduate confirmation form ....................................................................................... 54
Figure 30: Entity Relationship Diagram ........................................................................................ 55

P a g e 6 | 57
Graduate Verification System

List of Tables
Table 1: List of Acronyms ................................................................................................................ 8
Table 2: Functional requirement .................................................................................................. 19
Table 3: Non Functional Requirements ........................................................................................ 19

P a g e 7 | 57
Graduate Verification System

List of Acronyms
Abbreviation Words
API Application Programming Interface
BDU Bahir Dar University
CSS Cascaded Style Sheet
EBC Ethiopian Broadcasting Corporation
GVS Graduate Verification System
HTML Hyper Text Markup Language
IDE Integrated Development Environment
JS Java Script
LTS Long Term Support
MOE Ministry Of Education
MS Microsoft
MVC Model View Controller
PHP PHP: Hypertext Processor
SMS Short messaging service
SQL Structured Query Language
VCS Version Control System
Table 1: List of Acronyms

P a g e 8 | 57
Graduate Verification System

Chapter one
1. Introduction
1.1 Background
Ministry of Education is part of government which is responsible for everything related
to education.
The Federal Democratic Republic Government of Ethiopia's Ministry of Education strives
to
 Provide a good quality primary education with an ultimate aim of achieving
universal primary education over a period of 20 years.
 Make education relevant by providing problem solving skills and an all-round
education catering to the needs of the individual and the society.
 Provide vocational education and training at different levels attuned to the
manpower requirements of the economy.
 Provide a secondary education of appropriate quality in an equitable way.
 Promote a higher education of good quality, relevance and focusing on
research and development.
 Make available special and non-formal education in line with the needs and
capability of the country.
 Improve the quality of training, professional competence and career
structure of teachers and other professionals.
 Streamline the management and organization of the educational system so
as to make it decentralized, coordinated, participatory, professional and
efficient.
 Increase the financing of education by encouraging community participation,
introducing cost sharing mechanisms, and involving the private sector in the
provision of education.
 Improve the collaboration and coordination of the education sector with
other relevant sectors.
1.1.1 Vision of MOE
To see all school age children get access to quality primary education by the year 2015
as well as ensure an efficient and cost effective education system producing skilled and
qualified human power that could play a leading role in development and building a
democratic system.
1.1.2 Mission of MOE
To Ensure the production of citizens who properly respect and enforce others to respect
the rights and responsibilities of citizens the constitution provides, who are vigilant to
P a g e 9 | 57
Graduate Verification System

enrich their capacity to solve problems, who would actively participate in development,
in building democracy and in the promotion of science and technology.
1.1.3 Values of MOE
 We are highly devoted to always strive to upgrade ourselves so that we would
have a proper professional efficiency to discharge our mission.
 We are committed to work towards expanding quality and equitable education,
as well as enriching an appropriate democratic culture.
 We are highly devoted to always strive to upgrade ourselves so that we would
have a proper professional efficiency to discharge our mission.
 We shall practically ensure that education is the key instrument for dealing with
development.
 We shall commit ourselves to discharge our responsibilities to serve the public in
honesty and integrity.

1.2 Existing System Study

Currently government, private sectors and individuals in Ethiopian have manual process
of verifying graduated students from higher educational institutes. This process involve
letter or phone communication. Usually institutes have one or more assigned personnel
to communicate with other institutes, MOE and other sectors to verify graduate.
Or the graduate will be required to request official copy from his/her graduating
institute.
1.2.1 Problem of existing system
Because of the tedious and time consuming process employers skip the verification
process leading forgers to exploit this vulnerability.
Usually the verification process is issued when there is some suspicious behavior.
So there are many problems that are seen on verifying a given accredit.
 There is no means of verifying a graduate from other institute instantly.
 Existing method to verifying is through stamp.
 The stamp that is used for verification can be easily faked.
 The original stamps can be used illegally through corruption.
 The deceits can be placed in crucial positions.
 The deceits can cluster job opportunity for the legal persons.
 The deceits can gain illegal resource, power, popularity, money and opportunity.
 The deceits can be judges of EBC entrepreneur’s competition.
 The deceits can be speaker of an institute’s conference.
In general they can hurt the economy, facilitate corruption and kill a generation.

P a g e 10 | 57
Graduate Verification System

1.3 Proposed System

To overcome the problems that exist in the current system of graduate verification
system the proposed system is the right software to be incorporated into the
Automation of verification Software for helping the institute and other organization
needs with respect to skillful man power and eligible employee. The proposed system
will be user-friendly and easy to adapt it and has the following function.
 We will create a means of verifying graduates
 We believe our online system can avoid forgery
 Reduce forgeries in institutes through corruption
 Everyone can refer and verify the graduate’s information
 We solve Ethiopian’s lack of accreditations problem by automating the process.

1.4 Objective of the project

1.4.1 General Objective
The main aim of this project is to develop a web based graduate verification system for
higher educational institute of Ethiopia.
1.4.2 Specific Objective
 In order to attain the general objective, the following list of specific objectives is
set:
 Perform a requirement analysis to find out the system functional and non-
functional requirements.
 Design the system using object-oriented models for understanding the system
and to make the implementation easy.
 Design the database for storing graduate information using PostgreSQL
 Implement a web application using PHP, bootstrap, Laravel framework and web
server.
 Test the performance and reliability of web application.
 Create a Graduate Verification System
 Simplify and centralize the process of verification
 A system efficiently capable of verifying graduates from all over the country with
minimal cost and time.
 We believe that the system will be avoid forgery once and for all.
 The system will have maximum security with two factor Authentication and
forcing to change password with limited hours.

1.5 Scope and limitation of the project

The scope of this system is only focus on Ethiopian higher educational institutes.

P a g e 11 | 57
Graduate Verification System

1.6 Methodology for the project

To achieve the main and specific objectives of the proposed system, the producer
decided to use the following lists of methods in analysis, design and implementation
Phases of the project. By using different fact-finding methods producer will try to gather
information from the following data sources.
We use some techniques to find information to our project as a methodology this are:
Interview: to get the basic information about the existing system, producer will
interview the institute and some governmental body about the services that are used,
and the problems associates with that service.
Observation: by showing the deceits can be judges of EBC entrepreneur’s competition
through Ethiopian television and the deceits can be speaker of an institute’s conference.
1.6.1 Tools use in this project
1.6.1.1 Software to be used
This MOE graduate verification system will be implemented with the following software
technologies: -
Software tools
 Microsoft Word 2013
o Microsoft word it a proprietary rich text editor from Microsoft
Corporation.
o We have used MS Word for writing documentation.
o We choose Microsoft word because
 It the best rich text editor in the market
 It’s almost has no competitor with its feature list.
 We are experienced with it
 Visual Paradigm 8
o Visual paradigm is a proprietary software for Software Design
o We have use Visual paradigm for drawing UML diagrams
o We choose Visual paradigm because
 It is a modern software relative to Microsoft Visio
 It collaborative environment
 It can export diagrams in many formats
 PhpStorm 2016
o PhpStorm provides an editor for PHP, HTML and JavaScript with on-the-
fly code analysis, error prevention and automated refactoring’s for PHP
and JavaScript code. PhpStorm code completion supports PHP 5.3, 5.4,
5.5, 5.6 and 7.0 (modern and legacy projects), including generators, the
finally keyword, list in foreach, namespaces, closures, traits and short

P a g e 12 | 57
Graduate Verification System

array syntax. It includes a full-fledged SQL editor with editable query

results.
o We have used PhpStorm for doing implementation
o We choose PhpStorm because
 PhpStorm is simple the best IDE for PHP
 It understand modern Object Oriented PHP code
 It has the best autocomplete for PHP for faster development
 HeidiSQL 9.3 as a SQL Client for viewing data on database
o HeidiSQL is an open source SQL client
o We have used HeidiSQL to manage our database
o We choose HeidiSQL because
 We don’t want to use a web base SQL clients like PhpMyAdmin
because they are slow
 HeidiSQL is light weight (< 5 MB) free windows application
 Heidi SQL can connect to MySQL, MariaDB, PostgreSQL and SQL
Server
 Git 2.6
o Git is a widely used version control system for software development.
o It is a distributed revision control system with an emphasis on speed,
data integrity, and support for distributed, non-linear workflows.
o We are using git to track and collaborate on our project
o We choose git because
 Git is an open source VCS
 It is fast, secure and distributed
 It is state of the art software developed by Linus Torvalds which is
the creator of the Linux Operating System
 Composer
o Composer is an open source application-level dependency manager for
the PHP that provides a standard format for managing dependencies of
PHP software and required libraries.
o We have used composer to handle our dependencies
o We choose composer because
 It’s the recommended way of developing modern PHP application
 It’s has no competitor
 The framework and libraries we used requires it
Programing and scripting languages
 PHP
o PHP is a server-side scripting language designed for web development. As
of January 2013, PHP was installed on more than 240 million websites
(39% of those sampled) and 2.1 million web servers.
P a g e 13 | 57
Graduate Verification System

o We have used PHP in backend

o We used PHP because
 PHP is very fast
 PHP is open source
 PHP is what we learned on Bahir Dar University
 HTML / CSS
o We have used HTML and CSS for the front end of the project since it’s a
web application.
 JavaScript
o We have used Java Script as client side programming language
Framework and Libraries
 Laravel 5.1
o Laravel is a free, open source PHP web application framework, designed
for the development of MVC web applications.
o According to a December 2013 developers survey on PHP frameworks
popularity, Laravel was listed as the most popular PHP framework of
2013, followed by Phalcon, Symfony2, CodeIgniter and others.
o As of August 2014, Laravel is the most popular and watched PHP project
on GitHub.
o We have used Laravel Framework to develop our project
o We have chosen 5.1 version for its LTS Support
 Bootstrap 3.6
o Bootstrap is a free collection of tools for creating websites and web
applications. It contains HTML and CSS-based design templates for
typography, forms, buttons, navigation and other interface components,
as well as optional JavaScript extensions.
o As of February 2015 it was the No.1 project on GitHub with over 77,000
stars and more than 29,000 forks.
o We have used bootstrap to enhance our front end
 JQuery 2.0
o JQuery is a cross-platform JavaScript library designed to simplify the
client-side scripting of HTML.
o Used by over 60% of the 10,000 most visited websites, jQuery is the
most popular JavaScript library in use today.
o JQuery is free, open-source software
Database management system
 PostgreSQL
o PostgreSQL is an object-relational database management system
(ORDBMS).

P a g e 14 | 57
Graduate Verification System

o We have used PostgreSQL because

 PostgreSQL is an open source software
 It support very large data to be stored
 It is very efficient
Operating system
 Windows 10
1.6.1.2 Hardware to be used
 PC
 At least 1.2 GB of memory.
 Normal screen resolution (1366 X 768)
1.7 Significance of the project
 Simplified process for the information consumers
 Save the government and everyone else from hiring an ineligible forger
 Save cost and time for the manual communication
 Increasing job opportunity for the verified graduates.
 Increasing industrial productivity by hiring eligible employees.
 Increasing quality of education by hiring eligible instructors and teachers.
 Increasing health treatment by hiring eligible health professions
 Easy to control the accredited fields and programs given to the institute for MOE
 Easy to know the statistical data of educated people in the indicated fields and
programs in our country for the institute and MOE
Builds a corner stone and a platform to future automated integrated data warehouse
for MOE

1.8 Organization of the project

In these topic to discussing system details through each topics, included topics are
abstraction, existing system, Problem of the existing system, Significance of the project,
general and specific objectives of the project, scope the project, proposed system and
Methodology. After that the next step to do is system features, system design and
implementation of the project.

P a g e 15 | 57
Graduate Verification System

Chapter two
2 System Features
2.1 Existing system description
Existing system is using manual way of performing any activities for many processes
such as:
 Verifying graduate by phone communication
 Verifying graduate by sending official transcript
 Verifying graduate through stamp and signature
Verifying graduate by phone communication: - the graduates are going to the
organization to hiring and the organization manager will verify the graduate by calling
phone who graduates of the institute.
Verifying graduate by sending official transcript:-the graduate wants to hire to the
organization and the organization requests the graduate official transcript. Then the
graduate must be send the official transcript from their institute.
Verifying graduate through stamp and signature:- the institutes are verifying the
graduate certificate through their institute stamps and signature.

2.2 Proposed system description

To overcome the problems that exists in the current system of MOE graduate
verification System for higher educational institute in Ethiopia the new system with
more reliable way than the existing system. The proposed system can solve problems
that are maintained previously. New system verifying graduate automatically, control
the fields and programs by MOE. The new system allows organization to verify any
graduate information easily by using inserting some required fields and also this system
verifying process time and costs by minimizing some manual activities, this system
generate useful graduate information reports in any needed format. The system helps
the MOE to manage the institutes which give as programs and fields and the system
allow to register institutes, fields and programs for system administrators.

2.3 User requirement

In this topic we try to brief explanation of user requirements. User requirements include
functional and non-functional requirements. From functional requirements we try to
describe functionality or the system service by grouping each requirements .The same
as non-functional requirements we describe constraints on the service or functions
offered by the system in terms of timing constraints, constraints on the development
process, standards of the system.

P a g e 16 | 57
Graduate Verification System

The user requirements are divided in to two sections. One describes the functionality of
the system and the services it provide (Functional Requirements) and the other
describes the constraints under which it must operate (Non-Functional Requirements).
2.3.1 Functional requirement
Req ID Requirement Description Priority
R01 The administrator should able The user is validate upon login using HIGH
to provide his/her email and their email and password
password for authentication

R02 The administrator should able The administrator might forget their HIGH
to reset his password if they password and they should able to
forgot it reset their password with and a
reset email link

R03 The system should two factor The high privilege minister HIGH
authenticate higher privilege administrators should be
users with a SMS Code authenticated in two factor

R04 The minster administrator The minister administrator is the HIGH

should able to register one responsible for registering
institutes and institute institutes with its administrator
administrator

R05 The minster administrator The minister administrator is the HIGH

should able to accredit one responsible for accrediting
institutes offers institutes offers

R06 The minster administrator The minister administrator is the HIGH

should able to manage fields one responsible for registering,
in the system updating and deleting of the fields
in the system

R07 The minster administrator The minister administrator is the HIGH

should able to manage one responsible for registering,
programs in the system updating and deleting of the
programs in the system

R08 The mister administer should We don’t expect one minister HIGH
able to register another administrator to run the system so
minster administrator the minster administrator can fork
his role

P a g e 17 | 57
Graduate Verification System

R09 The minister administrator The minister administrator is MEDIUM

should able to generate responsible to generate report from
report the system

R10 The institute administrator The institute administrator is HIGH

should able to register offers responsible for registering the
departments of the institute offers

R11 The institute administrator The institute administrator is MEDIUM

should able to update responsible for updating the
institute information institute information

R12 The institute administrator The institute administrator is HIGH

should able to register and responsible for registering and
manage integrated removing institutes integrated
application APIs application API

R13 The institute administrator The institute administrator is MEDIUM

should able to register and a responsible for registering and
manage graduate removing graduate administrators
administrator

R14 The graduate administrator The graduate administrator is HIGH

should able to register responsible for the registration of
graduate graduate

R15 The graduate administrator The graduate administrator can HIGH

should able to import import graduates data from excel
graduates data

R16 The graduate administrator The graduate administrator can HIGH

should able to remove remove graduate if the data is
graduate from the system incorrect

R17 The system shall allow The system should have a way to HIGH
anyone to verify graduate verify graduate by anonymous user

R18 The system should Every API call must provide the key HIGH
authenticate every API call and secret token authenticated
with key and secret tokens

P a g e 18 | 57
Graduate Verification System

R19 An Integrated application The fields are required to register HIGH

should able to access an new graduate from external
available fields application

R20 An Integrated application The programs are required to HIGH

should able to access register an new graduate from
available programs external application
R21 An Integrated application Integrated application can register a HIGH
should able to register graduate with an API
graduate

R22 The system should provide a The unique URL will be embedded HIGH
unique URL to every graduate with graduate information

Table 2: Functional requirement

2.3.2 Non Functional Requirement

Describe the constraints the system will operate under.

Req.ID Requirement Category

NR1 The system shall be responsive for mobile devices Usability
NR2 The system shall have simple user interface.
NR3 The system should be to support all major browsers.
NR4 The system shall respond in maximum of 1 second Performance
NR5 The system shall run on all major operating systems. Portability
NR6 The system shall not fail at all. Reliability
NR7 The system shall inforce strong password Security
NR8 The system should store only hashed password
NR9 The system should be inforce to change password in a
limited time period
NR10 The system should checks the authorize administrator by
two factor

2.4 System requirement

The system requirements are expanded versions of the user requirements that are used as
the starting point for the system design. They add detail and explain how the user
P a g e 19 | 57

Table 3: Non Functional Requirements

Graduate Verification System

requirements should be provided by the system. The system requirement for this graduate
verification system includes the detailed descriptions of the functional requirements listed
above. This can be described in use case diagram and use case description given below.
The system’s requirements are here described in two parts. One describes in verbal
manner that could be understood by any user and diagrammatically for more advance
user.
2.4.1 Use case diagram
The following diagrams represents the overall functionality and associated actors.

Figure 1: Use case 1

P a g e 20 | 57
Graduate Verification System

Figure 2: Use case 2

Figure 3: Use Case 3

P a g e 21 | 57
Graduate Verification System

2.4.2 Use case description

Some of the use cases are of higher importance and relevance. Some of the most
relevant use cases are described below.

Use case No UC1

Use case name Login
Actor Ministry administrator, institute administrator and graduate
administrator
Description This use case should allow the administrator to enter into the functional
part of the system
Precondition The administrator must have user name and password
Post condition Desired administrator login to the system
Priority High
Basic course of User action System response
action 1. The administrator browse a. The system opens the site
the site of MOE of MOE to the
2. Administrators click on administrator
the login link b. System asks administrator
3. Administrator enter his/her to insert administrator user
user name and password name and password
4. Administrator click login c. The system validates the
button inputs are correct or not.
5. The use case ends d. Logged in page display.
Alternate course A1. If administrator the account information is not belonging to system
of action A2: the system asks to input the user name and password again.

Use case No UC2

Use case name Two factor authenticate
Actor Ministry administrator
Description This use case should allow the administrator to enter into the functional
part of the system
Precondition The administrator must have verification code
Post condition Desired administrator authenticate and login to the system
Priority High
Basic course of User action System response
action 1. Administrator enter his/her a. System sends a
user name and password verification code to
2. Administrator click verify administrator’s phone
button number to insert
3. The use case ends verification code
b. The system validates
the verification code
are correct or not.
P a g e 22 | 57
Graduate Verification System

c. Logged in page display.

Alternate course a. The administrator may b. System shows error
of action enter their verification messages.
code d. The system sends a
c. The administrator click try verification code.
again button. f. Logged in page display
e. The administrator enter the
verification code.

Use case No UC3

Use case name Change password
Actor Ministry administrator, institute administrator and graduate
administrator
Description The use case should allow administrator to change their password
Precondition The administrator must have password
Post condition Desired administrator successfully changed their password
Priority Medium
Basic course of User action System response
action 1. Administrator login into a. The system gives the
the system required field to
2. Administrator click change administrator
password button b. The system responses your
3. The administrator fill password is successfully
his/her old password, new changed.
password and confirm the
new password.
4. The use case ends.
Alternate course A1. The administrator may enter their old password and confirmation
of action password wrongly
A2. The administrator try to fill the required field.

Use case No UC4

Use case name Password reset
Actor Ministry administrator, institute administrator and graduate
administrator
Description This use case should allow the administrator to rest their password
Precondition The administrator must have a valid e-mail
Post condition Desired administrator reset their password
Priority High
User action System response

P a g e 23 | 57
Graduate Verification System

Basic course of 1. Administrators enters a a. The system asks login to

action valid e-mail and click on their e-mail.
the reset button b. The system should allow
2. Administrator login into reset their password.
his/her valid e-mail
3. Administrator enters their
new password
4. The use case ends

Use case No UC5

Use case name Signup
Actor institute administrator
Description This use case should allow the administrator to register into the system
Precondition The administrator must have their own name, e-mail, password and
institute name.
Post condition Desired administrator have an account
Priority High
Basic course of User action System response
action 1. The administrator browse a. The system opens the site
the site of MOE of MOE to the
2. Administrators click on administrator
the login link and next to b. System asks administrator
login click the register your to insert administrator
institute link. name, password e-mail and
3. Administrator enter his/her institute name.
name, password e-mail and c. The system force to
institute name. change password
4. Administrator click register d. The system shows the
button. desired interface
5. The administrator enters
the old password and new
password and click the
change password button.
6. The use case ends
Alternate course A1. If the institute administrators may not be signup on this step, you
of action can ask to the ministry administrator to register them.
A2. The ministry administrator register the institute and send their
password by their valid e-mail.

P a g e 24 | 57
Graduate Verification System

Use case No UC6

Use case name Print certificate
Actor graduate administrator
Description This use case should allow the graduate administrator to print a
certificate from the system
Precondition The administrator must have their own privileges.
Post condition Desired administrator can have print a certificate.
Priority High
Basic course of User action System response
action 1. The administrator login to a. The system allow to print
the system and click on the the certificate
print button.
2. The use case ends

Use case No UC7

Use case name Import graduate information
Actor Graduate administrator
Description This use case should allow the administrator to import graduate data
from excel file into the system
Precondition The administrator must have their user name and password.
Post condition Available the graduate information in the system
Priority High
Basic course of User action System response
action 1. The administrator login a. The system validate the file
into the system format is correct or not.
2. Administrator click the b. System response the data
import button and select is successfully imported.
the valid file.
3. The use case ends
Alternate course A1. If the graduate administrators may import wrong file
of action A2. You will check the correct format and import again.

Use case No UC8

Use case name Fetch program
Actor Integrated application
Description This use case should allow to communicate system to system through
web service.
Precondition The system should have a standard API
Post condition The integrated application fetch a program from another system
Priority High
User action System response
P a g e 25 | 57
Graduate Verification System

Basic course of 1. The integrated system a. The system validate the

action communicate the other requested data is correct or
system through soap or not.
restful web service b. System allow to put on the
2. The integrated system web service.
fetches the program
3. The use case ends

Use case No UC9

Use case name Fetch fields
Actor Integrated application
Description This use case should allow to communicate system to system through
web service.
Precondition The system should have a standard API
Post condition The integrated application fetch a fields from another system
Priority High
Basic course of User action System response
action 4. The integrated system c. The system validate the
communicate the other requested data is correct or
system through soap or not.
restful web service d. System allow to put on the
5. The integrated system web service.
fetches the fields
6. The use case ends

Use case No UC10

Use case name verify graduates
Actor Anonymous user and QR code reader
Description This use case should allow to verify graduates
Precondition The anonymous user should have graduate certificate in the form of
hard copy
Post condition The system should allow graduate verification
Priority High
Basic course of User action System response
action 1. The anonymous user a. The system opens the
browse the website of website of MOE.
MOE b. System validate the input
2. The anonymous user are correct or not.
inserts graduate c. The system displays the
information from the graduate information.
certificate or scans the
QR code on the
P a g e 26 | 57
Graduate Verification System

document by QR code
reader
3. The anonymous user
click on the verify
button or the ok button
on the smart phone.
4. The use case ends
Alternate course A1. If the anonymous user enters the graduate data wrongly
of action A2. The system asks to input the graduate data again

Use case No UC11

Use case name Authenticate token
Actor Integrated application
Description This use case should allow to match the secret key and secret token
between applications
Precondition Applications should have secret key and secret token
Post condition Sending a valid formatted data between application
Priority High
Basic course of User action System response
action 1. Integrated system a. The system validate the
sends secret key and secret key and secret token
secret token are matched or not to
2. Integrated application another application.
fetches needed d. The system allow to display
formatted data. information.
3. The use case ends

Use case No UC12

Use case name Manage programs
Actor Ministry administrator
Description This use case should allow to manage programs
Precondition The ministry administer should have a higher privilege
Post condition The desired administrator can be register, remove, edit and show
programs
Priority High
Basic course of User action System response
action 1. The administrator login a. The system allows to select
into the system the program to the
2. The administrator administrator.
select program from b. The system allow to
the drop down list manage to the
administrator
P a g e 27 | 57
Graduate Verification System

3. The administrator can

be select the wanted
button to manage
program.
5. The use case ends

Use case No UC13

Use case name Manage fields
Actor Ministry administrator
Description This use case should allow to manage fields
Precondition The ministry administer should have a higher privilege
Post condition The desired administrator can be register, remove, edit and show fields
Priority High
Basic course of User action System response
action 4. The administrator login c. The system allows to select
into the system the program to the
5. The administrator administrator.
select fields from the d. The system allow to
drop down list manage to the
6. The administrator can administrator
be select the wanted
button to manage
fields.
6. The use case ends

Use case No UC14

Use case name Manage institute
Actor Ministry administrator
Description This use case should allow to manage institute
Precondition The ministry administer should have a higher privilege
Post condition The desired administrator can be register, remove, and show and
approve institutes
Priority High
Basic course of User action System response
action 7. The administrator login e. The system allows to select
into the system the institute to the
8. The administrator administrator.
select institute from f. The system allow to
the drop down list manage to the
9. The administrator can administrator
be select the wanted

P a g e 28 | 57
Graduate Verification System

button to manage
institute.
7. The use case ends

Use case No UC15

Use case name Register minister administrator
Actor Ministry administrator
Description This use case should allow to register ministry administrator
Precondition The ministry administer should have a higher privilege
Post condition The desired ministry administrator registered on the part of the system
Priority High
Basic course of User action System response
action 1. The administrator login a. The system validate the
into the system user name and password
2. The administrator are correct or not.
enters the ministry b. The system allow to send a
administrator name password to the new
and email of the ministry administrator
administrator
3. The administrator click
on the register
administrator button
4. The use case ends

P a g e 29 | 57
Graduate Verification System

2.5 Analysis Model

2.5.1 Activity diagram

Figure 4: Login activity for minister administrator:

P a g e 30 | 57
Graduate Verification System

Figure 5: Register graduate process for graduate administrator

P a g e 31 | 57
Graduate Verification System

Figure 6: API graduate registration process

P a g e 32 | 57
Graduate Verification System

Figure 7: Administrator Password Reset

P a g e 33 | 57
Graduate Verification System

Figure 8: Graduate Verify Process

P a g e 34 | 57
Graduate Verification System

2.5.2 Sequence diagram

Sequence diagrams show the interaction between participating objects in a given use
case. They are helpful to identify the missing objects that are not identified in the
analysis object model. To see the interaction between objects, the following describe
the sequence diagram of each identified use cases. Is also used to add detail to use-
cases by showing the sequence of event processing in the system.

Figure 9: Minister Administrator Login Sequence Diagram

P a g e 35 | 57
Graduate Verification System

Figure 10: Graduate Administrator Registering Graduate Sequence Diagram

P a g e 36 | 57
Graduate Verification System

Figure 11: Anonymous User Verifying Graduate Sequence Diagram

P a g e 37 | 57
Graduate Verification System

Figure 12: Integrated Application Registe0ring Graduate Sequence Diagram

P a g e 38 | 57
Graduate Verification System

P a g e 39 | 57
Graduate Verification System

Chapter three
3 System design
3.1 Deployment diagram
The deployment diagram provides a physical look at the system with each processor and
device indicated. This provides a background for the rest of the document as no
software component can straddle two physical locations. Each physical location will
have its own software unit and units in different physical locations will collaborate to
provide the services that logically seem to be straddling the units.

Figure 13: Deployment diagram

P a g e 40 | 57
Graduate Verification System

3.2 Architectural design

3.2.1 Class Diagram
A class diagram describes the types of objects in the system and the various kinds of
static relationships that exist among them. A class is a description of a set of objects that
share the same attributes, operations, relationships, and semantics. Graphically, a class
is rendered as a rectangle, usually including its name, attributes, and operations in
separate, designated compartments.
Models
Models are class that extend the laravel ORM class. Every action in the database is
abstracted in this models. We didn’t write a single line of SQL code in our entire
application thanks to the laravel ORM. Because of this we can use any of the supported
database as we want from MySQL, MariaDB, SQLite, PostgreSQL or SQL Server.

Figure 14: Models Class Diagram

P a g e 41 | 57
Graduate Verification System

Requests
Requests are class which abstracts an HTTP request. Plus they handle the validation of a
request. Request objects are the one passed to the controller to be processed.

Figure 15: Requests Class Diagram

P a g e 42 | 57
Graduate Verification System

Controllers
Every request is routed to a specific controller. Controllers handle the business logic of
our application.

Figure 16: Controllers Class Diagram

P a g e 43 | 57
Graduate Verification System

3.3 User interface design

Describe the logical characteristics of each interface between the software product and
the users. This may include sample screen images, any GUI standards or product family
style guides that are to be followed, screen layout constraints, standard buttons and
functions (e.g., Logout) that will appear on every screen, keyboard shortcuts, error
message display standards, and so on. Define the software components for which a user
interface is needed.

Figure 17: Login Page

P a g e 44 | 57
Graduate Verification System

Figure 18: Password reset page

P a g e 45 | 57
Graduate Verification System

Figure 19: Graduate verify page

P a g e 46 | 57
Graduate Verification System

Figure 20: Graduate Verified page

P a g e 47 | 57
Graduate Verification System

Figure 21: Two Factor Authentication

P a g e 48 | 57
Graduate Verification System

Figure 22: Minister Administrator Dashboard

P a g e 49 | 57
Graduate Verification System

Figure 23: Programs page

P a g e 50 | 57
Graduate Verification System

Figure 24: Fields page

P a g e 51 | 57
Graduate Verification System

Figure 25: Change password page

Figure 26: Institute view page

P a g e 52 | 57
Graduate Verification System

Figure 27: Upload institute logo

Figure 28: Applications page

P a g e 53 | 57
Graduate Verification System

Figure 29: Graduate confirmation form

3.4 Data structure design

P a g e 54 | 57
Graduate Verification System

Figure 30: Entity Relationship Diagram

P a g e 55 | 57
Graduate Verification System

Bibliography
[1]. Ministry of Education Information Page, http://info.moe.gov.et
[2]. Ministry of Education, http://www.moe.gov.et
[3]. EthERNet, http://www.ethernet.edu.et
[4]. PHP Manual, http://www.php.net/
[5]. Laravel Framework doc, http://www.laravel.com/docs/5.2
[6]. Laracasts tutorials, https://laracasts.com/
[7]. Stackoverflow, http://www.stackoverflow.com

P a g e 56 | 57
Graduate Verification System

P a g e 57 | 57