Dilla University

College of Engineering and Technology

School of Computing and Informatics
Department of Computer Science
Title of Project: - Web Based of Facility Management System for DU
A project submitted in partial fulfillment of the requirements for the degree
of B.Sc. in Computer Science (Regular)-part 1
Submitted by:
Name of Student ID-No
1. Estahun Gebeyehuw RCSc-042/14
2. Gara Kusse RCSc- 050/14
3. Fantaye Muche RCSc-046/14

Advised by:
Mr.Girmay T.
Jun, 2010
Dilla, Ethiopia
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CERTIFICATE
The project titled
“FACILITY MANAGEMENT SYSTEM FOR DU”
Compiled by:
Name of Student ID-No
Estahun Gebeyehuw RCSc-042/14
Gara Kusse RCSc- 050/14
Fantaye Muche RCSc-046/14
As partial fulfillment of requirements for degree of Bachelor of Science in Computer
Science from Dilla University
Head of the Department
Meskele Y Signature ----------- Designation----------------
Date:-27/10/10EC.
Department of Computer Science
Examiner
Examiner name Signature Designation
Amanuel Z. --------------- ----------------
Tesgaye A. ---------------- ----------------
Girmay K. ----------------- -----------------
Date:-27/10/10EC.
Department of Computer Science
DECLARATION
This is to declare that the project entitled”<facility management system for DU>” is an
original work done by us, undersigned students in the Department of Computer Science,
School of Computing and Informatics, college of Engineering and Technology, Dilla
University. The reports are based on the work done entirely by us and not copied from any
other source.

[I]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Name of Advisor:-Mr.Girmay T.
Department of Computer Science
Date:-27/10/10EC.
Name of Students ID Signature
1. Estahun Gebeyehuw RCSc- 042/14 __________
2. Gara Kusse RCSc-050/14 __________
3. Fantaye Muche RCSc- 046/14 __________

[II]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Acknowledgement
We would like to thank GOD for giving us strength and health to complete this project. And
also, grateful to our advisor Mr. Girmay T. for his motivate and constructive guidance as of the
beginning of problem formulation to the completion of the project. We would also thanks Ato
Abayeneh and DU Facility Management workers devoting their golden time by explaining and
provide information and giving written documents. Finally, want to extend thanks to my
parents and friends for their encouragement, Motivation and support throughout my study.

[III]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table of content pages

Acknowledgement..................................................................................................................III
List of Table..........................................................................................................................VII
List of Figure.......................................................................................................................VIII
List of Acronym.....................................................................................................................IX
Abstract....................................................................................................................................X
CHAPTER ONE.......................................................................................................................1
1 Introduction.......................................................................................................................1
1.1 Background of facility management..........................................................................1
1.2 Introduction about the project....................................................................................1
1.3 Statements of the problem.........................................................................................2
1.4 Objectives of the Project............................................................................................3
1.4.1 General objectives..............................................................................................3
1.4.2 Specific objectives..............................................................................................3
1.5 Scope and Limitation of the Project..........................................................................4
1.5.1 Scope of the project............................................................................................4
1.5.2 Limitation...........................................................................................................4
1.6 Methodology..............................................................................................................5
1.6.1 Data gathering methodology..............................................................................5
1.6.2 Design methodology...........................................................................................5
1.6.3 Implementation methodology.............................................................................6
1.6.4 Testing methodology..........................................................................................7
1.6.5 Development Environment and programming Tool...........................................8
1.7 Feasibility Analysis....................................................................................................8
1.7.1 Operational feasibility........................................................................................8
1.7.2 Technical feasibility...........................................................................................8
1.7.3 Economic feasibility...........................................................................................9
1.7.4 Behavioral Feasibility.........................................................................................9
1.7.5 Schedule Feasibility............................................................................................9
1.8 Benefits of the project................................................................................................9

[IV]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.9 Project schedule (using Gantt chart)........................................................................12

CHAPTER TWO....................................................................................................................13
2 Existing System...............................................................................................................13
2.1 Introduction of Existing System..............................................................................13
2.2 Description of existing system.................................................................................14
2.3 Limitation of the existing system.............................................................................14
2.4 Model of existing system.........................................................................................15
2.4.1 Actor.................................................................................................................15
2.5 Business rules..........................................................................................................15
CHAPTER THREE................................................................................................................17
3 Proposed System.............................................................................................................17
3.1 Over View of the Proposed System.........................................................................17
3.2 Requirement specification.......................................................................................17
3.2.1 Functional Requirement...................................................................................17
3.3 Non-Functional Requirements.................................................................................19
3.4 User Interface Specification.....................................................................................20
CHAPTER FOUR..................................................................................................................21
4 System modeling.............................................................................................................21
4.1 Use case diagram and description............................................................................21
4.2 Sequence Diagram...................................................................................................31
4.3 Activity diagram......................................................................................................35
4.4 Class diagram...........................................................................................................40
4.5 Database Specification.............................................................................................41
4.5.1 ER-diagram.......................................................................................................43
CHAPTER FIVE....................................................................................................................44
5 System Design.................................................................................................................44
5.1 Introduction..............................................................................................................44
5.1.1 System Overview..............................................................................................44
5.1.2 Design Goals.....................................................................................................44
5.1.3 Architecture of the System...............................................................................45
5.2 System Design.........................................................................................................47
5.2.1 Sub-System Decomposition.............................................................................47

[V]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

5.2.2 Component Diagram........................................................................................48

5.2.3 Hardware/Software mapping............................................................................50
5.2.4 Deployment Diagram.......................................................................................50
5.3 Detail design............................................................................................................52
5.3.1 Package Diagram..............................................................................................52
5.3.2 Collaboration Model.........................................................................................52
5.4 User interface design...............................................................................................55
5.5 Access control and security.....................................................................................57
CHAPTER SIX......................................................................................................................59
6 Implementation...............................................................................................................59
6.1 Introduction..............................................................................................................59
6.2 Hardware and software acquisition..........................................................................59
6.2.1 Hardware tool...................................................................................................59
6.2.2 Software tool....................................................................................................59
6.3 User Manual Preparation.........................................................................................59
6.4 Installation Process..................................................................................................60
6.5 Algorithm and Outputs............................................................................................60
6.5.1 Sample Code.....................................................................................................60
6.5.2 Sample Result...................................................................................................64
CHAPTER SEVEN................................................................................................................65
7 Testing Plan.....................................................................................................................65
7.1 Introduction..............................................................................................................65
7.2 Unit Testing.............................................................................................................65
7.3 Integration Testing...................................................................................................66
7.4 System Testing.........................................................................................................67
7.5 Acceptance Testing..................................................................................................67
CHAPTER EIGHT.................................................................................................................68
8 Conclusion and recommendation....................................................................................68
8.1 Conclusion of final project......................................................................................68
8.2 Recommendation.....................................................................................................68
References..............................................................................................................................69
Appendix................................................................................................................................70

[VI]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

List of Table

Table1.8. 1: Hardware cost.....................................................................................................11

Table1.8. 2: software cost.......................................................................................................11
Table1.9. 1: Project schedule..................................................................................................12

Table 4.2. 1log In....................................................................................................................22

Table 4.2. 2Add Item..............................................................................................................23
Table 4.2. 3 log out.................................................................................................................23
Table 4.2. 4 View Request.....................................................................................................24
Table 4.2. 5 send Request.......................................................................................................24
Table 4.2. 6 Update Item information....................................................................................25
Table 4.2. 7: View user comment..........................................................................................26
Table 4.2. 8: Request facility................................................................................................26
Table 4.2. 9 View item...........................................................................................................27
Table 4.2. 10 Register User....................................................................................................27
Table 4.2. 11 Search for item.................................................................................................28
Table 4.2. 12 Delete User.......................................................................................................29
Table 4.2. 13: View Report....................................................................................................29
Table 4.2. 14 Manage user.....................................................................................................30
Table 4.2. 15 add employee....................................................................................................30

