LAN-Based Store Management System for Wachemo University

WACHEMO UNIVERSITY
COLLEGE OF ENGINEERING AND TECHNOLOGY
SCHOOL OF COMPUTING AND INFORMATICS
DEPARTMENT OF INFORMATION SYSTEMS
Project Title “LAN-Based Store Information Management System For WCU”
Advisor: - Getnet A.
Prepared by Group 8
NAME ID
1. FETIYA KEDIR----------------------------000790
2. ABDISSA BEDADA ----------------------000684
3. BIRTUKAN DESALEGN ----------------000743
4. ALEBACHEWU ABIYE-------------------5431/09
July, 29/2021
Hosanna, Ethiopia
LAN-BASED STORE INFORMATION MANAGEMENT SYSTEM FOR 2021
WCU
Declaration
The project entitled with LAN Based Store Information Management System submitted to the
department for the award of BSC in Information Systems is based on our original work carried
out under the guidance of Instructor Getnet A. The project has not been submitted elsewhere for
award of any degree. The material borrowed from other source and incorporated in the project
has been duly acknowledged and/or referenced. We understand that we ourselves could be held
responsible and accountable for plagiarism, if any, detected later on.
Name of Students Signature Date
1. Fetiya Kedir ____________ ____________

2. Abdissa Bedada ____________ ____________
3. Birtukan Desalegn ____________ ____________
4. Alebachewu Abiye ____________ ____________
Name of the Advisor Signature Date
____________________ ___________________ __________________
Final year project Documentation Page i

WCU
Approval Letter
The Project is our own and original work which has not been presented for a degree program in
any other university. Thus, our signature has duly acknowledged every piece of work that has
carried throughout the whole project.
Name of Students Signature Date
1. Fetiya Kedir ____________ ____________

2. Abdissa Bedada ____________ ____________
3. Birtukan Desalegn ____________ ____________
4. Alebachewu Abiye ____________ ____________
College: College of Engineering and Technology
Program: Information Systems
Project Title: LAN Based Store Information Management System. This is to certify that this
project satisfies all the requirements as a project for the degree of Bachelor of Science.
Name of program coordinator Signature

____________________________ _______________
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope
and quality, as a thesis for the degree of Bachelor of Science.
---------------------------- -------------------------------
Name of Advisor Signature
Examining committee members signature Date
Name Signature Date

1. Examiner 1 ____________ ____________ __________
2. Examiner 2 ____________ ____________ __________
3. Examiner 3 ____________ ____________ __________
It approved that this project has been write in compliance with the formatting rules laid down by
the college of the university
Final year project Documentation Page ii

WCU
Acknowledgment
First of all, we would like to thank our almighty of God, who gives us love, patience, health,
wisdom and the ability to walk through all the problems and obstacles during the period of our
study. Then our special thanks to our advisor Mr. Getnet Assefa for his constructive opinion and
willingness to participate in our project and his effective direction, assistance and guidance for
this project proposal. And for those, the employees in the organization for their approbation of
the information. We thank our friends and for their good wish whose name was not mentioned,
we say our Lord bless you for what you have done to us.
Final year project Documentation Page iii

WCU
List of Abbreviation
ASP.Net---------------------------Active Server Page Network
ASP--------------------------------Active Server Page
C#----------------------------------C-Sharp Programming Language
CD--------------------------------Compact Disk
CSS-------------------------------- cascading style sheet
ERP------------------------------- Enterprise Resource Planning
HTML----------------------------- hypertext markup language
JSP---------------------------------Java Server Page
LAN--------------------------------Local Area Network
LBSIMS---------------------------Lan Based Store Information Management System
MVP------------------------------Market Value Pricing
Mysql------------------------------My structural Query Language
OOA- ---------------------------------object oriented analysis
OOD-------------------------------- object oriented design
OOSD-------------------------------- object oriented system development
PHP-------------------------------- hypertext preprocessor
SDLC------------------------------ software development life cycle
WCU------------------------------Wachemo University
Final year project Documentation Page iv

WCU
Abstract
The store in Wachemo University (WCU) uses manual process system. When customers need to
borrow an item and return the borrowed item they must go to the office and record what they
want manually, this makes the process too late. And also, which requires the employee to use
paper-based recording files to know the status of each customer and to perform the process in
the system. The current manual system encounters problems of checking and registering the
entire list of materials and it consumes a lot of time and it also has difficulties in generating
timely report.
This project aimed to develop LAN Based Store Information management system, is the system
that provides information to efficiently manage the flow of materials, coordinate internal
activities and communicate with customers. It is extremely important for any organization as
they spend their resource and time in controlling the property of the organization. In this
proposal we have planned to solve this problem by using different data collection techniques like
an interview, observation, and documentation review and system development model. The
general objective of this project is to develop a LAN-Based Store Information management
system for Wachemo University. In designing this system, we will use C# programming language
as a development language and MySQL as a backend database. In addition to that due to its
effectiveness in developing a complete system we have planned to use iterative system
development model as system development approach. The application serves both in Amharic
and English. The system is designed in such a way to be accessible via the LAN.
Final year project Documentation Page v

WCU
Contents
Acknowledgment ........................................................................................................................... iii
List of Abbreviation ....................................................................................................................... iv
Abstract ........................................................................................................................................... v
List of Tables ................................................................................................................................. xi
List of Figure................................................................................................................................. xii
Chapter One .................................................................................................................................. 1
Introduction to The System.......................................................................................................... 1
1.1 Introduction .......................................................................................................................... 1
1.2 Background .......................................................................................................................... 2
1.2.1 Background of the Organization .........................................................................................2
1.2.1.1. Vision .................................................................................................................... 3
1.2.1.2. Mission .................................................................................................................. 3
1.2.2. Background of the Project .............................................................................................4
1.3. Statement of the problem ..................................................................................................... 4
1.4. Objectives of the Project ...................................................................................................... 5
1.4.2. General objective ...........................................................................................................5
1.4.3. Specific objective ..........................................................................................................5
1.5. Proposed system................................................................................................................... 6
1.6. Literature Review and Related Work .................................................................................. 7
1.7. Scope and Limitation of the project ................................................................................... 10
1.7.2. Scope of the Project .....................................................................................................10
1.7.3. Limitation of the Project ..............................................................................................10
1.8. Methodology ...................................................................................................................... 10
Final year project Documentation Page vi

WCU
1.8.1. Data Collection Tools/Techniques ..............................................................................10
1.8.2. Data Analysis ..............................................................................................................11
1.8.3. System Development model ........................................................................................12
1.8.4. Implementation of the proposed system ......................................................................13
1.8.5. System development tools (Hardware and Software tools) ........................................15
1.9. Significance of the Study ................................................................................................... 16
1.10. Beneficiaries of the System ............................................................................................ 17
1.11. Feasibility Study............................................................................................................. 17
1.11.1. Technical Feasibility ...................................................................................................17
1.11.2. Operational Feasibility ................................................................................................18
1.11.3. Economic Feasibility ...................................................................................................18
1.11.4. Legal feasibility ...........................................................................................................19
1.11.5. Time feasibility............................................................................................................19
1.12. Project Organization ....................................................................................................... 19
1.13. Project Plan .................................................................................................................... 20
1.13.1. Time Schedule .............................................................................................................20
1.13.2. Budget Plan .................................................................................................................20
Chapter -Two- ............................................................................................................................. 22
Description of The Existing System or Application ................................................................. 22
2.1. Introduction ........................................................................................................................ 22
2.2. Business Rule and Constraint ............................................................................................ 22
2.2.1. Business Rule of Existing System ...................................................................................23
2.2.2. Constraint .........................................................................................................................24
2.3. Naming Convention and Definition ....................................................................................... 24
2.4 Function or Main Activities of Existing System..................................................................... 25
Final year project Documentation Page vii

WCU
2.6 Organizational Structure ......................................................................................................... 26
2.7. Documents used in the Existing System ................................................................................ 26
2.8. Strength and Weakness of the Existing System ..................................................................... 32
2.8.1 Strength of the Existing System or Application................................................................32
2.8.2 Weakness of the Existing System or Application .............................................................32
2.8.3. Alternative Solutions .......................................................................................................... 34
Chapter Three ............................................................................................................................. 35
Requirement Specification and Analysis .................................................................................. 35
3.1. Introduction ............................................................................................................................ 35
3.2. Description of the Proposed System or Applications ............................................................ 35
3.2.1 User Characteristics ..........................................................................................................36
3.2.2 Constraints ........................................................................................................................36
3.2.3 Assumptions and Dependencies........................................................................................36
3.3. Requirement Specifications ................................................................................................... 37
3.3.1 Functional Requirement ....................................................................................................37
3.3.2 Non-functional Requirement.............................................................................................39
3.4. System Modeling ................................................................................................................... 41
3.4.1. Actor Identification ..........................................................................................................42
3.4.2. Use-Case Identification ...................................................................................................42
3.4.3. Use-Case Diagram ...........................................................................................................43
3.4.4. Description of Use-Case ..................................................................................................44
3.5. Requirement Analysis ............................................................................................................ 61
3.5.1. Activity Diagram..............................................................................................................61
3.5.2. Sequence Diagram .............................................................................................................. 75
Chapter -Four- ............................................................................................................................ 81
Final year project Documentation Page viii

WCU
System Design .............................................................................................................................. 81
4.1. Introduction ........................................................................................................................ 81
4.2. Class Diagram .................................................................................................................... 81
4.3. Database Model ................................................................................................................. 84
4.3.1 Entity Relationship Diagram (ERD) ...........................................................................84
4.3.2 Persistence Modeling ..................................................................................................86
4.3.3 Mapping with Normalization ......................................................................................89
4.4. Subsystem Decomposition ................................................................................................. 96
4.5. Deployment Diagram ......................................................................................................... 98
4.6. System Architecture (Layered Architecture of the System) .............................................. 99
4.7. User-Interface (UI) Design .............................................................................................. 101
4.8. UI Flow Diagramming ..................................................................................................... 105
CHAPTER-5- ............................................................................................................................ 107
IMPLEMENTATION AND TESTING .................................................................................. 107
5.1 Introduction ...................................................................................................................... 107
5.2 Algorithm Design............................................................................................................. 107
5.3 Sample Code .................................................................................................................... 108
5.4 Testing................................................................................................................................... 121
5.4.1 Unit Testing.....................................................................................................................121
5.4.2 Integration Testing ..........................................................................................................122
5.4.3 System Testing ................................................................................................................123
5.5 User-Manual ......................................................................................................................... 123
5.6 User Training ........................................................................................................................ 126
5.7 Start-Up ................................................................................................................................. 126
CHAPTER SIX ......................................................................................................................... 128
Final year project Documentation Page ix

WCU
Conclusion and Recommendations ......................................................................................... 128
6.1. Conclusion ........................................................................................................................... 128
6.2 Recommendation .................................................................................................................. 128
References ................................................................................................................................... 129
Appendix ..................................................................................................................................... 130
Final year project Documentation Page x

WCU
List of Tables
Table 1: Software tools ................................................................................................................. 15
Table 2: Hardware tools ................................................................................................................ 16
Table 3: Time schedule table ........................................................................................................ 20
Table 4: Budget plan table ............................................................................................................ 21
Table 5: Login use case description .............................................................................................. 47
Table 6: Logout Use case Description .......................................................................................... 47
Table 7: Create account use case description ............................................................................... 48
Table 8: Update account use case description .............................................................................. 49
Table 9: Post notification use case description ............................................................................. 50
Table 10: Register Item use case description ................................................................................ 51
Table 11: Edit item use case description....................................................................................... 52
Table 12: Search item use case description .................................................................................. 53
Table 13: Register Stock card use case description ...................................................................... 54
Table 14: Register user card use case description ........................................................................ 55
Table 15: Request item use case description ................................................................................ 56
Table 16: Edit request use case description .................................................................................. 58
Table 17: Give comment use case description .............................................................................. 58
Table 18: Generate report use case description ............................................................................ 59
Table 19: View report use case description .................................................................................. 60
Table 20: Transfer asset use case description ............................................................................... 61
Table 21: Persistence Modelling ................................................................................................... 89
Table 22: Table for 1NF ............................................................................................................... 94
Final year project Documentation Page xi

WCU
List of Figure
Figure 1: Iterative development process ....................................................................................... 12
Figure 2: Organizational Structure of WCU ................................................................................. 26
Figure 3: Receipt for article or property received ......................................................................... 27
Figure 4: Item request form .......................................................................................................... 28
Figure 5: Receipt for article of property issued ............................................................................ 29
Figure 6: Stock card ...................................................................................................................... 30
Figure 7: Bin Card ........................................................................................................................ 31
Figure 8: User Card ....................................................................................................................... 31
Figure 9: Asset transfer form ........................................................................................................ 32
Figure 10: Use case diagram ......................................................................................................... 44
Figure 11: Activity diagram for Login.......................................................................................... 62
Figure 12: Activity Diagram for create account ........................................................................... 63
Figure 13: Activity diagram for Deactivate account..................................................................... 63
Figure 14:Activity Diagram for Update Account ......................................................................... 64
Figure 15: Activity diagram for Post notification ......................................................................... 64
Figure 16: Activity diagram for View Notification ...................................................................... 65
Figure 17: Activity diagram for Register item information .......................................................... 65
Figure 18: Activity diagram for update item information ............................................................ 66
Figure 19: Activity diagram for view comment ........................................................................... 66
Figure 20: Activity diagram for Stock clerk Generate report ....................................................... 67
Figure 21: Activity diagram for view report ................................................................................. 67
Figure 22: Activity diagram for search item ................................................................................. 68
Figure 23: Activity diagram for request item ............................................................................... 69
Figure 24: Activity diagram for Register Stock card .................................................................... 69
Figure 25: Activity diagram for Register User card ..................................................................... 69
Figure 26: Activity diagram for Approve request......................................................................... 70
Figure 27: Activity diagram for Register Bin Card ...................................................................... 71
Figure 28: Activity diagram for update Request........................................................................... 71
Final year project Documentation Page xii
WCU
Figure 29: Activity diagram for cancel request ............................................................................ 72

Figure 30: Activity diagram for give comment ............................................................................ 73
Figure 31: Activity diagram for Transfer asset ............................................................................. 73
Figure 32: Activity diagram for Remove item information .......................................................... 74
Figure 33: Activity diagram for Logout........................................................................................ 74
Figure 34: Sequence diagram for Login ...................................................................................... 75
Figure 35: Sequence diagram for Register Item ........................................................................... 76
Figure 36:Sequence diagram for Give Comment ......................................................................... 76
Figure 37: Sequence diagram for Asset Transfer ......................................................................... 77
Figure 38: Sequence diagram for Create Account ........................................................................ 78
Figure 39: Sequence diagram for Update Request ....................................................................... 78
Figure 40: Sequence diagram for Request Item ............................................................................ 78
Figure 41: Sequence diagram for Edit item .................................................................................. 79
Figure 42: Sequence diagram for view report............................................................................... 80
Figure 43: Sequence diagram for search Item .............................................................................. 80
Figure 44: Class Diagram ............................................................................................................. 83
Figure 45: Entity relationship diagram ......................................................................................... 85
Figure 46: Persistent diagram ....................................................................................................... 86
Figure 47: Subsystem decomposition diagram ............................................................................. 98
Figure 48: Deployment diagram ................................................................................................... 99
Figure 49: System Architecture .................................................................................................. 100
Figure 50: User interface design for Home page ........................................................................ 101
Figure 51: User interface for Service .......................................................................................... 102
Figure 52: User interface for Comment ...................................................................................... 103
Figure 53: User interface design for Login ................................................................................. 104
Figure 54: User interface for Register stock card ....................................................................... 104
Figure 55: User interface For the Amharic service section sample ............................................ 105
Figure 56: User interface flow diagram ...................................................................................... 106
Figure 57: Unit testing for login page ......................................................................................... 122
Figure 58: User manual for login page ....................................................................................... 124
Final year project Documentation Page xiii

WCU
Figure 59: user manual for request item form ............................................................................ 125
Figure 60: User manual for transfer assets form ......................................................................... 125
Figure 61:User manual Report print ........................................................................................... 126
Figure 62: User manual for view item detail .............................................................................. 126
Figure 63: User manual for accept transfer................................................................................. 126
Final year project Documentation Page xiv

WCU
Chapter One
Introduction to The System
1.1 Introduction
Store is an important component of material management since it is a place that keeps the
materials in a way by which the materials are well accounted for, are maintained safe, and are
available at the time of requirement. Storage is an essential and most vital part of the economic
cycle and store management is a specialized function, which can contribute significantly to the
overall efficiency and effectiveness of the materials function. Literally store refers to the place
where materials are kept under custody. Typically, a store has a few processes and a space for
storage. The main processes of store are
 To receive the incoming materials (receiving),

 To keep the materials as long as they are required for use (keeping in custody), and
 To move them out of store for use (issuing).
