Professional Documents
Culture Documents
PROPOSAL
PROPOSAL
Project Title: - web based inventory management system For Wachemo University Durame
Campus
Proposal done :
DURAME, ETHIOPIA
Table of Contents
CHAPTER 1………………………………………………………………………………………………………………………………………1
1.1 INTRODUCTION.....................................................................................................................................1
1.2 Statement of the problem.....................................................................................................................3
1.3 Objective of the Project.........................................................................................................................4
1.3.1. General Objective..........................................................................................................................4
1.3.2. Specific Objective...........................................................................................................................4
1.4 Scope of Project.....................................................................................................................................5
1.5 Method and Tools.................................................................................................................................5
1.5.1 Data source and Data collection methods......................................................................................5
1.5.2 System analysis and design methods..............................................................................................6
1.5.3 System Implementation Methods..................................................................................................6
1.5.4 Development Environment and Programming Tools......................................................................7
1.5.4.1 Hardware tools........................................................................................................................7
1.5.4.2 Software tools..........................................................................................................................7
1.5.4.3 Programming language............................................................................................................8
1.7 Significance of the project.....................................................................................................................8
1.8 Beneficiaries of the System...................................................................................................................9
1.9 Project Team Organization..................................................................................................................10
1.10 feasibility analysis…………………………………………………………………………………………………………………….…8
An inventory is the stock of items used in an organization. An inventory system monitors the
levels of inventory and determines the recording of items and distributing the materials to the
staff based on the request of users. But, currently Wachemo University Durame Campus
property administration directorate performs recording items, managing, requesting materials,
register supplier through manually this leads to time consuming, error prone and boring. In order
to solve this problem, the team motivated to develop a web based inventory management system.
The implementation of this web-based inventory system can help the Campus to develop the
skills to handle with their operational environments. Because lack of system tool to be used to
monitor the availability and quantity of materials in this campus
Interview: To get information, interview with the store head will be conducted with
concerned staff of the corporation to get reliable information which is important to do the
project.
Observation: It helps us to get the right information how the organization performs its
function and this helps to strength the data that gathered through interview and document
analysis.
Document Analysis: This technique provides information on how the existing system
works .There for documents related to the existing system of the organization will be
assessed.
An iterative life cycle model does not attempt to start with a full specification of requirements.
Instead, development begins by specifying and implementing just part of the software, which is
then reviewed to identify further requirements. This process is then repeated, producing a new
version of the software at the end of each iteration of the model.
1.5.4 Development Environment and Programming Tools
There are different hardware’s, software’s and programing language individual use in the project.
1.5.4.1 Hardware tools
Computer with internet connection:- almost all tasks of our project are performed on
computer.
Secondary storage device like flash disk (32GB) and CD required for data movement and
store.
Memory :8GB RAM
Hard disk :797GB
Disk (CD):-necessary for the store of relevant data and for backup Pen and Paper: used
for write different question and resource.
A4 paper: used to write necessary data during data gather process.
1.5.4.2 Software tools
There are different kinds of software will be used to develop the project is:
Java script language: - used to validate our data or for client-side scripting.
For university(organization)
Reduce economy spend.
Users
Getting service without wasting their time.
Employees
Work their job without any difficulties.
Increasing their confidence.
Developers
Firstly we are getting a bachelor degree by developing this system.
Since it is the first time for us to prepare the whole document with the implementation that is the
base for our group to have an experience for developing software. So, from the project we gained
knowledge how to develop a system and solve the real world problem.
Nov
No Steps Nov1-16 De 03- Dec Fe Ma App May June
17-
18 19-Jan b r
Dec
12
02
1 Proposal
preparation and
Presentation
3 System analysis
4 System design
5 Implementation
6 Testing
7 Documentation
1.11.2 Budget Plan
No Terms Quantity total price birr
1 Laptop 1 25,000
4 Pen 5 50
5 Flash 1 400
6 CD RW 1 50
7 Total 26,100
Chapter two
Register supplier: register supplier organization to supply item for the organization.
Register new items: the new items are register before enter to the store.
Register item withdraws: the item is register after give to collage, department, employee
and office.
Register item transfer between two employees: during item transfer from one employee
to another it must register.
Approve clearance: when an employee is leave out from staff member he/she must fill the
clearance form.
Prepare report like damaged item, new item, withdraw item: reports are prepared based
on the category.
2.4 Business Rules and constraints
A business rule is successfully an operating standard or polices that we have try to specify for
both the existing system and the proposed system of the store management must satisfy.
A business rule is an operating principle or policy the software must satisfy. It often concern to
access control issues, policies and principles of the inventory management system.
The existing system has many business rules or principles some of them are:
Br1: new items are recorded and assigned a code by the stock clerks.
Br2: after recording and assigning code by the store clerk the items led to the store keeper then
he/she record, check and place them.
Br3: only staff members of the university are allowed to take an authenticated material.
Br4: when the users/staffs want to borrow any material he/she must register his id, full name,
email, status and other user details properly.
Br5: in order to get the item he /she must get permission from the academic president /president
and the store officer have to put their signature.
Br6: the staff member has to put his/her signature while taking the item.
Br8: if the staff member has loss or damage the item he/she has to replace that item or pay the
cost with additional percent
Br9: one employee to fill clearance first checked either any material with him/her or not.
Current System constraints: the manual system has the following problems
Security
Performance
Report generated in the existing system
In the current system, report is generated by consolidating all the data gathered by the employee
in the form of paper, after which the report will be submitted to the inventory level and to be
forwarded to the manager.
2.7.4 Efficiency
The overall efficiency of current system is not efficient. Since, the organization is using a semi
manual system there is a problem in providing service to the customers. Some of them are:
It needs more human power and time for selling products because of its low ability
to serve many customers at a time in their office.
The current system is not capable of serving many customers at a time.
When you are client esteemed you need to use the best technology to achieve
sustainability in your business. Most organizations have a lot of territories to
improve, particularly in their stockrooms. By following stock management best
practices, you'll run a proficient and compelling business.
Yet, if you don't start the way toward overhauling and smoothing out your business
activities now, you'll effectively fall back into terrible behavior patterns, wasteful
practices, and a significant expense of stock.
Below we have mentioned inventory optimization and management best practices
that can help your business. But first of all, let us know the basics of inventory
management
After the team has identified the real problem of the existing system which is in a manual
system, the team suggests an alternative option to overcome the problem.
The alternative solution is:-
Since the team are going to develop computerizing inventory management system that used by
the employee’s in the university, the system is used to manage and process data according to the
System.
Manage Account: The admin create, update, delete, view and activate/deactivate user
account the system shall to allow the system administrator can handle or manage all
system users’ account.
Login and logout into the system: -the system shall to support all system uses to login
and logout to the system.
Manage Items:-The store keeper register, update, view and delete Item.
Withdraw Item.
Transfer Item
Generate Report
View Report.
Approve Request
Request Item
Post Bid
Check Bin Cards
Send Feedback
View Comment
Post Bin Cards
View Feedback
Post Comment .
2.Non-Functional Requirements
Non-functional requirement describes the necessities of the computerized inventory management
system that are not directly related to the functionalities of the proposed system and any
constraints that may limit the boundaries of the proposed system. In short, non-functional
requirement is all about system attributes such as security, reliability, usability, integrity and so
on.
Security:-The system only permits authorized user to enter the system. Security is the
protection of the information assets through the use of technologies, processes, and training.
Access to the various subsystems will be protected by a user login screen that requires user
name and password.
User Interface: The interface is user friendly and can properly guide the user how to use the
system and perform operations easily.
Response time: - the system gives response to service request within a short period of times.
Availability: -This system should always be available for users to access item information.
Maintenance: The Inventory Management System is being developed in php. Php is an object
oriented programming language and shall be easy to maintain
Reliability: - The Inventory Management System service should not access without authenticate
user.
Standards Compliance: - The graphical user interface of the system shall have easily
understood to the user (have consistent look and feel graphical user interface).
. Actor Identification
Actors: An actor is a person, organization, or external system that plays a role in one or
more interactions with in the system.
We use Actor as user that interacts with system.
In inventory management system the following actors are involve: There are Four major
actors in our proposed system. These are:-
System administer
Inventory Director
Store Keeper
Staff member
3.4.2. Use-case identification
Use cases: A use case describes a sequence of actions that provide something of
measurable value to an actor.
Identifying the activities that are mainly performed on the proposed system is the
basic thing in analyzing a new system.
Admin: have the following activities
Manage Account(Create, Delete, Active/Deactivate, Update,)
Approve Request
Generate Report
View Report