Table4.6.1:managertable……………….…………………………………………………………….42
Table4.6. 2: Employer table...................................................................................................42
Table4.6. 3: storekeeper Table................................................................................................43
Table4.6. 4: User table............................................................................................................43

Table6. 1: List of
appendixes……………………………………………………………………….71

Table 7. 2 Test use case for login...........................................................................................67

[VII]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

List of Figure

Figure3.4. 1: user interface speciation diagram....................................................................20

figure4.2. 1Use case diagram.................................................................................................21

figure4.2. 2login sequence diagram........................................................................................31
figure4.2. 3register sequence diagram....................................................................................31
figure4.2. 4delete user sequence diagram...............................................................................32
figure4.2. 5 generate report sequence diagram.......................................................................32
figure4.2. 6 search facility diagram........................................................................................33
figure4.2. 7 update facility sequence diagram........................................................................33
figure4.2. 8 view item sequence diagram..............................................................................34

figure4.3. 1: login activity diagram........................................................................................35

figure4.3. 2 delete item activity diagram................................................................................36
figure4.3. 3 order facility activity diagram.............................................................................37
figure4.3. 4: register user activity diagram.............................................................................38
figure4.3. 5: view facility item activity diagram....................................................................39

Figure 4.4. 1class diagram......................................................................................................40

figure4.5. 1.ER diagram.........................................................................................................43

Figure5.1Classtype architecture diagram……………………………………………………46

Figure 5.2. 1: subsystem decomposition diagram………………………………………………………………49

Figure 5.2. 2: Component Diagram........................................................................................50
Figure 5.2. 3: Deployment Diagram.......................................................................................52

Figure 5.4. 1 Employee signup interface diagram……………………………………………………………..55

Figure 5.4. 2Item order report generate interface diagram.....................................................56
Figure 5.4. 3 Login interface diagram....................................................................................57

[VIII]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 6. 1 Sample Result diagram……………………………………………………………………………………64

List of Acronym
BR: - Business Rule
CFM:-Center for Facility Management
CSS:-Cascade Style Sheet
DB:-Database
DU:-Dilla University
ER;-Entity Relation
FM:-Facility Management
GUI:-Graphical User Interface
HTML:-Hypertext Markup Language
ID:-Identity
OO:-Object Oriented
OOA:-Object Oriented Analysis
OOD:-Object Oriented Design
OOP:-Object Oriented Programming
PHP:-Hyper Per Process
SQL:-Standard Query Language
UML:-Unified Model Language

[IX]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Abstract
The facility management in DILLA University uses manual process system. When customers
need to overtake an item, and return the item they must go to the office and record what they
want manually, that’s way it is making the process too late. Which requires the employee to use
paper based recording files to know the status of each customer and to perform the process in
the system. The system should insure the user’s satisfaction need usage must be over take in
short manner more over it must be time saving and precise form.

[X]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER ONE

1 Introduction
Facility management system for DU is giving an important service for its community which is
found in that campus that need the desirable issue that facilitates the teaching and learning
processes in a university.
All facilities are acquired from donation or supplier with appropriate facility management.
These properties are distributed based on formal request forms. The current system gives vast
service however it uses manual management system which leads the system to be inefficient.
As part of the effort to bring efficient and modern facility management system in facility
management of DU. The new system should be designed and implemented that enables
properties to be controlled and managed properly.

1.1 Background of facility management

The project entitled facility management system in DU management of facility in the campus
has been formed since in 2007 EC. The project takes care of all the requirements of facility in
a university to facilitate the whole activates in well manner of responsibility and equal sharing
of the recourse that is govern by the vies president and the facility directorate is so ahead. At
the present, information system is necessary for facility Office’s. The project uses the
information technology for managing all of facility data. That make more performance and
more reliability of data in facility managing system

1.2 Introduction about the project

As education plays an important role in the development of a country one of the objectives
that the Ethiopian ministry of education targeted is quality education development DU, one of
the universities in Ethiopia is also working on quality education in order to attain its mission.
so, it is unquestionable to get better computerized based application in order to achieve fast
and highly quality facility management. a big academic institution having a large number of
employees, still has a manual facility management system. So, it is unable to serve the
university employees effectively.

[1]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.3 Statements of the problem

Due to unorganized database about the facility management no one is can commentate
in similar manner at similar issue the university losses much money and time in every
year. This led time delay to assign the management to customers. On the other hand,
there is the case where more than two individuals participate in the same task of
facility distribution. Generally, the current system has the following problem:
 There is high redundancy in manual storage.
 Facility distributions preparation and allocation for facility is inefficient and time
consuming that results delays and frustration especially for customer in the
university.
 This discourages the work activity in the university
 Cross checking manual documents of the owner by document identification
method is very difficult.
 Very let delivery of facility management registration.
 The man who is responsible is not work in the desirable manner

 Inefficient information retrieval

 Announcement done through newspaper
 Unable to generate report

[2]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.4 Objectives of the Project

1.4.1 General objectives

The main objective of our project is to develop web based facility management system to DU.

1.4.2 Specific objectives

The following are the specific objectives:
 To solve the problems of facility management system
 Identify and design the requirement of the new system
 Developing the web based facility management system software on our
requirement for the existing system.
 Implement, test and install the new system in well manner.
 To build up a system that allows updating, generate report, send request,
create account, mange employers and customer. Deleting of data records
regarding for facility management system.
 To facilitate the daily activities/task by designing user friendly and flexible
web based facility management system.
 To minimize the time and employees load on file retrieving process.
 To build Report generating system based on the daily requests of the office.
 To build Well normalized and filtered Database system to avoid data
redundancy and flexible for speedy search of customers information when
needed.

[3]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.5 Scope and Limitation of the Project

The project provides specially to capture facility by providing seeking and order to
their needs. It is totally self-contained and works efficiently. It provides simple
database systems rather than complex one’s for high requirements and it provides
good and easy GUI (graphical user interface) to both new as well as experienced user
of the computer. The project will be supposed to implement storage of facility details
so that a large collection could be maintained with minimum storage space.

1.5.1 Scope of the project

Scope of the project includes the following:-
 Registering information about the facility.
 Generating reports.
 Update, delete the facility information.
 Searching facility information.
 Manage resources, employee and user.
 View item and comments.
 View report.
 Order facility.
 Distribute item
 Send request
 View request
 View response
 Give response
 Give feedback

1.5.2 Limitation
 The system cannot support the notification.
 The user interface is only supported in English i.e. another language is not
supported.
 It cannot work for GPS location.

[4]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.6 Methodology

1.6.1 Data gathering methodology

Data collection methods are the most important part of our project to find the main
requirements of system and how to understand the system is does. To gather the
information, we used data collection methods that mentioned as follow: -
 Interview: to gather information from representatives of the facility managements in
order to get crucial information we need for the project and also from direct users
regarding the procedures of facility registration and distribution system
 Questionnaires’: We prepare questionnaires for DU facility directorate office and we
get enough information about the existing system.
 Observation: to understand system process we have been see the store of facility
recourse and we have been asked the manger the way how the have been done to the
system.

1.6.2 Design methodology

Analysis and design the system using object oriented approach. We need a method for
analyzing a problem to be solved, a plan for the design of the solution and a construction
method that minimizes the risk of error. We have chosen the object-oriented approach (OO) to
follow for our proposed system. Object-oriented programming (OOP) is an approach to
designing modular reusable software systems. A module is a component of a larger system
that interacts with the rest of the system in a simple and well-defined manner. The object –
oriented approach is a logical extension of structured programming, module containing data .

[5]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