The auxiliary process of store is the stock control also known as inventory control. In a
manufacturing organization, this process of receiving, keeping in custody, and issuing forms a
cyclic process which runs on a continuous basis. The organizational set up of the store depends
upon the requirements of the organization and is to be tailor made to meet the specific needs of
the organization. (satyendra, 2015)
The store in Wachemo University (WCU) is giving an important service for its community
which is found in that Institute. The properties of the store are acquired from donation or supplier
with appropriate procurement these properties are distributed based on formal request forms. The
current system gives vast service however it uses manual management system which leads the
system to be inefficient. As part of the effort to bring efficient and modern store management
system in WCU, the new system should be designed and implemented that enables properties to
be controlled and managed properly.
LAN stands for “Local Area Network”. LAN is a computer network that interconnects computers
within a limited area such as home, school, computer laboratory, or office building, using network
Final year project Documentation Page 1

WCU
media. Computer technologies and devices are increasingly being introduced into offices to
enhance the working experience. Most mid to large-sized businesses today use LANs, which
makes it easy for employees to share information. LAN is useful for sharing resources like file
printers, games or other applications. Most LANs connect workstations and personal computers
and enable users to access data and devices, example printers and modems, anywhere on the
network. Due to the continuing change in environment and demand for technological
advancements increased, people tend to use technologies that would help them do their work easier
and faster. (Melendres, 2021,January)
In this project, we come up with an idea of creating an automated LAN Based Store Information
management system using C# programming language and MySQL databases.
1.2 Background
1.2.1 Background of the Organization

Wachemo University (WCU) is one of the public higher educational institutions, which was
found in 2009 G.C. It is located 230 km southwest of Addis Ababa, at Hosanna town in the area
of over 200 hectares. (wcu.edu.et, 2021)
The University commenced its function in 2012 admitting 538 students in 12 departments under
4 colleges. Currently, the University has admitted over 18,400 students in regular and continuing
education programs in 48 departments under 6 Colleges, namely (wcu.edu.et, 2021)
 Engineering and Technology,

 Natural and Computational Sciences,
 Medicine and Health Sciences,
 Agricultural Sciences,
 Business and Economics, and
 Social Sciences and Humanities.
In addition to these, the university is going to launch 10 new programs in undergraduate level
and 6 programs at MSc level in the next academic year The University has 957 academic staff
(from these 36 are expatriate academic staff) 39 technical support staffs and 808 administrative

WCU
support staff totaling 1029. In terms of the profile of the full time academic staff, 4(0.72%) are
PhD holders, 258(47%) are MSc/MA holders and 133(24%) are BSc/BA holders. In addition,
159 (117 for MSc/MA, 42 for PhD) academic staff are on study leave. In other words, the
percentage proportion of teaching staffs with PhD, Msc and Bsc are 1:55:24 percent respectively.
However, by 2020, the University has set a target to increase this to 30:70:0 percent.
Furthermore, the university has launched its branch campus at Durame town (Kambata Tambaro
Zone) about 60Km away from the Main campus, Hosanna. From On the top of that the university
has one teaching hospital: Nigist Eleni Muhamad General Hospital which is found at Hossana
town. (wcu.edu.et, 2021)
Finally, all the community members of WCU with their profundity and commitment are playing
immense role to achieve the national growth and transformation plan (GTP) via the university’s
vision, mission and goals. The University has been working hard in teaching, research and
community services for the last five years. It has been awarded the prize of “Best achieving
University” for three successive years, from 2013-15 academic years, among the newly
established third generation Universities of Ethiopia. (wcu.edu.et, 2021)
1.2.1.1.Vision
Aspires to Become one of the First-Class Universities in Ethiopia and Home of Brilliants by
2017 E.C. (wcu.edu.et, 2021)
1.2.1.2.Mission
Wachemo University is committed to provide quality education and training to produce educated
human power who attain fullest potential intellectually, ethically, morally, socially, and equip
them with critical and imaginative skills to face the real life challenges and play an active role in
the development of the country to transform the innovation, discovery, and communication, and
application of knowledge, through research based activities in a wide range of academic and
professional fields for the highest economic development of the citizens in Ethiopia. (wcu.edu.et,
2021)
In order to achieve this mission and vision of Wachemo university changing the way of Store
management which uses the manual system into a computerized system plays a great role which

WCU
will be done in our project. The Wachemo University store office is the backbone of the
University by managing any activities related to materials available in the University.
1.2.2. Background of the Project

The proposed system will enable a chain of stores to coordinate with their supplier to facilitate
on time supply and to maintain updated information about available stocks at each store. Store is
the physical place where many varieties of materials are kept for the purpose of capital work. In
Wachemo University there are around three stores section, this is fixed asset store, Non fixed
asset store and Durable asset store, the main function of stores is to receive, store and issue
materials.
Our proposed LAN-Based store Information Management system that attempts to replace the
manual system has the following nature.
The system can record any new item issue requested items with appropriate specification
and category.
The system generates a unique ID for each new fixed asset which is added to the
database.
The system can enable to search items that are available in the store house and use.
It shortens the step-by-step processes in delivering or returning items.
It generates up to date report at any time for decision makers for budget allocation and
controlling.
The proposed system allows to access the system in Amharic and English Language.
1.3. Statement of the problem

Store Information management system can have a great impact on the growth of an organization.
In Wachemo university the existing system uses manuals to keep the record of the items in the
store, which results in poor techniques handling the inventory of all the properties of the
University and very time consuming and tedious. Other major problems of the existing system
include:

WCU
 Loss of Items and materials record files: - when items and materials are enter to the store,
the storekeeper records the items and materials on paper. Due to this problem records of
items and materials are lost and expose the store for data loss. This problem not only
affects the store but also affect the work system of the organization.
 Searching an item is very complex as there could be thousands of entries every year.
 Registering materials is manual and not well organized. This will result in poor
techniques handling in arrangement related data.
 It needs more human power to facilitate all the necessary workflows.
 It is not easy to handle arrangement, because the store keeper is forced to check manually
the entire list of materials which are stored in the store.
 Since all records kept physically on shelves and file cabinets the store record subjects to a
number of problems 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.
 Performance is also another problem since a customer has to wait in line while another
customer is being served. Difficult to manage and control daily activities.
1.4. Objectives of the Project
1.4.2. General objective

The general objective of this project is to develop a LAN-Based Store information management
system for Wachemo University.
1.4.3. Specific objective

To achieve the above-described general objective, the project addressed the following specific
objectives. That includes the following specific activities:
 To gather a requirement related to our project.

 To analyze the gathered requirement
 To Make literature Reviewing to understand how others have approached or dealt with
the problem Analysis of existing system operation and procedure.

WCU
 To Design components of the LAN-Based Store Information management system and

database.
 To implement the designed system
 To Test the system.
 To evaluate the system.
 To deploy the system.
 To train and support the user of the system.
1.5. Proposed system

The project is a LAN-based system which is useful for developing paperless work and to have an
improved technique for monitoring the activities of the store employees within that organization.
The proposed system is designed to solve problems in related to the existing system. The
proposed system resolves the drawbacks of the Existing system by developing an automated,
user-friendly and interactive system. The proposed system Manage time effectively which means
it minimize the wastage of time with the aid of computer system.
The other main aim of the proposed system is to make the store item related data / information to
become error-free by avoid data redundancy or duplication. It also supports in utilizing available
resources effectively by minimizing the usage of any writing material like Paper, pen and any
other material that helps to write report, and to create efficient way of data management by using
database system so that there will not be anyway of losing data.
In this project the proposed system is enable University members: -
 To request for any item using this system

 To request for clearance from store
 To get any new information in related to universities store.
 To know items available in the university store.
 To access the system in Amharic and English Language.
 We will develop a database system that used to record items and materials to solve the
problem.

WCU
 The system provides information connection between the storekeeper and the administrator
in order to improve communication.
 The system shows the expired date of the item and the storekeeper does not get difficulty.
1.6. Literature Review and Related Work

According to Sabbu Book store management system: The project report consists of 2
phases. In the first phase, the problem assigned to us has been mentioned. Second phase provides
the solution for the same problem along with an insight into the development process involved.
The Bookshop Automation System is to automate all operations in a bookshop. Generally, it
includes the Order Processing, Stock Management and Accounts Management. This Bookshop
Automation System is an attempt to overcome the present inefficient and time-consuming
process of locating, reserving and purchasing quality reading materials available in the store.
Currently, clients have to go through a time-consuming process to perform aforementioned tasks
which cause waste of labor and firms’ resources. Through this automated book store solution,
they provide an easy way of searching, reserving and purchasing of books. User data are
validated and checked for authenticity with the data stored in the system database. All the newly
coined processes will address time consuming, ineffective and inefficient areas of the existing
system which has being wasting a lot of firms’ resources such as, labor, electricity, equipment,
products and services, while discouraging customers to make purchases and repelling clients
from the book store. (Sabbu, 2013,Apr)
A web application is a computer program that utilizes web browsers and web technology
to perform tasks over the Internet. Millions of businesses use the Internet as a cost-effective
communications channel. It lets them exchange information with their target market and make
fast, secure transactions. However, effective engagement is only possible when the business is
able to capture and store all the necessary data, and have a means of processing this information
and presenting the results to the user. Web applications use a combination of server-side scripts
(PHP and ASP) to handle the storage and retrieval of the information, and client-side scripts
(JavaScript and HTML) to present information to users. This allows users to interact with the
company using online forms, content management systems, shopping carts and more. In
addition, the applications allow employees to create documents, share information, collaborate

WCU
on projects, and work on common documents regardless of location or device. Web applications
are usually coded in browser-supported language such as JavaScript and HTML as these
languages rely on the browser to render the program executable. Some of the applications are
dynamic, requiring server-side processing. Others are completely static with no processing
required at the server. The web application requires a web server to manage requests from the
client, an application server to perform the tasks requested, and, sometimes, a database to store
the information. Application server technology ranges from ASP.NET, ASP and ColdFusion, to
PHP and JSP. (Gibb, 2016)
According to Punam Khobragade Inventory management system the motivation of

this paper is to create Inventory Management System is software which is helpful for the
businesses operate hardware stores, where storeowner keeps the records of sales and purchase.
Mismanaged inventory means disappointed customers, too much cash tied up in warehouses and
slower sales. This project eliminates the paper work, human faults, manual delay and speed up
process. Inventory Management System will have the ability to track sales and available
inventory, tells a storeowner when it's time to reorder and how much to purchase. Inventory
Management System is a windows application developed for Windows operating systems which
focused in the area of Inventory control and generates the various required reports. Finally, this
journal paper presents an alarm about the information section in the bill which in view of desktop
application. It's a straightforward desktop application in which the network to the immediate
distribution center with the goal that information ought to be refreshed in store for the
confirmation. It's a secure application in which no information spillage from the stockroom. And
furthermore, gives the one table organization look so that after the finish of month it allows to
know about what is sold. (Punam Khobragade, Apr 2018)
Efficient stores management - a case study on Takoradi polytechnic stores

department: The aim of the study is to find out the efficiency of stores department to reduce
financial losses with particular reference Takoradi Polytechnic. It will also help potential
entrepreneurs to be informed of what is at stake in businesses as far as stock management is
concern. The study will reduce the incidence of financial losses characterized by inefficient
stores management. To achieve their goal, they use a method that is an effective, efficient
techniques and research instrument have been employed. The researcher identified the
WCU
inefficiency of stores management in Takoradi Polytechnic as a problem. The problem was

investigated at the stores department Takoradi Polytechnic by collecting data with the use of
questionnaires. The data were analyzed and recommendations were made after findings. Finally
they conclude as a result that Takoradi Polytechnic stores department does practice a fairly
efficient stores system in avoiding financial losses, the stores department does not communicate
to purchasing department their reorder levels thus holding large stocks and inventories,
management must consider fixing close circuit television (cctv), within the stores/warehouse
department, internal audit department must put measures such as continuous and spot checking,
to ensure accurate quantities of product in the stores. (Bainson, February,2016)
According to Sushil Kumar and Rajeev Sunam Stores Management for

Implementing ERP in Manufacturing Organization The paper describes the importance of
ERP in manufacturing industries and examines the various articles published by eminent
Researchers in the field of ERP. Enterprise Resource Planning (ERP) software presents a frame
work for organizations to better utilize their processes. The report is about windows-based
application. The main idea of this paper is to handle the all details of stores management system.
In this project software package has been developed to smoothen the processing of item
transaction in stores such as item receive, item issue & report generation such as stock statement,
issue register & receive register etc. This Software will help in automating all the process like
receiving and issuing application in stores. Result provides the easy, fast and accurate system for
issuing, receiving & and Report generation of the item transaction in the stores. Main user
interface of store management is: (a) User Authentication: User authentication is a means of
identifying the user and verifying that the user is allowed to access some restricted service. The
server administrator needs to be able to control access on an individual basis; it is possible to
require a username and password before being allowed access to a document. This is called user
authentication. Finally, they conclude this it provides the easy, fast, accurate and efficient system
for the user. In this system the record of each request details is preserved along with their
transaction related to them. The system is also made secured as all the updating and transaction
can be done by the authorized person. The main purpose of this project is to give all details about
the Items transaction in the stores such as, Item issuing, Items receiving, & Report generation

WCU
about the stock statement, Issue Register, & receive register were successfully developed. (Sushil
Kumar and Rajeev Sunam, 2014)
1.7. Scope and Limitation of the project
1.7.2. Scope of the Project

Since Wachemo university Store information management performs its basic tasks manually the
scope of this project is to develop and implement a new interactive LAN-based store information
management system which will avoid the problems associated with manual processing and will
perform the following activities:
 To request an item through LAN.

 Record items with their detail information
 To generate a report.
 To add users and items.
 To search for items.
 Transferring an item between users.
 To give notification to customers.
 To manage item information
 To access the system in Amharic and English Language.
1.7.3. Limitation of the Project

o It does not relate to the purchase of items.
o It does not relate to the delivery of items for its customers.
o Our system does not include the management of WCU clinic store items
1.8. Methodology
1.8.1. Data Collection Tools/Techniques

Different fact-finding techniques were used to gather information about the current system. It is
the fundamental activity for the development of the system. Without them, data modeling cannot

WCU
be constructed. In order to know how the existing system work and what problem are there, we
will use the following fact-finding techniques.
Interview: To get the basic information about the existing Store management system, the
team will interview the Property Administrator Head, Stock clerk, store keeper and some
customers about the services that are given to them and the problems associated with that
environment. The type of interview that we use is behavioral interview to know how they
perform their work.
Observation: After we finished the interview, we used the other methodology of data
collection that is called practical observation. During this time, we directly enter into the
internal activities of the store to view what things are done? And what are the limitations
and strengths of the existing system? The essentiality of this method is that, to be
confident with the data that we collected using an interview.
Document analysis: - To get more information about the Store management we tried to
refer some documents related to the store.
1.8.2. Data Analysis

The team plan to use the object-oriented design methodology for the development of the system
among the different methodologies. Because it is better way to construct, manage and assemble
objects that are implemented in our system. Object oriented design methodology has two phases:
Object Oriented Analysis (OOA): During this phase the team will look at the problem domain
and with the aim of producing a conceptual model of the information that exists in the area
which will be analyzed. And this model the functions of the system (use case modeling),
identifying the business objects, organize the objects and also the relationship between them and
finally model the behavior of the objects.
Object Oriented Design (OOD): During this phase, our team will use Visio 2013 software to
refine the use case model and for designing the sequence, class diagram, state chart diagram, and
activity diagrams and to model object interactions and behavior that support the use case
scenario. This system analysis and design have many benefits:
 Increase Extensibility: - When we to need to add new feature to the system we only need
to make changes in one part of the applicable class.

WCU
 Increase Reusability: - The object oriented provides opportunities for reuse through the
concepts of inheritance, polymorphism, encapsulation and modularity.
 Improve Quality: - Quality of our system must be on time, on budget and meet our
exceeded the expectation of the users of our system, improved quality comes from
increased participation of users in the system development.
 Minimize maintenance costs: - Software organizations currently spend significant
resources maintain operating system so the object-oriented development methods help us
to overcome this problem.
 Minimize complexity: - The object-oriented methods solve our system complexity in the
following way, by design our system software expectation that it will need to be modified
and being able to respond quickly when our system environment changed.
1.8.3. System Development model

We will use the Iterative model in our project Because it used in our system to build the system
incrementally, starting from basic partial system features and gradually adding more features
until the entire system is completed. It allows us flexibility in accommodating new requirements
or changes. In the iterative model, we are building and improving the product step by step. Our
proposed system needs to consider unit testing and system testing, for this reason; iterative is
selected for our system.
Figure 1: Iterative development process

The reason behind iterative model
 Risk reduction. Issues are identified and resolved during iterations.

WCU
 Flexibility to modifications. If at a certain stage you understand that a particular function

has become a priority, you can start implementing it in the next iteration without waiting
for the entire project to be finished.
 Regular release of new versions. Using the iterative development approach, new versions
are released regularly and the project is constantly advancing.
 Efficient feedback. Development teams actively communicate with customers, creating a
product that meets their needs and business goals.
 Prompt release of MVP. This model allows bringing the product to the market and
starting its use much earlier than in the case of a waterfall model.
 Higher quality. An iterative approach allows for creating a more robust architecture since
all errors are fixed during several iterations.
1.8.4. Implementation of the proposed system

