DEBRE TABOR UNIVERSITY

FACULTY OF TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY
WEB BASED PROJECT
AND RESEARCH MANAGEMENT SYSTEM FOR DEBRE TABOR UNIVERSITY
Submitted
In partial fulfillment of the requirements for the degree of B.Sc.
In
Information Technology
BY:
GROUP 10 ID NO

1. Daniel Dagnaw -----------------------------------------------------IT/(R)/243/08

2. Melsew Worku-------------------------------------------------------IT/(R)/043/08

3. Mihrete Temesgen---------------------------------------------------IT/(R)/107/08

4. Solomon Yirdaw-------------------------------------------------------IT/(R)/105/08

Mr. Advisor Alemu Workneh

Submitted date: June/2019

Debre Tabor, Ethiopia

 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Declaration
This is to certify the project is very good and it can surely solve the current problem (the existing
system) as it is developed for the partial fulfillment of Bachler of degree in Information
Technology.

Group member

Student name Signature

Daniel Dagnaw -------------------
Melsew Worku -------------------
Mihrete Temesgen -------------------
Solomon Yirdaw --------------------

College: Technology program: Information Technology

Approval sheet

It is approved that this project has been written in compliant with the formatting rules laid down
by the technology college of the university.

Advisor Name Date Signature

------------------- ------------------ ---------------

June 26, 2019 i

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Acknowledgment
First of all we would like to thank almighty God for all giving us strength, peace and well health
throughout the journeys of this project. And we would like to acknowledge our advisor Alemu
W and Department head Senbto K very much, they was giving directions and leading how
to work the project from every beginning of the proposal writing up to the now. Next we would
like to acknowledge Debre Tabor University and also give great thanks for all over the
instructors who are doing in computer science and teach us.

June 26, 2019 ii

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Abbreviation and acronym

HTML……………………………Hyper Text Markup Language.
GUI………………………………. Graphical User Interface
DB………......…………………….Database
DBMS ……………………….... Database Management System.
GB……………………………....Giga Byte
RAM…………………………… Random Access Memory
SQL…………………………. .Structured Query Language
UC………………………………Use Case
UML………………………….. Unified Modeling Language
FPMS…………………............. Project and research Management System.
DTU…………………………….Debre Tabor University
CSS ……………………………...Cascading Style Sheets.
JS ………………………………..JavaScript
PRO……………………………..project
RES……………………………...research

June 26, 2019 iii

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table of Contents
Table of Contents ......................................................................................................................................... iv
Abstract ........................................................................................................................................................ ix
1. Introduction .............................................................................................................................................. 1
1.1. Background ........................................................................................................................................ 1
1.2. Statement of the problem ................................................................................................................. 2
1.3. Objective of the Project ..................................................................................................................... 3
1.3.1. General objective ................................................................................................................................ 3

1.3.2. Specific objective ................................................................................................................................ 3

1.4. Scope and Limitation.......................................................................................................................... 3

1.4.1 Scope of the project and research ....................................................................................................... 3

1.4.2. Limitation ............................................................................................................................................ 4

1.5. Significance of the project ................................................................................................................. 4

1.6 Feasibility ............................................................................................................................................ 5
1.6.1 Technical feasibility .............................................................................................................................. 5

1.6.2 Economical Feasibility .......................................................................................................................... 5

1.6.3 Operational Feasibility ......................................................................................................................... 8

1.6.4. Time Feasibility ................................................................................................................................... 8

1.6.5. Legal feasibility.................................................................................................................................... 8

1.7. Methodology for the project ............................................................................................................. 8

1.7.1. Data collection Methodology ............................................................................................................. 8

1.7.2 Analysis and Design Methodology ....................................................................................................... 9

1.7.3 Development and Programming Environment Tools .......................................................................... 9

1.7.4 System implementation method ....................................................................................................... 11

1.8. Team organization ........................................................................................................................... 12

1.9. Beneficiary of the project ................................................................................................................ 12
1.10. Testing Methodology....................................................................................................................... 13
CHAPTER TWO ............................................................................................................................................ 15

June 26, 2019 iv

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

2. Requirement Analysis Description .......................................................................................................... 15

2.1 .Overview of the existing system ...................................................................................................... 15
2.1.1. Activities of the existing system........................................................................................................ 15

2.1.2. Problem of the existing system......................................................................................................... 16

2.1.3. S (strength), W (weakness), O (opportunity), T (threat) analysis ..................................................... 17

2.2. Overview of the proposed/new system .......................................................................................... 18

2.2.1. Functional Requirement ................................................................................................................... 18

2.2.2. Non-Functional Requirement ........................................................................................................... 20

2.2.3. System Requirement......................................................................................................................... 21

2.2.4. User requirements ............................................................................................................................ 21

2.2.5. Business Rule .................................................................................................................................... 21

Chapter Three ............................................................................................................................................. 23

3. System Modeling..................................................................................................................................... 23
3.1. Use case Modeling ........................................................................................................................... 23
3.1.1. Actor Specification ............................................................................................................................ 23

3.1.2. Use case Diagram .............................................................................................................................. 23

3.1.3. Use case description ......................................................................................................................... 24

3.2. Sequence diagram ........................................................................................................................... 30

3.3. Class diagram ................................................................................................................................... 37
3.4. Activity diagram ............................................................................................................................... 38
Chapter Four ............................................................................................................................................... 43
4. System Design ......................................................................................................................................... 43
4.1. Design Goal ...................................................................................................................................... 43
4.2. System Decomposition .................................................................................................................... 44
4.3. System Architecture ......................................................................................................................... 46
4.4. Deployment Diagram ....................................................................................................................... 46
4.5. Persistence data management ......................................................................................................... 47
Chapter five: Implementation..................................................................................................................... 50
5.1. Tools and Environment .................................................................................................................... 50

June 26, 2019 v

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

5.1.1 System implementation method ....................................................................................................... 51

5.2. Environment..................................................................................................................................... 52
5.3. Algorism used:.................................................................................................................................. 53
5.5. Sample output:................................................................................................................................. 58
Chapter six: Testing ..................................................................................................................................... 63
6.1 Introduction .......................................................................................................................................... 63
6.2 Features to be tasted ........................................................................................................................ 63
6.2.1 Functional testing .............................................................................................................................. 63

6.2.2 Nonfunctional testing ........................................................................................................................ 63

Table 6.3 Test case specification for login user ...................................................................................... 64

6.4 .Testing approach.............................................................................................................................. 65
6.5. Unit testing....................................................................................................................................... 65
6.6. Integrated Testing ............................................................................................................................ 65
6.7. System testing .................................................................................................................................. 65
6.8. Testing material ............................................................................................................................... 65
Chapter seven: Conclusion and Recommendation ..................................................................................... 66
7.1. Conclusion ........................................................................................................................................ 66
7.2. Recommendation............................................................................................................................. 66
References .................................................................................................................................................. 67
Appendix ..................................................................................................................................................... 68

June 26, 2019 vi

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

List of Tables
Table 1. 1 cost break down ............................................................................................................. 7

Table 1. 2 Front End ..................................................................................................................... 10

Table 1. 3 Back End ...................................................................................................................... 10

Table 1. 4 Software Requirements ................................................................................................ 11

Table 1. 5 Hardware Requirements .............................................................................................. 12

Table 2. 1 Functional Requirement ............................................................................................... 19

Table 3. 1 Actor Specification ...................................................................................................... 23

Table 3. 2 Login use case description ........................................................................................... 24

Table 3. 3 Manage account ........................................................................................................... 25

Table 3. 4 Use case descriptions for manage project/research ..................................................... 27

Table 3. 5. View comment ............................................................................................................ 28