An object is a kind of self –sufficient entity that has an internal state (the data it
contains) and that can respond to messages (call to its subroutines). We select object-
oriented programming because it produces solutions that are
 Easier to write.

 Easier to understand

 Contain fewer errors

 Reduction of development time

 Reduction of time and resources required to maintain existing systems

Object oriented design methodology has two phases: -

1. Object Oriented Analysis (OOA):
During this phase the team look at the problem domain and with the aim of producing
a conceptual model of the information that exists in the area which analyzed. And this
model the functions of the system (use case modeling), identifying the business
objects, organize the objects and also the relationship between them and finally model
the behavior of the objects.
2. Object Oriented Design (OOD):
During this phase the model interactions and behaviors that support the use case
scenario, and finally update object model to reflect the Implementation environment.
And also transforms the conceptual model produced in object-oriented analysis to take
account of the constraints imposed to our system format, so that we will use this phase
to refine the use case model to reflect the implementation environment.

1.6.3 Implementation methodology

To implement our system, we use different tools such as hypertext markup language
(HTML) for client-side scripting, Java Script for validation, MySQL for database
server, Apache for web server, hypertext pre-processor (PHP) for server-side scripting,
and Macromedia Dream weaver and Notepad++ for writing source codes.

[6]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.6.4 Testing methodology

Before directly deploying this system, the team will perform different testing for its
functionality. First the team tests each unit at each phase. So, if each if a problem is
encountered it will immediately fixed. Then our group perform an integration testing to check
whether the system address all the functional requirements. The System tested using the
following system.

Alpha testing:-In this testing method, the system is tested by giving the correct input.

Beta testing: -In this testing method, team force the system to be tested for incorrect data
input. If any failures occurred while testing the system in all the above testing methods, the
team take immediate correction beginning where this fault occurred before jumping to next
work so that it meet the goal. If all the above testing methods are carried out and find to be
valid the system directly deploy.

Unit testing: -After developing an individual program module or component it would test
it to ensure that it works according to the specification, operates within acceptable
parameters, and meets the appropriate standards.

Integration Testing: -When a number of components are complete; it test to ensure that
they integrate well with each other, the operating system, and other components.

[7]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.6.5 Development Environment and programming Tool

Programming languages, tools and techniques used for the development of the facility
system:
 Notepad ++
 PHP (We use PHP language for the system development, and our system
(software) compatable on all hardware platforms such as windows & linux)
 MySql server
 Apache server
 HTML, CSS, JavaScript, markup language for front end
 WAMPP server for back end
 PHP framework
 Microsoft SQL for back end
 Sniping tools Image capture to help users how to use the system
 Microsoft office to write document

1.7 Feasibility Analysis

1.7.1 Operational feasibility

The services of new system that we are going to develop are flexible and expandable.
By looking this flexibility and expandability, the management supports this system.
Additionally, the new system is also supported by employers and facility user because
it makes them well informed about facility. Therefore, the system designed to be
operationally feasible. This means, the system operate in any kind of platforms
without any mal functionalities.

1.7.2 Technical feasibility

Our system technical feasible. The proposed platforms have sufficient capacity for
future needs regarding to the facility recourse. The user of is easily develops,
distribute, share, or operate the system by using technical facility distribution
resources. User uses our system without any difficulty.

[8]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.7.3 Economic feasibility

Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also, all the resources are already available, it gives an indication of the
system is economically possible for development.
The facility user also need not to waste their money as travel expenditure to find the facility it
can help easily to get simply by report method to the facility mangers so the proposed system
is economically feasible.

1.7.4 Behavioral Feasibility

Our system is behaviorally feasible, because both employers and facility resource user are
open minded towards the acceptance of this new system, and there is no specialized training
needed for the users. Disregarding the initial expenses,. Our system is free from any political
and environments difficulty.

1.7.5 Schedule Feasibility

All the team members is sure that the project have achieve completed within the time frame
stated, so that the system feasible regarding schedule project proposal four weeks,
requirement analysis 5-7 weeks, system and object design 8-12 weeks, implemention13-19
weeks and documentation and submission 20-22weeks.

1.8 Benefits of the project

The main purpose of this project is to develop application which enables the user to apply for
facilities that match their qualifications in an easy, cost effective and timely manner. That
means it enables the facility user to search for facility resource anywhere at any time. The
new system helps handling the important task of employee recruitment process. Users which
are applicant can access the system using any computer at any place. They can apply for the
facility resource via internet and check their application status easily. Facility users are kept in
the database system that is more secure as the paper files are not only wasting. The system
enables the process like update, edit and add new data to be easier and faster Benefits of the
system: -
 Reduces paperwork for all parties

[9]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

 Minimizes errors in ordering facility recourse

 Provides a comprehensive record of each transaction of facility
 Improves efficiency of the system accessibility of resource
 Gives chefs and managers time to focus on other activities of management
system of facility.
 Provides to report purchase and fulfillment data which can be analyzed for spend
patterns and supplier performance
 Easy and quick to use
 Provides a reliable ordering system which is available recourse
 Greater flexibility - items can be added to the distributing facility basket at any
time
 Hosted in the facility primary internet access Serve Fully scalable system to meet
customers’ demands on the facility.
 Facilitates growth strategies and operational change
As a project, these computerized financial management systems have the following
tangible and intangible benefits.
Tangible benefits: is a benefit that can easily be quantified. Our system provide
tangible benefits such as Increase speed of activities to the system.
 Easy to calculate item amount of facility recourse
 Decreases work load
 Increased efficiency & effectiveness of the information
 Problems & Error reduction
Intangible Benefits: - refers to items that cannot easily be measured in terms of
money and with certainty. It cannot be determined the exact amount of money
consumed. Intangible benefits are as follow: -
 Improved user satisfaction
 Time saving
 Motivate employees
 Decision making based on quality information etc.

[10]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Tangible cost
To get accurate information about materials the project team observes the market directly.
From our project point of view the following items are considered as tangible. Because you
can easily measure them in terms of money. These costs include:
 Hardware cost
 Software cost
 Development cost
Table1.8. 1: Hardware cost

No Name of quantit Cost in birr model total

material y
1 Pen 6 30 Bic
2 Paper 500 125 A4
3 Flash disk 1 200 sun disk

4 Desk top 3 1300 dell

5 Print 100 100 ……

13455

Table1.8. 2: software cost

No Material Cost in birr

1 Notepad++ free
2 E-draw max and visual paradigm 14.2 free
3 MYSQL free
4 Microsoft word 2010 free
5 WAMPP server free
Total 0.00

[11]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

1.9 Project schedule (using Gantt chart)

Table1.9. 1: Project schedule

No Task Start Date End Date November December March April May Jun
1 Select Title 5-3-2010 13-3-2010

2 Data Collect 14-3-2010 22-3-2010

3 Data Analysis 23-3-2010 6-4-2010

4 User Interface 7-4-2010 10-4-2010

Design
5 Database 10-4-2010 17-4-2010

Design
6 Coding 18-4-2010 30-8-2010

7 Tasting 1-9-2010 17-9-2010

8 Maintenance 18-9-2010 1-10-2010

9 Documentation 15-4-2010 20-8-2010

and Preparation

[12]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER TWO

2 Existing System
2.1 Introduction of Existing System
In the existing system, all the activities are performed manually and it’s tedious moreover has
to be taken of each and every facility resource transaction with the users. Presently, all the
access is maintained on paper, which increases the additional tasks of maintaining the paper
work. A report is later prepared manually on pre-defined format printed on paper. In the
existing system most of facility management system viewing available resource, or applying
for the facility at the facility management can be done for which facility user has to go the get
and check the available resource at a facility management system announcement by report on
facility directorate. This way of finding facility consumes, time and budget of a university and
customers.
The facility services collect information about and select to give appropriate support for most
facility service insecure distributions. So that register the selected beneficiary facility with
their full details and order or ask the manager to provide goods and items for the selected
people then the manager approved and forwards the request to the store manager to distribute
services of facility to the users. Therefore, the store manager checks the availability of goods
and items whether it found in the store or not. If it is sufficient take and distribute else the
distributor of facility ask requisition store manager. The manger orders the request of
distributor to the procurement officer then they ensure that sufficient supplies of goods and
items at the right price, with the required quantity, in the right place and at the right time
when performs the purchasing process after this process the facility manger get the facility
and he can distribute all recourse of facility to all round the teaching and learning issue of
DU.