The implementation document helps users on how to work with the system. It acts as a user
manual and it helps users not to be the system confused with. It includes sample forms and some
selected fragment code. It gives users a brief overview of the system.
The project implements php programming language, MySQL database. The project would be
capable of running on any operating system as it is a web application. The interface for the
project would provide good navigation to the user of the system with a nice look and feel.
One we have completed our system development we have planned to test its efficiency in
different testing mechanisms. Testing is a process to show the correctness of the program. It will
be the final phase after system implementation. The system can be tested in two ways.
o Nonfunctional requirements fulfillment: means the performance, response time, look

and feel, user interface simplicity, navigation, language usage in messaging, resource
usage, etc.
o Functional requirements fulfillment: means the functionality performed here in the
system are as required or not.
System testing

WCU
In this level of the testing process, we will have examined how the whole store management
subsystems came together to achieve the desired goal (user’s requirements of the system). The
goals of system testing are to detect faults that can only be exposed by testing the entire
integrated system or some major part of it. Sample Tests we will do:
 Evaluate the functionality of the subsystem after a combination of individual subsystems

whether it works correctly or not.
 Check the coherence and coupling of each subsystem.
 Check the interaction of each subsystem that performs the specified business process.
 Verify the store management system completeness-based user’s requirement.
Unit-testing
Unit testing, we planned to test this project, an individual module or component like for login to
the system, create account and register item to ensure that it works according to its
predetermined specifications, operates within acceptable parameters. In this level of testing
process Sample Tests that we will do:
 Check whether the return type of functions is correct.

 Check how the sub-procedures or functions are called correctly.
 Check if the correct output is produced for different inputs.
Integration testing
In this level of testing, we will examine how the different procedures work together to achieve
the goal of the subsystem. We will test the module transfer item, request item to ensure their
fulfillment of the subsystem functionality. Then we integrate each component from single
functionality (individual interface) to the main function incrementally.
Sample Tests we will do:
 Check the interaction between individual functionality which performs the specific tasks.
 Evaluate the functionality of the subsystem after combination all individual functionality.
 Identify the Independence of each subsystem with other subsystems.

WCU
1.8.5. System development tools (Hardware and Software tools)

The proposed system will be developed using the following development tools:-
Software tools:
Is software which installed on a computer for a different purpose from documentation up to the
implementation. The list of main software tools that we will use are listed as follow:-
Software Tools Description

Microsoft Word 2010 For documenting the corresponding
deliverables associated with the project.
Microsoft Visio 2013 For designing unified modeling language
(UML) diagrams.
Sublime text-4 Used to write at the front end because it has a
powerful programming language and has a lot
of tools to design easy to use user interface.
MySQL For database at the back end since it is
powerful database management system
software and easily integrated with vb.net.
Microsoft power point Used to present the document in abstract
forms. We would use it to present our
presentation in short and brief way.
Table 1: Software tools
Hardware Tools: - Different hardware tools will be used to develop our project.
Hardware Tools Description

Computer (desktop and laptop) For documentation and implementation.
Flash disk and CD Used for the movement of data from one
machine to another. For backup.
Printer For printing documentation

WCU
Table 2: Hardware tools
The reason behind PHP:

 Ease of database connectivity.
 PHP is platform-independent.
 It is a user-friendly language.
 Open-source general-purpose scripting languages that are especially suited for web
development and can be embedded into HTML
We can also use HTML, CSS and JavaScript for Front end design.
Why MySQL?
 There are several reasons to use MySQL.

 It’s quick and powerful
 It’s improving all the time
 It’s free
1.9. Significance of the Study

The significances of this project are:
 The system will enhance the service offered by the store office.
 Avoiding wastage of storekeepers and head offices time in searching, registering and
calculating materials for report.
 Avoiding data loss because of improper data storage: in manual system case the store
keepers store their data on paper and in case of this the papers may be lost due to some
problem. The proposed system keeps the data in server even if the server is lost due to
some reason, we have the backup of it.
 Avoiding improper item allocation: In manual case we waste most of our time in
searching location of objects but in automated system there is a proper location of
materials for store keepers.
 Avoid lack of communication: In manual system communication between storekeeper
and store manager and store manager and college heads is very slow since they will go

WCU
from one place to other, in this automated system since the proposed system is networked
it will speed up communication between them.
 Reduce the clerical labor of the staff working in Stores both technical and as well as
Accounts departments using the latest technologies and cost-effective tools there by
providing the better control to the management by avoiding manual errors etc.
Generally, the significance of our project is: accurate, timeliness, reliable, secured, relevant and
valuable data are needed for store management in all dimensions.
1.10. Beneficiaries of the System

First, Wachemo university Store management sector is most benefited from the system because it
creates an easy atmosphere to manage and control store.
Secondly, the customers are benefited since they save their time, energy and can simply order
items of their choice online just by visiting the site with their respective accounts.
The other benefited party is the Wachemo university itself because it simplifies the overall
management using the involvement of the Technology system.
1.11. Feasibility Study

It used to test the system according to its work ability, impact of the organization, ability to meet
Needs and effective use of the resources.
1.11.1. Technical Feasibility

This project will be easily maintainable and developed by using currently existing technology
such as hardware, software compatibility, and programming language. The system which we
have developed would be technically feasible. The new system does not require new professional
person that process the implemented system, because the system does not need many employees
which need special computer skill. The system can be operated in simple way and all users can
access it easily by giving some training for them. So, the system will be technically feasible.

WCU
1.11.2. Operational Feasibility

The system which we are developed would be operationally feasible. Since the design is very
easy to everybody to interact with the system it will not have any operational problem. It will
minimize the amount of effort to do all through manually.
1.11.3. Economic Feasibility

The organization will lose money and time since the system is manual. So, if our proposed
system is implemented unwise use of resource as well as time is saved. In manual System store
management if we take the materials that are expired in a year from the whole three stores, they
lose around 10000 birrs in a year. From this 30% is lose because of unknown materials expire
date, 50% lose by misuse of materials and 20% lose because of materials order in their
inappropriate place also when we calculate the time it takes for the manual record of received
material on stock card and give materials for requested on bin card it takes more day for one
person to complete but in our proposed system it will take around 1 hours and minimize around
800birr paid for one person in a month that are used for papers, pen.
Generally, the system that we are going to develop, LAN Based Store Information Management
System brought a number of tangible and intangible benefits.
Tangible benefits:
 Cost Reduction: It reduces the cost that uses for item when the item is lost by managing
the items efficiently.
 Error Reduction: In our proposed system information about store is well organized, so
this reduces the error in loss of information.
 Increase Speed of activity: Our proposed system speed up the work environment of the
sector. by making the process automate
Intangible benefits:
 Reduce Resource Consumption: It reduces the cost that uses for pen and paper cost to
fulfill different forms.
 Increase security:
 Increase Management flexibility and motivate employee morale.

WCU
 Faster decision making: It helps to make decision in the work environment.

 Increase accuracy and Increase information processing efficiency
1.11.4. Legal feasibility

The system which we will be developed does not conflict with any government directives, and
with any cultural aspects, because it gives services for Store management in Wachemo
University, all the Store workers also agreed before the system developed. So, the Wachemo
University and peoples are profitable and the system will be legally feasible.
1.11.5. Time feasibility

All members are expected to perform each and every activity within the defined time frame to
finalize the project so that the system will be feasible in terms of the schedule. In order to
accomplish the proposed system, we will follow a schedule that is presented below by the Gantt
chart.
1.12. Project Organization

In our document we have included the system details through all the chapters.
In chapter one, we have included introduction, background, general objective, specific

objective, scope of the project, the methodology we have used.
In chapter two, we deal about system features such as; existing system description, proposed
system description, functional requirement, non-functional requirement, and analysis models.
In chapter three, we deal about the analysis of the system that the basic thing in our system
development which helps the system designers (we) to find the purpose of the system and then to
model it. In case of the new system, we develop the purpose is to provide partial computerized
information handling system. In this chapter we use sequence diagram shows how processes
operate with one another and in what order, use case diagram to represent the interaction of user
with system, class diagram to describe the structure of the system by showing the system's class
their attributes, operations (or methods) and the relationships among objects.

WCU
In chapter four, we deal that the overall system designs its objective is to provide an efficient,
modular design that reduce the system’s complexity, facilitate change, and result in an easy
implementation. This is accomplished by designing a strongly cohesion system with minimal
coupling or combination. In addition, this document provides interface design models that are
consistent, user friendly, and provide straightforward transitions through the various system
functions.
In chapter five of this project implementation of the proposed system by using C# programming
language and testing the implemented system by different testing methodologies is discussed.
1.13. Project Plan
1.13.1. Time Schedule

No. Activities Start Finish 2021
Mar Apr May June July
1 Requirement Gathering 01-03-2021 08-03-2021
2 Proposal Writing 08-03-2021 16-03-2021
3 System Requirement 08-03-2021 29-03-2021

Specifications
4 Analysis Phase 30-03-2021 12-04-2021
5 Design Phase 13-04-2021 23-04-2021
6 Implementation 20-05-2021 22-06-2021
7 Testing 23-06-2021 01-07-2021
Table 3: Time schedule table
1.13.2. Budget Plan

All other requirements like MS Visio, MS Visual Studio, MS Access, MS Power point and
windows operating system are free. Below table describe the budget required for the proposed
system.

WCU
Item Quantity Price per Item Total Price

Paper 300 1 300
Pen 1 10 10
Mobile Card 2 25 50
Print 75 2 150
Binding 4 15 60
Additional Cost 50 2 100
Personal Computer 2 24,000 48,000
Flash drive 1 350 350
Total =49,020
Table 4: Budget plan table

WCU
Chapter -Two-
Description of The Existing System or Application
2.1. Introduction
The current Store management system of Wachemo University is a manual system that is used in
managing and controlling store materials. This system has some drawback like consuming a lot
of manpower which leads to be unmanageable. Since it works manually, information accessing is
very slow and to get some tasks to be accomplished it goes through much process and this is time
consuming. As a result, the current system becomes poor in providing services to the employee
of the organization. This leads employee of organization to wait several days as the likelihood of
finding the required information. The existing manual system can perform the following
activities.
 Registering new items of the stock by model 19.

 The stock clerk record stock card which holds item information.
 The stock clerk generates a report to the property administrator head.
 The customer asks or orders the item by model 22.
 Supply items from the store.
 The staff request for item by model 20.
 The customer received the item from the storekeeper by model 22.
 The storekeeper prepares the bin card for the item.
 The stock clerk record stock card.
 The stock clerk prepares a user card.
 The secretory prepares a soft copy for all item information.
 Transfer items from one user to another.
2.2. Business Rule and Constraint

The existing system has its own business rule and constraints in order to perform its activity. The
business rules and constraint of the existing system are listed as the following: -
Final Year Project Documentation Page 22

WCU
2.2.1. Business Rule of Existing System

 BR1: The items registered to the stock by model 19 and the stock card is made which
holds detail information about the item entered by the stock clerk.
 BR2: After items are recorded with their respective information by stock clerk then the
stock keeper places them on the shelf and takes care of them.
 BR3: To take a material the staff members ask the items by model 22 and sign their
signature. The staff members should have collage or department permission and their
signature. And the items they request should be found on the store then the property
administrator head approves the permission.
 BR4: After staff members have the permission of the property administrator head, they
sign their signature for taking items, the secretory attach the requested form to model 22,
stock keeper sign for issued property then finally the staff member takes the item they
request
 BR5: After staff member takes the property the stock clerk records the staff member's
name, department, block number, date, and detail of the taken item.
 BR6: Bin card is prepared by stock keeper right away the staff member takes the
property which includes balance, date and item detail.
 BR7: Stock card is prepared by the Stock clerk right away the staff member takes the
property which holds organization name, item type, measurement, item quantity, page
number, date, reference.
 BR8: The staff member communicates with secretory, secretory prepare model 19 form,
stock clerk record item description, model, quantity, staff member sign for their returning
the property, the stock keeper sign for receiving, then the property placed in the store.
 BR9: The stock clerk records the returned property name campus, department, building
number, room number, user number, item classification (fixed asset/durable), item detail
information in the item transfer form
 BR10: The stock clerk prepares a report of their activity and submits to the property
administrator head.
 BR11: The staff member asks for an item and if they need more than one item at a time
the approval based on their role.

WCU
 BR12: If the staff member needs to request for the same item which is broken, they must
first return the previous one.
2.2.2. Constraint
Constraints are the state of being checked, restricted, or compiled to avoid or perform some
action. Constraints for the existing system are: -
 Poor communication between staff member and store employee.

 The staff member lacks information about available item then the staff member does not
get item at wanted time.
 The stock card and user card may get damage and the stock clerk can’t generate report
timely.
 The Department Head is not found in work place then the approval activities can’t
perform on time and the staff member may waste time for waiting for the department
head.
 The store keeper may lose bin card and it’s difficult to know the item exemption and
remain from and in store respectively.
 The sock clerk may lose user card and the stock clerk doesn’t know which item is belong
to which user.
2.3. Naming Convention and Definition

 Stock card: This form is done by the stock clerk which records item detail information
and with its cost in the store. The stock card is a subsidiary accounting record that records
each individual transaction involving the movement in and out of the business of a
particular item of stock.
 User card: The document contains user detail information with the property they took.
 Bin card: Bin Card is a stores record card of quantities of a particular material or
component received, quantities issued and the balance of the material in store. These
balances can be checked against the actual quantities in stock by storekeeper.
 Model 22: The receipt the customer received the item from the storekeeper.
 Model 19: The receipt for registering new items of the stock.

WCU
 Model 20: The receipt staff member used to request for an item.
2.4 Function or Main Activities of Existing System

The major functions of the current system are described as the following.
 Register items to the store by using model 19.

 Record Bin Card and stock Card for the registered item.
 Create a user card to the user when they take an item from the store.
 Protect the items from danger in the store.
 Transfer items between users.
 Prepare stock balance after items storing and exiting.
 Save the user's card in excel.
 Generate report within 15 days based on item entering, exiting, and balance of the stock.
2.5 Players of the Existing Systems or Application
The main players of the existing system include Property Administrator head, Stock Clerk, Store
Keeper, Secretary, staff members.
 Store Manager: -The property administrator team leader is the Administrator of the store
which is responsible for controlling the overall store activity. The admin is also managing
the team leaders in all stores and all the existing system players.
 Stock Clerk: -Stock Clerk manages the stock, stock card, user card, transfer and
returning of the item in the system and generates a report for the activity of the system
per 15 days to the property administrator team reader. Responsible for managing
warehouses or delivering products to retail stores.
 Store Keeper Store Keeper keeps and records stock or one that keeps an item of goods
on hand, shipped, or received. Hold the key to the store. The storekeeper also manages
the store and prepare bin card which records and balance the received, issued and
available items.

WCU
 Secretary: -Secretary keeps all the documents or activities of the store and writes user
card in Excel and hold forms of model 22 and model 19 papers. Attach the requested a
file of the user to model 22 of the property issued.
 College dean, Academic vice president, President: They are responsible for approving
requests.
 Staff Members: -They request items from the store by mentioning why they need it.
2.6 Organizational Structure

An organizational structure is a system that outlines how certain activities are directed in order to
achieve the goals of an organization. These activities can include rules, roles, and
responsibilities. The organizational structure also determines how information flows between
levels within the company.
President office
Research and Academic affair vice Business and development

community vice Admin and student service
president vice president
president vice president
Community service Acadamic Construction project HRM

diroctorate program office
Research Directorate Academic quality RGM Managment SSD

Affair Office
Genius knowledge Teachers directorate ICT department Clinic

Directorate Director Office
Coordinators College Transport and Vehicle

Dean Maitenance
School Dean Counseling and

Quality Assurance
Guidance
Coordinator Coordinator
Department Finance
Research Dean Directorate
Coordinator
Inventory
Managment
Store
Coordinator
Figure 2: Organizational Structure of WCU
2.7. Documents used in the Existing System

 Receipt for articles or Property Received: This form contains detail information about
purchased assets like item number in expenditure registry, number of the entry in the

WCU
registry of incoming goods, classification of stock, store number, shelf number, and other
detail.
Figure 3: Receipt for article or property received

 Property request and ordering Form: This form is used when the staff members want
to order items, he/she should have this form to get permission from the concerned body
which contains the Type and name of the item, quantity of the requested item, the number
of the allowed item and other detail.

WCU
Figure 4: Item request form

 Receipt for articles of property issued: This form contains detail information of items
while staff members taking items from the store and getting permission from the stock
keeper.

WCU
Figure 5: Receipt for article of property issued

WCU
 Stock card: This form is done by the stock clerk which records item detail information
and with its cost in the store.
Figure 6: Stock card

 Bin Card: Bin Card is a paper document that records quantity received, quantity issued,
balance, remark, and other detail information.

WCU
Figure 7: Bin Card

 User Card: Which document contain user detail information with the property they took.
Figure 8: User Card

WCU
 Assets Transfer Form: Which records the details of when one user’s assets are
transferred to another user due to various reasons.
Figure 9: Asset transfer form
2.8. Strength and Weakness of the Existing System
2.8.1 Strength of the Existing System or Application

 The system does not need computer professional.
 To create work Opportunity for employee.
 Sector have its own mission and strategy for working process.
 Any employees easily understand without computer knowledge.