Table 3. 6 use case descriptions for Upload Project comment ..................................................... 29

Table 3. 7 Use case descriptions for give comment...................................................................... 30

Table 5. 1 Front End ..................................................................................................................... 50

Table 5. 2 Back End ...................................................................................................................... 51

Table 5.1. 1 Software component ................................................................................................. 52

Table 5.1. 2 Hardware component ................................................................................................ 52

June 26, 2019 vii

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

List of Figure

Figure 1. 1 Team organization ..................................................................................................... 12

Figure 3. 1 use case diagram ......................................................................................................... 24

Figure 3. 2 sequence diagram of login .......................................................................................... 31

Figure 3. 3 sequence diagram for manage schedule ..................................................................... 32

Figure 3. 4 upload project sequence diagram ............................................................................... 33

Figure 3. 5 sequence diagram of give comment ........................................................................... 34

Figure 3. 6 sequence diagram of post news .................................................................................. 35

Figure 3. 7 sequence diagram of view project .............................................................................. 36

Figure 3. 8 sequence diagram for update information .................................................................. 37

Figure 3. 9 class diagram .............................................................................................................. 38

Figure 3. 10 activity diagram login ............................................................................................... 39

Figure 3. 11 activity diagrams of register advisor and student ..................................................... 40

Figure 3. 12 activity diagram user changes password .................................................................. 41

Figure 3. 13 activity diagram for post notices .............................................................................. 42

Figure 4. 1 system decomposition ................................................................................................ 45

Figure 4. 2 System architecture .................................................................................................... 46

Figure 4. 3 deployment diagram ................................................................................................... 47

Figure 4. 4 persistence data management ..................................................................................... 48

Figure 5. 1 GUI for login .............................................................................................................. 58

Figure 5. 2 GUI error Display for login ........................................................................................ 59

Figure 5. 3 GUI for add committee............................................................................................... 60

Figure 5. 4 GUI for Add department ............................................................................................ 61

Figure 5. 5 GUI for change password ........................................................................................... 62

June 26, 2019 viii

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Abstract
Debre Tabor University has been established by the Ethiopian government as one of Ethiopian
universities established in 2003 EC. In Debre Tabor University, so far, the project and research
are undertaken by graduator student and the way it undertaken is in manual system. Some of the
main problem of the existing system are: students may perform project/research plagiarism during
project/research selection, and also is coasty since it west resources. The purpose of our project
is to develop web based project and research management system that makes communications
easy between students and advisors. It is designed to help students to upload their project/research
project and research system mainly consists of three users, the student who update task status,
view comment and schedule. Committee who manage the overall activity of in project and research
management, manage project, assign advisor. And the Advisor view project/research and give
comment for students

June 26, 2019 ix

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Chapter One

1. Introduction

1.1. Background
Debre Tabor University has been established by the Ethiopian government as one of Ethiopian universities
established in 2003EC. It is found in Amhara region that far from Bahirdar approximately 90kms and The
Debre Tabor University has 6 colleges namely Engineering and Technology, Medicine and health science,
social science, Business and Economics, Natural science and college of Agriculture. According to Debre
Tabor website [1] Each Colleges of Departments has given project thesis for graduating students. This is
performed by first the project coordinator gives orientation to these students for identifying relevant
project title selection. The students have to submit at least 3 project or research titles according to the
university project demands. The project or research coordinator will discuss with Department teachers in
order to identify whether the student’s titles are relevant or not. Projects or researches are assigned after
reviewing the student’s title by these Department members and the projector research coordinator
announce project or research title and advisor in the form of advertisement. Students are coming to notice
board to view posted notice. The posting notices are in the form of papers and it would be easily removed.
This will result the students cannot view the proper information as needed. Another big challenge for
Debre Tabor University is the problem of project or research repository. Projects or researches are not
centrally accessed in one place. In case they are stored in separate departments as a storage bin. These
results projects or researches will not be stored properly as the numbers of graduate students are
increased year to year. Generally, projects or researches performance is reduced due to lack of project or
research repository in the university.

The development of different computer-based system has provided tremendous advantages for
many organizations and institutions. Many developed countries are using computer technology to
accomplish their everyday activities effectively and efficiently. Now days many companies are
using automated system to accomplish their task but some are still using manual system as it is
known university is the place where intensively involve in creation of new knowledge. New
knowledge is created and developed mainly through project or research results. In Debre Tabor
University, so far, the project and research are undertaken by graduator student and the way it
undertaken was in manual system that makes many efforts for student as well as projector research

June 26, 2019 1

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

committee and advisors. The designed system will make job easy for student, project committee
and advisor. The project or research aimed to build a fully functional system in order to achieve the
Efficiency in the final projector research management. The overall mission of the system
development is to make all departments graduate by final project or research that they can manage
and control their activity easily

1.2. Statement of the problem

The overall activities of the Debre tabor university project and research information management
is under taken manually. Because of these manual activity’s problems like: - wastage of time
management i.e. incase student find their advisor, lack of submitting the projector research on
deadline date.
Student’s project or research submitted to the departments if anyone who wants to view the
project/research need to be reached to the department office in charge (physically). In case of fire
incidence or water the copies of the projects approved by the university could be damaged or
totally lost.
Searching worked projects or research is very boring and slow due to the quality of
projects/researches and narrower space to project or research repository.
Some of the main problem of the existing system are, Students may perform project/research
plagiarism during project/research selection. i.e. students might be copy previously worked
projects/researches with the same scope. According to [2]stated that, plagiarism is an illegal act,
researcher copy with in an authorized way. While the proposed project or research has until
restriction in Debre Tabor University. Search projector research documents from the pile of paper
is difficult It will be difficult to store long age projects/researches even 10 years due to space
consumption Project/research related posted notice are posting in notice board and it might be
removed Performance: there is no central project repository in Debre tabor university. Therefore,
data are not easily accessible in case of the file or data are not placed in appropriate location. Those
problems leads to inconsistency of file, loss of security, loss of copy right for the owner of the
project or research, in the other hand there is wastage of resource, time, human power, and effort
in research and project management.

June 26, 2019 2

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

1.3. Objective of the Project

Generally our project provide both General objectives and Specific objectives
1.3.1. General objective
The general objective of the project is to develop web-based project and research management
system for Debre Tabor University
1.3.2. Specific objective
In order to achieve the above general objective, the following specific objectives. Those are:
To gather information which is related to our project

To analyze the gathered data

To design the system based on the analyzed data

To implement the proposed system

To test and evaluate the system

To study the existing final project management system in the university

To identify functional and nonfunctional requirements of the new system

To design and develop the system based on the requirements identified

To make easy and suitable user friendly system for users.

To design solution the drawbacks the existing system project and research
management system

To implement the proposed(new) system

To test and deliver system

1.4. Scope and Limitation

1.4.1 Scope of the project and research
Geographical scope: The scope of the project or research is for Debre Tabor University
Functional scope: The scope project or research includes gathering information, analyze,
design, development, implementation and final submission
Application software development: the projector research has to do the following activities
as the part of the application software development for project and research management system
Registers the newly arriving projects and researches

June 26, 2019 3

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Organize project and research in the appropriate way

Notifies novelty of the project and research by comparing the stored one.
Generates the annual and monthly statistical information of how many projects and
researches have been done per year and show how much of them are critically important.
Calcify the project and research based on each department as well as the year of the project
and research is done
The scope of this project involves the development of project and research management system
for Debre Tabor University. And also it is web based system, generally the scope of the system
includes: - all operations in project and management works and it listed under functional
requirements of the system.
1.4.2. Limitation
Cannot accessed by blind people
Not support dual language

1.5. Significance of the project

