Web Based Inventory Management System

Web Based Inventory Management System in DMU

PROJECT REPORT

Submitted by:

Name ID

1. Yimer Amare…………………………………………TER/4699/07

2. Demeke Bilata…………………………………………TER/4655/07

3. Yibeltal Godahegn……………………………………TER/4697/07

4. ZinaWondem…………………………………………TER/4702/07

In partial fulfillment for the award of the degree of

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

Under the guidance of:

INSTRUCTOR GETNET MOSIE (MSC)

--------------------------------------
ADVISOR SIGNATURE

DEPARTMENT OF INFORMATION TECHNOLOGY

INSTITURE OF TECHNOLOGY
DEBRE MARKOS UNIVERSITY
DEBRE MARKOS, ETHIOPIA

May-2010.E.C
 Web Based Inventory Management System

Declaration
We,undersigned,declere that thesis our original work, has not been presented for a degree in
this or any other university, and all the source of martial used for the thesis/project have been
acknowledged.

Name Id No Signature
1. Yimer Amare 4699/07 ---------------------------
2. Demeke Bilata 4655/07 ---------------------------
3. Yibeltal Godahgn 4697/07 ---------------------------
4. Zena Wondem 4702/07 ---------------------------

I
 Web Based Inventory Management System

APPROVAL OF ADVISOR AND EXAMINERS

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

Advisor Name ____________________ Signature ____________

This project has been examined with our approval as the project examiner.

Examiner Name:

1. ____________________ signature______________
2. ____________________Signature______________
3. _____________________Signature_____________

II
 Web Based Inventory Management System

Acknowledgment
First we would like to thank GOD for helping us through this project. Secondly we would like to
express our deepest gratitude to our advisor Getnet Mosie for his great contribution guidance,
support and gives us continuous initiation and encouragement from the begging up to the end of
the project. Next, we would like to thank Property Administer team leader Mr. Tilahun for
giving the required information for us. And we would like tank for the department of
information technology by full fill the infrastructure of Computer laboratory equipment to
success this project. In addition to this we would like tanks for our classmate students for
sharing their knowledge and different idea and gives us suggestions and comments to correct this
project. Finally we would like thanks for our family for helped by allocating the budget for us to
complete this project.

Abstract
This project focuses with “Debre Markos university inventory management system is designed to
properly maintain properties of the university and distribute them appropriately to the employees
as per their requirement and approval of their user. Web Based Inventory management system
mainly provides effective and fast data processing and controlling of stocks. The system
performs item registration, supply registration, manage notice, bids, send item request and
approve item request. The project is implemented in PHP, html, css and MySQL Server
database. Object modeling tools like UML are also used.

III
 Web Based Inventory Management System

Contents
Declaration ..................................................................................................................................................... I
APPROVAL OF ADVISOR AND EXAMINERS.................................................................................................... II
Acknowledgment ......................................................................................................................................... III
Abstract ........................................................................................................................................................ III
List of Acronym and Abbreviations ............................................................................................................. VII
Chapter one .................................................................................................................................................. 1
1.1 Introduction ............................................................................................................................................ 1
1.2. Background of the Project...................................................................................................................... 1
1.3. Statement of the problem ................................................................................................................. 2
1.4. Objective of the Project ......................................................................................................................... 3
1.4.1. General Objective ........................................................................................................................... 3
1.4.2. Specific Objective ............................................................................................................................ 3
1.5. Scope of the Project ........................................................................................................................... 3
1.6. Limitation of the project .................................................................................................................... 3
1.7. Significance of the project ..................................................................................................................... 3
1.8. System requirement .......................................................................................................................... 4
1.8.1. Hardware tools required are:- ........................................................................................................ 4
1.8.2. Software tools required are:-.......................................................................................................... 4
1.8.3 Programming language .................................................................................................................... 4
1.9. Data collection methodology ............................................................................................................. 5
1.10. Feasibility Study of the New System ................................................................................................ 6
1.10.1. Economic Feasibility ...................................................................................................................... 6
1.10.2. Technical Feasibility ...................................................................................................................... 6
1.10.3, Operational Feasibilities ............................................................................................................... 6
1.10.4 .Legal Feasibility ............................................................................................................................. 6
2. Chapter two ............................................................................................................................................. 7
2.1 .Over view of the existing system ....................................................................................................... 7
2.2. Over view of the proposed system .................................................................................................... 7

IV
 Web Based Inventory Management System

2.3. Requirement Specification ................................................................................................................. 8

2.3.1. Functional requirement .................................................................................................................. 8
2.3.2 Non-Functional Requirements .................................................................................................. 9
2.3.3. Business Rule .................................................................................................................................. 9
2.4. System Requirement Analysis ............................................................................................................ 9
2.4.1 Actor and Use case Identification .................................................................................................... 9
2.3.2. Actor Identification ......................................................................................................................... 9
2.3.4 Use case Diagram ........................................................................................................................... 13
2.3.5 Use case Description ...................................................................................................................... 15
2.4. Sequence Diagram ........................................................................................................................... 16
2.5 Activity diagram ................................................................................................................................ 20
2.6 Analysis class Diagram ...................................................................................................................... 24
CHAPTER THREE .......................................................................................................................................... 26
3. SYSTEM DESIGN .................................................................................................................................. 26
3.1. Design Class Diagram ....................................................................................................................... 26
3.2 Database Design................................................................................................................................ 28
3.3 user interface design......................................................................................................................... 33
3.4 Deployment Diagram ........................................................................................................................ 36
IV.CHAPTER FOUR ....................................................................................................................................... 37
4. IMPLEMENTATION .............................................................................................................................. 37
4.1 Overview of the programming language used ................................................................................ 37
4.2 Algorithms Used ................................................................................................................................ 37
4.3 Sample Code ..................................................................................................................................... 38
5. CHAPTER FIVE.......................................................................................................................................... 41
5.1 TESTING ............................................................................................................................................. 41
5.1.1 Unite testing................................................................................................................................... 41
5.1.2 Integrating Testing ......................................................................................................................... 41
5.1.3 Acceptance Testing ........................................................................................................................ 41
5.1.4 System Testing ............................................................................................................................... 41
CHAPTER SIX................................................................................................................................................ 42
6. Conclusion and Recommendation ...................................................................................................... 42
6.1 Conclusion ......................................................................................................................................... 42

