DEBRE BERHAN UNIVERSITY

SCHOOL OF COMPUTING SCIENCE

DEPARTMENT OF INFORMATION TECHNOLOGY

ONLINE INVENTORY MANAGEMENT SYSTEM IN DEBRE

BERHAN UNIVERSITY
BY
NO. NAME ID.
1 NIGUS REDA COMPR/078/03
2 TARIKU ADERAW COMPR/136/03
3 MULUKEN KENDAYA COMPR/127/03
4 ELSA SHEFRWO COMPR/112/03
5 ELSHADIE MOSSISA COMPR/113/03
6 NIGIST GELANEH COMPR/077/03
INDUSTRIAL PROJECT-I and II

ADVISORS: INSTRUCTOR

HAFTE A. AND KIDANEMARYAM G.

FINAL PROJECT SUBMITED TO DEPARETEMENT OF INFORMATION
TECHNOLOGY IN PARTIAL FULFILLEMENT OF THE REQUIREMENTS FOR
THE DEGREE OF BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

JUNE, 2014
DEBRE BERHAN, ETHIOPIA
 ACKNOWLEDGEMENT
First of all, we would like to thank our God, who gives us love, patience, healthy, wisdom and ability
to walk through all the problems and obstacles during the period of our study. Then we would like to thank
our advisors Instructor Kidanemaryam G. and Hafte A. for thier constractive opinion and willingness to
participate in each part of our project and their effective direction, assistance and guidance for the
accomplishing of this project. We also wish to thank the stock Manager and the stock clerk, who gave us the
required information about the stock.
Our Special thank to Kasahun Minwuye, who had generously provided us his lap top for this Project.
Finally we would like to express love, thanks, appreciation, and respect to our families and also we would like
to thank the teaching staffs of Information Technology who have contributed wholly to the success of this
project.
TABLE OF CONTENTS PAGE
CHAPTER ONE ............................................................................................................................................... 1
[Link] BsACKGROUND ........................................................................................................................ 1
1.1. Organizational Background .................................................................................................................... 1
1.2. Statement of the Problem and its Justification ....................................................................................... 1
1.2.1. General Problem ............................................................................................................................... 1
1.2.2. Specific Problem .............................................................................................................................. 2
1.3. Objective of the Project .......................................................................................................................... 2
1.3.1. General Objective ............................................................................................................................. 2
1.3.2. Specific Objectives ........................................................................................................................... 2
1.4. Methodology .......................................................................................................................................... 3
1.4.1. Fact Finding Techniques .................................................................................................................. 3
1.4.2. System Analysis and Design Techniques ......................................................................................... 3
1.4.3. Tools Used in the Project ................................................................................................................. 4
1.5. Scope and Limitation of the Project ....................................................................................................... 4
1.5.1. Scope of the Project .......................................................................................................................... 4
1.5.2. Limitations of the Project ................................................................................................................. 4
1.6. Project Team Organization ..................................................................................................................... 5
1.7. Feasibility Study of the New System ..................................................................................................... 5
1.7.1. Economic Feasibility ........................................................................................................................ 5
1.7.2. Technical Feasibility ........................................................................................................................ 7
1.7.3. Operational Feasibilities ................................................................................................................... 7
1.7.4. Schedule Feasibility ......................................................................................................................... 7
1.8. Significance of the Study ....................................................................................................................... 8
CHAPTER TWO .............................................................................................................................................. 9
[Link] THE EXISTING SYSTEM .................................................................................................. 9
2.1. Introduction ............................................................................................................................................ 9
2.2. Description the Existing System ............................................................................................................ 9
2.3. Player of the Existing System ................................................................................................................ 9
2.4. Work Flow of the Existing System ........................................................................................................ 9
2.5. Report Generating in the Existing System ........................................................................................... 10
i
 2.6. Business Rules Identified in the Existing System ................................................................................ 10
2.7. Paper Document in the Existing System .............................................................................................. 11
2.8. Problem in the Existing System ........................................................................................................... 11
2.9. Practice to be Preserved ....................................................................................................................... 11
2.10. Alternative Solution .......................................................................................................................... 11
2.11. The Proposed System ........................................................................................................................ 11
2.11.1. Functional Requirement of the New System ............................................................................... 12
2.11.2. Non Functional Requirement of the New System ....................................................................... 12
CHAPTER THREE ........................................................................................................................................ 13
[Link] DELIVERABLES OF THE NEW SYSTEM ......................................................................... 13
3.1. Introduction .......................................................................................................................................... 13
3.2. Use Case Diagram ................................................................................................................................ 13
3.2.1. Use Case Documentation ............................................................................................................... 15
3.1. Analysis Level of Class Diagram ......................................................................................................... 22
3.4. Sequence Diagram ................................................................................................................................ 23
3.2. Activity Diagram .................................................................................................................................. 31
CHAPTER FOUR ........................................................................................................................................... 36
[Link] DELIVERABLE OF THE NEW SYSTEM................................................................................. 36
4.1. Introduction .......................................................................................................................................... 36
4.2. Design Class Diagram .......................................................................................................................... 36
4.3. Collaboration Diagram ......................................................................................................................... 37
4.4. State Chart Diagram ............................................................................................................................. 43
4.5. Database Design ................................................................................................................................... 47
CHAPTER FIVE ............................................................................................................................................ 49
[Link] DELIVERABLE OF THE NEW SYSTEM ........................................................... 49
5.1. Introduction .......................................................................................................................................... 49
5.2. Component Diagram ............................................................................................................................ 49
5.3. Deployment Diagram ........................................................................................................................... 50
5.4. User Interface ....................................................................................................................................... 50
CHAPTER SIX ............................................................................................................................................... 55
[Link] DEVELOPMENT ................................................................................................................ 55
CHAPTER SEVEN ........................................................................................................................................ 61

ii
[Link] AND RECOMMENDATION ........................................................................................... 61
7.1. Conclusion ............................................................................................................................................ 61
7.2. Recommendation .................................................................................................................................. 61
Appendix ................................................................................................................................. 62
Reference ................................................................................................................................................ 63

iii
List of Tables
Table 1.1: Project Team Organization ………………………………………………………………………….5

Table 1.2: Miscellaneous Costs …………………………………………………………………..….…………6

Table 1.3: Software Development Costs ………………………………….….…………………………….......6

Table 1.4: Time Schedule for our Project ……………………………………...…………………………....….7

Table 3.1: Main Course of Action about Login …………………………………………...………………..…15

Table 3.2: Main Course of Action about Add New User….……………………………………..……………16

Table 3.3: Main Course of Action about Update Account …………………………………………...……….16

Table 3.4: Main Course of Action about Inactivate Account ……………………………………...………….17

Table 3.5: Main Course of Action about Add Item ………………………………………………………...…18

Table 3.6: Main Course of Action about Update Item ……………………………………………………...…18

Table 3.7: Main Course of Action about Delete Item …………………………………...……………….……19

Table 3.8: Main Course of Action about View Report …….…………………………………..……………...20

Table 3.9: Main Course of Action about View Item ………………………………………...………………..20

Table 3.10: Main Course of Action about Take Item Request..………………………...……………………..21

Table 3.11: Main Course of Action about Return Item Requesting ...……………….…………………..……21