[13]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

2.2 Description of existing system

The existing facility management system currently is functioning using manual
system. Firstly, the user requests their needs to the store keeper and the purchaser
approves the request. And also, the store manager checks the item whether it found in
the system or not. If the requested item exists the user fill the form and take the item
that he/she need. But if the requested item is existed, store manager permitted to the
store manager to buy the requested item and the manager announce to the user the
item you need is coming.

2.3 Limitation of the existing system

 Performance
The performance of the existing system does not provide fast response time
because it is difficult to access data from the stored document. And also, it is
slow /time and energy consuming.
 Security and Controls
Every record of the existing financial management System is stored in the manual
way, so, it is difficult to control and secure these manual records, since it doesn’t
have any authentication and authorization system.
 Economics
Due to the operation that is done by the hand most of the activities are causes to
high consumption of resources like papers, man power, time etc. This makes the
existing system costs are too high.
 Data storage problem
Data are not easily accessible due to place in different location. Difficult to change
and edit.

[14]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

2.4 Model of existing system

2.4.1 Actor
The existing system is not securely supported system since it is manual; it needs number of
user to manage the overall function of the system and it is not Effective and clear. Those
actors in the existing system are: -
1. Manager: a person who direct and administers of the system that coordinates or
manages facility directorate of the facility
2. Employer: a person who works in professional manner of facility tasks in facility
directorate that overtake the task through facility management system.
3. Customer: User who needs service of the facility through the campus for the resource
of facility management information system.
4. Storekeeper:-person who manage and order the item resource of facility system that
are stored in the store hall

2.5 Business rules

The Business rules are statements about the facility directorate organization’s way of doing
business and they reflect business policies. Organizations have policies in order to satisfy the
business objective, make good use of resources, and conform to laws or general business
conversions. Business rule become requirement that is they may be implemented in software as
a means of requirements of this software system.
The existing system includes the following operating principles or rules:
BR1: submit annual budget of facility directorate office to the facility management. That
helps to approve the overall budget to done the works in the annual system.
BR2: employee must have a valid id/badge, salary.
R3: Mark their attendance at every day twice.
BR4: Employee salary depends on their working days if he done over time he can get
additional expenses for his work.
BR5: They have to punctual and must be accountable for the facility directorate and manger.
BR6: They must have a good conduct when thy works in the time of work.

[15]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

BR7: user must bring the receipt that show permission to use the facility resource more over
he must present the signature for taking row materials.
BR8: employer must obligate to pay the cost price when he loses the resource of
facility if he uses the resources for his self-need he is so accountable.
BR9: The organization does not functional on Saturday Sunday and holiday

[16]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER THREE

3 Proposed System
3.1 Over View of the Proposed System
The system currently has manual system like paper for storing facility management system
information, even if it has a manual system which leads the system to be inefficient. Some of
the problems are difficult to know either those facility is employed or not, difficult to bring
necessary students, difficult to identify facility in DU. In order to overcome such
inefficiencies, we initiate to develop web based facility management system for DU, so the
new system should be designed and implemented to know facility information properly. It has
many advantages such as faster access, storage and retrieval of data, cost effective, user
friendly, more secure and involve less manpower.

3.2 Requirement specification

A requirement specification is an agreement between the end user and the system developer.
Requirement Definition (Description of Current System) facility management System is a
web application written in PHP and MYSQL. The system would be very simple in design and
easy to implement. The system requires very low system resources and the system work in
almost all configurations. The main advantages of the proposed Systems are: This system
contains the following Requirements in advance
 Customer is responsible for using facility from the resource system
 Manager Assigns all Resources easing Customer Service
 Administrator if the system to validate and check in and out going messages

3.2.1 Functional Requirement

Functional requirements specify particular results of a system. This should be contrasted with
non-functional requirements which specify overall characteristics such as amount and
reliability of facility managements. A functional requirement describes the application
architecture of a system.

[17]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

The Web Ordering System:

The web ordering system, namely the facility management system, must be providing
the following functionality to users:
 Create a facility ID.
 Log in to the system.
 Navigate the facility management system menu.
 Select facility item from the menu.
 Customize facility options for a selected item.
 Add facility item to their current need.
 Review their current need order to use facility.
 Remove an item/remove all facility items from their current order.
 Provide delivery and distribution of facility details.
 Receive confirmation in the form of an order number.
Menu Management System Administrator:
The menu management system available only to the facility users and as the name
suggests, allow them to manage the menu that is displayed to users of the web
ordering /asking system. The functions afforded by the menu management system
provide user with the ability to, using a graphical interface:
 Add a new/update/delete vendor to/from the menu of facility system.
 Add a new/update/delete facility category to/from the menu.
 Add a new/update/delete facility item to/from the menu.
 Add a new/update/delete option for a given facility item.
 Update amount for a given facility item.
 Update default options for a given facility item.
 Update additional information (description, etc.) for a given facility items.

[18]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

3.3 Non-Functional Requirements

 Maintenance: The facility Management System is being developed in PHP. PHP is an
object-oriented programming language and shall be easy to maintain.
 Portability: -The Facility Management System shall run in any Microsoft Windows
environment that contains PHP Runtime and the Microsoft Access database.
 Reliability: - The Facility Management System service should not access without
authenticate user.
 Standards Compliance: - The graphical user interface of the system shall have easily
understood to the user (have consistent look and feel graphical user interface).
 Security: - Access to the various subsystems will be protected by a user log in screen
that requires a user name and password.
Performance Requirements: Acceptable response times for system functionality
 The system should be able to take any type of inputs, once the mouse is clicked on
the respective button.
 The system should be able to take any amount of order of facility and display it
when finished.
 The system should be able to calculate the recourse of facility and prompt the user
for the mode of facility and generate a receipt of service.
 The system should be able to pass on the order in the facility for processing the
distribution of resource.
 The system should be secured to restrict the management of facility the number of
people to:
 Enter the system to make changes in the menu and its items.
 System has a cash collector.
 System should be able to communicate to the central database to verify the
authenticity of the facility.
 System should allow facility manager to add/delete/alter system item.

[19]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.C

3.4 User Interface Specification

Home

About us Comment contact us Login logout

Admin page User page secretary

Employer page
p page

Manage View item Receive facility receipt

item
Generate View item signup
View item report

View View report

Manage
report
employee Generate
report
Manage
car

Send
report

View
report

Generate
report

Figure3.4. 1: user interface speciation diagram

[20]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.C

CHAPTER FOUR

4 System modeling
4.1 Use case diagram and description

Manage Facility Management System for DU

item
Generate Distribute Logout
report item
Order
item
Give Employer
response <<Exclude>>

Login
Give
Storekeeper Send feedback
View request
View Change
response
View feedback password
request

Give
decisions

Manage
account

Manager Customer
Manage
customer

Manage
employer

figure4.2. 1Use case diagram

[21]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.C

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between systems
and users in a particular environment and related to a particular goal. Use case is a list of steps, typically
defining interactions between a role (known in UML as an actor) and a system, to achieve a goal. The
actor can be a human or an external system.
Table 4.2. 1log In
Use case name Log In
Participating Facility manager, employee, storekeeper and user.
actor
Entry condition The user opens the home page of the system.