V
 Web Based Inventory Management System

6.2 Recommendation.............................................................................................................................. 42
6.3 Future Enhancement ........................................................................................................................ 42
Appendix ..................................................................................................................................................... 43
Reference .................................................................................................................................................... 43

Table 1 Use case Identification ................................................................................................................... 12

Table 2 login use case description .............................................................................................................. 15
Table 3 design class description for office .................................................................................................. 28
Table 4 design class description for department ......................................................................................... 28
Table 5 user detail table ............................................................................................................................ 29
Table 6 item request detail table ................................................................................................................. 30
Table 7 item detail table ............................................................................................................................. 31
Table 8 item withdraw detail table ............................................................................................................. 31

Figure 1 use case diagram........................................................................................................................... 14

Figure 2Sequence diagram for login ........................................................................................................... 16
Figure 3sequence diagram for register item............................................................................................... 17
Figure 4 sequence diagram for send feedback ........................................................................................... 18
Figure 5sequence diagram for view item ................................................................................................... 19
Figure 6 :Activity diagram for logins ........................................................................................................... 20
Figure 7Activity diagram for send request.................................................................................................. 21
Figure 8Activity diagram forregister item ................................................................................................... 22
Figure 9Activitydiagramfor view item ......................................................................................................... 23
Figure 10 Analysis class diagram ................................................................................................................. 25
Figure 11 Design class diagram ................................................................................................................... 27
Figure 12 interface for login........................................................................................................................ 33
Figure 13 interface for item registration .................................................................................................... 34
Figure 14 interface for collage dean ........................................................................................................... 35
Figure 15 Deployment diagram .................................................................................................................. 36
.

VI
 Web Based Inventory Management System

List of Acronym and Abbreviations

DMU-----------------------------------------------------------------------Debre Markos University

HTML------------------------------------------------------------------Hyper Text Markup Language

CSS---------------------------------------------------------------------Cascading Style Sheet

PHP---------------------------------------------------------------------Hyper Text Pre Processer

ID------------------------------------------------------------------------Identification

UML--------------------------------------------------------------------Unified Modeling Language

UC----------------------------------------------------------------------Use Case

WAMP--------------------------------------------------------------Windows, Apache, MySQL, PHP

MYSQL---------------------------------------------------------------My Structured Query Language.

PC------------------------------------------------------------------- Personal Computer

CD--------------------------------------------------------------------Compact Disc

VII
 Web Based Inventory Management System

Chapter one

1.1 Introduction
The use of technology is increasing day to day, we all depend on technology and we use various
technologies to accomplish specific tasks in our lives. Today we have various emerging
technologies which impact our lives in different ways. Technology is being implemented in
almost every section of our lives and business structures. Some of the uses of technology today
are in health, education, government, communication, purchasing, agriculture, control and
harness natural forces, transportation, bank etc. More specifically Technology has a bigger
impact on inventory control in terms of efficiency, ease of accessing information and accuracy
thereby affecting organization performance, centrally manage all store inventory management
and improve availability of the system.(3)

An inventory is the stock of items used in an organization. An inventory system monitors the
levels of inventory and determines the recording of items and distributing the materials to the
staff based on the request of users. But, currently Debre Markos University property
administration directorate performs recording items, managing, requesting materials, register
supplier through manually this leads to time consuming, error prone and boring. In order to solve
this problem, the team motivated to develop a web based inventory management system.

1.2. Background of the Project

Debre Markos University was established in 1999E.C.Now it has three campuses namely main
campus, Bichena campus and Burie campus. The main campus which is found near to Debre
Markos city and it has six colleges, two schools those are school of law and school of medicine
and one institution which is institute of technology. The five colleges are colleges of Natural and
computational science, colleges of Economics and Business, colleges of Agriculture and Natural
resource, colleges of social science and humanity and colleges of health science.(7)

In Debre Markos University property administrator office is started when the university was
established. Property administrator office is centrally maintained in the Office of property
administrator directorate. The Office of property administrator directorate currently works
1
 Web Based Inventory Management System

register supplier, register items, register item withdraw, transfer item, and generate report like
withdraw, received and damage items.

Property administrator office deals primarily with determining the amount and placement of the
materials within a facility or within multiple locations of a store. One way of managing this
system is to have a web-based system in place that can instantly track and update the information
about the tools or equipment. The importance of implementing a web based inventory system is
becoming vital as most of the time the information are accessible directly, so making the details
of the usage of the equipment available, and improving the movement and anticipation of their
demand as well as the productivity of the system as a whole.

1.3. Statement of the problem

The existing property administrator directorate in DMU is currently done through manually so, it
has the following problem.

 Difficult for department head, office head and collage dean to know list of items used by
his staff.
 Difficult for property administration teams to know list of items a specific employee
used.
 When errors are made by employees of the store at any point of their work during
register the item.
 Difficult for property administration teams to know where the specific item is found
 Difficult for property administration teams to know list of items a specific department,
office and college uses.
 Difficult to generate a report like received, withdraw items because it requires more