Table 3.12: Main Course of Action about Receive Response ………………………………….………..……22

iv
List of Figures
Fig 3.1: Usecase of Proposed Inventory Management System …………………………………………..……14

Fig 3.2: Class Diagram of Our System …………………………………………………………………..……23

Fig 3.3: Sequence Digram of Login ………………………………………………………………………...…24

Fig 3.4: Sequence Digram of Add New User ……………………………………………………...………….25

Fig 3.5: Sequence Digram of Update User Account …………………………………………………………..26

Fig 3.6: Sequence Digram of Inactive User Account …………………………………….…………….…….27

Fig 3.7: Sequence Digram of Add Item ……………………………………………………………………….28

Fig 3.8: Sequence Digram of View Report ……..…………..…………………………………………………29

Fig 3.9: Sequence Digram of Request Item …………………..……………………………………………….30

Fig 3.10: Activity Diagram of Add New User………………………………..................................................31

Fig 3.11: Activity Diagram of Manage User…………………………………………………………………..32

Fig 3.12: Activity Diagram of Add Item……………………………………………………………………....33

Fig 3.13: Activity Diagram of View Report ……….………………………………………………….………34

Fig 3.14: Activity Diagram of Taken Request Item…….…………….…………………………………….....35

Fig 4.1: Design of Class……………………………………….…….…………….…………………………...36

Fig 4.2: Collaboration Diagram of Login…………………………..…..... …………………………………...37

Fig 4.3: Collaboration Diagram of Add New User ……………..…..…............................................................38

Fig 4.4: Collaboration Diagram of Update User Account …………………………………….…………........39

Fig 4.5: Collaboration Diagram of Inactive User Account ………………........................................................40

Fig 4.6: Collaboration Diagram of Add Item ……………………….………………………………………....41

Fig 4.7: Collaboration Diagram of View Report …….…………….….............................................................42

Fig 4.8: Collaboration Diagram of Request Item…………………………………..………………………......43

Fig 4.9: State Chart of Login………………………………………..................................................................44

Fig 4.10: State Chart of Add User……………………….………….…............................................................44

Fig 4.11: State Chart of Update Item……………………………….….............................................................45

v
Fig 4.12: State Chart of Delete Item………………………………..….............................................................45

Fig 4.13: State Chart of View Report …....………………………..…..............................................................46

Fig 4.14: State Chart of View Item……………………………….…................................................................46

Fig 4.15: State Chart of Request Item……………………………….…............................................................47

Fig 4.16: Database Design of the Proposed Inventory Management System …………………………………48
Fig 5.1: Component Diagram………………………………………………………………………………….49
Fig 5.2: Layer of the System (Deployment Diagram)…………………………………………………………50
Fig 5.3: User Interface Design for Home………………………………………………………………………51
Fig 5.4: User Interface Design for Login………………………………………………………………………51
Fig 5.5: User Interface Design for Add Usser with Error Message……………………………………………52
Fig 5.6: User Interface Design for Add User…………………………………………………………………..52
Fig 5.7: User Interface Design for Manage User………………………………………………………………53
Fig 5.8: User Interface Design for View Report……………………………………………………………….53
Fig 5.9: User Interface Design for Report for Free Item……………………………………………………....54
Fig 5.10: User Interface Design for Clerk’s Approval Page…………………………………………………...54

vi
 Abstract
This system provides superior management over inventory by optimizing inventory stocking levels for
excellent customer service. It maintains the all information about the organization regarding employees,
different stock levels etc.
Online Inventory management system mainly provides effective and fast data processing and
controlling of stocks. This web based system of managing inventory in a our University setting is expected to
help various services keep an updated data on the status of their tools and equipments. In designing such a
system, PHP has been employed as a development language and MySQL as a backend database with CSS
implemented for the interface. Generally, the main goal of online inventory management system is to shorten
data-processing time, to reduce errors, to improve the accuracy of input and to provide data reliability of the
stock.

vii
 CHAPTER ONE
1. PROJECT BACKGROUND
Inventory management system 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.
The implementation of this web-based inventory system can help the University to develop the skills to handle
with their operational environments. Because lack of system tool to be used to monitor the availability and
quantity of materials in this University.

1.1. Organizational Background

Debre Berhan University was officially established in June 3, 1999. During this time it included three
faculties. These are natural science, social science, Business and Economics Faculty. At present the University
runs undergraduate programs. It is expected that with the on-going expansion a number of faculties and
programs will be opened and the enrolment capacity will increase.
The Debre Berhan University store office was established during this time and it is developed from time to
time with the development of the University. As it is developed from time to time it increases its capacity by
increasing the number of workers in the office. The Debre Berhan University store office is the back bone of
the University by managing any activities related to materials available on the University. Now a day’s, Debre
Berhan University store office gives many services, among these services the following are the main services:
 Registering new materials
 Generate report periodically
 Offering materials to the users

1.2. Statement of the Problem and its Justification

1.2.1. General Problem

Debre Berhan University Inventory System is using manual system on the inventory of all the properties
of University.

1
 1.2.2. Specific Problem

 Registering materials is manual and not well organized. This will result in poor techniques handling in
arrangement related data.
 It is not easy to handle reservation, because the stock clerk is forced to check manually the entire list of
materials which are stored in the stock. In addition, the current system does not allow speed processing
of users request adjustment and cancellation of what has been reserved.
 To generate a report from manual system requires much effort and it is time consuming.
 Since all records kept physically on shelves and file cabinets the stock record keeping system is poor
and subjects to number of problem such as files can be destroyed or stolen.
 It is difficult to identify the materials where they are stored because of the presence of different stores.
 Difficult to manage and control daily activities.

1.3. Objective of the Project

1.3.1. General Objective

To develop computerized system for inventory management system in Debre Berhan University.

1.3.2. Specific Objectives

 To shorten data-processing time: In processing the inventory, it will not consume much time to
process.
 Reduce errors: Through this system, fewer errors will be avoided because the system will be
easy to use.
 Improve the accuracy of input: It will help the user to avoid mistakes regarding the data that
they will give to the clients. There will be accurate information.
 Give information easily and efficiently: It will make easier to give information for the user.
 Data reliability: It gives users the assurance that the information they see is reliable.
 Data security: It ensures that data is kept safe from corruption and that access to it is suitably
controlled. Thus data security helps to ensure privacy. It also helps in protecting personal data.

2
 1.4. Methodology

1.4.1. Fact Finding Techniques

The Methods and techniques we use to analyze the existing system and designing web based system
includes, interview, document analysis and practical observation. Those methods which help us to gather the
required data to analyze our project and those methods selected due to the time and the organization’s
willingness.

I. Primary Techniques

i. Interview

To get information, discussions with the store head will be conducted with concerned staff of the
corporation to get general information. We asked the head of the store Ato Worku Asefa at 03/12/20013 G.C
about that store information when we wanted to write this proposal.

ii. Practical Observation

It helps us to get real information how the organization performs its function and this helps to strength
the data that gathered through interview and document analysis.

II. Secondary Techniques

i. 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.

1.4.2. System Analysis and Design Techniques

In this project, our team will use object oriented system development methodology (OOSD) for the
design.
This technique has several phases some of them are:

I. Object Oriented Analysis (OOA)

During this phase the team uses to model the function of the system (use case modeling), find and
identify the business objects, organize the objects and identify the relationship between them and finally model
the behavior of the objects in detail.

3
 II. Object Oriented Design (OOD)

During this phase our team uses Microsoft Visio software to refine the use case model and rational rose
for designing the sequence, collaboration, activity diagrams and to model object interactions and behavior that
support the use case scenario.

1.4.3. Tools Used in the Project

I. Back End Design Tool

MySQL software of the data base system will be used in developing and managing the back end of the
system.

II. Front End Design Tool

The user interface will be developed using php integrated development environment since it easily
designing the front end and connected in to data base easily.

1.5. Scope and Limitation of the Project

1.5.1. Scope of the Project

The project that we are trying to focus on inventory management system will cover only on the Debre
Berhan University and will perform the following activities:
 To add users and items.
 To search items.
 To update users and items.
 To request an item online.
 To generate report.
Generally, this system automates the functions of inventory management system.

1.5.2. Limitations of the Project

Limitation is element of factor or subsystem it restricts the system decision making from achieving
potential goal of the system. There are many constraints within our proposed system that limit their
effectiveness of performance. Our system is limited only in the process of inventory management system of the
Debre Berhan University.

4
The system does not include the following:
The system may not automate fully because:
 Our system does not include online payment.
 Transferring an item must be done manully.
 Users must contact physically to administrator to change their password.

The above activities or subsystems are proposed system limitations because of the following reasons:
 Time:-Is the main factor of limitation our proposed systems that limit its performance because
while we are developing the system it takes more time and we may not get enough time to
automate the system.
 Resource: - we have not laptop as an alternative when arbitrary failed the desktop and also
when the power is off for a long time.

1.6. Project Team Organization

The project team composed of 6 members, one team leader, one deputy leader, one secretary and
members organized as follows.

Team Members Tasks

Nigus Reda Design/Assistance Implementer
Nigist Gelaneh Requirement Gathering/Testing
Muluken Kendaya Implementation/assistance designer
Tariku Aderaw Analysis/ Requirement Gathering
Elsa Sheferwo Assistance Implementer
Elshaday Mosisa Testing
Table 1.1: Team Organization

1.7. Feasibility Study of the New System

1.7.1. Economic Feasibility

The proposed web based inventory system is economically feasible because:

 The system requires very less human power.
 The system will provide fast and efficient automated environment.
 The system will have GUI interface and very less user-training is required to learn it.

5
  This project is economically feasible because its anticipated benefit is greater than the expected
cost.

I. Cost of the Project

i. Tangible Costs

The tangible costs to be acquired in developing the system are:-

 Miscellaneous Cost which includes hardware development cost and other costs.

 Software development cost

a. Miscellaneous Cost
This cost contains the various types of costs in which we spent for the development of the project or the University
covers some of the hardware expenses.
The following table lists the different miscellanies costs that we spent in the process of the development of the system.

Resources Amount Price

Pen 12 pen 60 Birr
Printing 200 pages 200 Birr
Paper 1 DESTA 90 Birr
Flash disk 3 450 Birr
CDRW 6 60 Birr
Laptop 1 12000 Birr
Desktop 1 By university
Total 12860 Birr
Table 1.2: Miscellanies Costs
b. Software Development Cost

For this particular project we will use different software but the software is provided by the university.

Type of Software’s Price

Microsoft windows 7/8/XP by the university
Microsoft Office by the university
MySQL from Xampp Free down load
Visual Paradigm for UML 11.0/Microsoft Visio /Rational Rose Free download
Notepad++ Free download
Total 0.00 Birr
Table 1.3: Software Development Costs

6
 ii. Intangible Costs
Those are costs which are uncountable .The intangible costs to be acquired in developing the system are:-
a. Human Knowledge
Our knowledge that we will spent to develop the system may not be measureable in terms of money.

1.7.2. Technical Feasibility

We have technical knowledge about:

 PHP to write the code or implementation with XAMPP.
 Mysql to build the database to store the data.
 Requirement analysis to know the stockholders constraint for their satisfaction
 Unified Modeling Language (UML) model to do analyzing and designing in good manner.

The technical requirement for the inventory management system in order to do their operation by the new
computerized system is:
 Training on the new system to know how it operates and how to use the computerized system.

1.7.3. Operational Feasibilities

It determines how the proposed system will satisfy the organizations need and it also offers Secure,
accurate and efficient system to the organization.
The system in which we are developing is also compatible to all operating systems and web browsers.

1.7.4. Schedule Feasibility

Within the time duration, we have identified the activities of the project in order to accomplish the project
objective within their schedule requirement which is on the table below.

Activities Submission date

November

December

February
No.

January

–June

1 System proposal
2 Requirement analysis
3 System design
4 Implementation
Table 1.4: Time Schedule for Our Project
7
1.8. Significance of the Study

The relevance why we have to conduct the study is:

 To understand how DEBRE BERHAN UNIVERSITY’s inventory management system works
and to design an appropriate computerized system.
 To enhance the service offered by the store office.
 To Enables the store customer’s to get fast access and help to the organization in service giving
operations.

8
 CHAPTER TWO
2. DESCRIBING THE EXISTING SYSTEM

2.1. Introduction

It is possible to develop a better system by understanding the existing system. Even if it is a manual
system; it is performing the following activities. Registering new items of the stock, supply items from the
stock, maintain and update records, prepare report and others.

2.2. Description the Existing System

The existing inventory management system performs the following function with semi manual system
and this leads to less security issues. Because of the manual system recording and posting of materials is time
consuming and boring .This is the result of lack of computerized system or web based system

2.3. Player of the Existing System

The main players of the existing system include the following:

i. Stock manager
ii. Stock keeper
iii. Stock clerk
iv. Customer/staff members

2.4. Work Flow of the Existing System

The work flow in the existing system is performed starting from the top store head to the lower or store
kipper person. First the store clerk receives the material detail from the store head and he/she assigns a code
and record the information.
Then the store keeper must get permission to receive and give the materials to the staff members by the
head of the store office and the store keeper checks the incoming and outgoing materials by the related
professionals. Then the store keeper documents the information and reports those materials detail based on
their type to the officer.

9
2.5. Report Generating in the Existing System

The stock clerk generates report to the stock manager then the manager generates report perodically
according to the task of the organization what activities are performed. But at the end of the year, the report
must be within a total income and an item.

2.6. Business Rules Identified in the Existing System

A business rule is successfully an operating standard or polices that we have try to specify for both the
existing system and the proposed system of the store management must satisfy.
We mainly focus on the existing system business rules.

The existing system has many business rules or principles some of them are:
Br1: new items are recorded and assigned a code by the stock clerks.
Br2: after recording and assigning code by the store clerk the items led to the store keeper then he/she
record, check and place them.
Br3: only staff members of the university are allowed to take an authenticated material.
Br4: when the users/staffs want to borrow any material he/she must register his id, full name, email, status and
other user details properly.
Br5: in order to get the item he /she must get permission from the academic president /president and the store
officer have to put their signature.
Br6: the staff member has to put his/her signature while taking the item.
Br7: the staff member should not damage the item.
Br8: if the staff member has loss or damage the item he/she has to replace that item or pay the cost with
additional percent.