Basic course of step1. The user wants to log in into the system.
action step2.The system displays the form
step3. The user inputs his/her username and password into the facility
system.
Step 4. The facility system verifies that the user is eligible to log in into the
system (account checking in the database).
step5. The user login into the system.
step6. use case end
Alternative 4a. The system determines that the password or username is incorrect
course of action 1). The system updates the user period of time and the number of log in
failure and prompts the user to re-enter the username and password.
4a1.The system determines that the re-entered password is incorrect.
2). The system provides the option for the user to retrieve a forgotten
password.
Exit condition When the user clicks log off button.
Pre-condition The user has a user name and password.
Post condition The user login into the system and do in the system the allowed

[22]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 2Add Item

Use case name Add Item
Participating actor storekeeper
Entry condition The manager activates received item form.
Pre-condition The manager should login to the system
Basic course of action 1. The user wants to add item into the system.
2. displays item entry form
3. The manager enters details of new item.
4. The system checks the entered criteria
5. The item stores to database
6. 6.Use case end
Alternative course of action 4a.If there is any invalid entry
1. Then the system displays error message and allows the
facility to re-enter the correct data.
Exit condition When the manager closes the form
Post condition The item is added to the database.

Table 4.2. 3 log out

Use case name log out
Participating actor Facility manager employee, store keeper and user.
Entry condition The user stays in the home page of the system.
Basic course of action 1, The user stays in its home page.
2, The user wants to log out into the system.
3.The user clicks the log out button
4. The user logout from the system.
5.use case end
Exit condition When the user clicks log off button.
Pre-condition The user stays in the home page of the system.
Post condition The user logout from the system.

[23]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 4 View Request

Use case name View request
Participating actor Manager, employee, store keeper and user.
Entry condition The manager, employee, storekeeper and user
activate view request form.
Pre-condition The manager should log in to the system.
Basic course of action 1. The system displays view request form.
2. The manager clicks the view button.
3. The system displays the requested data.
Exit condition When the manager employee, secretary and user
closes the form.
Post condition The manager views the list of requested from the
system.

Table 4.2. 5 send Request

Use case name Approve request
Participating actor Employee and user.
Entry condition The actor activates request form.
Pre-condition The actor should log in to the system.
Basic course of 1. actor wants to approve requests
2. The system display request approval form
action
3. actor select user request
4. The system displays the requested data that request by the user
5. actor check the request form data and approve/ reject the request
and use case end
Alternative course of 5a.If the requested item is not existing
action 1.The system displays not found message
Exit condition When the actor closes the form.
Post condition save the data to the store database.

[24]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 6 Update Item information

Use case name Update Item info.
Participating actor storekeeper
Entry condition The storekeeper activates form for update
Pre-condition The storekeeper should login to the system
Basic course of action 1. user wants to update an item
2. The system displays the update search item form
3. The storekeeper inserts item name to search the updated item.
4. The system displays the update information
5. The storekeeper fills the updated information and click update
button
6. System validate update entry
7. The item will be updated
8. use case end
Alternative course of 6a.If there is any invalid entry
action 1.then the system displays error message
2. The system display entry form and Allows the storekeeper to re-enter
the correct item name.
Exit condition When storekeeper close the form
Post condition The item will be updated

[25]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 7: View user comment

Use case name View user comment
Participating actor Manager
Entry condition The manager activates form.
Pre-condition The manager should log in to the system.
Basic course of action 1. Step1.The system displays the form
2. Step2.The manager clicks the view button
3. Step3.The system displays the comment type
Exit condition When the manager closes the form.
Post condition The manager views the list of all comment users and other
related information.

Table 4.2. 8: Request facility

Use case name Request facility resourse
Participating actor Users
Entry condition The users find form to send request.
Basic flow of event 1. Step1.The system displays the request form.
2. Step2.The users fill the form to send request
3. Step3.The system validates request form.
4. Step4.The users send request by clicking send button.
5. Step5.The request form is now registered.
6. setp6. use case end
Exit condition When The users log off from the system
Pre-condition The users should log in to the system.
Post condition The users request registered to the system.
Alternative course of action 3a. if request entry is invalid
1 .system display error, 2 .system direct user to the
request entry form to enter valid data

[26]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 9 View item

Use case name View item
Participating actor storekeeper
Entry condition The actors need view item form.
Pre-condition The actors should log on the system.
Post condition Retrieve stored items and view the item list.
Basic flow of event 1. User wants to view items
2. The system displays the view form.
3. The actors click the view button
4. The system displays the items that are stored in the system.
5. Then the actors see the list item and decide what they want.
6. Use case end
Exit condition When the actors close the displayed view item

Table 4.2. 10 Register User

Use case name Register User
Participating actor Manager
Entry condition The actor activates the form.
Basic course of action 1. Step1.The system displays the register form
2. Step2.The actor fills the attributes of the beneficiary
3. Step3.The actor clicks register button
4. Setp4. The system is registered to the Database
5. Step5.use case end
Exit condition When the actor exits from the form.
Pre-condition The actor should log in to the system.
Alternative course of action Step2a.If the entered attribute is incorrect.
1.displaye error massage
2. Manager re-enter attributes into the system.

[27]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 11 Search for item

Use case name Search for item
Participating actor storekeeper
Entry condition The actors activate the form.
Basic course of action 1. 1 User wants to search and view items
2. 2 The system displays the search item form.
1. 3 The actors insert the search name to the form and click
search button
2. 4 The system displays the information of search item
3. 5 use case end
Exit condition When the manager, employer and users close the form.

Pre-condition The storekeeper should log in to the system.

Post condition Storekeeper search the item by click search button.
Alternative course of action 3a.If the entered item name is incorrect.
1. 1. system display error
2. 2. system direct user to the request entry form to enter
valid data

[28]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 12 Delete User

Use case name Delete User
Participating actor manager
Entry condition The actor activates the form.
Basic course of action 1. Step1.User wants to delete
2. Step2.The system displays the form
3. Step3.The facility manager enters user ID.
4. Step4.The system Search the user information from the
database
5. Step5.The system display user information or it is not
found massage
6. Step6.The facility manager Delete the user successfully.
7. Step7.use case end
Exit condition When the actor exits from the form.
Pre-condition The actor should log in to the system.
Post condition The user is out of the service.

Table 4.2. 13: View Report

Use case name View Report
Actor storekeeper
Description: The system allows facility manager to viewing report.
Pre-condition The storekeeper r is log on to the system
Post condition storekeeper view the report
Basic course of action1. Step1.The system displays the form
2. Step2.The actor clicks the view button
3. Step3.The system displays the report.
4. Step4.use case end.

[29]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 4.2. 14 Manage user

Use case name Manage user
Participating actor Manager
Entry condition The manager activates the form.
Pre-condition The manager should log in to the system.
Basic course of action 1. Step1.The system displays manage user form.
2. Step2.The facility manager search user by entering user id.
3. Step3.The system displays the user info page.
4. Step4.facility manager can enable/disable the user
5. Step5.end use case
Exit condition When the facility manager closes the form.

Usecase name Add employee

Actor Manager
Description: The system manager will add new room with new attributes to the system.

Basic course of action User action System response

1. The system manager will 3. The system will display the ‘add
login to the system. employees’ form with fields such as:
2. The system manager will  Employee name.
open the ‘add employees’ page.  Employee ID.
4. The system manger will fill  Employee salary.
the form.  Employee address.
6. End of use case. 5. The system will check all fields of
the form are filled or not.
Alternative course of 5a.If entered same filed invalid
action 1.display error massage
2. All fields are filled correctly show successful message.
Table 4.2. 15 add employee

[30]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

4.2 Sequence Diagram

figure4.2. 2login sequence diagram

[31]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

figure4.2. 3register sequence diagram

figure4.2. 4delete user sequence diagram