effort and time consuming to recover and check the registered item.
 Difficult to approve clearance because not get easily employee information
 In transfer of item problem is exist, because the signature of employee is put in paper
so, the paper is may be lost or damage.
 Files put in excel difficult to search specific information about items and employees.
 Data is not secured because any user that have access to that computer can modify the
excel files.

2
 Web Based Inventory Management System

1.4. Objective of the Project

1.4.1. General Objective

The general objective of this project is to develop web based inventory management
system for Debre Markos University.

1.4.2. Specific Objective

 To keep records of new, taken of the university properly.
 To relocate, change the status of items whether issued or not
 To develop secure database that holds information about items and customers.
 To develop system that register items and users.
 To develop system that update items and users.
 To minimize delay of service by providing lists of properties available in the store

1.5. Scope of the Project

The project that we are trying to focus on inventory management system will cover only on
the Debre Markos University.

1.6. Limitation of the project

 The system not prepare well organized report
 The system not develops android in a way to support mobile users.
 The system not including other language like Amharic language
 The system not including integrated system like human resource management system

1.7. Significance of the project

Some of the significances of the system are:

 Easy to know where the materials are found.

 When items are issued to employees the system can automatically update the
information an item or change its status
 Better security and management of item file.
 Easy to manage clearance because the record is well organized and can search by
its Id and easy to check the materials under on each employee.
 It reduces the probability of errors that will be made during registering the issued,
received and remained items to the store.

3
 Web Based Inventory Management System

 It improves item transfer because easily know where specific item is found. i.e.
the movement of item from one employee to another is easily updated by the
system

 Proper utilization of inventory resource such as cost, human resource, time etc. can
be maintained.

1.8. System requirement

1.8.1. Hardware tools required are:-

 Personal computer (PC):- almost all tasks of our project are performed on computer.
 Flash Disk: required for data movement and store.
 Disk (CD):-necessary for the store of relevant data and for backup Pen and Paper: used for
write different question and resource.
 A4 paper: used to write necessary data during data gather process.

1.8.2. Software tools required are:-

 WAMPSERVER:-to test the system by running.
 MYSQL (My Standard Query Language) (database), for creating and manipulating
databases.
 Microsoft word 2007: to write on any necessary documents about the project.
 Code lobster php edition: to write the code we use this application.
 Microsoft office Visio 2007: used to draw UML diagrams.

1.8.3 Programming language

The programming language the team uses are:

 PHP (Hypertext Preprocessor):- Because of we select PHP:-

 Easy to use
 Platform Independent(It can be run on all major operating systems)
 Supports all major Web Servers
 Supports all major Databases
 open source
 Easy to fix problems etc

4
 Web Based Inventory Management System

 MySQL (My Standard Query Language): - for creating and manipulating databases.
 MySQL database- the project team used MySQL database since
 Easy to use
 Open Source
 It is fast and secure
 runs on many operating system
 Hypertext Markup Language (HTML):-allow for building HTML pages website
creation.
 Java script language: - to create interactive WebPages.

1.9. Data collection methodology

Data collection is the most important part of our project to find the main required information to
system and to understand how the system works. We used the following methods to collect
relevant data required to our project.

 Interview: To get information, interview with the store head will be conducted with
concerned staff of the corporation to get reliable information which is important to do
the project.
 Observation: It helps us to get the right information how the organization performs
its function and this helps to strength the data that gathered through interview and
document analysis.
 Document Analysis: This technique provides information on how the existing
system works .There for documents related to the existing system of the organization
will be assessed.

5
 Web Based Inventory Management System

1.10. Feasibility Study of the New System

1.10.1. Economic Feasibility

An economic feasibility is a process of identifying the financial benefits and costs associated
with a development of a project.

The proposed web based inventory system is economically feasible because:

 The system will provide fast and efficient automated environment.
 This project is economically feasible because its anticipated benefit is greater than
the expected cost.

1.10.2. Technical Feasibility

The proposed system can be easily maintained and repaired technically; the system will be
powerful to be applied by low skilled users as much as possible. It is easily accessible by the
people who can easily understand natural languages.

1.10.3, Operational Feasibilities

The system will also be on behalf of origination’s goal and user satisfaction, because the system
will be possible to run and use in the organizations LAN internet. So the system will be
operationally feasible or it will be operationally acceptable to users in Debre Markos University
inventory office.

1.10.4 .Legal Feasibility

The project team members built the system without violating rules and regulations of the
governments as well as the organization. The system being built is for the importance of
productivity of the organization, so that the project is legally feasible. Legal feasibility
determines whether the proposed system conflicts with the legal requirement or not.

6
 Web Based Inventory Management System

2. Chapter two

2.1 .Over view of the existing system

The existing system is performed activities from storing material on stoke to deliver the
employee. First the store clerk post bids and register the designated supplier, after the
designated supplier supply the item, the store head receive material from supplier, checks the
incoming item by related professionals. Then the store clerk receives the material from the
store head and he/she assigns a code and record the item information.
After that the store clerk must get permission to receive and give the materials to the staff
members by the head of the store office. Then the store clerk documents the item
information and reports those materials detail based on their item type to the store head. And
the store clerk gives the material to the employee, department, president, vice president,
director, collage or office based on their request.
The existing system performs the following main activities in manually.

 Register supplier: register supplier organization to supply item for the organization.
 Register new items: the new items are register before enter to the store.
 Register item withdraws: the item is register after give to collage, department,
employee and office.
 Register item transfer between two employees: during item transfer from one
employee to another it must register.
 Approve clearance: when an employee is leave out from staff member he/she must fill
the clearance form.
 Prepare report like damaged item, new item, withdraw item: reports are prepared based
on the category.

2.2. Over view of the proposed system