10
2.7. Paper Document in the Existing System

I. Get Pass for stock

It is a paper formate to take an item from the stock. (see Appendix A: I)
II. Stock record card
It is a paper format to record an item to the store. (See Appendix A: II)

2.8. Problem in the Existing System

The major problem of the existing system is often used manual system so that it takes much time to
generate reports, to manipulate the overall activity of this system.

2.9. Practice to be Preserved

Practice to be preserved means an experience to be encouraged or the strong sides of the inventory during
operation of services. They are:
 Keeping the security of the materials physically.
 Manual signature.
 Physical control of materials in a store.
 Identifying the damaged and undamaged materials.
 Returning an item.
 Dispatching an item.

2.10. Alternative Solution

We try to put an alternative solution to the problems of the current existing system that are described in
the above section. The best alternative solution to the existing system is to change the existing manual system
and producing a computerized for the inventory management system.

2.11. The Proposed System

This is the new system that removes the existing problems which usually occurred in the inventory
system. The main purpose of the 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.
We all know the importance of automation. The application areas for the computerization have been
selected on the basis of following factors:

11
Minimizing the manual records kept at different locations.
 There will be more data integrity.
 Facilitate desired information display very quickly by retrieving information from users.
 Facilitating various statistical information which helps in decision-making.
 To reduce manual efforts in activities that involved repetitive work.
 Updating and deletion of such a huge amount of data will become easier.

2.11.1. Functional Requirement of the New System

There are several functions that are included in the system to satisfy the needs of the university. Some of
these are as follows:
The proposed system is intended for inventory purposes. Thus, it can perform different processes
included in the inventory. It will be able to monitor the delivery of a certain items; the newly ordered items
will be added to the current stocks and for the outgoing stocks that can be subtracted from the current stock.
Therefore, the University will able to track the item/supply that are running out of stock and thus prepare order.
Functional requirements of the system are:
 The stock clerk adds the new material’s information.
 The stock clerk updates the item information periodically.
 The users request item online.
 The system permits users to login according to their privilege.
 The manager views a report and the comment.
 The administrator manages(add, update, inactive) the user information.
 The users Search(view) an item.
 The staff members receive a response which is approved or disapproved.

2.11.2. Non Functional Requirement of the New System

User interface: attractive, easy to use and user friendly window for the users.
Performance and Access time: The system is capable of carrying huge amount of data with one database and
will provide fast access to the customer according to their privilege.
Security: the system should enable to task a back up at any time and able to restore from backups. The users
are allowed to do task only after the login process Based on their privileges.
System Modification &Maintainability: the system that we develop will be easily maintainable and
modifiable for new features.

12
 CHAPTER THREE
3. ANALYSIS DELIVERABLES OF THE NEW SYSTEM
3.1. Introduction

This chapter focuses on developing the requirement and analysis models for the new system using the use
case model, sequence diagram, activity diagram and class diagram.

3.2. Use Case Diagram

We use a use case to identify a sequence of actions that provides a measurable value to the actor which is
participating in our system and our use case describes a way to which the environment interacts with the
system.

13
 Web based Inventory Management System in DBU

Add User Update User

<<include>> <<include>> Inactive User

<<include>>

Manage User

View
<<in
c lude
>>
Comment
<<in
c lude
>>

Delete View Report

Login
Administrator <<extends>> Manager

Logout
View Item

Request Item

<<include>> <<include>>
Take Request
Return Request
Staff Member
Stock Clerk Recieve Response

Manage Item

>>
c lude
<<in

<<in
c lude
Add Item >>

<<in
c lude
>> Update Item

Delete Item

Fig 3.1: Use Case of the Proposed Inventory Management System

14
 3.2.1. Use Case Documentation
It is a sequence event that describes what the proposed inventory system we will develop does and how it
interacts with the environment mainly. This section describes the most important activates that the user of
inventory system do experience to make use of the system.

Name: Login
UC_ID: UC_01
Actor: users (administrator, manager, stock Clerk and staffs)
Description: this use case is used to ensure security in system usage.
Precondition: the user must have at least username and password.
Post condition: the user get access to the system according to their predefined system privilege and finally
he/she logout or turn off the page.

Main course of action:

Actor action System response

Step1: User has to activate the system. Step2: The System responses by
Step3: User selects account type and fills displaying the login interface and allow the
his or her username and password. user for the user name and password.
Step4: he/she select login button. Step5: System verifies user_name and
Step6: the User get authentication and Password.
access the system. Step7: System displays its main window.
Step8: Use case ends.
Table 3.1: Main Course of Action about Login

Alternative course of action (if user enters wrong user ID and / or password)
Step6: System displays an incorrect username and password message.
Step7: System enables user to try again.

Name: Manage User

UC_ID: UC_02
Actor: Administrator
Description: This use case is done by the Administrator when they need to delete, edit and make some
modification.

15
Preconditions: The Administrator login to the system to manage users.
Post conditions: The user information will be managed by administrator.
Main course of action:
About adding new user account

Actor action System response

Step1: the Administrator wants to add new user to the Step4: the system validates the new user detail.
system and he/she login to the system. Step5: the system save the user detail to the
Step2: the Administrator enters the new user name, database.
account type, Password and reenter password to the Step6: the system permits some operational
system via adding new user form. tasks according to his/her category of the new
Step 3: the Administrator submits the new user user.
information. Step8:the system ends
Step7:the Administrator tells the category, user name
and password to the user
Table 3.2: Main Course of Action about Add New User Account

Alternative course of action:

Step2: If the Administrator does not enter the username or the password or he/she entered which does not
match correctly, the system displays a message please enters the user name and password correctly.
Step4: if not correct the system doesn’t save the entered information to the database.
Step5: the system displays a fill again message and allow him/her to fill again.
About updating an account:

Actor action System response

Step1: the Administrator wants to update an Step4: the system checks the new account
account and he/she login to the system. information with the existing account in the
Step2: the Administrator inserts account _type, database.
user_name, password, and other user information. Step5: the system save the new account to the
Step3: he/she submits the data. database.
Step6: the updating process ends
Table 3.3: Main Course of Action about Update Account

16
Alternate course action:

Step5: the system doesn’t save the new account to the system database and it displays a fill again message.
About inactivate the account:

Actor action System response

Step1: the administrator wants to inactivate Step5: the system checks the entered
the account. information with the existing account in the
Step2: he/she login to the system. database
Step3: the administrator enters the account Step6: the system sends message “Do you
type, user_name of the user to be inactivated want to inactive?” to the administrator
in the form . Step8: the system inactvated the account from
Step4: the administrator selects the inactiveate the system.
button.
Step7: the administrator selects the yes option.
Table 3.4: Main Course of Action about Inactivate Account

Alternate course action:

Step3: the system displays fill again message to Administrator.

Step4: it does nothing.
Step5: the system sends a try again message.
Step7: the system ends if he/she selects no.
Name: Manage Item
UC_ID: UC_03
Actor: Stock Clerk
Description: This use case is done by the stock clerk when items are needed to be managed.
Preconditions: The stock clerk has to login to the system when he/she wants to manage item to the system.
Post conditions: The item information will be recorded to the database of the system.