2.8.2 Weakness of the Existing System or Application

At the start of a business, the store manual document filing can be quick easy and necessary.
However, as your business grows manual filing can become a very cumbersome practice.

WCU
The existing manual system has a number of drawbacks that are highly labor-intensive to
operate, Prone to Damage and Being Misplaced and It is also more difficult to share store
information throughout the business because they lack computerization makes accessing store
information a more cumbersome process. These problems can be seen from the following
perspectives like Human Error,
 Prone to Damage and Being Misplaced: Manual document filing means you are
placing faith in the people handling the files. There are so many ways they can be
damaged, lost, or misplaced. A fire or natural disaster could mean the loss of all your
clients’ important information. You will have to start over at square one getting the
information back. It can also lead you to lose clients who don’t appreciate your
mishandling of their information.
 Performance: The current manual store system’s performance is weak. To generate
reports, to manipulate the overall activity of this system to the user is so slow. This is due
to the acceptable throughput rate is relatively high which means the time required from
initiation to completion of a particular task is relatively high.
 Access Time: The current Manual document filing is very time-consuming. Not only do
you have to organize and store the files, hunting down the information when it is needed
can take time. It can take anywhere from minutes to hours to hunt down a file. This can
cause annoyance for clients as well as for employees. Their productivity is lowered by
having to spend excessive time dealing with a paper filing system.
 Efficiency: In manual operation, most of the activities are prone to wastage of resources
like papers, manpower, and time to produce the corresponding outputs. This makes the
current system inefficient while utilizing resources. There should be a mechanism that
reduces wastage of resources and that make the system to be efficient.
 Human Error: The current manual store system relies heavily on the actions of people,
which increases the possibility of human error. People might forget to record a
transaction or simply miscount the number of goods. This results in needless additional
orders that increase the inventory carrying costs and use up precious storage space.
Inaccurate physical counts could also result in not ordering enough of a product, meaning
the business could run out of a crucial item at the wrong time.

WCU
 Difficulty in a modification of data: In the current manual store system, it is much

harder to make changes. If you want to make any change you will have to make a copy,
so you don’t destroy the original with any edits or comments you might add. This means
the editing process is more time consuming and costly than if you were working with
digital copies.
 Insufficient Storage Space: Paperwork can take up a significant amount of space, and
the need of space will increase as the number of the document increases with an increase
in growth of the activity within the organization. The organization activity increase,
paperwork also increases, data will increase, records will also increase leads to
insufficient space.
 High costs: One of the biggest drawbacks of manual-based document management
systems is the associated costs. In addition to tones of paper, you will need more printers,
photocopier, stationery and other office supplies. These costs add up and can become a
significant expense in many organizations.
2.8.3. Alternative Solutions

The proposed system can solve some of the above problems as much as possible. The
proposed system of the new system will mainly provide the following solutions: -
 Change manual system into a computerized system without affecting the structure of
the existing system
 Reduce the workload of employees.
 The proposed system improves performance and work efficiency by automating the
existing system.
 Give notification related to the store.
 The proposed system reduces the associated cost with existing system.
 Allow the staff member to request and transfer an item through LAN by using this
system.

WCU
Chapter Three
Requirement Specification and Analysis
3.1. Introduction
This section consists of the modeling of the proposed system using object-oriented methodology
by using unified modeling language (UML). The team used an object-oriented system
development methodology which incorporates two principal phases. Object-Oriented Analysis
and Object-oriented Design, this chapter discusses object-oriented analysis (OOA) which
includes major activities such as Use case Diagram and documentation (for each use case
identified), and the development of sequence and activity diagrams.
A UML diagram is a diagram based on the UML (Unified Modeling Language) with the purpose
of visually representing a system along with its main actors, roles, actions, artifacts or classes, in
order to better understand, alter, maintain, or document information about the system.
Object Oriented Analysis (OOA) is the first technical activity performed as part of object-
oriented software engineering. OOA introduces new concepts to investigate a problem. It is
based in a set of basic principles, which are as follows-
 The information domain is modeled.

 Behavior is represented.
 Function is described.
 Data, functional, and behavioral models are divided to uncover greater detail.
3.2. Description of the Proposed System or Applications

The proposed system is designed to solve problems affecting the manual system. It is designed to
be used through WCU LAN thereby relieving any workers of the store from much stress as
experienced in the manual system. The proposed system improves the drawbacks of the Existing
system by developing an automated system with user-friendly and interactive graphical user
interface. The proposed system Manage time effectively which means it minimize the wastage of
time with the aid of computer system, Make the data error-free by avoid data redundancy or

WCU
duplication, utilize available resource effectively by minimizing the usage of any writing
material like Paper, pen and any other material that helps to write report document, efficient way
of data management by using database system there is no way of loose of data.
3.2.1 User Characteristics

The system provides different types of services based on the type of users. The user logged into
the system according to his/her privilege. Here end-users are accessing the system by their
unique ID, username and department (sector). When users open his/her account then shows
his/her pages. Users can also edit their profile along with all the details and can access the system
based on their privilege in the system and get new information related to store. All types of Users
should be comfortable with the English and Amharic language. The administrator must be
capable to manage user rights.
3.2.2 Constraints
Project constraints may influence how you manage your project and may even determine
whether or not you (and your project’s drivers and supporters) decide to proceed with your
project. Project limitations typically fall into several categories. The following are main
constraints:
 Administrator and end-users must remember login id and password.

 User need to have a personal computer connected with WCU LAN.
 It’s not suitable for blind people.

 The system performs its work only in the WCU LAN
 It needs some computer skill to operate on the system.
 The interface is provided only in English and Amharic Language.
3.2.3 Assumptions and Dependencies

The assumptions are:
 The coding should be error free.

 The system should be attractive and user-friendly so that it is easy to use for the users.

WCU
 Valid information of every user and item must be stored in database that is accessible by
the system.
 The system should provide more storage capacity and provide fast access to the database.
 Users may access the system from any computer that has connected to the WCU LAN.
 Users must have their correct usernames and passwords to enter into the system and do
actions.
The dependencies are:
 The specific hardware and software are requiring due to which the product will be run.
 The end users should have proper understanding of the system.
 Any update regarding the user’s profile, posts and any other updating is to be recorded to
the database and the data entered should be correct.
3.3. Requirement Specifications

These requirements are feature that the new system should satisfy to be accepted by the
stakeholder and user. These are functional requirements and non-functional requirements.
3.3.1 Functional Requirement

A functional requirement is a description of the activities and services that a system should
provide. The proposed system is expected to provide store-related services and functionalities.
Therefore, the university will able to track the items and supply that is running out of stock. The
following are the functional requirements that should be fulfilled by our system.
 FREQ-1: The system shall require login before allowing providing any function for the
user.
 FREQ-2: The system shall display an error message “Incorrect password or username”
when the user tries to login with the wrong password or username.
 FREQ-3: The system shall allow the administrator to control the overall activities in the
system.
 FREQ-4: The system shall allow an administrator to change his /her account information.
 FREQ-5: The system shall allow the user to Request items.

WCU
 FREQ-6: The system shall allow the admin to manage the user account
 FREQ-7: The system shall allow the user to search items.
 FREQ-8: The system shall allow the admin to view comments.
 FREQ-9: The system shall allow the store manager to view reports,
 FREQ-10: The system shall allow the user to transfer items.
 FREQ-11: The system shall Inquiry all currently enrolled users to update their details.
 FREQ-12: The system shall allow the user to change his /her account information
 FREQ-13: The system shall allow the stock clerk to register the new item's information
 FREQ-14: The system shall allow the stock clerk to updates the item information
periodically
 FREQ-15: The system shall allow the stock clerk to register stock cards information in
digital format.
 FREQ-16: The system shall allow the stock clerk to generate reports within 15 days
periodically.
 FREQ-17: The system shall allow the stock clerk to give notification to other users
 FREQ-18: The system shall allow the users to give comment on the system
 FREQ-19: The system shall allow the store keeper register Bin Card information in
digital format.
 FREQ-20: The system shall allow the staff member to receive notification that is the
request approved or disapproved
 FREQ-21: The system shall allow the staff member to View notification.
 FREQ-22: The system shall allow the staff member to edit their request.
 FREQ-23: The system shall allow the college dean to approve the request.
 FREQ-24: The system shall allow the property admin to manage store activities.
 FREQ-25: The system shall allow the property admin to approve the request.
 FREQ-26: The system shall allow the stock clerk to register user cards information in
digital format.
 FREQ-27: The system shall allow property admin to View report generated by stock
clerk.
 FREQ-28: The system shall validate the filled form by using JavaScript.

WCU
 FREQ-29: The system shall allow stock clerk to view detail item information.
 FREQ-30: The system shall allow storekeeper to know item issued and remained in
store.
 FREQ-31: The system shall allow user to recover their password if they forgot by
remembering their user’s name from their previous input.
 FREQ-32: The system shall allow multi user to access the system through LAN at the
same time.
 FREQ-33: The system shall allow user to logout from the system.
3.3.2 Non-functional Requirement

Non-functional requirement is that it essentially specifies how the system should behave and that
it is a constraint upon the systems Performance requirement. The following are the Non-
functional requirements that should be fulfilled by our system.
User Interface and Human Factors:
As the system is developed that follows the good user interface guideline the interface of the
proposed system is simple to understand, easy to use and user-friendly interface and users of the
system easily use and perform their tasks. Everything stems from knowing our users, including
understanding their goals, skills, preferences, and tendencies. Once we know about our user, we
consider the following details when designing our interface.
 Clear and simple: we avoid unnecessary elements and are clear in the language they use
on labels to prevent user errors, make important information obvious, and contribute to
ease of learning and use.
 Create consistency and use common user interface elements: we use common element
in our UI, users feel more comfortable and are able to get things done more quickly,
layout and design throughout the site to help facilitate efficiency.
 Strategically use color and texture: The colors used should also correspond to common
conventions and user expectations.
 Responsive: The interface talks back to the user to inform them about what’s happening.
Hardware Consideration
As the system is web application the hardware that should be considered as a server are there that
enables the user to access the system through the LAN. And also, client computers or personal

WCU
computers like a laptop that user uses to access the system. The system is compatible with any
computer that enables a user to access the system through LAN.
Security Issues
The proposed system will highly secure, for preventing unauthorized access that uses the
username, password, SQL injection, Session and cookies. The system is much secured based on
the username and password for all user activity. Nobody can access the system without an
authorized person. Passwords are not visible cannot be accessed by anyone because the
passwords are encrypted by the MD5 encryption mechanism. Nobody can access the system
without an authorized person. If an unauthorized user attempts an incorrect password and
username more than five times to enter into the system, the unauthorized user is prevented and
blocked from typing again. But if the authorized user quirkily forgot his user’s name and
password it can recover by remembering some previously entered information. And also, the
system use watermark signature to verify approval process.
Performance Consideration
We will develop the system that multi-user can access simultaneously without the failure of the
system. The proposed system loads information in a few-second and gives output response for
user input data in two seconds for all performance issues we will use the performance testing
tool. The system shall minimize errors and a clear error message should be displayed that guides
users to handle it. The performance of this system is measured in terms of load time, concurrent
processing and response time.
 Load time: this system loads the request and information as quickly as possible.
 Concurrent Processing: The proposed system is LAN-based can multiple users execute
at once concurrently in that network.
 Response Time: Upon request for user inquiry the system under normal condition should
display results as quickly as possible based on the LAN bandwidth. One way of Improve
Server Response Time makes sure that the server side is updated.
Error Handling and Validation
The system will check user inputs to the system to handle the error. It handles and shows error
for a user. The proposed system uses front-end validation which is JavaScript. This is because of
considering response time. However, if the system validates from the back-end it will take time

WCU
to access the database which leads to less response time. Also, the systems can handle exceptions
that may happen while user uses the system. It handles exceptions of data duplication to save
memory space.
Quality Issues
The system is reliable, available and consistently performs its intended function. Unless there is
an internet connection problem that occurs in our system is available at any time. In the quality
assessing the users will be involved by the feedback mechanisms in which they can give
comments on the system. The system should provide fast and efficient service to all users. We
use suitable software and hardware to develop the system. The system should be available at any
time. The system tolerates some faults like username and other inputs, and it gives related
feedbacks for the error encountered like” enter correct username or password” using JavaScript
as control of faults.
Physical Environment
The system is deployed or installed on the server-side so that client computer access and can use
it. We recommend that the system deploys on Wachemo University server to make it free from
any disaster and better protection.
Documentation
For a system, the user-level document is provided that the user can read the document on how to
use the system and what responsibilities should use to take while using the system. And also
development is provided that the user can read to know about the process and what type of
model the developer uses to develop the system. So that if some failure occurs the maintainer can
easily maintain the system using the documentation.
3.4. System Modeling

To produce a correct, complete and consistent model of the system we construct the analysis
model which focuses on structuring and formalizing the requirements of the system. We can
represent our system by using different system models such as functional, object and dynamic
models the functional model of this system described by use case diagrams. The class diagrams
of this system describe the object model (in the next chapter). The dynamic model of this system
can also describe in terms of sequence and activity diagrams.

WCU
3.4.1. Actor Identification

In the use cases, an actor interacts with the system to perform a piece of meaningful work that
helps them to achieve a goal and has access to define their overall role in the system and the
scope of their action. Depending on the above explanation actors in this system are the
following:
 System Admin: Manage the user account, create account for user, activate the account
and deactivate the account.
 Stock Clerk: Register the new item's information, Updates the item information
periodically, Record stock cards, generate reports periodically, give and view
notification, give comment, search and request item and Transfer items, edit request,
update account.
 Store Keeper: Record Bin Card, Search item, give comment, Request item, Transfer
item, Edit request, Update account, view notification.
 Store Manager: Request item, Search item, Transfer item, give comment, edit request,
Update account, view notification, view report, and Approve the request.
 Staff Members: Request item, Transfer item, search item, give comment, View
notification, Edit request, update account
 College Dean: Request item, Transfer item, give comment, Search item, edit request,
Update account, view notification and Approve request.
 Academic Vice President, President: Request item, Transfer item, give comment,
search item, edit request, Update account, view notification and Approve request.
3.4.2. Use-Case Identification

Each Use Case describes the functionality to be built in the proposed system, which can include
another Use Case's functionality or extend another Use Case with its own behavior. The most
important and basic use cases of this system are the following: -
 Manage user account (Activate/Deactivate, Create)

 View Comment
 View report
 Request items

WCU
 Search items
 Register Bin Card
 Approve (deny, accept)
 Manage item information (Register, Remove, Update)
 Give comment
 Transfer items
 Generate report
 View notification
 Edit Request
 Post notification
 Register user card
 Register stock card
 Update Account
3.4.3. Use-Case Diagram

Use case diagrams are used for capturing the functional requirements of the system. It is the
functionality of the system or the service provided by the system.

WCU
Activate
Create Account
Account Update Request
Deactivate Account Cancel Request
<<extend>>
<<extend>>
<<extend>> <<extend>> <<extend>>
Manage Give Comment Transfer Item
Request Item Search Item Edit Request
Account
View Comment
<<include>>
Manage System
<<include>>
System Admin
<<include>>
<<include>> <<include>>
<<include>>
Accept
Deny
Login <<extend>> <<extend>>
Staff Member <<extend>> <<include>>
President
Approval
Logout
<<include>>
AVP
<<include>>
<<include>> <<include>>
View Report
Store Keeper <<include>>
<<include>> <<include>> College Dean
Register Bin
<<include>>
Card View Register User
Notification Update Account
Card
<<include>> Register Stock Store Manager
Card
Post
Notification
Generate
Report
Manage Item Stock Clerk

Information
<<extend>> <<extend>>
<<extend>>
Update Item
Register Item Information
Remove Item
Figure 10: Use case diagram
3.4.4. Description of Use-Case

WCU
Use Case Name Login

U
C
_
1

WCU
Actor All users of the system (administrator, stock clerk,

storekeeper, staff member, College dean, property admin).
Description This use case is used to ensure security in system usage
Pre-condition All users must have an account in the system.
Basic Course of Action Actor Action System Response
Step1: A user has to activate Step2: The system responds

the system and click it on the by displaying the login
login button. interface and allows the user
Step3: The user selects the to enter their login detail
account type and fills his or Step 5: The system verifies
her username and password. username and Password.
Step4: he/she select the login Step 6: The system displays
button “access granted welcome to
your page”.
Step 7: User can get
authentication and the
System display account page.
Step 8: End use case.
Alternative course of Step5: If the user enters Step6: The System displays
Action invalid username and messages that contain “field
password cannot be empty or you
Step7: User repeats Step 3 entered wrong username or
from the normal flow. password” will be displayed.
Step5: If the user forgets its Step6: The system allows the
password and username click user to recover from previous
forget password link input.
Step7: The user enters Step8: The system displays
recovery inputs username and password
Post-Condition The user logged into the system according to his/her privilege

WCU
Table 5: Login use case description
Use Case Name Logout