The proposed system will reduces the existing problems which usually occurred in Debre
Markos University inventory office. Proposed system is to improve some activities through
computerized way that simplifies the workload of the existing system and speedup the
operation of the system. The new system performs from send request to deliver item based on
request from different department, college and office. Stock clerk register new, withdraw and
transfer item from the beginning to the end. Proposed system is a system which avoids more

7
 Web Based Inventory Management System

manual hours that need to spend in record and keeping the data in a centralized way which is
available to all the users simultaneously. It is very easy to manage historical data in database.
No specific training is required for the employees to use this system. They can easily use the
system to decreases manual hours spending for normal things and hence increases the
performance. Generally the proposed system has advantages by easy to manage all the daily
transactions, can generate required reports easily, easy to manage historical data in a secure
manner, centralized database helps in avoiding conflicts and easy to use GUI that does not
requires specific training.

2.3. Requirement Specification

System Requirements Specification is requirement by the system to achieve its goal. In this
section we have kept the basic understanding of the requirements and dependencies of the
current system prior to any actual design or development work. We deal the functional and non-
functional requirements of the proposed systems.

2.3.1. Functional requirement

Functional requirements are the planed behaviors of the system. This behavior may be expressed
as services, jobs, utilities or functions that the system is required to perform.

Since the team are going to develop computerizing inventory management system that used by
the employee’s in the university, the system is used to manage and process data according to the
System.

The new system is expected to provide the following functionalities:

 Register of supplier, collage, department and office.
 Registering of the new items based on their category.
 Displaying information about the item.
 Searching for items that are available in the stock.
 Generating and recorded new items.
 Generating withdrawal items in the stor.
 Generating received and withdraws item.

8
 Web Based Inventory Management System

2.3.2 Non-Functional Requirements

Non-functional requirement describes the necessities of the computerized inventory management
system that are not directly related to the functionalities of the proposed system and any
constraints that may limit the boundaries of the proposed system. In short, non-functional
requirement is all about system attributes such as security, reliability, usability, integrity and so
on.

Security:-The system only permits authorized user to enter the system. Authorized users are who
have username and password by using encryption technique is called md5 algorithm.

User Interface: The interface is user friendly and can properly guide the user how to use the
system and perform operations easily.

Response time: - the system gives response to service request within a short period of times.

Availability: -This system should always be available for users to access item information.

2.3.3. Business Rule

A business rule is an operating principle or policy the software must satisfy. It often concern to
access control issues, policies and principles of the inventory management system.

The existing system has business rules or principles some of them are: only staff members of the
university are allowed to take an authenticated material, one employee to fill clearance first
checked either any material with him/her or not.

2.4. System Requirement Analysis

2.4.1 Actor and Use case Identification

 Actors: An actor is a person, organization, or external system that plays a role in one or
more interactions with in the system.
 We use Actor as user that interacts with system.
 Use cases: A use case describes a sequence of actions that provide something of
measurable value to an actor.

2.3.2. Actor Identification

In inventory management system the following actors are involve: System administer, Property
Administration Director, Collage dean, Department head, Stock clerk, Employee, Customer,
president, vice president, director. Procurement commute

9
 Web Based Inventory Management System

 Customer: have the following activities

 View bids
 View notice
 Admin: have the following activities
 Create user account
 View account
 Take Backup
 Restore Data Base

 Director: have the following activities

 View item
 Send item request
 View Response
 Send feedback
 President: have the following activities
 View Response
 View item
 Send item request
 View bids

 Vice President: have the following activities

 View item
 Send item request
 View bids
 Property Administration Director: have the following activities
 view item
 send item request
 View item request response
 View feedback
 Post bid
 Post notice

10
 Web Based Inventory Management System

 College dean: have the following activities

 View item to assign college
 Send item request
 Approve request
 Send feedback
 Register allowed employee

 Department head: have the following activities

 View item to assign department
 Send item request
 View response
 Send feedback
 Stock clerk: have the following activities
 Register college
 Register department
 Register employee
 Register office
 Register item
 Register item withdraw
 Register item transfer
 Register supplier
 Register position
 View item
 Update item
 Register item withdraw
 Register item transfer

 Employee: have the following activities

 View item
 Send feedback

11
 Web Based Inventory Management System

Table 1 Use case Identification

Use case name Use case ID Include

Login Uc1
View response Uc2 Login
View item Uc3 Login
Register item transfer Uc4 Login
Register item withdraw Uc5 Login
Send item request Uc6 Login
Register item Uc7 Login
View request Uc8 Login
Send feedback Uc9 Login
View feedback Uc10 Login
Take Backup Uc11 Login
Approve clearance Uc12 Login
Approve request Uc13 Login
Register supplier Uc14 Login
Create user account Uc15 Login
Register collage Uc17 Login
Register department Uc18 Login
Register office Uc19 Login
Post notice Uc20 Login
View notice Uc21

Post bid Uc22 Login

View bid Uc23

12
 Web Based Inventory Management System

2.3.4 Use case Diagram

A use case diagram is a collection of actors, use cases, and their communications. A use case
diagram is a graphic depiction of the interactions among the elements of a system. A use case is
a methodology used in system analysis to identify, clarify and organize system requirements. A
Use Case Model describes the proposed functionality of a new system. A Use Case represents a
discrete unit of interaction between a user and the system. Use case is a list of steps, typically
defining interactions between a role and a system to achieve a goal.(2)

13
 Web Based Inventory Management System

Use Case Diagram for Web Based

Inventory Management System
Manage Account
Post Bid

Procurment
Take Backup Commuty
View Request

Restore DB include()
Admin include() Approve Request

include()
include()
Post Notice include() include() Reg allowed
Employee College Dean