17
Main course of action:
About adding item:

Actor action System response

Step1: the stock clerk wants to add new item Step4: the system checks the item detail.
to the system. Step5: the system saves the item input
Step2: the stock clerk inserts the item type, information to the database.
serial_no, brand, model and quantity, to the Step6: the system check whether it have saved
system via add item form successfully or not.
Step3:the stock clerk selects Add Item button Step7: the system displays a message
“successfully added”.
Step8: end the system.

Table 3.5: Main Course of Action about Add Item

Alternative course of action:

Step 3: the system does nothing.

Step4: the system displays “fill again” message.
Step5: does not save the entered data.
Step6: the system displays “not added” message.
Main course of action:

About updating the item detail:

Actor action System response

Step1: the stock clerk wants to update the item Step5: the system checks the entered
from the system. information with the existing item deail in the
Step2: he/she login to the system. database
Step3: the stock clerk enters the item type, item Step6: the system sends message “Do you
name, item code to be updated in the update want to update?” to the stock clerk.
form. Step8: the system updates the item from the
Step4: the stock clerk selects the update button. system.
Step7: the stock clerk selects the yes option.
Table 3.6: Main Course of Action about Update Item

18
Alternate course action:
Step5: displays “try again” message.

Basic course action:

About deleting item detail:

Actor action System response

Step 1: the stock clerk wants deletes the item Step 4: the system checks the entered
from the database. item_code with the existing item_code in the
Step 2: the stock clerk enters item_code to the database.
form. Step 5: the system sends confirmation option
Step 3: the stock clerk clicks on delete button. message to the stock clerk.
Step6: the stock clerk selects the yes option. Step 7: the system deletes the item from the
database.
Step 8: the deleting process ends.
Table 3.7: Main Course of Action about Delete Item

Alternative course of action:

Step5: the system displays fill again message to the stock clerk.
Step7: the system ends if he/she selects no.
Name: View Report
UC_ID: UC_04
Actor: Managers
Description: This use case is seen by manager and the stock clerk when they want to view about the item
report, employee report, scheduling report.
Preconditions: The manager and stock clerk login to the system and the staffs and the items are already in
database.
Post conditions: the manager and the stock clerk views a report of some activities based on their task.

19
Main course of action:

Actor action System response

Step 1: the manager wants to view the report. Step3: the system displays the selected report
Step2: The manager selects a report type. automatically.
Step 4: the report process end

Table 3.8: Main Course of Action about View Report

Alternative course action: .

Step2: the system does not display the report.
Name: View Item
UC_ID: UC_05
Actor: Manager, Stock Clerk, Staff Members
Description: This use case is seen by all system users except the Administrator about the item detail.
Preconditions: The users login to the system and the items were already registered.
Post conditions: the staff views all the information that is available.
Main course of action:
Actor action System response
Step 1: the manager, staff or stock clerk wants Step 4: the system validates the item detail.
to see the item detail. Step5: the system displays the item detail.
Step2: they enter the item code. Step 7: the process end
Step3: they click on view item.
Step 6: the staff will see the item information.
Table 3.9: Main Course of Action about View Item

Alternative course action:

Step2: displays please fill the form.
Step5: the system displays a fill again.
Name: Request Item
UC_ID: UC_06
Actor: Staff Members
Description: this process is done by the staff members when they need to request to take or return an item.

20
Preconditions: The staff members have to login to the system and they have to fill the request item form
correctly.
Post conditions: The staff member will sent take or return item request .
Main course of action about taking Item Request:
Actor action System response
Step1: the staff wants to request the item. Step 4: the system validates the item detail.
Step2: the staff member enters the item Step5: the system sends the request.
description (item type, item name, brand, Step6: the process ends.
quantity, model, serial_no etc.) he/she wants.
Step3: the staff member clicks on request
item.
Table 3.10: Main Course of Action about Take Item Request.
Alternative course of action:
Step5: system displays a try again message.
About returning item request:
Actor action System response
Step1: the staff wants to request the item. Step 4: the system validates the item detail.
Step2: the staff member enters the item Step5: the system sends the request to the manager
description (item type, item code, name, brand, and the manager approves the return request.
quantity, model, serial_no and other specifications Step6: the process ends.
based on the item type) he/she want to return.
Step3: the staff member clicks on return
Item request.
Table 3.11: Main Course of Action about Return Item Requesting.
Alternative course of action:
Step4: the system displays try again message.
Name: Receive Response
Actor: Staff Members
UC_ID: UC_07
Description: this use case is done by the staff members when the manager sends a response to them.
Precondition: the staff members have to send a request and the manager is interested to give a
response to them.
21
Post condition: the staff members receive an approval response or disapproval message.

Main course of action:

Actor Action System Response

Step1: the staff members login to the system. Step 3: the system displays the response
Step2: the staff member select the receive information either approval or not; if the response
response menu. is an approval, then the message should contain
Step4: the staff member views the response. an item detail he/she requested and its item code
and the quantity allowed to him/her.
Step5: the process ends.
Table 3.12: Main Course of Action about Receive Response

3.1. Analysis Level of Class Diagram

Diagrams are used to represent the structure of the system in terms of objects, their notes and nature of
relationship between classes. It shows the static features of the objects and do not represent any particular
processing.
Our system has the following classes:
Manager: is the representation of the real world class of manager which interacts with system to accomplish
the managerial activity such as view report, approve request.
Staff members: is the representation of the real world user.
Administrator: is an administrator which uses the automated system to manage users.
Item: it is the representation of the real world class of materials.
Stock clerk: the representation of the real world class which interacts with system to accomplish the activity
such as managing items.

22
Fig 3.2: Class Diagram of our System

3.4. Sequence Diagram

A sequence diagram is a kind of interaction diagram that shows how processes of the proposed system
of inventory management system operate and in what order. It is a construct of a Message Sequence Chart. A

23
sequence diagram shows object interactions arranged in time sequence. It depicts the objects and classes
involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the
functionality of the scenario of the proposed system. Sequence diagrams typically are associated with use case
realization in the logical view of the proposed system under development. The main sequence diagrams of the
new system of inventory management system are listed below.

main window login link login form login controler Database

Login users
UC #01

1:user activate UI()

2:click on login link()

1. all system users
activate the user
interface(UI)
[Link]/select on the
3:Display login form to users()
login link
3. system diisplays
the login form 4:select account type and fill user name and password()
4. select the aaccount
type and fill the user
name and password .
[Link] on submit 5:clik submit()
button. 6:validate()
6. validate the account
information.
[Link] again, 7:try again()
[Link] in 8:login to the system()
9. check 9:Check ()
[Link] response

10:Response to login form()

Fig 3.3: Sequence Diagram of Login

24
 Add new user Add user link New user form User Controller Database
UC#02 Adminstartor

1:click add user()

1. adiminstrator click
add new user 2:display add new user form()
[Link] system displays
new user form
[Link]/she fill new user
information and account 3:fill new user information()
type.
[Link] Adminstraator 4:Click on Add User button()
click on Add user
button 5:validate()
[Link] checks the
validation of input data 6:fill again()
[Link] it is not correct the 7: Added to Database()
system displays fill 8:check()
again and go to new
user foorm 9:Display response to Adminstrator()
[Link] it is correct save the
new user information to
Database
[Link] the user detail
in Database
[Link] system displays a
response