The significance of this project is:
Project or research will stay for a long period of time.
To make simple the work of project or research coordinators to manage the work flow of
each project or research designers and to manage the process scheduling of each project or
research developing by different project or research designer.
This project will reduce the time and resource wastage to register the project or research,
and record the project information because it is available, and every student will not wait
until the project or research advisor come to his/her office to advice students
This project will avoid the redundancy of projects or researches (i.e. it will check whether
the projector research is repeated or not by comparing the scope of the project or
research. If the projector research is similar with scope of the previous project or
research.
Also, our project will use to check the dead line time of the project or research online
through this system from the created schedules.
The worked projects or researches can be accessible at anywhere and at any time in the
campus using the campuses network

June 26, 2019 4

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

There will be a good communication between students, advisors and project or research
coordinators

1.6 Feasibility
A feasibility is a test of system proposal according to its workability impact on the organization,
ability to meet user needs and effective use of resources. According to the author [3] feasibility
study is how the system is functional based on different perspectives. There are different types of
feasibility
Technical feasibility
Economic feasibility
Operational feasibilities
Time feasibility
Legal feasibility
1.6.1 Technical feasibility
Our system will be self-explanatory which is developed by using the language of HTML, CS, and
JAVA_ SCRIPT, PHP. Then this project did not need extra experienced training. As the system
has been built by concentrating on the graphical user interface concepts and the application can
also be handled very easily with novice user. Therefore, the system will be technical feasible.
The designed system is expected to be technically feasible as: the requirement for the proposed
system are easily obtained from the existing system.
The software used to implement the system is well understood.
The facility to produce outputs in a given time.
1.6.2 Economical Feasibility
The economic feasibility of our projector research is for evaluating the cost feasibility the cost
feasibility of the system When we see the existing system, which is not more feasible in cost but
this project will feasible on cost because most of the user would use the system. At that time the
user will not pay more money. This project or research would be economically feasible for Debre
Tabor University.

Tangible cost: These are cost derived from the creation of an information system that can be
measured in birr and with consistency. Reduce resource requirements or unnecessary wastage of
resource in PM and RS, like paper, pen, flash etc.

June 26, 2019 5

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Intangible Cost: are costs derived the creation of an information system that cannot be easily
measured in birr and with consistency. The intangible costs of the new system would be:
Faster decision making by searching records from database
Increase security by providing authorized user can access

Error reduction

June 26, 2019 6

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 1. 1 cost break down

Types of tools Tool Name Quantity Unit price (in Total price (in
Birr) Birr)

Pc 1 14000 14000

Flash(8 Gb) 1 180 180

For printing 300 1 300

Paper 1 packet 110 110

Hardware Pen 4 6 24
Tool
Note book 2 25 50

Software Tool Xamp server 1 Free available Free available

Microsoft 1 Free available Free available

office

Notepad++ 1 Free available Free available

Microsoft 1 Free available Free available

office viso

Windows 8 1 Free available Free available

OS

Adobe 1 Free available Free available

Photoshop

Total cost 14664

June 26, 2019 7

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

1.6.3 Operational Feasibility

Our system would bring better achievement for the operations announced by actors for providing
efficient services and project or research information easily register Advisor (Student) on project.
Existing system didn’t use such operations. This intern would increase the efficiency of work in
the Project or research. So our team members can say that the system would be operationally
feasible.

1.6.4. Time Feasibility

Our system would bring better achievement for the operations in a short period of time compared
to the manual system.
1.6.5. Legal feasibility
Legal feasibility study is use to conclude whether the proposed plan or system is conflicts with
the national or International legal requirements. In case of this feasibility study this project is
legally feasible. Especially in our country context as we all know it is the time to change and
renascence journey so our country needs different innovations so this project is able to restrict
plagiarism so it puts its big role for those new innovations by prevent others projects/researches
from illegal activity.

1.7. Methodology for the project

1.7.1. Data collection Methodology
We will use the following methods to collect relevant data required to our project. According to
chinelo [4] in order to complete the task information or data is needed. [5]According to jams
primary data is collected the owner himself and these primary data collection techniques are
interview, observation, questionnaire etc. and also secondary data is collected other person
Interview
For knowing detail information about the existing system, the team used an interview with some
project or research advisors and project or research coordinator in Department of information
Technology and social departments and other departments.

Observation
The team used to analysis the existing projector research repository in Debre Tabor
University by direct site in Department of information technology, electrical engineering

June 26, 2019 8

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

and computer science. We have seen previous projects are stored in pile of papers in
department office. We will identify the problem of the existing system
How different department manage projects or researches
How projects or researches were stored in each department
Document Analysis
Using this method of gathering requirements, our team will try to analyze the existing project
report registered in its own documents in Debre Tabor University. This information will helps us
to identify the project problems and also to understand the existing System. So, the team member
will analyze the information of the project and obtained some basic concepts on how the project
is managed in the current system.
1.7.2 Analysis and Design Methodology
We prefer OOSAD (Object Oriented System Analysis and Design) Methodology and iterative
waterfall model to develop our system. Because of OOSAD provides the following advantages:-
Promote better understanding of user requirements
Leads to clear design by using use case, activity diagram, sequence diagram
The development time, the level of organization, and the code reuse are all greatly
enhanced by the OOSAD methodology
Code reusability
Easy maintenance
Enables the standardization of objects or researches which increase design understanding
and decrease the risk associated with project or research development
It enables us to comprehensively model a system before we develop it
Modification of the object implementation is easy
1.7.3 Development and Programming Environment Tools
Programming language Server side: (PHP) because it increase efficiency & usability PHP
provides incomparable efficiency when it is used for the development of websites.

Back-end: MYSQL is a relational database management system which is an open source

database. Supports large number of embedded applications which makes MYSQL very flexible.

June 26, 2019 9

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 1. 2 Front End

S.NO Front end REQUIREMENT

1 HTML Interface design

2 JS For validation

3 CSS Control appearance of

web site

Table 1. 3 Back End

S.NO Back End REQUIREMENT

1 PHP SERVER SIDE

LANGUAGE

2 SQL SERVER For validation

3 WAMP/XAMP DATABASE
SERVER

4 NETPADE++ FOR EDIT CODE

5 SUBLIME FOR EDIT CODE

Front End

Html:-to interface design

JS:-they used to validate the script and it makes application interactive and faster
CSS:-they used to control the appearance of web site by creating style sheets
Bootstrap:-Bootstrap(front end framework) to compatible to all devices

June 26, 2019 10

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

For Witting document and for presentation Microsoft

Microsoft word 2013
Power point 2013
E-draw, UML and Visio:-to draw diagrams
E-draw, UML and Visio Windows OS
Picasso:-to edit image and text
Laptop computer
Hard disk for data back
1.7.4 System implementation method
After we complete the project or research system will compatible to all operating system a web
browser. Which means the system is platform independent as well as browser independent. It is
compatible with all browsers such as chrome, Mozilla Firefox, internet explorer and other
browsers.

Table 1. 4 Software Requirements

Components Requirements
Client side code HTML JavaScript,CSS
Server side language Php
Documentation Microsoft word 2016
Slide presentation Microsoft power point 2013
Code editor Sublime, notepad++, code lobster Php editor
Drawing tool Microsoft Visio 2016
Server wamp/xamp server
Browser Firefox, internet explorer, uc browser, chrome
Pdf reader Ado reader ,foxit reader

Reason for choosing Php programming languages:

Session management-User sessions are maintained and managed easily on Php.

Security.-Php has its own security framework.

Reduce time from writing the HTML tags

June 26, 2019 11

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Good support for distributed system.

Writing in Php also gives one access to all the Php Framework class libraries,

Components Requirement
Computer and processor Intel core i5 or higher
Flash More than 4Gigabytes
Hard disk 500GB

Table 1. 5 Hardware Requirements

1.8. Team organization

The team that develops the project or research consists of four persons. The team members
will meet daily bases to discuss about the project or research, and to assess where each member
is on his/her prospective task in reference to the schedule.

Daniel Dagnaw:
manager and implementer

Melsew Worku: Solomon Yirdaw:

System analysit requirement

gather

Mihret
Temesgen:
System Design

Figure 1. 1 Team organization

1.9. Beneficiary of the project

After the compilation of the project/research the main beneficiary of this system is Debre tabor
university mainly departments, advisors, and students.

June 26, 2019 12

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Student: student is benefiting in case of gate enough information about the project/research
and they can

easily perform many kind of advice in short time

Department: manage and store worked projects /researches for a long period of time.

Advisor: can easily advice project/research and easily communicate with student

Institution: facilitate the way of developing project/research in the university by controlling

plagiarism

1.10. Testing Methodology

Testing: is the process of evaluating as system us its component(s) with the intent to find
whether it satisfies the specified requirements or not according to Robert [5] testing is evaluating
each component.

Unit testing: every module of the system is separately tested. i.e. the team tests every module by
applying some selection mechanism. Through this mechanism every modules gets tested. If an
error occurs correction will be taken without affecting another module.

Integrated Testing: in this testing part all the modules will be combined together and tested it for
its fitness with the each other and with the system functionality. If error occurs in combining them,
the module with problem will be identified and recombined. Both unit testing and integrated testing
are performed by all team members at the workplace. System testing, here compile the whole
system stating from initial and proceeds testing the whole system check out for errors and flow
control of the system.

Acceptance testing: - is a level of software testing where the system is tested for acceptably. The
purpose of this test is to evaluate the systems compliance with the business requirements and assess
whether it is acceptable for delivery and used to determine whether or not the system satisfies the
acceptances criteria and to enable the use, customers or other authorized entity to determine
whether or not to accept the system

June 26, 2019 13

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Alpha Testing: - Alpha testing is a type of acceptance testing; performed to identify all possible
issues/bugs before releasing the product to everyday users or the public.

We will test the system before we deploy the system for the users in the laboratory class. If there
is some error we will maintain the system it helps us to Better insight about the software's
reliability at its early stages Reduce delivery time to users and also it helps us to early feedback
helps to improve software quality
Beta Testing: - This is a testing stage followed by the internal full alpha test cycle. This is the
final testing phase where the companies release the software to few external user groups outside
the company test teams or employees. This initial software version is known as the beta version.
Most companies gather user feedback in this release.
We will select some samples of actor (student, advisor, and coordinator) in order to test the
system before we deploy the system for the whole users in the laboratory class. If there is some
error we will maintain the system according to user requirements

Error Handling:-The integration testing and system testing are used to test whether the
entered values are valid or not. We have done this by providing error message when
invalid input is entered. For example, if the user enters wrong user name and password
the system displays an error message.

Maintainability: - The system is imagined to design taking care of modularity. Faults in

the system can be traced to modules.

June 26, 2019 14

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

CHAPTER TWO
2. Requirement Analysis Description

2.1 .Overview of the existing system

As we have analyzed the system, we understood the features that the existing the system is
experienced. In Debre Tabor university project or research repository is managed through the
following ways: according to Anne [6] the existing system is boing and time consuming but the
proposed system is better and better.
Project or research coordinator discuss with the project or research committee/department
teachers about student’s title selection and their title approval
Students title will be approved or disapproved by a committee/department teacher based
on the title’s relevance
Students project or research submitted is in hardcopy form to project or research
coordinator
Then Project or research coordinator submit students project or research to department
To access projects or research, we need to go to the department office physically
2.1.1. Activities of the existing system
A. Project title selection procedures
The project or research coordinator post notices about deadline of student’s project title
submission
Students will submit at least three project or research titles
Project or research coordinator discuss with departments lecturer about the titles
After discussion, project or research coordinator post Approved project or research title
and project or research advisors of the students to the notice board
Students can see their approved title and assigned advisor from notice board
B. project or research repository procedures
After finalizing projects or research, it has to be seen by project or research coordinator,
examiners and project advisors
If it is not approved, projects or research cannot be accepted
If it is approved, the hard copy of the projector research is handled by projector research
coordinator

June 26, 2019 15

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Projector research coordinator submit the project or research hard copy to department
Then Projects or researches are stored in Department office like a shelf
Input:
List of candidate students for graduating
List of Department project or research advisors, project or research coordinator
List of available project or research titles
Project or research repository office
List of project or research notices
Process:
Assigning project or research title to students manually
Post projects or researches notice on department notice board
Receive student project or research documents in hardcopy
Output:
Post projects or researches notice about project or research schedule, students advisor
announcement and other project or research related notices
Students must go to the department to see any project or research related notices
Projects or researches are stored in department office in hard copy form
2.1.2. Problem of the existing system
The main problems of the existing system are:
Performance: The existing system cannot give better response when we want to access the
projects or researches from repository. We must go to the department office in order to access the
stored projects or researches. Students’ project or research may be disappeared if it takes long time
because it is stored in paper form.
Security: If any theft or natural and human accidents are happened on the department building;
the existence of the project or research is in danger .It is difficult to check project or research
duplication from other departments. Hence the student’s may copy projects from other
departments.
Availability: Projects or researches did not be available 24 hours per day and it may or may not
accessible until the department office is opened
Efficiency: there is resource wastage like time spending for searching projects or researches and
spaces for storage

June 26, 2019 16

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Input:
It is not faster to identify projects or researches titles that are experienced before
Process:
There is a delay when assigning project or research advisor to students
Output:
It will be difficult to store long age projects or researches even 10 years due to space
consumption
2.1.3. S (strength), W (weakness), O (opportunity), T (threat) analysis
Strength

Does not need internet connection

It supports the proposed system because the proposed system needs the existing system as
a source

Does not need specialized knowledge

Weakness

The existing system consumes time and money

Needs human power and effort

Exposed to theft

Needs a large storage space

Opportunities

In the proposed system one or two person can control the system but in the existing system needs
more people, the existing system creates an opportunities for employers to gain additional fees.

Threat

There is an interference between department head and committee, advisor and examiner etc.
Generally there is no a clear decision making among different employees.

June 26, 2019 17

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

2.2. Overview of the proposed/new system

In general the proposed system is an automated web application that can able to solve project or
research repository or storage problems that faced in Debre Tabor University.
After a thorough investigation of the existing system, we need able to identify the critical problems
clearly observed (that was explained in the problems of existing system in the above). Therefore,
in order to solve these problems, we have established a new system that would benefit the
organization. The new system works by taking the input from the user and store the input in the
database for the future use. The inputs are likes: Project or research schedule with related with
tasks, Advisor Biography, Reports and comments from user, Current project or research status and
etc.
When this system is advanced for web-based project and research Management system in order to
facilitate the activity for evaluation of project or research wisely. This system wants to develop to
manage
We are planned to do this project or research that covers the following main target points.
To allocate students advisor and their project or research titles effectively
To register/add ,delete and update projects or researches for better throughput
To create better communication between department to department about projects
To access projects at any time ,any place with internet connection
Better projects may be offered and get recognition if it has to be done well
Advisor ,coordinator will be successfully manage and control students in projector
research participation
Student will qualified in their pro/res because they submit their initial pro/res and take
comment at any time, any where
2.2.1. Functional Requirement
Functional requirement of the new system is focus on the intended tasks that a system able to
perform. It will answer for question like what the system do and how it is functional. According
to Mohamed and M.pariz [7] the functional requirement is how the proposed system should do.
the system is important to resolve project or research repository by using advanced database
system with secured authentication level.

June 26, 2019 18

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

The following are the main functional requirements that our system should perform:
Assign advisor
Create account
Upload project and research
scheduleing
Chat advisor with student online
Give comment
View comment
Post notice
Submit title
Approve title
Table 2. 1 Functional Requirement

No. Tasks Responsible Actor Description

Submit title
1 Student The system allows students to submit title
to Coordinators
Approve title,progress
2 Advisor, Coordinators The system shall allow advisors and
and final pro/res
coordinators to approve pro/res

3 Committee, head, admin The Shaw allow committee, head and

Create account
admin create accounts

4 Prepare schedule Coordinators The system shall allow Coordinators to

prepare schedules

5 Select Title and add to students A system shall allow students able to add
database their project titles to database

6 View student title Students, committee A system shall allow users can able to
view project titles

June 26, 2019 19

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

7 Download project titles Project/research committee The system shall allow to project
coordinator download project titles

8 Approve project title Project/research committee The system shall to display page for title
Approval for coordinators to compare the
scope

9 Assign Advisor Pro/res committee The system shall allow pro/res committee
to able assign advisor
Coordinator
10 Post project notice He/she shall post project notice

11 View post notices Student, advisor, committee The system shall allow users to view
notices
Upload documentation
12 Student The system shall allow students to upload
pro/res documentation

13 Store project/research Project/research committee The system shall allow users can able to
store projects after it has to be approved
and registered

2.2.2. Non-Functional Requirement

Non-functional requirements of the proposed system focus on quality that the system to behaved.
It is the aim of the teams to increase quality of the system in order to fulfill functional requirements
of the system.
Usability: The proposed system is designed to simple to understand, easier to use with attractive
user interfaces and graphics.
Security: The users who have a valid username and password only can utilize the system based
on their roles. In addition to this Users can able to change and recover if they lost their password
and username.

June 26, 2019 20

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Performance: The system should provide fast and steady response times (Quality of Service). The
maximum user response time should be less than 5 seconds and average response time should be
less than 5 seconds for the next screen to appear or the existing screen to refresh for submission of
data. The speed and efficiency of the system should not be affected with growing volumes,
especially during search operations, data storage and retrieval operations. The system should be
operational with good response time using low band width in the location of about 15Kb per user.
Scalability: All components of the PM&RS must support scalability to provide continuous growth
to meet the requirements and demand of the university. A scalable system is one that can handle
increasing numbers of requests without adversely affecting the response time and throughput of
the system.
Portability: The system must be designed to support latest window operating system, UNIX
operating system, Ubuntu and other familiar operating system.it is almost platform independent.
Availability: The system is available 24 hour a day and 7 day a week with the existence of internet
connection and other requirements.
Maintenance: The system must be maintained easily without spending much time and cost. It has
to be handling both server and client side errors, bugs and failures that suits to user easily
understand the cause of errors (wrong form fill errors), validation errors and other bugs.
2.2.3. System Requirement
2.2.3.1. Hardware Requirement
Computer with: 500 megahertz (MHZ) processor and 500GB hard drive.
2.2.3.2. Software Requirement:
Web Browser: Familiar browser like Mozilla Firefox, Google Chrome, Internet explorer
and others
Operating system: later window version, Linux and others operating system
Database: The Advisor is a person who guides students when they do their project.
2.2.4. User requirements
Users should have their own account in order to login the system, user should have a good skill in
English language.

2.2.5. Business Rule

The following are some rules and Regulation of Debre Tabor university during student final project
work

June 26, 2019 21

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Students have to select at least three titles for project/research selection

Teams in project /research must be not more than 4 in number
Project /research members must be found in any session that they are needed
Project /research members must be free from any abuse of crime
PROJECT MANAGEMENT

June 26, 2019 22

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Chapter Three
3. System Modeling
System modeling is architectural modeling which uses the systems architecture to conceptually
model the structure, behavior, and more view of a system. According to sparx [8] use case is
describes the proposed functionality of the new system. We tried to model the system functionality
using use case diagram, sequence diagram, class diagram and Activity diagram.

3.1. Use case Modeling

3.1.1. Actor Specification
Actors are those users of the system that plays an important role in the system. We are trying to
identify system in the following tables:
Table 3. 1 Actor Specification

NO. Actor Description

1 Administrator The person who can oversee the overall activities of the system
2 Project Coordinator Is a person who assign advisors to students
3 Project Advisor Is a person who advises students in project
4 Students are a candidates that develop the project
5 Department Head Create account for committee

3.1.2. Use case Diagram

Use Case Diagrams describe what a system does from the viewpoint of an external observer. The
emphasis is on what a system does rather than how. A use case describes a function provided by
the system that yields a visible result for an actor. An actor describes any entity that interacts with
the system (e.g., a user).

June 26, 2019 23

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

create account
create account
<<include>>

change password
Admin

deparment head

manage comment
download project
<<include>> /research
logout

pro/res
cordinator manage projects
<<include>> view notice
/researchs <<include>>
<<extend>>
advisor
<<include>> <<include>>

create news perform chat

<<include>> <<include>>
login
<<include>> <<include>>

create schedule <<include>>

<<include>>
give comment
<<include>>
<<include>>

assign advisor
uplod project
/research
studen

select title submit title

Figure 3. 1 use case diagram

3.1.3. Use case description

Table 3. 2 Login use case description

June 26, 2019 24

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

1.Use case name Login

2.ID UC #1

3.Primary actors Project /research Committee, Advisor, Student and admin

4.Description Login used to authenticate and validate system users so that only
Validated users can have access.

5.Precondition All users must have account.

6.Event flow User action System response

1.click login button 2 the system displays login screen

3. The user inputs his/her
4 the system verifies user name and
username and password.
password and displays login successful
message
7.Alternative action If either username or password is incorrect, the system will pop up
with Alert message like” incorrect username or password.”

8.Post condition Go to step

1.The user 3will login in to the system
2.Users will be validated and identified

Table 3. 3 Manage account

June 26, 2019 25

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

1.Use case name Manage account

2.Identifier UC#2

3 Description The admin manages accounts of committee that manages all pro/res activities in
departments and pro/res committee manages students accounts and advisor’s
4.Actor Admin, Project /research Committee

5 precondition The admin pro/res committee must be login to perform those activities

6.post condition System has successfully managed and display information to the committee

7 basic course of 7.1 admin creates account for committee and committee clicks the “add new”
Action advisor, student, delete student,/edit use/ search students “link” consequently
7.2 the system displays department, faculty, advisor, student, pro/res
registration form/ enter user ID to delete/enter user ID to edit/enter advisor ID
to view consequently
7.3 pro/res committee fills advisor, student, pro/res data/ enter advisor ID
when pro/res committee click “submit/delete/update/view” button added/
deleted/updated/search stored in system database/deleted from database/ save
to database/ search and from the database consequently
7.4 use case ends
8.Alternative 8.1 When there is not filled the Advisor data correctly “please fill advisor,
Student, project data correctly” message would be displayed.
Course of action
8.2 when the pro/res committee fills the form incorrect manner, the message
“Invalid data entered please fill in appropriate format” would be displayed

June 26, 2019 26

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 3. 4 use case descriptions for manage project/research

1.Use case name Manage project/research

2.Identifier UC#3

3.Description Use Case to add/delete/update/upload to database and to view project

information consequently.

4.Actor Project/research Committee

5.Precondition The Project/research Committee must be login to perform those

activities.

6.Post condition System has successfully add/delete/update/ and display project

information to the Project /research Committee

7.Basic course of action Pro/res committee clicks the “add new pro/res /delete pro/res, edit
pro/res, search pro/res” link as the necessity. The system displays
pro/res registration form/enter pro/res ID to delete/enter pro/res ID to
view consequently. Pro/res committee fills pro/res data or enter pro/res
ID.
Use case ends

8. Alternative course of action When there is not filled the pro/res data correctly “please fill pro/res
data correctly” message would be displayed.
When the pro/res committee fills the form incorrect manner, the
message “ invalid data entered please fill an appropriate format” would
be displayed

June 26, 2019 27

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 3. 5. View comment

1. Use Case Name View comment

2.Use case Id UC#4

3.Description To see comment given from advisor

4.Actor Students

5.Precondition The Students must have account

6.Basic course of Action 1. The user must log to his/her page

2. The user select show view comment link
3. The system displays the options (criteria)
4. The user selects the criteria from the given options and clicks
on Display button.
5. The system displays the information to the user
6. Use case ends

7.Post condition When there is comment, the Students would get it.

June 26, 2019 28

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 3. 6 use case descriptions for Upload Project comment

1. Use Case Name Upload Project

2. Use Case Id UC#5

3. Description Upload pro/res for Advisor and advisor upload for pro/res
Committee

4.Actor Students ,advisor

5. Precondition The Students and advisor must have account

6. Basic course of action The Students and advisor must log to his/her
page select upload project link
The system displays the open the file on the upload form
Dis play on upload form the upload
. Use case ends

7.Alternative course of action The system verify information is not correctly

1 Thesystem displays error message as invalid selection
2 Go to step4
3 Use case ends

8.Post condition The project would be uploaded

June 26, 2019 29

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 3. 7 Use case descriptions for give comment

1.Use case name Comment

2 .Identifier UC#6

3.Description A use case to give comment

4 .Actor Advisor and student

5.Precondition the Advisor must be registered Advisor to give comment

6. post condition System has successfully post comment information to

Advisor or student

7.Basiccourseofaction 7.1 Advisor or/ clicks the “feedback link.

7.2 The system displays username and comment text area.
7.3 Advisor or/and student write their username, id and
comment in text area appropriately.
When they click “submit” button the comment saved to systems
DB
Use case ends.

8.post condition the comment would be sent

3.2. Sequence diagram

The following sequence diagram is used primarily to show the interactions between objects in
the sequential order that those interactions occur in our system. According to Yeol song
[9]sequence diagram is the popularity of the sequence diagram originality called an object

June 26, 2019 30

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

interaction diagram is attributed to Jacobson. Sequence diagram focus on time sequencing

diagram or time ordering messages or the order in which messages are sent.

User home page login link login controller database

1 open

2 click
3 display login
form()
4 fill the form 5 check form
and submit() and user()

6 please try 7 validation

again() true()

8 login
success full

X X X X X
Figure 3. 2 sequence diagram of login

June 26, 2019 31

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

pro/res manage
project commite
cordina schedule manage schedule validator database
page
tor link
1 pro/res
committee login to
2 select manage
this page
schedule link

3 display
manage
schedule page

4 manage
schedule
5 check 6 validate

7 try again

8 manage()

10 response

11 schedule
managed successfully

X X X X X X
Figure 3. 3 sequence diagram for manage schedule

June 26, 2019 32

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

project commite upload pro/res

student upload pro/res validator database
page link

1student
login to this page 2 select upload
pro/res link

3 display upload
form

4 upload pro/
res
5 check 6 validate

7 try again

8 manage()

10 response
11 pro/res uploaded
successfully

X X X X X X
Figure 3. 4 upload project sequence diagram

June 26, 2019 33

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

student
<<actor>>
and home comment give comment
advisor<< validator(ul) database
page link form
actor>>
1 login to
this page 2 select comment
link

3 display
comment form

4 write comment

5 send 6 validate

7 try again

8 continue

10 sent

11 display comment
message successfully

X X X X X X
Figure 3. 5 sequence diagram of give comment

June 26, 2019 34

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

pro/res pro/res
post notice
commeti commetiee post notice form validator database
link
ee page

1 login to
2 select post
notice link

3 display post
notice form

4 post notice

5 send
6 validate

7 try again

8 if valid

11 display notice

message successfully

X X X X X X
Figure 3. 6 sequence diagram of post news

June 26, 2019 35

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

pro/res pro/res
home page pro/res validator database
commetiee link

1 login to
2 select pro/
res link

3 display pro/res
form

4 select pro/res

5 send 6 validate

7 try again

8 if valid

10 display pro/res
successfully

X X X X X X
Figure 3. 7 sequence diagram of view project

June 26, 2019 36

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

pro/res repoty
homepage login database
committe controller

1 open system
2 login
3 go to update

4 update result

5 send

6 data update
and sored database
7 data update and
stored successfully

X X X X X
Figure 3. 8 sequence diagram for update information

3.3. Class diagram

Object model deals with object oriented of the system. This includes class diagram, relationship
between these classes, methods in the class and property

June 26, 2019 37

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Figure 3. 9 class diagram

3.4. Activity diagram

The purpose of activity diagram is to model the procedural flow of actions that are part of a large
activity. In projects in which use cases are presents, activity diagrams can model specific use
case at a more detailed level according to Kauisson [10]activity is diagram is shows that flows
of actions.

June 26, 2019 38

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

User open login

page

enter user name

and password

check

no
incorrect usernamr
Is valid
and password

Yes

system display
requestea UI

Figure 3. 10 activity diagram login

June 26, 2019 39

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Pro/res
committee
login

main UI

Click

registry hyper link

fill

Pro/res committee
provides inputs
on registry form

Click register
button

yes
invalid data try no
IS VALID account created
again

Figure 3. 11 activity diagrams of register advisor and student

June 26, 2019 40

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

User open
Loin page

enter correct
username
and password

yes
log in to the system correct

no

press change
password

enter old usename

and password

no yes
correct enter new password

reenter new
password

Figure 3. 12 activity diagram user changes password

June 26, 2019 41

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Project
committee
login

post notices link

Post notice
button

fill inputs on
notification form

Click send
button

no
invalid try again Is valid

yes

notify

Figure 3. 13 activity diagram for post notices

June 26, 2019 42

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Chapter Four
4. System Design

4.1. Design Goal

The goal of this system is to simplify student’s final project/research work and store projects
/research efficiently. Higher institution like Debre Tabor University is familiar to work
project/research from different faculties and their Departments. It is usual that students are working
their final project/research as a bachelor degree in their graduation time.

As we have analyzed the system, we understood the features that the existing the system is
experienced.

In student’s project/research work it better to develop a system for the improving cooperatively
work of the project/research team and creating interactive system for project/research coordinator,
project/research advisor and students. These are effectively communicated and interact for
producing qualified projects/research in the university. Generally we are aimed to improve
project/research related problems especially its storage, performance and accessibility. This
system focus on storage by automating manual storage system to advanced database. On
accessibility of the project/research our system is guaranteed to access project/research at any time
at anywhere as needed. In Addition to the above definition we can state some design goals as
below. These are derived from non-functional Requirements.

Performance: The performance of this system can be measured by in terms of response time for
users query, and scalable for handling multiple users request unless internet connection and
hardware problems.
Availability: if internet connection is available the system is accessed at any time anywhere.

Usability: We can say that this system is usable because of its attractive interface and users can
learn easily without taking training.

Security: The system is secured that unauthorized users cannot access it .even hackers cannot
modify it because it must be implemented through three tier architecture so code sniffers are unable
to view it directly. Not only database contents they cannot also access system scripts, styles

June 26, 2019 43

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

because we link them externally outside of the user interface of the web page. We also secure the
system using cookies and sessions so system simply identifies users of the system.

Maintainability: The system is designed using object oriented approach so it easily to maintain
system failure without reconstructing the whole parts. The unique features of following object
oriented design is due to its code reusability and it’s easiest for maintainability.

4.2. System Decomposition

This Project Repository system is modularized into sub systems in order to correlate parts of the
system functionality with strong coherence. It is because of to simplify work load and to form
better interactive works in the system. Sub systems are integrated with the main system but these
are divided for the purpose of good management, control and decentralized for minimizing work
load

June 26, 2019 44

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

upload pro/
student
res
view pro/res head
store pro/
committee
res create
account

manage
information
update
notice post
comment
delete
notice view
comment

assign advisor
approve pro/
res title

Figure 4. 1 system decomposition

June 26, 2019 45

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

4.3. System Architecture

Web server
User

Figure 4. 2. System architecture

4.4. Deployment Diagram

AUML deployment diagram shows static view of the run time configuration of processing nodes
(Advisor, Students, project/research Committee and other user) and the components (manage
schedule, manage project/research, manage account, manage comment view project/research
status, view schedule and submit project/research) that run on those nodes. In other words,
deployment diagram shows the hardware of our system, the software that to be installed in that
hardware and the middle ware used to connect the disparate machines one another. It also shows
how hardware and software components work together.

June 26, 2019 46

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

4. 3 deployment diagram

4.5. Persistence data management

Persistent data management in this context means persistent data that stored in database. This
includes tables, attributes and its relationship from one table to other tables. According to III [11]
persistence data management is that store different data in the database like attribute, tables etc.
Generally we are creating our database using Sql server database management system. Persistent
objects may contain data exclusively contained in the active object. The data is computed during
creation or loading of the object or is added during execution, but is not taken into consideration
for later storage. Creation and loading of objects is carried out by special operations. For storage
of persistent objects, object-oriented database system is used. Loading and storing of objects is
usually performed autonomously.

June 26, 2019 47

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Figure 4. 4 persistence data management

June 26, 2019 48

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

4.6. Access Control and Security

The following table shows the privilege of actors in the system

Table 4.1 Access Control and Security

Actor Privilege
1.Administrator Create Account()
Update project/research ()
View project/research ()
Maintain system()
2.project/research coordinator Post notices()
Register project/research ()
Download project/research t()
Assign Advisor()
Approve project/research title()
Approve project/research ()
3. Advisor View post notice()
Give Comment()
Send message()
Approve project/research title()
Approve project/research ()
Download project/research ()
4.Student Submit title()
Upload project/research ()
Download project/research ()
Upload project title/research ()
View comment()
View post notices()

5.Head Create account()

June 26, 2019 49

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Chapter five: Implementation

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 project and
research 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.1. Tools and Environment

Programming language Server side: (PHP) because it increase efficiency & usability PHP
provides incomparable efficiency when it is used for the development of websites.

Back-end: MYSQL is a relational database management system which is an open source

database. Supports large number of embedded applications which makes MYSQL very flexible.

Table 5. 1 Front End

S.NO Front end REQUIREMENT

1 HTML Interface design

2 JS For validation

3 CSS Control appearance of

web site

June 26, 2019 50

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 5. 2 Back End

S.NO Back End REQUIREMENT

1 PHP SERVER SIDE

LANGUAGE

2 SQL SERVER For validation

3 WAMP/XAMP DATABASE
SERVER

4 NETPADE++ FOR EDIT CODE

5 SUBLIME FOR EDIT CODE

Front End

Html:-to interface design

JS:-they used to validate the script and it makes application interactive and faster
CSS:-they used to control the appearance of web site by creating style sheets
Bootstrap:-Bootstrap(front end framework) to compatible to all devices
For Witting document and for presentation Microsoft
Microsoft word 2013
Power point 2013
E-draw, UML and Visio:-to draw diagrams
E-draw, UML and Visio Windows OS
Picasso:-to edit image and text
Laptop computer
Hard disk for data back
5.1.1 System implementation method
After we complete the project or research system will compatible to all operating system a web
browser. Which means the system is platform independent as well as browser independent. It is
compatible with all browsers such as chrome, Mozilla Firefox, internet explorer and other
browsers.

June 26, 2019 51

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 5.1. 1 Software component

Components Requirements
Client side code HTML,JavaScript,CSS
Server side language Php
Documentation Microsoft word 2016
Slide presentation Microsoft power point 2013
Code editor Sublime, notepad++, code lobster Php editor
Drawing tool Microsoft Visio 2016
Server wamp/xamp server
Browser Firefox, internet explorer, uc browser, chrome
Pdf reader Ado reader ,foxit reader

Table 5.1. 2 Hardware component

Components Requirement
Computer and processor Intel core i5 or higher
Flash More than 4Gigabytes
Hard disk 500GB

5.2. Environment
The environment is very restrictive for implementing this system as well using it. When we say
this it is impossible to access this system out of coverage of network access mean that it is
connection dependent. Since our system is web based; it is allowed on all operating system, and
all electronic devices that are capable to access web.
When we are develop our system we use the following tools in the development environment.
Personal computer to be able to run the system.

PHP MYSQL (xampp), software data base system would be used in developing and managing
the database.

Web browser to run our system which project and research management system for Debre
Tabor University.

June 26, 2019 52

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

5.3. Algorism used:

Login to the system

Login ()

1. Display login page

2. User enters username and password

3. If “login” button is clicked

4. Open database

5. If “username” is matched and password is “matched”

6. Display Users Home Page

7. Else

8. Display Error Message

9. Close table

10. Close database

11. End function

June 26, 2019 53

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Add title

Add title ()

1. Students log into the system

2. Students click “add title” link

3. Display add title page

4. Enter title

5. If title is valid

6. Add the title

7. Then the title insert to student info table

8. Display successfully message

9. End function

5.4. Sample code

After we complete the project or research system will compatible to all operating system a web
browser. Which means the system is platform independent as well as browser independent. It is
compatible with all browsers such as chrome, Mozilla Firefox, internet explorer and other
browsers.
Coding: First phase of implementation is coding. Coding is the process whereby the physical design
specification created by the designers is turned in to working computer code by the programmer. After
we have finished the requirements, the methodology of data gathering, the design methodology and
other essential requirements we shall to start the coding or the implementation part, so coding is the final
phase of the above listed requirements, as much as possible we shall do the coding part according to
permission of God and by working hard in order to include the functional requirements .in this coding part
the group member should participate as well to complete the project at the specified date and time.
Modern language that used is Hypertext Preprocessor (PHP). We use PHP because it increase efficiency
& usability PHP provides incomparable efficiency when it is used for the development of websites.
we recommend that someone who is interested to do, php is powerful language The code is made

June 26, 2019 54

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

simple in such a way that another programmer can easily understand and work on that in future.

<? Php

include_once "../Database/connection.php";

session_start();

if(isset($_POST['login'])){

$user = $_POST['user'];

$password = $_POST['pass'];

$pwd = md5($password);

$acc = $_POST['acc_type'];

$query1 = "select * from users where username = '$user' and password = '$pwd'";

$query2 = "select * from student where username = '$user' and password = '$pwd'";

$query3 = "select * from advisor where username = '$user' and password = '$pwd'";

$query4 = "select * from committee where username = '$user' and password = '$pwd'";

$query5 = "select * from head where username = '$user' and password = '$pwd'";

if($acc == "Administrator"){

$result1 = mysqli_query($con, $query1);

if(mysqli_num_rows($result1) > 0){

while($row1 = mysqli_fetch_array($result1)){

$_SESSION['committe_id'] = $row1[0];

header("location:../admin/index.php");

}else{

$_SESSION['login_wrong'] = 'error';

header("location:../index.php");

June 26, 2019 55

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

}else if($acc == "student"){

$result2 = mysqli_query($con, $query2);

if(mysqli_num_rows($result2) > 0){

while($row2 = mysqli_fetch_array($result2)){

$_SESSION['student_id'] = $row2[0];

header("location:../students/index.php");

}else{

$_SESSION['login_wrong'] = 'error';

header("location:../index.php");

}else if($acc == "advisor"){

$result3 = mysqli_query($con, $query3);

if(mysqli_num_rows($result3) > 0){

while ($row3 = mysqli_fetch_array($result3)){

$_SESSION['advisor_id'] = $row3[0];

header("location:../advisor/index.php");

}else{

$_SESSION['login_wrong'] = 'error';

header("location:../index.php");

}else if($acc == "commiitte"){

$result4 = mysqli_query($con, $query4);

if(mysqli_num_rows($result4) > 0){

June 26, 2019 56

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

$row4 = mysqli_fetch_array($result4);

$_SESSION['committe_id'] = $row4[0];

header("location:../committe/index.php");

else{

$_SESSION['login_wrong'] = 'error';

header("location:../index.php");

else if($acc == "head"){

$result5 = mysqli_query($con, $query5);

if(mysqli_num_rows($result5) > 0){

$row5 = mysqli_fetch_array($result5);

$_SESSION['head_id'] = $row5[0];

header("location:../head/index.php");

}else{

$_SESSION['login_wrong'] = 'error';

header("location:../index.php");

?>

June 26, 2019 57

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

5.5. Sample output:

We show sample user interface as below that designed in development of Web based project and
research management system

Figure 5. 1 GUI for login

June 26, 2019 58

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Figure 5. 2 GUI error Display for login

June 26, 2019 59

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Figure 5. 3 GUI for add committee

June 26, 2019 60

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Figure 5. 4 GUI for Add department

June 26, 2019 61

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Figure 5. 5 GUI for change password

June 26, 2019 62

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Chapter six: Testing

6.1 Introduction
Testing is a process of executing a program with the aim of finding error. To make our system
perform well it should be error free. If testing is done successfully it will remove all the errors
from the software.

6.2 Features to be tasted

To test this system we use functional and non-functional testing
6.2.1 Functional testing
1. Input/ output testing: - This system accept only correct input when user enter data to the
form else display error message if the input is incorrect.

2. Database connection: - we test that the data entered by the user match with the database.
3. Report generation testing:-This system or our system display/generate the expected result
/output such as report card and transcript generation.
6.2.2 Nonfunctional testing
1. Security:-only authorized user perform their task i.e. student cannot access teacher’s
page and teacher cannot access admin page so forth.

2. Error handling: when the user enter invalid data the system display error message.
3. GUI:-team member, adviser, and classmate recommended that, this system provides a
convenient and user friendly interface.

June 26, 2019 63

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Table 6.3 Test case specification for login user

Test case Admin

name

Purpose To ensure only authorized student to be registered

Pre- Form should be fill correctly

condition

Special admin must get user name and password from committee
requireme
nt

Input Expected Actual outcome valid invalid

result

Empty User
student detail
detail should not
be empty

June 26, 2019 64

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

6.4 .Testing approach

Generally, we used the following fault detection technique .In order to identify the possible faults that
may occur during and after developing the system it help us to assure the quality of our product.
Basically there are many ways of testing methodology; that we have been use to test our
system are the following.
6.5. Unit testing: every module of the system is separately tested. i.e. the team tests every
module by applying some selection mechanism. Through this mechanism every modules gets
tested. If an error occurs correction will be taken without affecting another module.

6.6. Integrated Testing: in this testing part all the modules will be combined together and
tested it for its fitness with the each other and with the system functionality. If error occurs in
combining them, the module with problem will be identified and recombined. Both unit testing
and integrated testing are performed by all team members at the workplace.

6.7. System testing: here compile the whole system stating from initial and proceed testing
the whole system check out for errors and flow control of the system.

6.8. Testing material

1. Hardware

Printer, we use printer to print student report card and transcript

PC: we use deferent pc/computer to execute and test this system.

2. Software:

We use google chrome, Firefox etc. to execute the system.

June 26, 2019 65

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Chapter seven: Conclusion and Recommendation

7.1. Conclusion
In analyzing of the existing manual system, we found that services in Web based project
and research management system are enough to serve and a lot of problem. This manual

system is highly time consuming. So that the existing system creates a lot of work
load on advisors, project committees and students. These lead to service delay, job and
service dissatisfaction and inefficiency, and user need to find resources from the office.

The designed Web Based Project and research Management System believes to minimize
the problem in our university departments by automating the current manual system. In
this project we tried to gather information’s about our university department’s existing
project management system and prepare the blue print for mitigating the mentioned
problems. The data gathering techniques we employed helped us to understand the real
environment. As a result we followed software development life cycle to prepare the
Software Requirement Specification Document (SRS) document in the current semester.

7.2. Recommendation
The system that we have tried to automate is not the whole system of the Project and research
management system. Because of time limitation we can’t develop all parts of the system, but we
tried to automate some sub systems and functionalities

We recommend that for the next developer who are going to develop the same system as we have
developed to add some functionalities that we did not cover in this developed project because of
several reasons like loss of internet connection due to the situations of the country, lack of time.

The following functionalities can’t be automated because of the limitations that we have
discussed above like:

plagiarism checker
dual language

Therefore, others who are interested to develop on project and research management system
for Debre Tabor University can get some initial idea about the system and no need of more data
gathering process the only need will be improving the system

June 26, 2019 66

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

References
[1] "dtu," 21 03 2004. [Online]. Available: http//:www.adatum.com.

[2] K. W. and J. M. , "Generating Knowledge and Avoiding Plagiarism: Smart Information

Use by High School Students," American school of library, pp. 1-22, 2011.

[3] A. s. and R. dabestani, "feasibilty study," reza dabestani university of Isfaban(IRAN), pp.
1-15, 2011.

[4] c. l. data gathering methodology, Nigeria: april, 2016.

[5] j. l. primary and secondary data collection, USA: ON MARCH, 2013.

[6] A. m. A. "overview of the proposed system," vasa university of applid science, pp. 1-2,
2010.

[7] m. d. and r. M.pariz, functional and non-functional requirements, USA: published online
march, july 2015.

[8] s. "usecase uml model or diagram," sparxsystem uml tutorials, pp. 1-5, 2004.

[9] I. -y. s. "developing sequnce diagrams in UML," college of information science and
technology Drexel university, pp. 4-7, 2001.

[10] K. "activity diadram," oxfod university, pp. 1-10, 1998.

[11] I. Y. s. "persistence data menagement," college of information seience and technology

drexel university, pp. 1-2, march 2012.

[12] R. s. "Testing methodology," kolobia university of technology and related science, pp. 1-1-
10, 2009.

June 26, 2019 67

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

Appendix
Questionnaire

1. How final project/research related file management system is working in your department?

2. Manual Computerized Sem i-manual

3. How final projects /researches are stored in your after the students finalized their work?

4.

5. What are the mechanisms that you use to notify students and advisors in your
department? Please specify

6. Through notice board El ectronic mechanisms oth please specify

8. what are the existing communication mechanisms among students and advisors in

9. Your department final project or research activities

10. in person vi a email Via hardcopy exchange another please

specify

11. Is there any documents handled in the department that can explain
about previous research/project works conducted in the department

12. If y..es----.what are the formats you used to handle the files

13. If no, please state the reason

June 26, 2019 68

DEBRE TABOR, ETHIOPIA
 PROJECT AND RESEARCH MANAGEMENT SYSTEM

14.

15. Do you think that system based automated project management systems can
help your daily activities in efficient ways in the course of project /research
advising activities?

June 26, 2019 69

DEBRE TABOR, ETHIOPIA