include() include()
View Feadback Reg transfer item
include()
include()
include() include()
Property View withdraw Item
Login View Item
Administrator include() include()
Directorate
Director
View Item include()
include()
View request
include() include()

View Bid
include() include()Register employee

Presidant include() include()

Reg transfer item Dept Head
include() include() Register supplier
Extend()
include()
send request include() Register postion
Vice
Presidant
Register transfer
View request
item

View Item Register Item

Employee
Stockclerk
Register withdraw
View notive Logout Item

View Bid Register

Customer Dept,office,Collage

Figure 1 use case diagram

14
 Web Based Inventory Management System

2.3.5 Use case Description

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.

Table 2 login use case description

Use case name Login
ID Uc1
Description To authenticate the user
Actor , Admin, Property Administration Directorate, stock clerk,
collage dean, Department head, Employee. Director,
president. Vice president. procurement commute
Pre condition All actor must have an account
Post condition The user is logged in the system and provided with
privileges for actions according to their roles.
Basic course of Action Actor action System response
1. User opens the web page. 3. Login form
2. Select Login link. displayed
4. Enter username and password. 6. Validate data entry
5. User clicks on Login button. 7. User’s homepage
displayed.
8. Use case end.

Alternative Course of Action 6.The system returns the login form to resubmit valid data
if wrong user name and password submit[ACA]

15
 Web Based Inventory Management System

2.4. Sequence Diagram

A UML Sequence diagram showing the sequence of interactions among objects and used to
represent or model the flow of messages, events and actions between the objects or components
of inventory Management System. Sequence Diagrams are also used primarily to design,
document and validate the architecture and interfaces of the system by describing the sequence
of actions that need to be performed to complete a task or scenario.

Actor home page login User page Database

Open()

validate()
Enter User name and Password()

Check()

if correct
Display user page()

Else()
please enter user name and password

Figure 2Sequence diagram for login

16
 Web Based Inventory Management System

Stock clerk Register item

home page Login Stock clerk
<<actor>> Form Data base
page page

open()

enter user name and password validate()

check()

invalide input if incorrect

display() else

click register link()

display()

fill form and click submit button()

valid form()

register()

not exist
registered

already exist else

logout

Figure 3sequence diagram for register item

17
 Web Based Inventory Management System

Employee home page

login form Employee Send feedback
<<actor>> DataBase
page form

open()

display()

validate()
enter user name and password
if incorrect

check()
invalid input()

display() else
click send feedback link()

display()

fill comment and click send feedback()

validate()
add()

successfull
logout

Figure 4 sequence diagram for send feedback

18
 Web Based Inventory Management System

Collage dean
<<actor>>
home page College Dean View item Data base
Login
page form
Form
open()

display()

enter user name and password

validate()
check()
invalid input() if incorrect()

else
display()

click view item link()

display

enter item id and click view item button

validate()

check()

if exist
display information)
invalid()

not exist else

logout

Figure 5sequence diagram for view item

19
 Web Based Inventory Management System

2.5 Activity diagram

Activity diagrams provide a way to model the workflow of a business process. Different tools
such as decisions, start states, end states, are used on the activity diagram.Activity diagram is
basically a flow chart to represent the flow form one activity to another activity.

open system

Enter user name

and password

invalid input click login

correct

Redirect actor page

Figure 6 :Activity diagram for logins

20
 Web Based Inventory Management System

open system page

System display request link

User click on
Request link

Display request form

Fill form and click

Request button

invalid data

yes

Send successfully

Figure 7Activity diagram for send request

21
 Web Based Inventory Management System

System display
Login form

Enter user name

and password

incorrect

correct

System display
Stock clerk page

Click on register link

Fill item data

And click save button

invalid input

correct

Successfully
register

Figure 8Activity diagram forregister item

22
 Web Based Inventory Management System

System display login page

Enter user name

and password

Invalid Input

correct

System display
employee page

Click on view
item link

System display
item information

Figure 9Activitydiagramfor view item

23
 Web Based Inventory Management System

2.6 Analysis class Diagram

A class diagram is diagram that describes the structure of a system by showing the systems
Classes, their attributes, operations (or methods) and the relationships among objects Class
Diagrams can also be used for data modeling. Class diagram has three components. The top
Component contains the name of the class. The middle components contain the attributes of the
class. The bottom component contains the operations the class can execute.

24
 Web Based Inventory Management System

1
Employee
Admin *
-Emp_ID
Directorate
-First name
+Manage Account() -Middle Name Allowed Employee
+Take Backup() -Last Name +view item() -ID
+Restore DB() -Sex +view request() -emp-id
-Email +send item request() -Dept_offic_colleg_id
*
-Dept_office_collage_id +Register allowed employee() -item name
-Emp_status +register transfer item() -date
Property Admin Directorate -Date -status
Inherits +view item()
+view item() +send feadback()
+view withdraw item() * *
+send item request() Inherits
Inherits Collage Dean * register
+view bid()
+view feadback()
+post notice() User +view item()
Inherits
-UserName +view request()
-Password +send item request()
* *
-Emp_ID +approve item request()
1 Inherits
-UserType +Registerallowed employee()
Presidant Inherits *
-Status +Register transfer item()
Inherits
+view item() *
+view withdraw item() Department Head
+view request() Inherits
+view bid() Inherits +view request()
Inherits +view item()
+send request()
post +register transfer item() +send request() *
Stock Clerk +register
* transfer item() *

+manage item() Procurment Committee