Fig 3.4: Sequence Diagram of Add New User

25
 update user
account UC#02 Update User link update user updated user Database
: Adminstrator
form controler

1. adiminstrator select on
update user link 1:select update user link()
[Link] system displays the
update user form
[Link] adminstrator fills
the user information 2:the system displayys the updaate user form()
[Link]/she click on update
button.
[Link] system validate the
data. 3:fill user detail()
[Link] it is not correct it
displays fill it again.
[Link] he/she fills correctly
the system updates the
4:click on update button()
database
5:validate()
[Link] checks the data
if it is correctly updated
[Link] system displays the
response .
6:fill it again()
7:update the data()

8:check the detail()

9:display responnse()

Fig 3.5: Sequence Diagram of Update User

26
Inactive user
account Inactive User Inactive user Inactive user Database
UC#02 Adminstartor
link form controler

1. adiminstrator select 1:select inactive user link()

to Inactive user link
2:displays the form()
[Link] system displays a
inactive user form 3:fill the user information to be inactive()
[Link] adminstrator fills
the uer detail to be
inactvated
[Link] on inactive user
5. validate the data
[Link] system displays
fill again message.
[Link] inactivates
user from the database.
[Link] system checks if it
is properly inactivated 4:click the inactive user button() 5:validate the data()
or not.
[Link] system displays a 6:fill again()
messag to the form.

7: inactive the user from database()

8:check()

9:display response()

Fig 3.6: Sequence Diagram of Inactive User Account

27
 Add Item
UC#03 Add Item link Add item form Item controler item Database
: Stock Cerk

[Link]/she select Add Item

link. 1:select add item link()
2:the system displaays add
item form.
[Link] item information 2:Display Add Item form()
he/she want to Add and
press Add Item button.
[Link] checks the
validation of input data
[Link] not correct the 3:fill item information()
system displays try again
and go back to add item
form
[Link] it is correct Add the
Item information to 4: the stock clerk click on Add item button()
database
7. the system checks the
item detail in Database 5:fill again()
8:system displays
response

6:Save to Database()
7:check()

8:displays response()

Fig 3.7: Sequence Diagram of Add Item

28
View Report
view Report link Report Type Report controler Database
UC#05 Manager/Stock
Clerk
1:select view report link()
1. the manager select
view Report link
[Link]/sheselect the
Report type.
[Link] on view report.
[Link] system fetch the
data.
5. the sytem displays 2:Manager select the Report type ()
the report to the stock
clerk or manager.
3:Clik on view()

4:fetch ()

5:display report()

Fig 3.8: Sequence Diagram of View Report

29
 Take Item
Request Take Request Take Request Take Request Database
: Staff Member
UC#07 Link Form Controler

1:select request link()

1. the staff member
select Request link
[Link] system displays the
Request from.
[Link]/she fill the Request 2:Display request form()
form
[Link] on Request
button 3:fill the request form()
[Link] the Data
[Link] not correct the
system Displays try
again message. [Link] 4:click on take request button()
the request and save to 5:validate()
database
[Link]
9:display response 6:Try Again()

7:submit the request()

8:check()

9:display response()

Fig 3.9: Sequence Diagram of Request Item

30
 3.2. Activity Diagram
As we have seen, a sequence diagram shows how objects interact over time to accomplish specific
system functions or activity of inventory management system. Activity diagram shows also the conditional
logic for the sequence of system activities needed to accomplish a business process of proposed system in a
good way.

Add new user

UC#02
Actor:Adminstr Login
ator

check
not correct Help to login

Correct

Main Menu
Solved

Select

Add new
user

Enter

New user
information

Submit

Wrong

True Not Solved

Added

Fig 3.10: Activity Diagram of Add New User

31
 Login

manage User
UC#02
Actor:Adminstrator check

not correct Help to login

Correct

Main Menu Solved

Select
update user
enter Select
user detail Manage User
Inactive
user

Check

Try Again
Not Solved

Found Managed

Fig 3.11: Activity Diagram of Manage User

32
 Add Item
UC#03
Actor:Stock Login
Clerk

check
not correct Help to login

Correct

Main Menu
Solved

Select

Add Item

Enter

Item
Information

Submit

not correct

Not Solved
correct

Added

Fig 3.12: Activity Diagram of Add Item

33
 Login

View Report
UC#05 check
Actor:Manager/Stock
Clerk
not correct Help to login

Correct

Main Menu Solved

view Item Report Select

item Report

view Select
Employee Employee View Report
report Report
view User Report
User report

Not Solved
Displayed

Fig 3.13: Activity Diagram of View Report

34
.

Take Request Item

UC#07
Actor:Staff Member Login

check
not correct Help to login

Correct

Main Menu
Solved
Select

Take Request
Form

Enter

Item,user
Not Correct Detail

Request

Not Solved
Correct

Send Item
Request

Fig 3.14: Activity Diagram of Take Request Item

35
 CHAPTER FOUR
4. DESIGN DELIVERABLE OF THE NEW SYSTEM
4.1. Introduction
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.
During system design we concentrate on the process of data structures and soft ware and hard ware
components necessary to implement it.

4.2. Design Class Diagram

Fig 4.1: Design of Class Diagram

36
 4.3. Collaboration Diagram

A collaboration diagram is an illustration of the relationships and interactions among objects in the
unified modeling language.

9: Check ()

2: click on login link()

main login link Data Base
window

1: ser activate UI() 10: Response to login form()

login form

8: step 5 continue()
4: select account type and fill user name and password()

6: validate()
7: try again()
3: Display login form to users()

5: clik submit()
login
controler

user

Fig 4.2: Collaboration Diagram of Login

37
 3: fill new user information() New user
form
2: display add new user form()
Adminstartor

6: fill again()

4: Click on Add User button()

1: click add user()

5: validate()

9: Display response to Adminstrator()

User
Controller

8: check()

7: Added to Database()

Add user Database

link

Fig 4.3: Collaboration Diagram of Add New User

38
 8: check the data()

update user
form Database

9: display responnse()

2: the system displayys the updaate user form()

Update User
link

3: fill user detail()

7: update the data to data base()

1: select update user link()

6: fill it again()

5: validate()

4: click on update button()

updated user
controler

: Adminstrator

Fig 4.4: Collaboration Diagram of Update User Account

39
 8: check()

Inactive user Database

form
9: display response()

2: displays the form()

7: inactive the user from database()

6: fill again()

5: validate the data()

3: fill the user information to be inactive()

Inactive user
controler

4: click the inactive user button()

1: select inactive user link()

Inactive User
link

Adminstartor

Fig 4.5: Collaboration Diagram of Inactive User Account

40
 3: fill item information()
Add item
form
2: Display Add Item form()
: Stock Cerk

1: select add item link()

5: fill again()

8: displays response()
4: the stock clerk click on Add item button()

Add Item
link

7: check()

6: Save to Database()
Item item
controler Database

Fig 4.6: Collaboration Diagram of Add Item

41
 1: select view report link()
view Report link

Manager/Stock
Clerk

5: display report()

3: Clik on view() Database