Actor All users of the system (administrator, stock clerk, storekeeper,
College Dean, staff member, property admin).
Description This use case allows to logout and back to the login/main page
to ensure security in system usage
Pre-condition The user should be login to the system and wants to log out
Basic Course of Actor Action System Response
Action
Step 1: The User click Logout Step 2: The system ask
UC_2
Button confirmation for logout

Step 3: The user confirms for Step 4: The system returns to
logout the main page
Step 5: End use case
Alternative course of
Action Step 3: The user not confirm Step 4: The system stays the
For logout user on the page
Post-Condition The user logout from their page and go back to the home page.
Table 6: Logout Use case Description
Use Case Name Create Account

Actor system administrator
Description This use case is done by the Administrator when he/she need
to register a new account.
UC_3
Pre-condition This use case is done by the Administrator when

he/she need to register a new account.

WCU
Step 1: Login into the system. Step3: The system display

Step 2: System Administrator creates a new account page.
click on Add New Account Step6: System validate
Step4: The Administrator entered data
enters the new user name, Step7: The system will
account type, Password and Register user and display
all user required information Successfully registered
to the system message.
Step 5: The system Step 8: Use case end
Administrator click on the add
account button
Alternative course of Step 4: Invalid new user Step 7: System display
Action information entered invalid user detail
Step 7: User repeat Step 4 information message.
from the normal flow.
Post-Condition New Account created
Table 7: Create account use case description
Use Case Name Update Account

Actor System Administrator
Description This use case is to allow the system administrator to update
UC_4
Account
Pre-condition The System Administrator must log in into the system

WCU
Step 1: System administrator Step 3: The system displays

login into the system manage account page which
Step 2: click on manage contains update user,
Account Button activate/deactivate user, view
Step 4: System admin click detail information and other
on Update User Account details.
Button Step 5: The system displays
Step 6: Insert the correct all user detail information.
information that wants to Step 8: The system validates
update entered data
Step 7: Click submit button Step 9: The system saves
entered to data into the
database.
Step 10: Use case end
Alternative course of Step 6: If the system Step 9: System response to
Action administrator does not enter the system administrator he
valid user information or she does not enter valid
Step 9: System administrator information and allows to
repeat step 6 enter again.
Post-Condition Account information is updated successfully
Table 8: Update account use case description
Use Case Name Post notification

Actor Stock clerk
Description This use case shows when stock clerk post notification
UC_5
Pre-condition Stock clerk must be login into the system according to

his/her privilege

WCU
Step1: The Stock clerk Step 3: The system displays

login into the system the notification form.
Step 2: Click on Give Step 6: System validate
notification button entered information
Step 4: The stock clerk Step 7: The system displays
fills the form a successfully Posted
Step 5: Click Post button message.
Step 8: Use case end.
Alternative course of Step 4: Invalid input or Step 7: System display “field
Action blank field left cannot be blank or invalid
Step 7: Stock clerk repeat information entered” and
step4 allows to re-enter the correct
information
Post-Condition Notification posted successfully to the user
Table 9: Post notification use case description
Use Case Name Register Item

Actor Stock clerk
Description Register new property into the system
Pre-condition Login into the system
Step 1: Stock clerk login Step 3: The system displays

UC_6
into the system a form that contains item

Step 2: Click register item type, date, model, price,
Step 4: The stock clerk fills quantity and other property
all the fields that the system detail information.
provides. Step 6: The system validates
Step 5: Click submit the entered data
Step 7: The property

WCU
recorded into the system.

Step 8: The system notifies
the stock clerk that property
has successfully registered.
Step 9: Use case end.
Alternative course of Step 4: If the stock clerk Step 7: The system display
Action enters invalid data or forgot “you entered invalid data or
to fill some fields the stock the field could not be empty”
clerk repeats step 4. and allows you to fill again
the correct data.
Post-Condition The property added to the system
Table 10: Register Item use case description
Use Case Name Edit item

Actor Stock clerk
Description Update or delete items
Pre-condition The stock clerk must log in to the system and items should
be in the system.

UC_7
clicks edit item link in all the property information

his/her home page that previously registered
Step 4: The system validates
Case update the entered data.
Step 3: stock clerk clicks Step 5: The system will
update link and fills display “successfully
information that he /she Updated message” and
wants to update and click display the Updated page.
the update button Step 6: Use case end

WCU
Step 2: The system displays

Case deletes all the property information
Step 1: The stock clerk that previously registered
clicks edit item link in Step 4: The System displays
his/her home page a message that contains” are
Step 3: The stock clerk you sure, you want to delete
clicks on a delete item link with yes and no button”
Step 5: Stock clerk select Step 6: the system deletes
(yes) button, the item from the database
and display successfully
deleted messages.
Alternative course of Case update Step 6: System display
Action Step 3: Invalid data message that contains
entered or left blank fields “field cannot be empty or
Step 5: Repeat step 3 you entered the wrong
character” will be displayed
Case deletes Step 7: The system cancels

Step 5: The stock clerk deleting an item
clicks ‘no’ Button
Post-Condition The item information updated accordingly
Table 11: Edit item use case description
Use Case Name Search items

Actor All users of the system
Description To see available property
UC_8
Pre-condition The item should be registered


WCU
Step 1: All actors login to Step 5: The system displays

the system all available items with their
Step 2: All actors’ click detail information
search bar on their user Step 6: Use case end
page
Step 3: The actors inserts
the item name to the form
Step 4: The actors click
search button
Alternative course of Step 2: If the actor does Step 3: The system does not
Action not click view item button display items.
Post-Condition Successful completion, the user sees items
Table 12: Search item use case description
Use Case Name Register stock card

Actor Stock clerk
Description Register the property detail information with their
respective cost
Pre-condition Login into the system
UC_9

study model 19 the stock card form.
Step 2: Click register stock Step 5: The system validates
card button the entered data and missed
Step 4: The stock clerk field
fills all the fields and press Step 6: The system records
record button the stock card to the database
and notifies successfully

WCU
resisted message.
Alternative course of Step 4: Invalid data Step 6: System display

Action entered or left some field message that contains “field
Step 7: Repeat step 4 cannot be empty or you
entered the wrong character”
will be displayed
Post-Condition The stock card registered to the system database
Table 13: Register Stock card use case description
Use Case Name Register user card

Actor This use case describes how the stock clerk records user
card
Description Stock clerk
Pre-condition The stock keeper announces to the stock clerk that the user
issued an item from the store
UC_10
Step 1: The stock clerk sees Step 3: The system displays

a notification about an a form that contains the user
issued item from the store card.
Step 2: Click the prepare Step 5: The system validates
user card button. the entered data
Step 4: Fill all the fields and Step 6: record to the
press record button database and display a
message that contains
successfully recorded

WCU
Alternative course of Step 4: Missing filed or Step 6: System display filed

Action invalid data cannot be empty or invalid
Step 6: Repeat step 4. character entered
Post-Condition User card recorded to the database
Table 14: Register user card use case description
Use Case Name Request item

Actor All users of the System
Description This use case describes how user request item
Pre-condition The user should see items through LAN and request
available items.
UC_11
Step 1: Use login according to Step 4: The System

their privilege and click the displays the request
request button form
Step 2: The user asks request Step 7: The System
form from their team leader (for validates the entered
instance, the staff member ask the data and sends the form
request from college dean) which is approved by
Step 3: The team leader (college their team leader to

WCU
dean) sends request form with system admin

approval to the user (staff Step 10: Notify request
member) is successful.
Step 5: The user (staff member) Step 12: Use case end
fills the item information they
need with their signature
Step 6: Click submit button
Step 8: The property
administrator approves the
request then send to the stock
clerk
Step 9: The stock clerk receives
the request and fill the request
information on model 22 and
send to the stock keeper
Step 11: The user receives the
requested property
Alternative course of Step 3: The team leader Step 2: The system
Action disapproves the request notifies invalid
Step 10: User repeat step 3 again username and password
and allows to enter
again
Step 4: The system
display request denied
message.
Post-Condition The user takes the property
Table 15: Request item use case description
Use Case Name Edit request

UC_12

Description This use case describes when the users need to update and

WCU
delete their request.

Pre-condition The user must loin into the system and request for item
Actor Action System Response
Step 1: User login to the Step 3: The system displays

system and want to return the page which contain new
Step 2: The user click request and previous request.
Request item link on their Step 5: The system displays
user page the previous request form
Step 4: User click previous Step 7: The system validates
Basic Course of Action request the entered input
Case update Step 8: The system display
Step 6: user clicks update “Request updated
link and fills information successfully” message and
that he /she wants to update display the updated page
and click the update button Step 10: Use case End
Case deletes Step 5: The system displays

Step 1: The user clicks Edit the previous request form
request link in his/her home Step 7: The system displays
page. a message that contain “Are
Step 6: user clicks delete you sure you want to delete
request link with yes and no button”.
Step 8: User select yes Step 9: The system displays
button a message “the request
deleted successfully”
Alternative course of Case update Step 7: You entered
Action Step 6: Invalid data entered incorrect data retry again
or left blank fields

WCU
Step 8: Repeat step 6
Case deletes Step 9: The system cancel

Step 8: The user clicks ‘no’ delete request.
Button
Post-Condition The request edited successfully
Table 16: Edit request use case description
Use Case Name Give comment

Description This use case describes how the user give comment on the
store service
Pre-condition The user login to the system to give comment
Actor Action System Response
Step 1: User login into the Step 3: The system displays

system the comment form
Basic Course of Action Step 2: User click on Step 5: The system validates
UC_13
comment link on their the entered input

home page Step 6: The system sends
Step 4: The user enters the the comment to the system
comment and clicks the and property administrator
submit button page
Alternative course of Step 4: The user enters the Step 6: The system displays
Action wrong input or left blank Messages that contain “field
Step 6: Repeat step 4 cannot be empty or you
again entered the wrong character”
will be displayed
Post-Condition Property administrator get feedback on store service
Table 17: Give comment use case description

WCU
Use Case Name Generate report

Actor Stock clerk
Description This use case describes how the stock clerk generate the
report
Pre-condition Stock clerk login into the system
Step 1: Stock clerk login Step 2: The system

into the system and click automatically generates a
UC_14
generate report link on report.

his/her page Step 4: Use case end
Step 3: Submit the report to
the system administrator
Alternative course of Step 1: Stock clerk enter Step 2: The system notifies
Action invalid user name and invalid username and
password password and allows to enter
Step 2: Repeat step 1 again
Post-Condition Report generated and submitted to the system and property
administrator
Table 18: Generate report use case description
Use Case Name View Report

Actor Store manager
Description This use case describes how system and property admin view
Report of items and employees
UC_15
Pre-condition The system administrator must log in into the system, items,
and employee registered into the system

WCU
Step 1: System and property Step 3: System display

admin login into the system report type
Step 2: Click on view report Step 5: The system displays
Step 4: The admin select the selected report
report type automatically
Alternative course of Step 1: Invalid user name and Step 3: The system notifies
Action password to the admin incorrect user
Step 3: Repeat step 1 name and password and
allows to retype
Post-Condition System and property admin view the desired report
Table 19: View report use case description
Use case Name Transfer Asset

Actor Staff Member
Description This use case describes how staff member transfer items
to
another staff member
Pre-Condition The staff member login into the system
Step 1. staff member login Step 3. System display
UC_16
into the system asset transfer form, which

Step 2. Click transfer item contain Assets transfer
Step 4. Fill all the field from, Asset transferred to,
Step 5. Click submit name, campus, department,
Step 7. send to Head of building number, room
FAMU for approval number, user number,
Step 8. Head of FAMU stock classification, and
approve the request and item detail information
send to stock clerk and description

WCU
Step 9. The stock clerk Step 6. The system

records detail information validates the entered
of the user's property. information
Step 11. Asset transferred
successfully
Step 12. Use case end
Alternative course of Action Step 4. Invalid data Step 6. The system
entered or left blank notifies the staff member
Step 6. Repeat step 4 that he /she enters invalid
again character or field cannot
be empty and allow to retry
again
Post-Condition The assets are transferred from one staff member to
another staff member
Table 20: Transfer asset use case description
3.5. Requirement Analysis
3.5.1. Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. Activity diagrams are constructed from a
limited number of shapes, connected with arrows. The purpose of the activity diagram is to
model the procedural flow of actions that are part of a larger activity. In projects in which use
cases are present, activity diagrams can model a specific use case at a more detailed level. The
activity diagram shows the various activities step by step with the carrying for both parallel and
conditional behavior. The most important shape types are:
 Rounded rectangles represent activities.
 Diamonds represent decisions.
 The first circle represents the start (initial state) of the work-flow.

WCU
 An encircled end circle represents the end (final state).
All user of the system
Home Page Click login button
Enter username,
password and select role
Display Error Message Incorret Validate Correct
Display user page

Forgot Password
Enter password recovery
Invalid
Validate
Valid
User name and password

Displayed
Figure 11: Activity diagram for Login

WCU
Login into Admin Click Manage

Home page
page Account
Fill form to create Create Account

Click Create button
account Form Displayed
Error message Invalid Validation Valid Click save button
Account Created
succefully
Figure 12: Activity Diagram for create account

Login into Admin Click Manage
Home page
page Account
Click Edit account

Select Account Account displayed
button
Click Deactivate
button No
Confirmation
Yes/No
Yes
Account Deactivated
successfully
Figure 13: Activity diagram for Deactivate account

WCU
Home page Login into page
Click Edit account

Account displayed
button
Click update Fill account

account button information
Invalid
Validation
Valid
Click update button
Account updated
successfully
Figure 14:Activity Diagram for Update Account

Give Notification
Home page Login
Click Prepare Notice Form Display
Fill information
Invalid
Validation
Valid
Click Post button
Notice post successfuy
Figure 15: Activity diagram for Post notification

WCU
View Notification
Home page Login User Page Displayed
Click view Notification Not Available
Check Availablity
Available
Notification Displayed
Figure 16: Activity diagram for View Notification

Register New
Item
Home page Login into page Click Manage Item
Fill form to Register Registration Form Click Register

Item Displayed button
Click Register
Error message Invalid Validation Valid
button
Item Registered
succefully
Figure 17: Activity diagram for Register item information

WCU
Update item
information
Home page Login into page Click Manage Item
Select one Form Displayed Click Edit button
Click update button Fill information
Invalid
Validation
Valid
Click update button
Item information
updated successfully
Figure 18: Activity diagram for update item information

System Admin
View Comment
Home page Login into Page
Click View System Admin page

Comment Displayed
Display No comment
Check if found No comment
found yet
Comment found
Display comment Admin View Comment
Figure 19: Activity diagram for view comment

WCU
Stock Clerk
Home Generate Report
Login into page
page
Detail of item Click Generate Stock Clerk

Displayed Report page Displayed
Click Submit Report Submit to

Button Property Admin
Figure 20: Activity diagram for Stock clerk Generate report
View
Report
Home page Login into page Admin page Displayed
Click View Report
Display No Report found No Report Found?
Yes
Report Displayed
Figure 21: Activity diagram for view report

WCU
Search Item
Login int o
Home page User Select search Bar User Enter Item Name
page
Invalid Validation
Valid
System Display list of

User select item
iitem
System Display
Information of iitem
Figure 22: Activity diagram for search item

Request Item
Home page Login
User Page Displayed No
Click Request Item System display Request

Button form
User fill the form
Invalid
Validation
Valid
Click Send Button Item available
Yes
Request send Succefully

WCU
Figure 23: Activity diagram for request item
Record Stock
card
Home page Login Page displayed
Click Prepare stock

Fill Stock card form
card Button
Invalid
Validation
Valid
Record saved
Click Save Button
Succesfully
Figure 24: Activity diagram for Register Stock card
Record User
card
Click Prepare User

Fill User card form
card Button
Invalid
Validation
Valid
Record saved
Click Save Button
Succesfully
Figure 25: Activity diagram for Register User card

WCU
Approve request
Click Requested Display No request is

Item Button found yet
Select form Yes Available No
Accept Accept/Deny Deny
Click Deny Button

Click Accept Button
No
Accepted Warn Message

successfully
Yes
Figure 26: Activity diagram for Approve request

WCU
Record Bin
card
Click Prepare Bin

Fill Bin card form
card Button
Invalid
Validation
Valid
Record saved
Click Save Button
Succesfully
Figure 27: Activity diagram for Register Bin Card

Update Request
Select Previous Click Request Item

Request Button
Request displayed Click update button
Fill Request
information
Invalid
Validation Valid Click Save Button
Request updated
successfully
Figure 28: Activity diagram for update Request

WCU
Cancel Request
Select Previous Click Request Item

Request displayed
Request Button
Click Cancel request Request Canceled

Warn Message Yes
Button successfully
No
Figure 29: Activity diagram for cancel request

Give Comment
Comment form Click Comment

Displayed Link
Fill Form
Invalid
Validation
Valid
Comment Sent To
Click Submit Button
system Admin

WCU
Figure 30: Activity diagram for give comment
Transfer Asset
Staff member page

Home page Click login link
Displayed
Invalid
Tranfer form
Click Tranfer Item
displayed
Fill Form
Invalid
Validation Valid Click submit Validation
Valid
Send successfull
Stock clerk save detail Send to stock clerk Send to college dean
Message
Figure 31: Activity diagram for Transfer asset