VicePresidant +manage employee()
+manage withdraw item() +view request()
send +view item() +manage transfer item() +approve request()
+view request() +manage postion() +post bids() manage
+send request() +manage collage()
+register transfer item() +manage department() 1 Bid
manage *
+register allowed employee() +manage office() * 1
1 view -bid_id
+manage supplier() -subject
* * view -content
Notice manage * manage
* 1 1
* * 1 -start_date
-notice_id *
* * approve
* and view
manage manage -end_date
-subject
-content Item Request -status
-start_date * Item
-end_date -request_id
-status 1 -emp_id -item_register_id * *
*
-item name -item model Withdraw Item Item Transfer
-specification manage -serial number *
-withdraw id -transfer id
-quantity * -catagory
* -item register id -withdraw id *
-request from -description
-stock clerk id -transfer emp_id
-status -shelf number
Supplier -emp_id -reciver emp-id
-date -request id *
-supplier_id -date -wittnes_id
-stock clerk id
-organization name -item price * -date
-total price *
1 -date
-country Postion1 1 -status
-city Department
-postion_id Collage
-phone -emp_id -dept_id
Office -college_id
-tin number -Dept_office_college_id -dept_name
-office_id -college name
-date -postion status -college_id
-office name -status
-status -date -status
-status

Figure 10 Analysis class diagram

25
 Web Based Inventory Management System

CHAPTER THREE

3. SYSTEM DESIGN
Systems design is the process of defining the architecture, components, modules, interfaces, and
data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development.

The purpose of designing is to show the direction how the web page is built and to obtain clear
and enough information needed to drive the actual implementation of web page. It is based on
understanding of the model the web page built on system design also focuses on decomposing
the system in to manageable parts. To give right service for the right user at the right time on
subject of his/her need make the design properly. The design goals are derive from the
nonfunctional requirement, which is the part of the analysis document, and they describe the
quality of the system to be implemented.

3.1. Design Class Diagram

Class Diagrams are used to represent the structure of the system in terms of objects, their
methods and nature of relationship between classes.

26
 Web Based Inventory Management System

Employee 1 *
Admin -Emp_ID
-First name:varchar(30) Allowed Employee
Directorate
-Middle Name:varchar(30) -ID:varchar(30)
+Manage Account() -Last Name:varchar(30)
+Take Backup() -emp-id:varchar(31)
-Sex:varchar(32) +view item() -Dept_offic_id:varchar(30)
+Restore DB() -Email:varchar(40) +view request() -item name:varchar(40)
-Dept_office_id:varchar(30) +send item request() -date:date
-Emp_status:varchar(22) +Register allowed employee() -status:varchar(30)
-Date:date +register transfer item()
Property
Administrator +view item()
Inherits +send feadback()
Directorate **
*
*
+view item()
Inherits *
Collage Dean
+view withdraw item() register
+send item request()
+view bid() +view item()
+view feadback() Inherits User Inherits +view request()
+post notice() +send item request()
-UserName +approve item request()
-Password +Registerallowed employee()
1 +Register transfer item() *
* * -Emp_ID
Inherits
Presidant Inherits -UserType
-Status *
Department Head
* view *
+view item()
*
+view withdraw item() +view request()
+view request() Inherits Inherits
+view item()
+view bid() Inherits +send request()
+send request() +register transfer item()
+register transfer item() *
Stock Clerk
Procurment Committee
post *
VicePresidant +manage item()
+manage employee() +view request()
+manage withdraw item() +approve request()
1+post bids() manage
+view item() +manage transfer item()
+view request() +manage postion() 1
send
+send request() +manage collage() 1
+register transfer item() +manage department() Bid*
+register allowed employee() +manage office() * manage -bid_id:varchar(19)
+manage supplier() manage -subject:varchar(30)
view
* * -content:longtext
* * view
* 1 1* -start_date:date
-end_date:date
1
* -status:varchar(30)
manage1
*
Notice manage
-notice_id:varchar(28) *
* * Withdraw Item
Item Request
-subject:varchar(30) manage -withdraw id:varchar(30)
-content:varchar(33) -request_id
* -emp_id:varchar(30) -item register id:varchar(20)
-start_date:date manage
-end_date:date * -item name:varchar(32) -stock clerk id:varchar(32)
-status:varchar(28) -specification:varchar(20) * -emp_id:varchar(30)
-quantity:number *
-date:date *
-request from:varchar(30)
-status:varchar(20) *
Item
-date:date
-item_register:varchar(28)_id *
-item model:varchar(38)
* Item Transfer *
1 -serial number:varchar(20)
-catagory:varchar(23) -transfer id:varchar(30)
Supplier *
-description:varchar(23) -withdraw id:varchar(20)
-supplier_id:varchar(18) Postion -shelf number:varchar(25) -transfer emp_id:varchar(18)
-organ_name:varchar(38) -request id:varchar(30) -reciver emp-id:varchar(30)
-postion_id:varchar(18)
-total price:varchar(28) -stock clerk id:varchar(26) -wittnes_id:varchar(20)
-country:varchar(30)
1 -emp_id:varchar(28)
-Dept_office_id:varchar(20) -item price:varchar(23) * -date:date
-city:varchar(28) -date :date *
-postion status:varchar(28)
-phone:varchar(40) -status:varchar(21)
-date:date 1
-tin number:varchar(33)
-date:date Department
Collage
-status:varchar(28) -dept_id:varchar(20)
Office -college_id:varchar(28)
-dept_name:varchar(24)
-college name:varchar(31)
-office_id:varchar(23) -college_id:varchar(23)
-status:varchar(50)
-office name:varchar(28) -status:varchar(30)
-status:varchar(28)

Figure 11 Design class diagram

27
 Web Based Inventory Management System

Table 3 design class description for office

Attribute Purpose Data type

Emp-Id Used as employee unique identifier Varchar(20)
Name Represent name of employee Varchar(20)

Table 4 design class description for department