2: Manager select the Report type ()

4: fetch ()

Report Report
Type controler

Fig 4.7: Collaboration Diagram of View Report

42
 3: fill the request form()
Take Request Form

2: Display request form()

: Staff Member
1: select request link()

Take Request Link

4: click on request button()

9: display response()

6: Try Again()

5: validate() 8: check()

7: submit the request()

Take Request Database
Controler

Fig 4.8: Collaboration Diagram of Request Item

4.4. State Chart Diagram

State chart diagram describes the flow of control of the inventory management proposed system from one
state to another state to describe the system dynamically. States are defined as a condition in which an object
exists and it changes when some event is triggered. So the most important purpose of State chart diagram is to
model life time of an object from creation to termination.
43
 not correct

main click login link fill Login form verify Login

window

Activate

Idle
correct

initial state
Final State

Confirm
Complate State Login

Fig 4.9: State Chart of Login

not correct

loged in select add user fill add user verify add user
link form

main
window correct

Activate
confirm add
Idle Final State
initial state user
complete state

Fig 4.10: State Chart of Add User

44
 not correct

loged in select update fill update item verify update

item link form item

correct

Idle Activate main

window
confirm
Final State update item
initial state
complete state

Fig 4.11: State Chart of Update Item

not correct

main loged in select Delete Item fill Delete Item verify Delete
window link form Item

Activate

correct
Idle
initial state

Final State

Confirm
Complate State Delete Item

Fig 4.12: State Chart of Delete Item

45
 main loged in select view report select report type
window link

Activate

Idle

initial state
confirm view
Final State report
complete state

Fig 4.13: State Chart of View Report

not correct

loged in select view item fill view item verify view item
link form

main
window correct

Activate

confirm view
Idle Final State
initial state item
complete state

Fig 4.14: State Chart of View Item

46
 not correct

loged in select request fill request verify request

item link form

main
window
correct

Activate
confirm
Idle Final State
initial state request
complete state

Fig 4.15: State Chart of Request Item

4.5. Database Design

Database design is a visual representation of different table using agreements that describe how these tables
are related to each other on our proposed system. The proposed inventory systems have the following tables.

47
Fig 4.16: Database Design of the Proposed Inventory Management System

48
 CHAPTER FIVE
5. IMPLEMENTATION DELIVERABLE OF THE NEW SYSTEM
5.1. Introduction
Implementation is an understanding of a technical specification or algorithm as a program, software
component, or other computer system through computer programming and deployment. In our project,
implementation exist for a given specification or standard. So the team is in a position of converting all
documents gathered and designed into the code so that the system will be implemented for the user to be used
for the purpose it developed. To implement it, the organization must have a server on which the system will be
hosted because this system can run on intranet site with connection available or on internet connection.

5.2. Component Diagram

By this Diagram, components of the system will be wired showing that there is relation among
components, management of the system, database and operations performed on databases such security issue.
This in some extent shows which component or objects will be accessed by whom and what type of security
infrastructures it is using. The diagram is displayed below.

Fig 5.1: Component Digram

49
 5.3. Deployment Diagram

Deployment diagrams model the physical architecture of a system, and it shows the relationships
between the software and hardware components in the system and the physical distribution of the processing.

Fig. 5.2: Layer of the System (Deployment Digram)

5.4. User Interface

In this system, users will interact with the system through the following user interfaces.

Home Page: This form appears on the site in which the system deployed is opened and contains some links
which lead the user to other page according to his/her privilege, and if the user is authorized user or has an
account, he/she will directly go to the page that he/she wants by entering correct category, User ID and
password.

50
Fig: 5.3: User Interface Design for Home

Fig 5.4: User Interface Design for Login

51
Fig 5.5: User Interface Design for Add User with Error Message

Fig: 5.6: User Interface Design for Add User

52
Fig 5.7: User Interface Design for Manage User

Fig 5.8: User Interface Design for View Report

53
Fig 5.9: User Interface Design for Report for Free Item

Fig: 5.10: User Interface Design for Clerk’s Approval Page

54
 CHAPTER SIX
6. PROTOTYPE DEVELOPMENT
Prototype development can be defined it is the sample code of the given project. These are some of the
sample codes that we have done it.

//Sample code for Login