[32]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

figure4.2. 5 generate report sequence diagram

[33]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

figure4.2. 6 search facility diagram

figure4.2. 7 update facility sequence diagram

[34]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

figure4.2. 8 view item sequence diagram

[35]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

4.3 Activity diagram

Login form

Click login page

Display login form

Enter username and password

Click login links

Incorrect username and password

Checked
validity

Display home page

figure4.3. 1: login activity diagram

[36]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Click delete link

Get item id

Search from database

If not found
Checker

Delete from database

figure4.3. 2 delete item activity diagram

[37]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Order facility page

User login

Login error Checker

No Yes Prompt to next page

User select from menu

item

Facility item add

User agree terms and condition of

facility

Save to database

figure4.3. 3 order facility activity diagram

[38]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

User register

User login display page

display

Login Registration

fill registration
form Registration prompt

Got to the next page System user error

figure4.3. 4: register user activity diagram

[39]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

View facility item

Login to system

Enter username and

password

Incorrect

correct

Click view link

Display item

View all item

figure4.3. 5: view facility item activity diagram

[40]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

4.4 Class diagram

Figure 4.4. 1class diagram

[41]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

4.5 Database Specification

Table4.6. 1: manager table

Column Data type Primary key Null value

name
Id Varchar (20)  No
first name Varchar (20) No
last name Varchar (20) No
Birth date Varchar (20) No
Email Varchar (20) No
Gender Varchar (20) No
Phone Varchar (20) No
State Varchar (20) No
Salary Float (20) No
Nickname Varchar (20) No

Table4.6. 2: Employer table

Column Data type Primary key Null value

name
Id Varchar (20)  No
First name Varchar (20) No
Last name Varchar (20) No
Age Int (11) Yes
Phone Varchar (20) No
Sex Varchar (20) No
location Varchar (20) No
city Varchar (20) No
street Varchar (20) No
salary float(11) No
Email Varchar(25) No

[42]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table4.6. 3: storekeeper Table

Column nameData type Primary key Null value

Id Varchar (10)  No
First name Varchar (20) No
Last name Varchar (20) No
Replay Varchar (30) No
Location Varchar (20) No
Age Int (11) No
Sex Varchar (20) No
Nickname Varchar (20) No
Salary Float(32) No
Email Varchar (20) No

Table4.6. 4: User table

Column name Data type Primary key Null value

Id Varchar (10)  No
First name Varchar (20) No
Last name Varchar (20) No
Nickname Varchar (30) No
Address Varchar (20) No
Age Int (11) No
Sex Varchar (20) No
Email Varchar (20) No
Phone Varchar (20) no

[43]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

4.5.1 ER-diagram Quality

Type Quantity

Manufacture name
Fname Lname
Recourse price Fname Lname
Gender M
M-id Name Salary
e
nag M M Name Sex
Phone Ma Order Phone
age Salary
Street
1 M
Nickname Manager 1 Manages M Employer Adress City

Email 1 Emp_id Location

1 use
Birthday M M age
1

H
as
a

g
Manage

n
Fname

lo
Be
Send
M Belong
Lname

Name M M M
M
User_id M
M Comment Leave M
M
Nickname User View
Sent time Salary
Body
Adress 1 source M Email
Phone
Report
Sex
M Storeke Sex
age
age
eper Lname
Phone

Nickname Fname
Location Name
Replay

figure4.5. 1.ER diagram

[44]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER FIVE

5 System Design
5.1 Introduction
In designing a process of facility system describing, organizing and structuring system
components at architectural design level and detailed design level of facility recourse. It
converts functional models from analysis into models that represents the solution. This
chapter describes about the system design for facility management system .In this phase we
illustrates design goal of the project, component diagram, deployment modeling, and
persistence model

5.1.1 System Overview

System design is the transformation of the analysis model into a system design model. This is
the System Design document defining the component, modules, interface and data for a
system to satisfy specific requirement document to facility management system. The
document includes system design, design goals, architecture of our system, deployment
design and class interface.

5.1.2 Design Goals

The Design Goals specify the qualities of facility management system that should be achieved
and addressed during the design of the system. The design goals for the system are grouped
into four categories.
Performance criteria
The part of the system to be used for the Register facility resourse.it should have a fast
response time (real time) with maximum throughput. Furthermore, the system should not be
taking up too much space in memory. The store keeper has chosen fast response time over
throughput and hence the system should try to be more interactive. In the case of the
timetabling subsystem, the system should be more reliable in order to satisfy the constraints
than fast response time.
Dependability Criteria: The Dilla University needs the system to be highly dependable as it
is expected to be used by all customers. The system should be robust and fault tolerant for
facility users. Furthermore, as the system is handling sensitive data of the Dilla University
[45]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

registration facility resource, high emphasis should be given with regards to security, as there
are subsystems to be accessed through web.
Maintenance Criteria
Facility systems have easily extensible to add new functionalities at a later stage. It should
also be easily modifiable to make changes to the features and functionalities.
End User Criteria
Usability: Usability of facility management system is the extent to which a product can be
used by specified users to achieve specified goals with effectiveness, efficiency and
satisfaction in a specified context of use. From the end users’ perspective the system should
be designed in such a way that it is easy to learn and use, efficient and having few errors if
any.
Security Requirement Criteria
Since the facility system hold an important information (data), the system require strong
security features to protect that valuable information i.e. not allow other users or unauthorized
users to access data that has no the right to access it.

5.1.3 Architecture of the System

Class type architecture provides a strategy for layering the classes of the facility system to
distribute the functionality of the software among classes. Furthermore, class type
architectures provide guidance as to what other types of classes a given type of class will
interact with, and how that interaction will occur. This increases the extensibility,
maintainability, and portability of the systems.
Interface
This layer wraps access to the logic of our system. This layer consists of interface class – user
interface (UI) classes that provide people access to our system.
Domain:-This layer implements the concepts to our facility domain, focusing on the data
aspects of the facility objects, plus behaviors specific to individual objects.
Process:-The process layer implements facility logic that involves collaborating with several
domain classes or even other process classes.

[46]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Persistence: - Persistence layers encapsulate the capability to store, retrieve, and delete
objects/data permanently without revealing details of the underlying storage of facility system
System:-System classes provide operating-system-specific functionality for your applications,
isolating your software from the operating system (OS) by wrapping OS-specific features,
increasing the portability of your application.

Interface (User interface) index.php

aboutus.php
contactus.php
login.php

Process (Application) System

(infrastructure flat
mode)

Domain (facility)

Persistence (Data)
PHP My Admin

Data source

Figure 5. 1 architecture diagram

User Interface Description

1.index.php Main page
2.aboutus.php Describes about the facility features and services
3.contactus.php The location and map of facility management

Persistence (Data) Description

1.database.php Holds information to create the database and tables
2.configuration.php Connecting local host and database
[47]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

3.auth.php Verifying user

Database(Data Source) Description

1. Local Host Hold the server information
2. PHP MY Admin Store all tables and database
3. super Database that hold all tables

5.2 System Design

5.2.1 Sub-System Decomposition
In Subsystem decompositions we reduce the complexity of the facility system. The sub
systems that we take the classes that our systems contain and the operation performed in the
class. The following are sub systems:-
 Report management sub system: This subsystem allows for managing information and
performs this operation of report.
o Item store report
o Item order report
o Distribution report
 Manage account subsystem: in this subsystem managing of information regard to account
and perform.
o Create account
o Delete account
o Update account
o Search account
o View account
 Request sub system: These sub systems handles information of of request and perform.
o Send request
 Database Connection Subsystem: this subsystem used for established connection between
facility class and database management system.
 View management subsystem: This subsystem allows for managing response and
performs the following operation.

[48]
 FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

o View feedback
o view response
 Feedback management subsystem: This subsystem allows for managing feedback and