Attribute Purpose Data type

Dept.-Id Used as department unique identifier Varchar(22)
Name Represent name of department Varchar(22)
Collage-Id Used as department unique identifier Varchar(22)

3.2 Database Design

Physical database design translates the logical data model into a set of SQL statements
that define the database. Rules in database design are:-

 Unique identifiers are not allowed to have NULL values. These referred to as
primary keys in the physical database has unique value.
 Foreign keys may have many values in the table.
 Entities become tables in the physical database.
 Attributes become columns in the physical database.

28
 Web Based Inventory Management System

Table 5 user detail table

29
 Web Based Inventory Management System

Table 6 item request detail table

30
 Web Based Inventory Management System

Table 7 item detail table

Table 8 item withdraw detail table

31
Web Based Inventory Management System

32
 Web Based Inventory Management System

3.3 user interface design

User interface design requires a good understanding of user needs. The goal of user interface
design is to make the user's interaction as simple and efficient as possible, in terms of
accomplishing user goals what is often called user-centered design.(6)

The following interface design pictures describe the logical characteristics of some interfaces
between the system and the users. So the sample interfaces are shown as follows.

Figure 12 interface for login

33
 Web Based Inventory Management System

Figure 13 interface for item registration

34
 Web Based Inventory Management System

Figure 14 interface for collage dean

35
 Web Based Inventory Management System

3.4 Deployment Diagram

Deployment diagram shows the hardware of our system, the software that to be installing in that
hardware. It also shows how hard ware and software components work together.(5)

client Application server Database

server

manage collage
Admin

manage department

Director

manage account

President view report

Property approve request

Administration
Directorate
view item
Security

Collage Dean
send request

Department
head Register allowed
employee

Employee
Register item

Register item withdraw

Stock clerk

Register supplier
DataBase
Customer
view notice

Vice president view bids

Figure 15 Deployment diagram

36
 Web Based Inventory Management System

IV.CHAPTER FOUR

4. IMPLEMENTATION
The implementation document helps users on how to work with the system. These phase
transform the design and analysis of the system into a tangible system by writing the code to the
system to be developed and make it operational and applicable by testing and debugging the
functionalities that are done.

4.1 Overview of the programming language used

PHP is a server side scripting language that is embedded in HTML. It is used to manage dynamic
content, databases, session tracking, even build entire e-commerce sites.
This project used php server side programming technology integrated mysqli database with a
Programming language. Because:
 The code and its syntax is simple to understand
 It's quick to develop in PHP is flexible.
 It's available for free
 It runs on many different operating system

4.2 Algorithms Used

1. Register Item
Logged in to stock clerk page
Click on register item link
Registration form is displayed
Fill item profile data
Click on register button
If (valid)
Display successful message.
Else display invalid input message
2. Send Item Request

Logged paged
Click on Send Item Request link
Item request form is displayed
Fill item request data
Click on send button
If (valid)
Display successful message.
Else display invalid input message

37
 Web Based Inventory Management System

4.3 Sample Code