<?php
session_start();
include("config/[Link]");
?>
<?php
if(isset($_POST['submitMain']))
{
$account_type=$_POST['acc_type'];
$userid =$_POST['txt_userid'];
$password=$_POST['txt_password'];
$query = "SELECT * FROM users WHERE account_Type = '{$account_type}' AND emp_id = '{$userid}'
AND password = '{$password}' ;";
$result_set=mysql_query($query);
if(!$result_set){
die("query is failed".mysql_error());
}
$row=mysql_fetch_array($result_set);
$stat=$row['status'];
if(mysql_num_rows($result_set)>0)
{
if($stat==1)
{
if($account_type=="Staff")
{
$_SESSION['emp_id']=$row['emp_id'];
echo "<script>[Link]='[Link]';</script>";
}
else if($account_type=="Admin")
{
$_SESSION['emp_id']=$row['emp_id'];
echo "<script>[Link]='[Link]';</script>";
}
else if($account_type=="Manager")
55
{
$_SESSION['emp_id']=$row['emp_id'];
echo "<script>[Link]='[Link]';</script>";
}
else if($account_type=="Clerk")
{
$_SESSION['emp_id']=$row['emp_id'];
echo "<script>[Link]='[Link]';</script>";
}
else
{
echo"Your account is deactivated Please contact the Administrator";
}

}
else
{
echo '<div align="center"><strong><font color="#FF0000"> Account Type, User Name & Password not
match !!</font></Strong></div>';
}
}
mysql_close($conn);
?>
//Sample code for manage user
<?php
session_start();
include("config/[Link]");
//echo "User".$_SESSION['user'];
if(isset($_SESSION['emp_id']))
{
$username=$_SESSION['emp_id'];
} else {
?>
<script>
alert('You Are Not Logged In !! Please Login to access this page');
alert([Link]='[Link]');
</script>
<?php
}
?>
<?php
$result = mysql_query("SELECT * FROM users");
56
while($row = mysql_fetch_array($result))
{
$ctrl = $row['emp_id'];
$account=$row['account_type'];
$emp_id=$row['emp_id'];
$status=$row['status'];
?>
<tr>
<td><?php echo $account;?></td>
<td><?php echo $ctrl;?></td>
<td align = 'center' width = '1'><a href = '[Link]?key=<?php echo $ctrl;?>'><img width='25px'
height='25px' src = 'IMG/[Link]' title='View Detail'></img></a></td>
<td><a href = '[Link]?key=<?php echo $ctrl;?>'><img src = 'IMG/[Link]' width='25px'
height='25px' title='Edit' ></img></a></td>
<td><?php
if(($status)=='0')
{
?>
<a href="[Link]?status=<?php echo $row['emp_id'];?>" onclick="return confirm('Really you activate
(<?php echo $emp_id?>)');">
<img src="IMG/[Link]" id="view" width="16" height="16" alt="" />Deactivated </a>
<?php
}
if(($status)=='1')
{
?>
<a href="[Link]?status=<?php echo $row['emp_id'];?>" onclick="return confirm('Really you De-activate
(<?php echo $emp_id?>)');">
<img src="IMG/[Link]" width="16" id="view" height="16" alt="" />Activated</a>
<?php
}
?>
</td>
</tr>
<?php
}
print( "</table>");
mysql_close($conn);
?>
// sample code of add user
<?php
if(isset($_POST['add']))
57
 {
$rdate=date("d/m/Y");
$sql="insert into users
(account_type,emp_id,password,firstname,lastname,email,Phonenumber,blocknumber,officenumber,regest_dat
e,status )
values('$_POST[acc_type]','$_POST[regusername]','$_POST[regpassword]','$_POST[regfirstname]','$
_POST[reglastname]','$_POST[mail]','$_POST[regphonenumber]','$_POST[regblocknumber]','$_POST[regoff
icenumber]','$rdate','1')";
$result=mysql_query($sql,$conn);// or die(mysql_error());
if(!$result){
print "<h3><img src='IMG/[Link]' width='20px' height='20px'>&nbsp;<font face='arial' color='red'
size='2'>Already Exist!</font></h3>";
}
else{
print "<img src='IMG/[Link]' width='25px' height='25px'><font face='arial' color='green' size='2'>
Successfully registered</font>";
}
}
mysql_close($conn);
?>
// sample code of request
<script language="javascript">
function Clickheretoprint()
{
var disp_setting="toolbar=yes,location=no,directories=yes,menubar=yes,";
disp_setting+="scrollbars=yes,widtd=900, height=400, left=100, top=25";
var content_vlue = [Link]("print_content").innerHTML;
var docprint=[Link]("","",disp_setting);
[Link]();
[Link]('<html><head><title>Lists</title>');
[Link]('</head><body onLoad="[Link]()" style="widtd: 900px; font-size:16px; font-
family:arial;">');
[Link](content_vlue);
[Link]('</body></html>');
[Link]();
[Link]();
}
</script>
<style>
#print_content{
width:434px;
margin:0 auto;
58
}
</style>
<?php
session_start();
include("config/[Link]");
//echo "User".$_SESSION['user'];
if(isset($_SESSION['emp_id']))
{
$username=$_SESSION['emp_id'];
} else {
?>
<script>
alert('You Are Not Logged In !! Please Login to access this page');
alert([Link]='[Link]');
</script>
<?php
}
?>
<?php
$emp_id=$_SESSION['emp_id'];
$result=mysql_query("select * from users where emp_id='$emp_id'")or die(mysql_error);
$row=mysql_fetch_array($result);
$emp_id=$row['emp_id'];
$fname=$row['firstname'];
$lname=$row['lastname'];
$email=$row['email'];
$phone=$row['Phonenumber'];
?>
<?php
if(isset($_POST['sent']))
{ $code=$_POST['code'];
$reason=$_POST['reason'];
$reqdate=date("d/m/Y");
$sql="select * from users where emp_id='$emp_id'";
$re=mysql_query($sql);
while($row=mysql_fetch_array($re)){
$fname=$row['firstname'];
$lname=$row['lastname'];
$emp_id=$row['emp_id'];
$email=$row['email'];
}
$sql=mysql_query("insert into request (firstname,lastname,emp_id,email,item_code,reason,request_date)

59
 values('$fname','$lname','$emp_id','$email','$code','$reason','$reqdate')");
if (!$sql)
{
echo"<img src='IMG/[Link]'>&nbsp;<font color='red'>You already take the item</font>";
echo' <meta content="10;[Link]" http-equiv="refresh" />';
}
else{
echo' <p align="center"><font color="green" size="2"><img width="30px" height="30px"
src="IMG/[Link]">&nbsp;&nbsp;Your Request Information has been Sent successfuly!</font></p>';
$query="SELECT * FROM request where emp_id='{$emp_id}'";
$result=mysql_query($query);
$count=mysql_num_rows($result);
if($count==1){
while($row=mysql_fetch_array($result)){
$fn=$row['firstname'];
$ln=$row['lastname'];
$emp=$row['emp_id'];
$code=$row['item_code'];
$reason=$row['reason'];
}
echo'<a href="javascript:Clickheretoprint()">Print</a>
<div id="print_content">';
echo" Confirmation Detail";
echo'<br>';echo'<br>';
echo"First Name:&nbsp;&nbsp;&nbsp;".$fn."<br>";
echo"Last Name:&nbsp;&nbsp;&nbsp;".$ln."<br>";
echo"Employee Id:&nbsp;&nbsp;&nbsp;".$emp."<br>";
echo"Item code:&nbsp;&nbsp;&nbsp;".$code."<br>";
echo"reason:&nbsp;&nbsp;&nbsp;".$reason."<br>";
$update = mysql_query("update item set status='reserved' WHERE item_code='{$code}'") or
die(mysql_error());
echo' <meta content="20;[Link]" http-equiv="refresh" />';
}
}
}
mysql_close($conn);
?>

60
 CHAPTER SEVEN
7. CONCLUSION AND RECOMMENDATION

7.1. Conclusion
The system that we have developed has two phases; the first phase deals with the analysis phase of
the life cycle with the organization, and the next phase addresses the design phase. As the end of the first
phase, we need to review what we have planned at the beginning. We began our work by identifying the
significance of the new system for the store and the overall techniques to be used in the development process.
This concerned defining the system development methodology, identifying process and resource, and setting
the deliverable and scheduled for the project.

The business area Analysis helps the team to understand the major functional areas and processes of
the proposed system. Through this business area, we identifyed the weakness and strength of the existing
system by developing the proposed system.

After that, we discovered system requirements. Through this phase, we identify functional and non-
functional requirements of the new system. Then we have undertaken a major phase in system development
process: object oriented Analysis. Here, we tried to model the new system we proposed using UML diagrams:
Use case, sequence, and activity and class diagrams. Also, we designed the new system user interface
prototype.

As a result, we proposed the new system to solve the problem of existing system such as time
management and security. And also we developed our capacity during working this new system so that the
manual system changed to computerized system.

7.2. Recommendation
The system that we are trying to develop is not a working online payment system because of limited
development capacity and time. Therefore, we recommend the following features need to be included in any
further revision and extension attempt.

- Integration with other section of the store.

- Online digital signature.
- Online orders of items.
- The system should develop the online payment system for the future.

61
 Appendix
Appendix A: Paper Document in the Exisisting System
I. Get pass for stock
Public body__________________ Date ____________ serial No______________
Reason for dispatching stock________________________

Date Posting Receipt Issue

Reference Qut. Unit Total Qut. Unit Total Qut Unit Total
Price Value Price Value . Price Value

The following goods are authorized to dispatch

Name and Signature of the PAO
Name___________________
Signature _______________

II. Stock record card

Public body_______________ page no__________________
Description of item_________ tem code _________________
Unit__________________ min. level ____________ max. level________________
Shelf no.___________
[Link]. List of Item Unit Quantity Remark

62
 Reference
1. [Link]
2. [Link]
3. [Link]
4. [Link]
5. [Link]
6. [Link]
7. Ambler, Scott (2001) The Object primer: The application Developers Guide to Object Oriented and
the UML.2nd rev. Ed England: The Cambridge University Press.
8. Different Video Tutorials.

63