WCU
Remove Item
Information
Home page Login
Stock clerk Page Click Manage Item

Displayed Button
Item information
Display
No Click Remove Button
Confirm
Yes
Item Information
Deleted Successfully
Figure 32: Activity diagram for Remove item information

Logout
Home page Login User Page Displayed
Select Logout No
Return to Home page Yes Confirm
Figure 33: Activity diagram for Logout

WCU
3.5.2. Sequence Diagram

The sequence diagram is used primarily to show the interactions between objects in the
sequential order that those interactions occur. During the requirements phase of a project,
analysts can take use cases to the next level by providing a more formal level of refinement.
When that occurs, use cases are often refined into one or more sequence diagrams. The main
purpose of a sequence diagram is to define event sequences that result in some desired outcome.
The focus is less on messages themselves and more on the order in which messages occur;
nevertheless, most sequence diagrams will communicate what messages are sent between a
system's objects as well as the order in which they occur.
Homepage: Login page: Login page: Database: Menu page:

User
<<UI>> <<UI>> <<controller>> <<server>> <<UI>>
1.Open system
Login
2.Click login
1. Open system
2. Click login 2.1 Request login form
2.1. Request login form
3. Display form 3.Display form()
4.Enter role,username,password
4. Enter role, username,password
4.1.Request for validation
4.1 Request for validation
5. Validate 5.Validate
6. valid check
6.1 Not found 6.Valid check
6.1.1. Error message
6.1.1.1. Display error message
6.2 Valid(found) 6.1. Not found
6.2.1 Display logged page 6.1.1.display error message (Invalid)
6.2.1.1. Display to user 6.1.1.1.Display invalid username or password
6.2. Found(Valid)
6.2.1. Display()
6.1.1.1.Display()
Figure 34: Sequence diagram for Login

WCU
Stock clerk page: Register Item: Register Item: Database:

Stock clerk
<<UI>> <<UI>> <<Controller>> <<Server>>
1.Click Add Item
Register Item 1.1 Request form
1. Click Add Item button 2.Display form()
1.1 Request form 3.Fill Item Information
4.Request for Validation
2. Display form
3. Fill Item information 5. Validate
4. Request for validation
5.1.Invalid information
5. Validate Display Error message()
If the form is invalid 5.2.Valid infomation
5.1. Error message displayed 6. Click save
If the form is valid 7.Record to database
5.2.valid information 8.Display success message
display
6. Click Save button
7. Record to database
8. Display successful message
Figure 35: Sequence diagram for Register Item
Userpage: Give comment: Give comment: Database:

User
<<UI>> <<UI>> <<controller>> <<server>>
Give comment 1.Click Give comment
1. Click Give comment button 1.1 Request comment form

2.Display form
1.1 Request comment form
2. Display form 3.Fill form
4.Request for validation
3. Fill form
5.Validate
4. Request for validation
5. Validate 5.1..Invalid input
5.1.1.Error Message
5.1. Invalid input: Error
message displayed 5.2.Valid information
5.2.1..Display()
5.2.valid input information 6.Click submit
display
6. Click submit button
8.Comment sent successfully
7. Record to database 8.1 Display()
Figure 36:Sequence diagram for Give Comment

WCU
Userpage: Tranfer asset: Tranfer asset: Head of FAMU: Stock clerk: Database:
User
<<UI>> <<UI>> <<controller>> <<UI>> <<UI>> <<server>>
Tranfer Asset 1.Click Tranfer asset

1.1 Request form
1. Click Tranfer asset button
1.1 Request asset tranfer 2.Display form
form 3.Fill form
2. Display form 4.Request for validation
3. Fill form
4. Request for validation 5.Validate
5. Validate
5.1. Invalid input:Error 5.1..Invalid input
5.1.1.Error Message
message displayed 5.2.Valid information
5.2.valid Input information 5.2.1..Display()
display
6. Click submit button 6.Click submit
7 Send to head of FAMU
7. Send to Head of FAMU
8. Send to stock clerk
9. Record to database 8. Send to sock clerk
10. Display successful
message 9. Record to Database
10.Asset Transferred successfully

11. Display()
Figure 37: Sequence diagram for Asset Transfer
Admin page: Create Account: Create Account: Database:

SystemAdmin
<<UI>> <<UI>> <<controller>> <<server>>
1.Click Create Account

Create Account 1.1.Request Form
1. Click Create Account 2.Display form
1.1 Request form 3.Fill form
2. Display form 4.Request for validation
3.Fill form 5. Validate
4. Request for validation 5.1. Invalid input or field cannot
5. Validate Empty
5.1.1.Display Error message()
5.1. Invalid input or field 5.2. Valid input
cannot empty
5.2. Valid input displayed 5.2.1.Display()
6. Click Create button
7. Record to database 6.Click create
8.1 Display for Admin 8. Account Registered
Successfully
8.1 Display()

WCU
Figure 38: Sequence diagram for Create Account
User Page: Edit Request: Edit Request: Database:

User
Edit Request in case of update 1. Click Edit Request

1. Click Edit Request button 1.1 Request form
1.1. Request form
2. Display Request detail 2.Display Request Information()
information 3. Click Update
3. Click Update button 4. Display form
4. Display form
5. Fill form 5. Fill form
6. Request for validation 6. Request for Validation
7. Validate 7. Validate
7.1.If the form is invalid
7.1.1. Error message displayed 7.1. Invalid input
7.2. If the form is valid 7.1.1. Display error message
7.2.1.valid information display 7.2. Valid input
Display()
8. Click Update button
9. Record to database 8. Click update
10. Display successful message 9. Record to Database
10. Request information updated successfully
Figure 39: Sequence diagram for Update Request
Request
User Page College Dean Request Item: Store Manager Stock clerk Storekeeper Database
User Item:
<<UI>> <<UI>> <<Controller>> <<UI>> <<UI>> <<UI>> <<server>>
<<UI>>
1.Click Request item
Request Item 1.1 Request form
2.Display form() with approval
1.Click request item
1.1 Request form
2. Form display with approval 3. Fill Form
4.Request for Validation
3. Fill form for request
4. Request for validation 5. Validate
5. Validate
5.1. Invalid infomation
5.2. Valid() 5.1.Invalid information
6. Send to system admin Display Error message()
7. The system admin send to stock clerk 5.2.Valid infomation
8. Stock clerk notify store keeper
9. Stock clerk send request approved
message to the user 6. Send to Store Manager
7. Send to stock clerk
10. The stock clerk record detail to the
database
8.Notify request
9. View Request approved

Message 10. Record to database
Figure 40: Sequence diagram for Request Item

WCU
Stock clerk Page: Edit Item: Edit Item: Database:

Stock Clerk
Edit Request in case of update 1. Click Edit Item

1. Click Edit Item button 1.1 Request Item form
1.1. Request item form
2. Display Item detail information 2.Display Item Information()
3. Click Update button 3. Click Update
4. Display form 4. Display form
5. Fill form
6. Request for validation 5. Fill form
7. Validate 6. Request for Validation
7.1.If the form is invalid 7. Validate
7.1.1. Error message displayed
7.2. If the form is valid 7.1. Invalid input
7.2.1.valid information display 7.1.1. Display error message
8. Click Update button 7.2. Valid input
Display()
10. Display successful message 8. Click update
9. Record to Database
10. Item information updated successfully
Figure 41: Sequence diagram for Edit item
Store Manger Page: View Report: View Report: Database:

Store Manager
View Report 1. Click View Report

1. Click View report 1.1 Request For Report
1.1 Request for Report
2. Check report Availability
2. Check report availability
2.1 Not avilable Display report not 2.1 . Display report not found()
found Not available
2.2 Available goto database 2.2 Available
3. Display Report Automatically
3. Display report Automatically

WCU
Figure 42: Sequence diagram for view report
User page: Search Item: Search Item: Database:

User
<<UI>> <<Ui>> <<Controller>> <<Server>>
Search Item 1. Click Search Item

1.1 Request form
1. Click Search Item button
1.1. Request form 2. Display form
2. Display form 3. Write item name to search
4. Request Availability
3. Write item name
4. Request Availability 5. Check Availability
5.Check availability 5.1 Not Available
5.1. Not available item not found Item Not found
5.1.1. Display for user 5.1.1. Display() 5.2 Available
6.Display list of item
5.2. Available send to database 7. Select item
6. List of item displayed 7.1. Request
7. Select item
7.1.Request 8. Display Item Information
8. Display item information 8.1. Display()
8.1 Display for user
Figure 43: Sequence diagram for search Item

WCU
Chapter -Four-
System Design
4.1. Introduction
Design is process of describing, organizing, and structuring system components at architectural
design level and detailed design level. Design converts functional models from analysis into
models that represent the solution. Design may use structured or Object-oriented approaches.
The proposed system design overview is designed in a way to provide a solution for the existing
system problem by minimizing the workload of the existing system and user of the system. It
provides more efficient, reliable and time-saving in the store system. The purpose and goal of
designing is providing the overview of the newly proposed system as if it is actual and to obtain
the necessary information to implement the system. According to different circumstances the
design has many purposes and goals. For example, according to performance, designing the new
system will facilitate the implementation and creates better understanding of the newly proposed
system.
In this section the document is organized as Class Diagram, Entity Relationship Diagram (ERD),
Persistence Modeling, Subsystem Decomposition, Deployment Diagram, System Architecture,
UI Design and UI flow diagram.
4.2. Class Diagram

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application. The class diagram
describes the attributes and operations of a class and also the constraints imposed on the system.
The class diagrams are widely used in the modeling of object-oriented systems because they are
the only UML diagrams which can be mapped directly with object-oriented languages. The class
diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It

WCU
is also known as a structural diagram. The class diagram includes access modifier. There are two
main access modifiers in our project.
 (-) symbol describes private and protects attribute and methods.
 (+) symbol used to describe the method or attribute is accessible for all (public).
Association if two classes in a model need to communicate with each other there must be link
with them and that can be represented by association or connector.

WCU
1...*
1 1
Update User
User Account +Role:Varchar(30)
-User_ID:Varchar(15) +Fname:varchar(30)
-Username:Varchar(45) +Lname:varchar(35)
-Password:Varchar(20) 1 Owned By 1 +Sex:(12)
* +Role:Varchar(30) +User_ID:varchar(20)
+Login() +Block_no:varchar(30)
Notification
+Logout() +Offce_no:varchar(30)
1...* 1...* -NotificationTitle:varchar(45)
1 +phone_no:varchar(15) -Notification_ID:varchar(20)
+Login() View
Give -NitificationContent:varchar(45) *
+Logout()
* +RequestItem() +view()
Managed By Comment +TranferItem() +post()
+User_ID:varchar(20) +SearchItem()
-message:varchar(500) +ViewNotification()
* -Email_address:varchar(50) +GiveComment()
+sent() Posted by
+UpdateAccount()
+view() +CancelRequest()
+UpdateRequest()
Request,Transfer,Search Viewed By
Store Keeper Stock Clerk

Staff Member 1
-Staff_dep:varchar(45) -RegisterBinCard() -RegisterUserCard()
1 1 -RegisterStockCard()
Bin_card Register -RegisterItemInfo()
System Admin 1
-Username: Varchar(45) -ID:varchar(30) -RemoveItemInfo()
-Password: Varchar(45) -QuantityReceived:varchar(23) -UpdateItemInfo()
-role:Varchar (45) -QuantityIssued:varchar(45) -GenerateReport()
-Ref_no:varchar(45) * +ViewReport()
-Create Account()
-Activate Account() -ItemName:varchar(45) -PostNotice()
-Deactivate Account() College Dean President -ItemUnit:varchar(45) 1 Register
-Reg_Date:Date()
1 1
-AcceptRequest() -AcceptRequest() -Balance:varchar(34)
Generate *
-DenyRequest() -DenyRequest() +RegisterBinCard()
* * Stock_card
Report User_card -StockCard_ID:varchar(45)
AVP
-ID:varchar(30) -ID:varchar(30)
-Reference_no:varchar(45)
-AcceptRequest() * -ReportDate:Date() +Fname:varchar(34)
Store Manager -ReportTitle:varchar(45) +Lname:varchar(34) -Received item:varchar(45)
-DenyRequest() View -ReportContent:varchar(55) +DeptName:varchar(45)
1 -Issued Item:varchar(45)
-AcceptRequest() +Sent() +Block_no:varchar(45)
-Item name:varchar(45)
-DenyRequest()- +View() -Office no:varchar(45)
+ViewReport() -Unit:varchar(45)
Approve -Item name:varchar(45)
-Min level:varchar(45)
-Unit:varchar(45)
-Max level:varchar(45)
-Quantity:varchar(45)
-Register Date:Date()
1...* -Price:varchar(45) -Balance:varchar(45)
-Date:Date() +RegisterStockCard()
Item +RegisterUserCard()
-ItemType:varchar(45)
1...*
+ItemName:varchar(45)
-ItemCode:varchar(55)
-Price:varchar(10)
-Unit:varchar(66) * Manage
-Quantity:varchar(65)
-Date: Date()
+RequestItem()
+TransferItem()
+SearchItem()
Figure 44: Class Diagram

WCU
4.3. Database Model

A database model is a type of data model that determines the logical structure of a database and
fundamentally determines in which manner data can be stored, organized and manipulated.
4.3.1 Entity Relationship Diagram (ERD)
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is an object, a component of data. An entity set is a collection of similar
entities. These entities can have attributes that define its properties. By defining the entities, their
attributes, and showing the relationships between them, an ER diagram illustrates the logical
structure of databases. ER diagrams are used to sketch out the design of a database.
1. User (Name, Role, Sex, user_ID, block no, office no, phone no)
2. Item (item code, item name, item type, quantity, price, Date, expiry date)
3. Request (ID, request detail, item type, item unit, amount requested, Date)
4. Transfer (from name, to name, item price, item unit, quantity, Date, transfer reason)
5. Stock clerk (user name, password, role)
6. Store keeper (user name, password, role)
7. College dean (user name, password, role)
8. AVP (user name, password, role)
9. Store Manager (user name, password, role)
10. President (user name, password, role)
11. Stock card (ID, reference no, received item, issued item, balance, item type, max level,
min level)
12. User card (dept name, block no, office no, item name, unit, quantity, item price)
13. Bin card (ID, reference no, qty received, qty issued, balance, item name, unit, min level,
max level, Date, Shelf no)
14. Notification (ID, title, content)
15. Account (ID, username, password)
16. System Admin (username, password, role)
17. Comment (ID, email, first name, last name, message)

WCU
Block_No
Type Item_Code Name Price Unit
Sex ID Username Password
Fname ID Phone_No Quantity
Office_No Record_date Balance
Ref_no SC_ID
Lname Name 1* Item
Staff Member request 1* 1* managed by 1 Stock Clerk 1 register Redeived Item
Role 1* 1* 1 1
1 1 Item code Stock card Issued Item
1 1* 1* transfer 1* 1
Title post
give Content 1 generate Item Detail
1* ID
search
1* Rep_ID * FName
1* LName
ID view 1* notification request_Date Report
Comment 1
has 1*
Email 1* Name
edit request_detail Title
1
update Message Request viewed by
viewed by itemtype Date Dep_Name
ID
request_ID 1*
Name 1 1*
content Item price
Fname Username User Card
item_unit ammount_req
1 System Admin office_no
1 Lname Phone User_ID
1 ammount_approved
Password Block_no Item name
Account 1*
approved by UC_ID
manage Unit
ID ID
Username Password ID
Username 1 1 1
Storekeeper 1 1 User_Name
Password College Dean AVP President Store Manager
1 Password
register
ID ID
ID Password
Issued_Quantity
Password
1* User_Name Password User_Name
Quantity User_Name
Bin_card Balance
received
Bin_ID
Item_code
item name
Date
Unit
Figure 45: Entity relationship diagram

WCU
4.3.2 Persistence Modeling

Persistent data management deals with how the persistent data such as file, database, etc. are
stored and managed and to outlive a single execution of the system. This Persistent data
management describes the persistent data stored by the system and the data management
infrastructure required for it. The proposed system will use MySQL database for storing data.
This will allow the database to be easily integrated and accessible by the rest of the system.
1
User
User_ID:varchar(20)
PK
1
UserName:varchar(45)
System_Admin
Password:varchar(45) Notification
ID:varchar(33)
1 PK * 1 Role:Varchar(30) PKNotification_ID:varchar(20)
UserName:varchar(45) * *
Fname:varchar(30) NotificationType:varchar(45)
Password:varchar(56)
Lname:varchar(35) NotificationContent:varchar(45)
Role:varchar(43)
Sex:(12)
Block_no:varchar(30)
Offce_no:varchar(30)
phone_no:varchar(15)
*
Comment 1
1 1
PKC_ID:varchar(20)
* Fname:varchar(45)
Lname:varchar(45)
message:varchar(500)
Email_address:varchar(50)
* * * *
Item Bin_card Report User_card Stock_card