performs this operation.
o Give feedback
 Item management subsystem: This subsystem allows for managing registration process
and performs the following activity.
o Register for new Facility
o View Facility
o Search Facility

View sub
Generate Report system
sub system

Item order View feedback Manage account

report sub sytem

View request Remove Block

Store item Distribute
report report
Change
Enable
password
Item order sub
system
User page
View Distribut
Connection
sub system
order e item Give
Record feedback
Database
ordered View
connection
item response

Mange Item
sub system

Mange employer
Add item Search sub system
Manage customer
sub system
item
Signup employer Delete Signup customer
View item Update account employer account
item
Search Search Update
View employer
Employer employer employer

[49]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 5.2. 1: subsystem decomposition diagram

5.2.2 Component Diagram

We use Component diagrams to show facility management system how the physical
components of a system are organized. And also shows which component or objects will be
accessed by whom and what type of Create
security infrastructures it is using. The diagram is
account
simulated below. Mange customer
Manager
Mange employer

Give response Security

View feedback
Store keeper View request

Order Item Persistence

Manage Item
Employer
Generate report
Change
password

Customer View response

Give feedback

Send request

Figure 5.2. 2: Component Diagram

[50]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

5.2.3 Hardware/Software mapping

Dilla University facility management system will be web-based that will be accessed through
Dilla University LAN. the web server will run over wamp or wamp Server, The programming
language used to develop this product will be PHP version 5.2.6 and some scripting language
such as hypertext markup language (HTML), Java script (JS) and we have used MYSQL
version 5.0.51b as the database management system.

client

client
Data base server
My sql

http
php

web server
xampp

5.2.4 Deployment Diagram

We use this diagram to depict the static view of facility system that runtime configuration and
the software components that run on those nodes. And it shows our system, that software have
been installed on system, and the middle tier used to connect the disparate system to one
another. The deployment diagram of our system is shown as follows:-

[51]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Create account

Mange
customer
Manager
Mange employer

Store Give response

keeper
View feedback
Security
View request

Employer Order Item

Manage Item
Generate
report
Change
Customer password

View response

Give feedback

Send request

Figure 5.2. 3: Deployment Diagram

[52]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

5.3 Detail design

5.3.1 Package Diagram

5.3.2 Collaboration Model

By using Collaboration diagram we have represented a combination of facility system
information taken from class, sequence, and use case diagrams describing both static structure
and dynamic behavior of a system. And it also shows some data flows between objects and
the interaction caused between them. The following figures show the Collaboration Modeling
of the system.

[53]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 5.3. 1Account manage Collaboration diagram

Figure 5.3. 2 item register Collaboration diagram

[54]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 5.3. 3 create account collaboration diagram

[55]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 5.3. 4 login collaboration diagram

5.4 User interface design

Figure 5.4. 1 Employee signup interface diagram

[56]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 5.4. 2Item order report generate interface diagram

[57]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Figure 5.4. 3 Login interface diagram

5.5 Access control and security

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

[58]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 1: Access Control and Security

Function Actor

customer employee storekeeper manager

Create user account 
Manage account 
send Request  
Request view  
Send response  
view response  

Manage item 
Order item 
Generate report 
Send feedback  
View feedback  

[59]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER SIX
6 Implementation
6.1 Introduction
Implementation is one of parts of the project development phase where project inputs are
converted to project outputs. In implementation phase, main task is coding. The crucial phase
in the system development life cycle is the successful implementation of the new system
design. The process of converting as new system into an operational one is known as system
implementation. In implementation; we tried to put into practice what was proposed in the
project document i.e. transforming the project proposal into the actual project. Then the
developed system is implemented or hosted on the server for the users to get the purpose or
benefit of the system.

6.2 Hardware and software acquisition

For the project implementation; the following Software and hardware tools are used.

6.2.1 Hardware tool

 Server
 Computers
 Network connection

6.2.2 Software tool

 Xamp and wamp server
 Browser (Google chrome or Mozilla Firefox)
 Notepad ++

6.3 User Manual Preparation

No more manual preparation is needed for facility management users, because the system
have developed a software and it is not installed on a client computer. After the
implementation has been completed, it is directly mange by the manger.

[60]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

6.4 Installation Process

Installation process is something simple once implantation phase is in the progress. For
installation best method first install wamp/Xampp server. Then copying website (files) to
wamp /Xampp server. Then simply type the path on the browser link bar and press GO.

6.5 Algorithm and Outputs

It defines the algorithm required for each element of the architectural design to accomplish its
tasks.
Pseudo code for login
Method name: login
Begin
GET Username
GET Password
IF (Username == Entered Username && Password == Entered Password) THEN
Put cookies Login Successful
ELSE
Login failed display error message.
END
Pseudo code for logout
Begin
If the user login to the system then and click logout link then
Delete cookies and display home page
End

6.5.1 Sample Code

<HTML>
<link rel="stylesheet" href="get_files/main.css">
<div id="rightmenu">
<div id="contentbox">
</div></div>
<div id="mainmenu">
<body>

[61]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

<center>
<table width="" height="" border=0px id="table1"bgcolor=""#000000"">
<td bgcolor=" #ffffff "valign="top"height="" width="" margin-top="0px" border="0px" align-
top="0px"><!--center -->
<FORM ACTION="itemPost.php" METHOD="POST" enctype="multipart/form-data">
<font face="timesnewroman">
<fieldset><legend>Resource register Form:</legend>
<center>
<table bgcolor="#ffffff" style="border:0px solid black;width:500px;height:330px;border-
radius:15px">
<!--
<tr >
<td width="150px" border="1px">Item Type :</td><td><input name="txttype" type="text"
size"20" required="required" placeholder="Enter Item Type"></input></td>
</tr>
<tr>
<td>Item Name :</td><td><input name="txtname" type="text" size"20"
required="required" placeholder="Enter Item Name" ></input></td>
</tr>
-->
<tr><center><td>Item Type:</td>
<td><select name="Type" style="width:148px;" required x-moz-
errormessage="Please select one" style="width:135px;" "height:20px;" margin-left="20px">
<option ></option>
<option value='Computer'>Computer</option>
<option value='office material'>Office Material</option>
<option value='Car'>Car</option>
<option value='Oil'>Oil</option>
<option value='Clean material'>Clean material </option>
<option value='water Material'>water Material </option>
<option value='light Material'>light Material </option>
<option value='other'>Others</option>
</select></td></center></tr>
<tr><center><td>Item Category:</td>
<td><select name="Category" required="required" style="width:148px;"
required x-moz-errormessage="Please select one" "height:20px;" margin-left="112px">
<option ></option>
<option value='Returnable'>Returnable</option>
<option value='Disposable'>Disposable</option>
<option value='Consumable'>Consumable</option>
<option value='other'>Others</option>
</select></td></center></tr>

[62]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

<tr><center><td>Item Name:</td>
<td><select name="Name" style="width:148px;" required x-moz-
errormessage="Please select one" style="width:135px;" "height:20px;" margin-left="20px">
<option ></option>
<option value='desktop'>Desktop</option>
<option value='laptop'>Laptop</option>
<option value='Soap'>Soap</option>
<option value='Detergent'>Detergent</option>
<option value='gauntlet'>gauntlet</option>
<option value='selverbrush'>selverbrush</option>
<option value='metsrga'>metsrga</option>
<option value='loary'> loary</option>
<option value='watergage'> watergage</option>
<option value='vavola'> vavola</option>
<option value='switch on/off'> switch on/off</option>
<option value='wire'> wire</option>
<option value='other'> Other</option>
</select></td></center></tr>
<tr>
<td>Quantity:</td><td><input name="Quantity" type="int" size"20" pattern="\d{2,15}"
style="border:1px #480000 solid;width:144px;height:25px;background:#FFFFFF;border-
radius:5px;" required="required" placeholder="Enter amount item"></input></td>
</tr>
<tr>
<td>Item Code:</td><td><input name="Itemcode" type="text" size"20" pattern="\d{2,15}"
style="border:1px #480000 solid;width:144px;height:25px;background:#FFFFFF;border-
radius:5px;" required="required" placeholder="Enter Item Code"></input></td>
</tr>
<tr>
<td>Item Model :</td><td><input name="Model" type="text" size"20" pattern="\w{3,15}"
style="border:1px #480000 solid;width:144px;height:25px;background:#FFFFFF;border-
radius:5px;" pattern="\w{4,10}" required="required" placeholder="Enter Item
Model"></input></td>
</tr>
<tr><td colspan=2 align="center">
<input type="submit" value="Save" name="add"/> <input type="reset" value="Reset"/>
</td></tr>
</table>
</center></fieldset></form>
<?php
if(isset($_POST['add']))