Sample code for view own item
<?php
session_start();
include("connection.php");
?>
<html><head>
<title>view item withdraw</title>
<link href="mystyles.css" rel="stylesheet" type="text/css"/>
</head><body bgcolor="#B0C4DE">
<?php
if(isset($_SESSION['sun'])&& isset($_SESSION['spw']))
{
$emppostionoffid1=$_SESSION['$emppostionoffid'];
$empid= $_SESSION['Employee_id'];
$oid=$_SESSION['$empoffid'];
$poname=$_SESSION['$emppostionoffname'];
?>
<center>
<div id="divWrapper">
<table border=0 ><tr><td colspan="6">
<div id="divheader"><?php include("header.php");?></div>
<div id="divNav">
<?php
include("internalmenu.php");
?>
</div></td></tr><tr>
<td><div id="divSideContentLeft">
<?php
include("collagemenu.php");
?>
</td><td><div id="divContentCenter">
<?php include("print.php") ?>
<?php
if($con)
{ echo "<h1>List of employee to receive item in $poname College</h1>";
$sql="select
postion.Employee_id,First_Name,Middle_Name,Last_Name,Did,collage_id,item_withdr
aw.item_Register_ID,item_model,catagoryfromemployee,department,item_withdraw,ite
m,postion where postion.Employee_id='$empid' and
postion.Dept_Office_collage_Id='$emppostionoffid1'andpostion.Employee_id=item_wit
hdraw.Employee_id and item_withdraw.item_Register_ID=item.item_Register_ID and
catagory='fixed' and postion.Employee_id=employee.Employee_id".mysqli_error($con);
$sql1=mysqli_query($con,$sql);
$row0=mysqli_fetch_array($sql1);

if($row0){

echo "<table border=2>";

echo"<tr><th>Employee Full Name</th> <th>Item Name</th> </tr>";

38
 Web Based Inventory Management System

echo "<tr><td>".$row0['First_Name']." ".$row0['Middle_Name']."

".$row0['Last_Name']."</td>
<td>".$row0['item_model']."</td>

</tr>";
$sql4="selectpostion.Employee_id,First_Name,Middle_Name,Last_Name,Did,collage_id
,item_withdraw.item_Register_ID,item_model,catagoryfrompostion,employee,item_with
draw,item,department where postion.Dept_Office_collage_Id=department.Did and
department.collage_id='$emppostionoffid1'andpostion.Employee_id=item_withdraw.Em
ployee_id and item_withdraw.item_Register_ID=item.item_Register_ID and
catagory='fixed' and postion.Employee_id=employee.Employee_id";
$sql4=mysqli_query($con,$sql4);
$row4=mysqli_fetch_array($sql4)
if(!$row0 && $row4){
echo "<table border=2>";
echo"<tr><th>Employee Full Name</th> <th>Item Name</th></tr>";
echo "<tr><td>".$row4['First_Name']." ".$row4['Middle_Name']."
".$row4['Last_Name']."</td>
<td>".$row4['item_model']."</td>
</tr>";
}

if($row0 && $row4){

echo "<tr><td>".$row4['First_Name']." ".$row4['Middle_Name']."

".$row4['Last_Name']."</td>
<td>".$row4['item_model']."</td>
</tr>";
}

// postion.Dept_Office_collage_Id=department.Did and
department.collage_id='$emppostionoffid1'

$sql="select
employee.Employee_id,First_Name,Middle_Name,Last_Name,Did,collage_id,item_with
draw.item_Register_ID,item_model,catagory from
employee,department,item_withdraw,item where
(employee.Dept_Office_collage_Id='$emppostionoffid1' or
employee.Dept_Office_collage_Id=department.Did and
department.collage_id='$emppostionoffid1')and
employee.Employee_id=item_withdraw.Employee_id and ((select count(*) from postion
where postion.Employee_id=employee.Employee_id)=0 ) and
item_withdraw.item_Register_ID=item.item_Register_ID and
catagory='fixed'".mysqli_error($con);
$sql1=mysqli_query($con,$sql);

//$recordfound=mysqli_query($con,$sql);
if($sql1)

{
if(!$row0 && !$row4){

39
 Web Based Inventory Management System

echo "<table border=2>";

echo"<tr><th>Employee Full Name</th> <th>Item Name</th> </tr>";
}
while($row=mysqli_fetch_array($sql1))
{
echo "<tr><td>".$row['First_Name']." ".$row['Middle_Name']."
".$row['Last_Name']."</td>

<td>".$row['item_model']."</td>
</tr>";

}
echo "</table>";
}
else
echo "No records found!".mysqli_error($con);;}
else
echo "Unable to connect the database:";
?>
</div></td>
<tr><td colspan=6>
<div id="divFooter"><br>
<?php include("footer.php");?>
</div></td></tr>
</table>
</div>
</center>
<?php}
else{
header("location:login.php");
}?>
</body>
</html>

40
 Web Based Inventory Management System

5. CHAPTER FIVE

5.1 TESTING
Testing is a process to show the correctness of the program and designed to analyze the logic
used in the implementation of the System. It also checking of the system workability in an
attempt to discover errors and avoiding such errors from the system.

5.1.1 Unite testing

Unit testing is every module of the System is separately tested. It is often done by the
programmer to test that the unit he/she has implemented is producing expected output against
given input. Test specifications: that will be done in our proposed system the tests done as
follow

 Test for login

 Test for register item
 Test for withdraw and transfer item
 Test for send item request

5.1.2 Integrating Testing

Integration testing is the activity of software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before acceptance testing. Thus,
Integration testing is a logical extension of unit testing.

5.1.3 Acceptance Testing

A system is said to be accepted if and only if the user of the system is satisfied. In this
perspective acceptance testing is widely used to prove that system performs as per the
requirements. In acceptance testing the customers provides the input data to validate the system
operation. It is also known as functional testing, black-box testing, release acceptance,
application testing, confidence testing, final testing and validation testing.

5.1.4 System Testing

It is the final step of testing. In this the team members tests the entire system as a whole with all
forms, code, modules. In test the team members test all the functionalities in the System. All
errors in the forms, functions, modules are tested.

41
 Web Based Inventory Management System

CHAPTER SIX

6. Conclusion and Recommendation

6.1 Conclusion
An effort has been made to study Web Based Inventory management system as partial fulfillment in
Information technology. In order to solve or reduce different problems of the existed system that we
tried to develop web based system. We believe that different tools and techniques has helped us a lot in
capturing real user requirements and model the right system for the users for their day to day activities.

Generally, the project is aimed at developing a Web Based Inventory management system system. The
system allows employee to perform tasks in an easy way.

6.2 Recommendation
Nowadays, the world is highly becoming a competitive world in technology. So, Organizations
should have to divert their attention on using the recent technology to facilitate their work
properly. This can be real if they are able to use recent information technology (IT) to
successfully achieve their objective.

Generally, since technology is mandatory to help or accomplish all tasks qualitatively and
quantitatively we recommend to the organization to automated the whole system as much as
possible to fasten their work and to become enough competent to other organizations.

6.3 Future Enhancement

 The system will prepare well organized report
 The system will be developed by using android in a way to support mobile users.
 The system will be including other language like Amharic language
 The system will be including integrated system like human resource management system

42
 Web Based Inventory Management System

Appendix
Activity diagram: diagram that describes procedural logic, business process and work flow
supporting parallelism.
Actor: a role that a user takes when invoking a use case. Also see actor modeling.
Class the primary declarative construct of Object-oriented Programming; a cohesive unit of
Attributes and Operations; a compile-time template for an Object
Class diagram: type of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes, and the relationships between the classes.
Sequence diagram describes the Messages sent between a numbers of participating
.

Reference
(1)https://www.modelio.org/tutorials/how-to-create-uml-use-case-diagram.html

(2)http://docs.embarcadero.com/products/rad_studio/delphiAndcpp2009/HelpUpdate2/EN/html/devc
ommon/uml15usecasediagramdefinitionexample_xml.html

(3)https://www.useoftechnology.com/technology-today-tomorrow/

(4)http://www.agilemodeling.com/style/classDiagram.htm

(5)https://www.tutorialspoint.com/uml/uml_deployment_diagram.htm

(6) https://en.wikipedia.org/wiki/User_interface_design

(7)https://en.wikipedia.org/wiki/Debre_Markos_University

43