PKItemCode:varchar(55) PKID:varchar(30) PK ID:varchar(30) PKID:varchar(30) PKID:varchar(30)
ItemType:varchar(45) QuantityReceived:varchar(23) ReportDate:Date() FKUser_ID:varchar(45) ReferenceNo:varchar(45)
* ItemName:varchar(45) IssuedProperty:varchar(45) ReportTitle:varchar(45) Fname:varchar(34) RegisterDate:Date()
Price:varchar(10) Balance:varchar(34) ReportContent:varchar(55) Lname:varchar(34) Balance:varchar(56)
Unit:varchar(66) DeptName:varchar(45)
Quantity:varchar(65) Block_no:varchar(45)
*
Expiry Date: Date()
RequestItem TransferItem
PK ID:varchar(30) PKID:varchar(30)
FK User_ID:varchar(30)
* FKUser_ID:varchar(30)
RequestDate:Date() FromName:varchar(45)
ToName:varchar(45)
TransferDate:Date()
Figure 46: Persistent diagram

WCU
Table Name Attribute Data Type Primary Key Foreign Key

Admin ID Varchar (45) ID
Username Varchar (45)
Password Varchar (45)
Role Varchar (45)
User First name Varchar (45) User_ID
Last name Varchar (45)
User name Varchar (45)
Password Varchar (45)
Role Varchar (45)
User_ID Varchar (45)
Sex Varchar (45)
Block_no Varchar (45)
Office no Varchar (45)
Request Request ID Varchar (45) Request ID User_ID
User_ID Varchar (45) Item_id
Request Date Date ()
Item name Varchar (45)
Amount requested Varchar (45)
Reason Varchar (45)
Item unit Varchar (45)
Transfer Transfer ID Varchar (45) Transfer ID User_ID
User_ID Varchar (45)
From Name Varchar (45)
To Name Varchar (45)
Transfer Date Date ()
amount Varchar (45)
Reason Varchar (45)
Item_Info Item Name Varchar (45) Item Code

WCU
Item Type Varchar (45)

Item Code Varchar (45)
Price Varchar (45)
Quantity Varchar (45)
Report Report ID Varchar (45) Report ID
Report Date Varchar (45)
Report Title Varchar (45)
Report Content Varchar (45)
User Card User Card_ID Varchar (45) User Card_ID User_ID
Serial no Varchar (45)
Employee Name Varchar (45)
Item category Varchar (45)
Office no Varchar (45)
Brand Varchar (45)
Amount Varchar (45)
Price Varchar (45)
Item condition Varchar (45)
Date Date ()
Bin Card Bin_ID Varchar (45) Bin_ID Item code
Quantity Received Varchar (45)
Quantity issued Varchar (45)
Item code Varchar (45)
Amount Varchar (45)
Date Date ()
Balance Varchar (45)
Stock Card StockCard_ID Varchar (45) StockCard_ID Item code
Amount Varchar (45)

WCU
Item Image Varchar (45)

Register Date Date ()
Item category Varchar (45)
Comment C_ID Varchar (45) C_ID
Email Varchar (45)
First Name Varchar (45)
Last Name Varchar (45)
Message Varchar (45)
Notification ID Varchar (45) ID
Content Varchar (45)
Title Varchar (45)
Table 21: Persistence Modelling
4.3.3 Mapping with Normalization

Normalization is a database design technique that reduces data redundancy and eliminates
undesirable characteristics like Insertion, Update and Deletion Anomalies. Normalization rules
divides larger tables into smaller tables and links them using relationships. The purpose of
Normalization in SQL is to eliminate redundant (repetitive) data and ensure data is stored
logically. There are three types of normalization rule:
 First normal form (1NF): An entity type is in 1NF when it contains no repeating groups
of data.
 Second normal form (2NF): An entity type is in 2NF when it is in 1NF and when all of
its non-key attributes are fully dependent on its primary key.
 Third normal form (3NF): An entity type is in 3NF when it is in 2NF and when all of
its attributes are directly dependent on the primary key.
First normal form:
Admin
ID User name Password Role

WCU
User
ID User Password Role Fname Lname Office Block Sex Phone

name no no no
The above table is not in 1NF, because a person may be having more than one phone number.
We can take example:
User
001 meSara ****** Staff Sara Samuel 0123 140 F 0987654321

member
0912345678
Not in the 1NF because single row contains two value
User

member

member
Now it fulfills 1NF
Request
ID Req_deatail Item name Amount Amount Date Item

requested approved unit
The above table is not in 1NF, because a person may be request more than one item with
different amount at a time. We can take example:
Request

WCU
005 For teaching Laptop 1 1 12/03/2013 Number
Marker 10 10 12/03/2013 number
Request
005 For teaching Laptop 1 1 12/03/2013 Number
005 For teaching marker 10 10 12/03/2013 Number
Now it fulfills 1NF
Transfer
ID User From To Date Item Item Item Quantity Reason

ID name name description price unit
The above table is not in 1NF, because a person may be transfer more than one item with
different quantity at a time. We can take example:
Transfer
sara Helen 18/05/2013 Dividers 463 Number 03 Replacement

of department
laptop 34000 Number 01
head
Transfer

WCU
Sara Helen 18/05/2013 Dividers 463 Number 03 Replacement

of department
head
Sara Helen 18/05/2013 Laptop 34000 Number 01 Replacement

of department
head
Now it fulfills 1NF
Notification
ID Title Content
Item
Item Item type Item name Item price Item Quantity Expiry
code unit date
The above table is not in 1NF because one item type may have different item name with
different quantity and price
Item
09875/pr laptop Dell 43000 Number 10 -
HP 23000 Number 5 -
Item
09875/pr laptop Dell 43000 Number 10 -

WCU
09875/pr laptop HP 23000 Number 5 -
Now it fulfills 1NF
User card
ID User Fname Lname Date Item price Item Quantity Reason Block Office
ID name unit no no
Bin card
ID Item Qty Qty Date Item Reference Item Min Max

code received issued description no unit level level
The above table is not in 1NF because one item description may have different Qty issued,
reference number in different date.
Bin card
843472 095/Pc 121256 6587 12/05/2013 Soap 459913 No Min Max

level level
3412 13/05/2013 459918 no
Bin card
843472 095/Pc 121256 6587 12/05/2013 Soap 459913 No - -
843472 095/Pc 121256 3412 13/05/2013 Soap 459918 no - -
Now it fulfills 1NF

WCU
Stock card
ID Item Received Issued Date Item Ref. Item Quantity Min Max
code item item name no unit level level
Report
ID Title Content Date
Comment
ID Fname Lname Email Message
The above table is not in 1NF, because a person may be having more than one email number. We
can take example:
Comment
008 Bekele Alemayewu Alexa@gmail.com I enjoyed the system. Thank you

for your service.
beki@gmail.com
Comment
008 Bekele Alemayewu Alexa@gmail.com I enjoyed the system. Thank you

for your service.
008 Bekele Alemayewu beki@gmail.com I enjoyed the system. Thank you

for your service.
Now it fulfills 1NF
Table 22: Table for 1NF

WCU
Second normal form
Transfer
ID User From To Date Item Item Item Quantity Reason

ID name name description price unit
The above table is not in 2NF because all non-key attribute is not fully dependent on keys
Transfer
ID From To Date Item Item Item Quantity Reason

name name description price unit
New created table
Transfer_ID User_ID
User card
ID User Fname Lname Date Item price Item Quantity Reason Block Office
ID name unit no no
User card
ID Date Item name Price Item unit Quantity Reason
User
User_ID Fname Lname Block no office

WCU
New created table
User Card_ID User_ID
Third normal form
Item
Item Item type Item name Item price Item unit Quantity Expiry date
code
The above table is not in 3NF because item price fully functionally dependent on item name
Item
Item Item type Item name Item unit Quantity Expiry date
code
New created table
Item code Item price
4.4. Subsystem Decomposition

Subsystem decompositions help to reduce the complexity of the system. The subsystems that we
take the classes that this system contains and the operation performed in the class. The following
are subsystems: -
A. Account subsystem: This subsystem responsible for managing of information regarding

account by taking care of login information of different users. It manages the name and
password of all users of the system for security purposes.
 Create Account
 Update Account
WCU
 Active Account
 Deactivate Account
B. Item subsystem: - this subsystem responsible for handle and records detail information
of the property
 Register new Item
 Update Item Information
 Remove Item Information
 Request Item
 Search Item
 Transfer Item
C. Report management subsystem: This subsystem responsible for managing report
 Generate Report
 View Report
D. Request tracking Subsystem: This subsystem is responsible for managing information
regarding a request
 Send Request
 Cancel Request
 Update Request
E. Comment subsystem: This subsystem responsible for management information of
comment
 Give Comment
 View comment
 Delete comment
F. Approval of request Subsystem: This subsystem responsible for handling information
of the notification
 Approve request
 Disapprove Request

WCU
LBSIMS
Account Item Info Report Request Comment Approval of request

Management Management Management Management Management Management
Subsystem Subsystem Subsystem Subsystem Subsystem Subsystem
Figure 47: Subsystem decomposition diagram
4.5. Deployment Diagram

It describes the physical architecture of the hardware and software in the system. They depict the
software components, processors, and devices that make up the system’s architecture.
Deployment modeling depicts a static view of the run-time configuration of processing nodes
and components that run on those nodes. And it shows: -
 The hardware for the system

 The software that is installed on the hardware
 Depict the hardware/network infrastructure of an organization.
 Depict a major deployment configuration of a business application.

WCU
Application Server Layer
Manage Account
View Comment
RequestItem
TransferItem
SearchItem
Client Side Browser
Database Server
Give Comment
System Admin
View Notice Security
Staff Member Update Account
Edit Request
Store Keeper
Register BinCard
LMSIMS
Stock Clerk DB
Register StockCard
Store Manager Register UserCard
College Dean ManageItemInfo
GenerateReport
AVP MYSQL
Database
View Report
President
Post Notice
ApproveRequest
DisapproveRequest
Figure 48: Deployment diagram
4.6. System Architecture (Layered Architecture of the System)

Our proposed system is consisting of 3-tier architecture namely presentation layer, business logic
layer, and the data layer. The presentation layer is the client layer and the topmost layer of the
application. This is the layer we see when we use this system. It is the interface to our system

WCU
which takes information from the user. The main function of this layer is to communicate with
the application layer. This layer passes the information given in terms of keyboard action and
mouse click to the application layer. In general clients of our system use browsers to access the
system using the WCU LAN, in this case when the user enters input and takes certain action
application server process client requests to interact with the database server. The reason why 3-
tier architecture is selected for this project is the following: -
 It provides an ease of maintenance of the code base, managing presentation code

and business logic separately, so that a change to business logic, for example,
does not impact the presentation layer.
 It gives the ability to update the technology stack of one tier, without impacting
other areas of the application.
 Because each tier can be managed or scaled independently, flexibility is
increased.
WCU LAN
Resource
Services
Client Server Business Logic

Database Server
HTTP
Queries
Desk Top Client Laptop Client
MYSQL
HTML
Data
Tablet Client Mobile Client
Server
Figure 49: System Architecture

WCU
4.7. User-Interface (UI) Design

User interface design or user interface engineering is the design of computers, appliances,
machines, mobile communication devices, software applications, and websites with the focus on
the user's experience and interaction. 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.
Figure 50: User interface design for Home page

WCU
Figure 51: User interface for Service

WCU
Figure 52: User interface for Comment

WCU
Figure 53: User interface design for Login
Figure 54: User interface for Register stock card

WCU
Figure 55: User interface For the Amharic service section sample
4.8. UI Flow Diagramming

User interface flow diagrams depict the user's interactions with software; these are defined with
use case. A use case can have many screens and gives information on how these screens are
being used. This information supports users draw a user interface flow diagram which shows the
behavior of the use case. Also, they make user to get high-level abstraction of the user interface
for an application. This represents the behavioral views derived from user's use cases.

WCU
Home Services Gallery Comment Help Login
Admin Stock Clerk Store Keeper Store Manager College Dean AVP President Staff Member
Create Account Generate Report Approve Request Approve Request Update Account
Register Bin Card Approve Request Approve Request
Activate Account Register User Card View Report Update Account

Update Account Update Account Request Item
Update Account
Deactivate Account Register Stock Card Request Item Update Account Request Item Transfer Item
Request Item Request Item
View Comment Update Account Transfer Item Request Item Transfer Item View Notice
Transfer Item Transfer Item
Request Item View Notice Transfer Item View Notice

View Notice View Notice
Transfer Item View Notice
Approve Request
Post Notice
Manage Item
Figure 56: User interface flow diagram

WCU
CHAPTER-5-
IMPLEMENTATION AND TESTING
5.1 Introduction
The Implementation Phase has one key activity: deploying the new system in its target
environment. Supporting actions include training end-users and preparing to turn the system over
to maintenance personnel. After this phase, the system enters the Operations and Maintenance
Phase for the remainder of the system’s operational life. Multiple-release projects require
multiple iterations of the Implementation Phase one for each release.
Implementation refers to the Coding of the all documents gathered starting from requirement
analysis to Design phase. So now, 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. For the implementation of this system the user must have a server on
which the system will be hosted.
The proposed LAN Based store information management system design overview is designed in
a way to provide a solution for the existing system problem by minimizing the workload of the
existing store management system and user of the system. It provides more efficient, reliable and
time-saving in the store management system. we define the design goals of the system and
decompose the system into smaller subsystems that it can be understandable.
5.2 Algorithm Design

Algorithm design for Login
Home page displayed
User click on Login link
System display Login page.

WCU
The user enters the user’s name, and password.

If user name and password are correct, then
If the user is a system administrator, then the system display system administrator page.
Else if the user is a stock clerk, then the system displays the stock clerk page.
Else if the user is a stock keeper, then the system displays a stock keeper page.
Else if the user is store manager, then the system displays the store manager page.
Else if the user is college dean, then the system displays the college dean page.
Else if the user is a staff member, then the system displays a staff member page.
Else user name and password is not correct, then system display error message and
redisplay login page.
Algorithm for Request item
Display home page.
Display Login page.
Fill user name, password in the appropriate place.
If the filled input is valid System provides user page.
System displays request form and Actor fills the form.
System Acknowledges and prompts the form.
End if Else if the actor doesn’t fill the form properly System displays an error message with
registration form.
5.3 Sample Code

Login sample code
<?php
require_once '../database/Database.php';
require_once '../interface/iLogin.php';
class Login extends Database implements iLogin
{
private $username;
private $password;

WCU
public function __construct()

{
parent::__construct();
if (session_status() == PHP_SESSION_NONE) {
session_start(); //start session if session not start
}
}
public function set_un_pwd($username, $password)
{
$this->username = $username;
$this->password = $password;
}
public function check_user()
{
//$type = 1;//1 = user 2 = admin
$at_inventory = 1; //1 if he or she is still working at inventorry
$sql = "SELECT *
FROM tbl_employee
WHERE emp_un = ?
AND emp_pass = ?
AND emp_at_inventory = ? ";
$result = $this->getRow($sql, [$this->username, $this->password, $at_inventory]);
return $result;
}
public function get_user_id()
{
$type = 1;
$at_inventory = 1; //1 if he or she is still working at inventorry
$sql = "SELECT emp_id FROM tbl_employee WHERE emp_un = ?
AND emp_pass = ?

WCU
AND pos_id = ?
AND emp_at_inventory = ? ";
$result = $this->getRow($sql, [$this->username, $this->password, $type, $at_inventory]);
return $result;
}
public function user_session()
{
if (!isset($_SESSION['user_logged_in'])) {
header('location: ../index.php');
}
}
public function clerk_session()
{
if (!isset($_SESSION['clerk_logged_in'])) {
}
}
public function smanager_session()
{
if (!isset($_SESSION['smanager_logged_in'])) {
}
}
public function dean_session()
{
if (!isset($_SESSION['dean_logged_in'])) {
}
}
public function keeper_session()

WCU
{
if (!isset($_SESSION['keeper_logged_in'])) {
}
}
public function user_logout()
{
unset($_SESSION['user_logged_in']);
header('location: ../login.php');
}
public function clerk_logout()
{
unset($_SESSION['clerk_logged_in']);
}
public function dean_logout()
{
unset($_SESSION['dean_logged_in']);
}
public function smanager_logout()
{
unset($_SESSION['smanager_logged_in']);
}
public function keeper_logout()
{
unset($_SESSION['keeper_logged_in']);
}

WCU
public function admin_session()

{
if (!isset($_SESSION['admin_logged_in'])) {
}
}
public function admin_logout()

{
unset($_SESSION['admin_logged_in']);
}
public function admin_data()
{
/*get admin user and password through session id*/
$at_inventory = 1; //1 means
$id = $_SESSION['admin_logged_in']; //
$sql = "SELECT * FROM tbl_employee WHERE emp_id = ? AND emp_at_inventory = ? ";
return $this->getRow($sql, [$id, $at_inventory]);
}
}
$login = new Login();
/* End of file Login.php */
Sample php Code for Register user card
<?php
require_once('../class/Item.php');
require_once('../class/Employee.php');
$employees = $employee->get_employees();
$categories = $item->item_categories();
$conditions = $item->item_conditions(); ?>

WCU
<div class="modal fade" id="modal-add-item">