[63]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

{
$code=$_POST['Itemcode'];
$itemname=$_POST['Name'];
$model=$_POST['Model'];
$Quantity=$_POST['Quantity'];
$date=date('y/m/d');
$itemtype= $_POST['Type'];
$itemcategory= $_POST['Category'];
$query1 = "INSERT INTO stock (Itemcode,Quantity,Name,Type,Category,Model, status,
date) VALUES
('$code','$Quantity','$itemname','$itemtype','$itemcategory', '$model' , 'register','$date')";

$result=mysql_query($query1);

if(!$result){
die("error".mysql_error());
print "<h3>Try Again</h3>";
}

else{

print "<img src='img/tick.png' align='center' width='25px' height='25px'><font face='arial'

color='green' size='5'> Successfully registered</font>";
echo' <meta content="6;itemPost.php" http-equiv="refresh" />';
}
}
mysql_close($con);
?>
</div>
</td><!--center end-->
</td></tr></table>
</center>
</div>
<div id="leftmenu">
<div id="video">
</div>
</div>
</body></html>

[64]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

6.5.2 Sample Result

Figure 6. 1 Sample Result diagram

[65]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER SEVEN
7 Testing Plan

7.1 Introduction
We have Test an integral part in our facility system in software development. It is broadly
deployed in every phase in the software development cycle. The facility system Testing is
done during implementation. Facility system Testing is often done during the analysis phase
because testing requirements are related to system requirements.
The purpose of facility system testing can be quality assurance, verification and validation, or
reliability estimation.

7.2 Unit Testing

In the test-design specification, there are criterions for the tests to discover username or
password in correct. The standard terminologies for pass/fail are:
• If the actual outcome and the expected result are the same, the pass/fail criteria is “pass”

• If the actual outcome and the expected result are different, the pass/fail criterion is “fail”.
Login
Login (Authentication)
The login or the authentication module deals with authorizing users in order to use the system
and keep privacy of….

[66]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Table 7. 1 Test use case for login

Test case:1
Test Case Name: Login
Purpose: To verify (authenticate) authorized users
Input Expected result output Pass/fail
Valid user name and The system Successfully The system successfully Pass
password combination accept the actor and accept the actor and
display the main page display the actor page
Valid user name and The system displays ” The system displays ” pass
invalid Password incorrect User Name or Incorrect User Name an
Password” or Password”
Incorrect user name The system display” The system display” pass
and valid Password Incorrect User Name Incorrect User Name
and/or Password” and/or Password”
Incorrect user name The system display” The system display” pass
and Incorrect Incorrect User Name Incorrect User Name and
Password and/or Password” Password”
Null user name and The system displays The system displays pass
Password “Please fill username” “Please fill username ”
User name and null The system displays The system displays Pass
Password “Please fill password “ “Please correct password”

7.3 Integration Testing

In this phase we have focused on how individual software modules are combined and tested
as a group. It occurs after unit testing.
Tasks that we have performed under Integration testing
 Prepare integration test plans of facility system.
 Identify integration test objectives of the system.
 Identify integration test acceptance criteria of facility system.

[67]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

 Perform the tests according to our plan in facility.

 Document the test results.

7.4 System Testing

In System testing we have destined facility system to check the behavior of a complete and
fully integrated system product based on the software requirements specification document.
For this type of testing do not required knowledge of internal design or structure or code. We
have check this facility system in black box type of testing. The bringing together of all the
programs is that a system comprises for testing purposes. All results of facility system
documented on the Test Analysis Report, Test Problem Report and on the Test Analysis
Approval Determination. Any failed components should be migrated back to the development
phase for rework, and the passed components should be migrated ahead for security testing.

7.5 Acceptance Testing

In the Acceptance testing of facility system a level of the software testing where a system is
tested for acceptability. The processes whereby actual users are test a completed information
system. The end result of which is the users acceptance of it. The purpose of this test is to
evaluate the system's compliance with the business requirements and assess whether it is
acceptable for delivery.
It is a formal testing with respect to user needs, requirements, and business processes
conducted to determine whether or not a system satisfies the acceptance criteria and to check
if the system is acceptable to the users. In this testing all the interfaces are combined and the
complete system is tested.

[68]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

CHAPTER EIGHT
8 Conclusion and recommendation

8.1 Conclusion of final project

The main purpose of facility system is to simplify any access of facility resource over facility
management that available products in the facility system and also to provide available
products for the customers. Here in the system we are providing a great flexibility for the
facility manager to add, delete or update etc. the information in the facility system. The
system manager can also enable or block the personal account. We are also providing great
flexibility for the users that they need to use this facility system; they just access the system
search for accessing the existing facility. We are maintaining good communication between
manager, storekeeper and the customers.

8.2 Recommendation
Since the system is more users friendly every user can access it without any trouble. So we
recommend to the facility managers to use this system, but it might have some limitations
should be taken in considerations. So we are willing to welcome every interested person’s
idea and they should have to need support of programmers to make the best is needed for the
accurate that makes in more sustainable manner system, so concerned body should take in
consideration for assurance the system and also it should be up to date. To make this
collaboration of concerned is needed.

[69]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

References
1) https://www.youtube.com/results?search_query=uml+diagrams+tutorial(20/5/10E.c.)
2) https://www.youtube.com/results?search_query=ER+diagrams+tutorial(25/5/10E.c.)
3) https://www.smartdraw.com/entity-relationship-diagram/(25/5/10E.c.)
4) https://www.wikihow.com/Write-an-Appendix(20/5/10E.c.)
5) http://libguides.usc.edu/writingguide/appendices(23/5/10E.c.)
6) Create table of figure and list of table (https://www.youtube.com/watch?v=ErIY5hrFMzc)
(12/5/10E.c.)
7) http://www.edrawmax.com/uml-activity.php(10/5/10E.c.)
8) https://www.edrawsoft.com/Software-Diagrams.php(20/5/10E.c.)
9) https://www.edrawsoft.com/edrawmax-guide.php(05/5/10E.c.)

[70]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.
C

Appendix
Table6. 1: List of appendixes

Symbol Description
Actor

Use Case, Attribute

Message line extend from the lifeline, Entity
Attribute relationship
Starting point of activity/state diagram

Entity

Ending point of activity/state diagram

Dependency line
Return message extend from the lifeline of one
object
Decision

Note

Activity

[71]
FACILITY MANAGEMENT SYSTEM FOR DU 2010E.C

As we describe in the methodology part we use the methodology or interview, observation and
documentation here are the question we raise during doing the project. But, we get answer from
interview, observation and documentation.
Question address to the facility management directorate office in DU:
Q1. What are the objectives of your facility management?
Q2. What is the mission and vision of FM?
Q3. How does your current system work?
A. Is it manual?
B. Is it computerized?
Q4. How to register candidate for take facility resource, employee and user?
Q5. How to do work?

[72]