<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-
hidden="true">×</button>
<h4 class="modal-title"><i class="fa fa-plus"></i>Add Item</h4>
</div>
<div class="modal-body">

<form class="form-horizontal" role="form" id="add-item-form">
<div class="form-group">
<label class="control-label col-sm-3" for="catID">Category:</label>
<div class="col-sm-3">
<select name="" class="btn btn-default" id="catID">
<?php foreach ($categories as $category) {
# code...
$catID = $category['cat_id'];
$catDesc = ucwords($category['cat_desc']); ?>
<option value="<?php echo $catID; ?>"><?php echo $catDesc;
?></option>}
<?php }//end foreach of category ?>
</select>
</div>
</div>
<label class="control-label col-sm-3" for="itemname">Item Name:</label>
<input type="text" class="form-control" id="itemname" placeholder="Enter Item Name"
autofocus>

WCU
</div>
</div>
<div class="form-group" id="sr">
<label class="control-label col-sm-3" for="serialNumber">Serial No.:</label>
<input type="text" class="form-control" id="serialNumber" placeholder="Enter Serial
No">
</div>
</div>
<div class="form-group" id="mn">
<label class="control-label col-sm-3" for="modelNumber">Model No.:</label>
<input type="text" class="form-control" id="modelNumber" placeholder="Enter Model
No">
</div>
</div>
<div class="form-group" id="b">
<label class="control-label col-sm-3" for="brand">Brand:</label>
<input type="text" class="form-control" id="brand" placeholder="Enter Brand">
</div>
</div>
<label class="control-label col-sm-3" for="amount">Amount:</label>
<input type="number" step="any" class="form-control" id="amount" placeholder="Enter
Amount">
</div>
</div>

WCU
<label class="control-label col-sm-3" for="purDate">Purchase Date:</label>

<input type="date" class="form-control" id="purDate">
</div>
</div>
<label class="control-label col-sm-3" for="empID">Employee:</label>
<select class="btn btn-default" id="empID">
<?php foreach ($employees as $empployee) {
# code..
$fN = $empployee['emp_fname'];
$mN = $empployee['emp_mname'];
$lN = $empployee['emp_lname'];
$fullName = "$fN $mN $lN";
$fullName = ucwords($fullName);
$emp_id = $empployee['emp_id']; ?>
<option value="<?php echo $emp_id; ?>"><?php echo $fullName; ?></option>}
<?php }//end foreach ?>
</select>
</div>
</div>

<label class="control-label col-sm-3" for="conID">Condition:</label>
<select name="" class="btn btn-default" id="conID" disabled>
<option value="4">Working</option>}
</select>
</div>

WCU
</div>
<div class="col-sm-offset-2 col-sm-10">
<button type="button" class="btn btn-default" data-dismiss="modal">Close
</button>&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp
<button type="submit" id="btn-submit" value="add" class="btn btn-primary">Save
<span class="glyphicon glyphicon-saved" aria-hidden="true"></span> </button>
</div>
</div>
</form>

</div>
</div>
</div>
</div>
Employee.php class sample code
<?php
require_once('../database/Database.php');
require_once('../interface/iEmployee.php');
class Employee extends Database implements iEmployee {
public function __construct()
{
parent:: __construct();
}
public function my_session_start()

{
if(session_status() == PHP_SESSION_NONE)
{
session_start();//start session if session not start

WCU
}
}
public function insert_employee($fN, $mN, $lN, $pos, $off, $type)
{
$un = $fN.'_'.$lN;
$pass = $fN.'_'.$lN;
$pass = ($pass);
$fN = ucwords($fN);
$mN = ucwords($mN);
$lN = ucwords($lN);
$sql = "INSERT INTO tbl_employee
(emp_fname, emp_mname, emp_lname, pos_id, off_id, type_id, emp_un, emp_pass)
VALUES(?, ?, ?, ?, ?, ?, ?, ?);";
return $this->insertRow($sql, [$fN, $mN, $lN, $pos, $off, $type, $un, $pass]);
}
public function update_employee($fN, $mN, $lN, $pos, $off, $type, $eid)
{
$sql = "UPDATE tbl_employee SET emp_fname = ?, emp_mname = ?, emp_lname = ?, pos_id
= ?, off_id = ?, type_id = ?
WHERE emp_id = ?; ";
return $this->updateRow($sql, [$fN, $mN, $lN, $pos, $off, $type, $eid]);
}
public function get_employee($emp_id)
{
$sql = "SELECT *
FROM tbl_employee e
INNER JOIN tbl_pos p
ON e.pos_id = p.pos_id
INNER JOIN tbl_off o
ON e.off_id = o.off_id

WCU
INNER JOIN tbl_emp_type t

ON e.type_id = t.type_id
WHERE e.emp_id = ?
ORDER BY e.emp_fname; ";
return $this->getRow($sql, [$emp_id]);
}
public function get_employees($inner_joined = false)
{
$still_work_here = true;
if(!$inner_joined){
$sql = "SELECT *
FROM tbl_employee
WHERE emp_at_inventory = ?
ORDER BY emp_fname; ";
return $this->getRows($sql, [$still_work_here]);
}else{
//get all including FK
$sql = "SELECT *
FROM tbl_employee e
INNER JOIN tbl_pos p
ON e.pos_id = p.pos_id
INNER JOIN tbl_off o
ON e.off_id = o.off_id
INNER JOIN tbl_emp_type t
ON e.type_id = t.type_id
WHERE e.emp_at_inventory = ?
ORDER BY e.emp_fname;";
return $this->getRows($sql, [$still_work_here]);
}
}

WCU
public function employee_positions()

{
$sql = "SELECT * FROM tbl_pos;";
return $this->getRows($sql);
}
public function employee_offices()
{
$sql = "SELECT * FROM tbl_off;";
}
public function employee_account_types()
{
$sql = "SELECT * FROM tbl_emp_type;";
}
public function employee_remove_undo($at_inventory, $eid)
{
$sql = "UPDATE tbl_employee
SET emp_at_inventory = ?
WHERE emp_id = ?; ";
return $this->updateRow($sql, [$at_inventory, $eid]);
}
public function insert_employee_position($position)
{
$sql = "INSERT INTO tbl_pos(pos_desc) VALUES(?); ";
return $this->insertRow($sql, [$position]);
}
public function insert_employee_office($office)
{
$sql="INSERT INTO tbl_off(off_desc) VALUES(?); ";

WCU
return $this->insertRow($sql, [$office]);

}
public function change_employee_password($id, $un, $pwd)
{
SET emp_un = ?, emp_pass = ?
WHERE emp_id = ?;
";
return $this->updateRow($sql, [$un, $pwd, $id]);
}
public function item_owned()
{
/*
*this function select all the user login owned items
* 3 or Condemed
*/
$condition = 1;
$status = 4;//must =
$this->my_session_start();
$uid = $_SESSION['user_logged_in'];
$sql = "SELECT *
FROM tbl_item i
INNER JOIN tbl_cat c
ON i.cat_id = c.cat_id
INNER JOIN tbl_con co
ON i.con_id = co.con_id
INNER JOIN tbl_item_status s
ON i.status_id = s.status_id
WHERE i.emp_id = ?
AND i.con_id = ?

WCU
AND i.status_id = ?";

$result = $this->getRows($sql, [$uid, $condition, $status]);
return $result;
}
public function update_admin_data($un, $pass)
{
$this->my_session_start();
$id = $_SESSION['admin_logged_in'];
$pass = md5($pass);
SET emp_un = ?, emp_pass = ?
WHERE emp_id = ?;
";
return $this->insertRow($sql, [$un, $pass, $id]);
}//end update_admin
}
$employee = new Employee();

/* End of file Employee.php */
?>
5.4 Testing
Testing is a process to show the correctness of the program. It will be the final phase after system
implementation. Once code has begun, the testing process can begin and proceed in parallel as
each program module is produced, it can be tested individually. We test its efficiency in different
testing mechanisms.
5.4.1 Unit Testing

Unit-testing: Unit testing, we tested this project, an individual module or component like for
login to the system, create account and register item to ensure that it works according to its

WCU
predetermined specifications, operates within acceptable parameters. In this level of testing

process Sample Tests that we do:
 Check whether the return type of functions is correct.

 Check how the sub-procedures or functions are called correctly.
 Check if the correct output is produced for different inputs.
Some of errors that controls are
When the login field input is incorrect, the system will display the following message.
Figure 57: Unit testing for login page
5.4.2 Integration Testing

Integration testing: In this level of testing, we examine how the different procedures work
together to achieve the goal of the subsystem. We will test the module transfer item, request item
to ensure their fulfillment of the subsystem functionality. Then we integrate each component
from single functionality (individual interface) to the main function incrementally.
Sample Tests we be done:
 Check the interaction between individual functionality which performs the specific tasks.
 Evaluate the functionality of the subsystem after combination all individual functionality.
 Identify the Independence of each subsystem with other subsystems.

WCU
5.4.3 System Testing

System testing: In this level of the testing process, we have examined how the whole store
management subsystems came together to achieve the desired goal (user’s requirements of the
system). The goals of system testing are to detect faults that can only be exposed by testing the
entire integrated system or some major part of it. Sample Tests we be done:
 Evaluate the functionality of the subsystem after a combination of individual subsystems

whether it works correctly or not.
 Check the coherence and coupling of each subsystem.
 Check the interaction of each subsystem that performs the specified business process.
 Verify the store management system completeness-based on user’s requirement.
5.5 User-Manual
The User Manual contains all essential information for the user to make full use of the
information system. This manual includes a description of the system functions and capabilities,
contingencies and alternate modes of operation, and step-by-step procedures for system access
and use. We used graphics where possible in this manual. The manual format may be altered if
another format is more suitable for the particular project.
This manual helps all the users of this system by guiding the steps what they want to do
according to their authorities. To access our site first user should install the browser and then
type on the search engine the internet protocol address of the site of
http://192.168.1.246:80/LBSIMS/index.html or by using the WCU LAN IP address. Then if the
user is already registered, they can put their Username and password in the login page.

WCU
Fill user name and

password. The eye
icon changes the
hidden password
value into visible
Figure 58: User manual for login page

If you want to request and transfer an item by using this system you must to login first and also
the system checks the item availability. To have an account you must be an employee at WCU.
After that the user page is displayed and if you click order asset, request form is displayed and if
you click transfer link transfer form is displayed then fill your information properly.
Fill the form and click

submit form button.

WCU
Figure 59: user manual for request item form
Fill the form and click

transfer button.
Figure 60: User manual for transfer assets form
The system shall allow the stock clerk and store manager to
see and print report

WCU
Figure 61:User manual Report print
User can see item with

their details
information before
they order it
Figure 62: User manual for view item detail
Click here to accept transfer
Figure 63: User manual for accept transfer
5.6 User Training
User training helps the user in operating the system in efficient way. During the training a
manual is given to every user so that they can understand the problem and solved it. The content
of training is about the use of data that how they can edit, add, query and delete the records.
records. If a user has not sufficient capability of working on system, then many kinds of errors
and problems can occur.
5.7 Start-Up
Once the system is hosted, it has two start-up strategies: the first start-up strategy is for the
administrator, stock clerk, store Manager, staff member, college dean and store keeper which

WCU
require the username and password to access the system. The user’s accessibility part is
restricted for the users and the other one is for system administrator. The second start-up strategy
part is the system home page and other link like if they need to know about services provided
this system which does not require the username and password and it can be viewed by anybody

WCU
CHAPTER SIX
Conclusion and Recommendations
6.1. Conclusion
The project titled as LAN Based store information management system is a LAN based
application. This software provides facility sending support request through LAN, take generate
report, it enables for restoring exporting database, it enables for system administrator to view log
file, evaluate the support request. This software is developed with scalability in mind. Additional
modules can be easily added when necessary. The software is developed with modular approach.
Thus, the system has fulfilled some of the objectives identified and is able to replace the existing
system.
6.2 Recommendation
The system that we develop is a LAN Based store information management system for WCU
makes Through LAN each task. While doing this system the team members has faced different
challenges. But by the cooperation of all the group members the team is now able to reach to the
final result. i.e. all the group members strongly fight these challenge and take the turn to the
front. We strongly recommend for our new system has provide a better service than the existing
system by forming better interaction among them. Our recommendation to other system
developers is that to develop an android part for the system.

WCU
References
Bainson, B. a. (February,2016). Efficient Store Managment-A case study on Takoradi polytechnc
stores Department. Busness and Managment Review, 33-46.
Dias, N. D. (August ,2017). Web-based Applications: Extending the General Perspective of the .
Dias, N. R. (2017). Web-based Application:Extending the General Perspective of the Service of

Web.
Gibb, R. (2016, May 13). blog.stackpath.com. Retrieved from Web application:

blog.stackpath.com/web-application
Melendres, U. (2021,January). Development of Dyanamic Local Area Network(LAN).

International journal of computing research science.
Punam Khobragade, R. S. (Apr 2018). Inventory management system. International Research

Journal of Engineering and Technology (IRJET).
Sabbu. (2013,Apr). Book store Managment system.
satyendra. (2015, March 28). Store Managment. Retrieved from Ispat Guru:
http://ispatguru.com/store-managment
sdlc-models. (2017, August). Retrieved from existtek.com: existtek.com/blog/sdlc-models
Sushil Kumar and Rajeev Sunam, N. G. (2014, March 13). Store Managment for Implementing
ERP in Manufacturing Organization. ResearchGate.
wcu.edu.et. (2021, Mar 13). Retrieved from wcu.edu.et:

http://www.wcu.edu.et/missionvision.aspx
wcu.edu.et. (2021, Mar 13). Retrieved from wcu.edu.et: http://www.wcu.edu.et/Background.aspx

WCU
Appendix
Interview question
Question 1: - Who are the user of the existing system?
Question 2: -What are the major functions of the existing system?
Question 3: -What are the drawbacks of the existing system?
Question 4: - What are the Forms and Documents of the Existing Systems?
Question 5: - What are the business rule of the existing system?

LAN-Based Store Management System for Wachemo University

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LAN-Based Store Management System for Wachemo University

Uploaded by

Copyright:

Available Formats

WACHEMO UNIVERSITY

COLLEGE OF ENGINEERING AND TECHNOLOGY

SCHOOL OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION SYSTEMS

Project Title “LAN-Based Store Information Management System For WCU”

Name of Students Signature Date

1. Fetiya Kedir ____________ ____________

Final year project Documentation Page i

Name of Students Signature Date

1. Fetiya Kedir ____________ ____________

Name of program coordinator Signature

Name Signature Date

the college of the university

Final year project Documentation Page ii

Final year project Documentation Page iii

Final year project Documentation Page iv

Final year project Documentation Page v

List of Abbreviation ....................................................................................................................... iv

List of Tables ................................................................................................................................. xi

List of Figure................................................................................................................................. xii

Chapter One .................................................................................................................................. 1

Introduction to The System.......................................................................................................... 1

1.1 Introduction .......................................................................................................................... 1

1.2 Background .......................................................................................................................... 2

1.2.1 Background of the Organization .........................................................................................2

1.2.1.1. Vision .................................................................................................................... 3

1.2.1.2. Mission .................................................................................................................. 3

1.2.2. Background of the Project .............................................................................................4

1.3. Statement of the problem ..................................................................................................... 4

1.4. Objectives of the Project ...................................................................................................... 5

1.4.2. General objective ...........................................................................................................5

1.4.3. Specific objective ..........................................................................................................5

1.5. Proposed system................................................................................................................... 6

1.6. Literature Review and Related Work .................................................................................. 7

1.7. Scope and Limitation of the project ................................................................................... 10

1.7.2. Scope of the Project .....................................................................................................10

1.7.3. Limitation of the Project ..............................................................................................10

1.8. Methodology ...................................................................................................................... 10

Final year project Documentation Page vi

1.8.1. Data Collection Tools/Techniques ..............................................................................10

1.8.2. Data Analysis ..............................................................................................................11

1.8.3. System Development model ........................................................................................12

1.8.4. Implementation of the proposed system ......................................................................13

1.8.5. System development tools (Hardware and Software tools) ........................................15

1.9. Significance of the Study ................................................................................................... 16

1.10. Beneficiaries of the System ............................................................................................ 17

1.11. Feasibility Study............................................................................................................. 17

1.11.1. Technical Feasibility ...................................................................................................17

1.11.2. Operational Feasibility ................................................................................................18

1.11.3. Economic Feasibility ...................................................................................................18

1.11.4. Legal feasibility ...........................................................................................................19

1.11.5. Time feasibility............................................................................................................19

1.12. Project Organization ....................................................................................................... 19

1.13. Project Plan .................................................................................................................... 20

1.13.1. Time Schedule .............................................................................................................20

1.13.2. Budget Plan .................................................................................................................20

Chapter -Two- ............................................................................................................................. 22

Description of The Existing System or Application ................................................................. 22

2.1. Introduction ........................................................................................................................ 22

2.2. Business Rule and Constraint ............................................................................................ 22

2.2.1. Business Rule of Existing System ...................................................................................23

2.2.2. Constraint .........................................................................................................................24

2.3. Naming Convention and Definition ....................................................................................... 24

1. Fetiya Kedir

1. Fetiya Kedir