Warehouse Management System

Warehouse Management System
A Project Report On
MAHARAJA KRISHNAKUMARSINHJI
BHAVNAGAR UNIVERSITY
Submitted To:
Shree Adarsh bca College-BOTAD
B.C.A. (Sem-6):
Academic Year 2019-2020
Prepared By:
Makani Amee B.
Project Guided:
Pratvi lavingiya
Page 1
Warehouse
Management System
Page 2
INDEX
Chapter no Content Page no
1 Introduction 5
• introduction to project 5
• Background 8
• Objective 9
• Purpose 9
• Scope 10
• Applicability 10
2 Requirement and Analysis 11

• Problem definition 12
• Requirement specification 13
• Hardwar software requirement 14
• Planning and scheduling 15
3 System Design 16
• Over all system design using Designing tools 17
• Data Dictionary 24
• Input/Output Design 28
4 Testing And Implementation 44

• Testing Approach Used 45
• Test Cases 49
• Implementation Approaches 51
5 Conclusion 52
• Limitation Of System 54
• Future Scope Of System 54
• Bibliography 55
Page 3
• Acknowledgment
It is a great pleasure for us to acknowledge all those who have contributed towards the
conception, origin and nurturing of this project that is on System analysis and designing of the
“Warehouse Management System”.
This way can’t walk itself. We have to walk on it. For that we must have a guide. Many
guides have contributed to the successful completion of the Project. We would like to place on
record my grateful thanks to each one of them who help me in this project.
Our grateful thanks go to our Department, which provides me an opportunity as a project

subject in 6th Semester to develop a report work skill in this System designing and analyzing.
We would like to thanks our parents and friends for giving us full feedback when we are in
trouble. I am sincerely thankful to Assistant Prof. Ms. Pratvi lavingiya(Internal Guide) and the
whole staff of SHREE ADARSH BCA COLLEGE, BOTAD, for their extensive help and for
providing valuable information, suggestions, and inputs at various stages of work.
With sincere regards,

➢ Makani Amee B.
➢ Gotrija Shivani D
Page 4
Chapter:-1
INTRODUCTION
Page 5
• Introduction
A Warehouse Management
System (WMS) is a software application
specializing in supporting the day to day
operations within a warehouse.Warehouse
Management system provide a set
of computerized procedures for
manageme of warehouse inventory,
space,equipment,workers,and people with
the goal of minimizing cost and
fulfillment time. Warehouse is nothing but selling and transaction their stock between
people. Warehouse is a flow of so many processes ranging from procuring goods to
correct delivery of finished products.This project mainly concerns about management
of procuring goods, which is a main part of trading system. Successful trading allows
an enterprise to anticipate demand and deliver the right product to the right place at the
right time at the lowest possible cost to satisfy its customers The application does this
by allowing the users to have a centralized system where different warehouse
management tasks are managed through an interface on a handheld device or a tablet
working in the warehouse or a desktop in the office. This makes running a warehouse
both efficient and easy, and also ensures that minimal if any losses occur in the
different warehouse processes. The real gain is in customer service. Imagine knowing
exactly where every product is, knowing when to re-order, and how much to re-order or
produce. These things seem like a business goal, but for a customer it means they can
get the product faster, without backorders or errors, so they are more likely to return.
This includes:
• Arranging the warehouse and its inventory.
• Having and maintaining the appropriate equipment.
• Managing new stock coming into the facility.
• Picking, packing and shipping orders.
• Tracking and improving overall warehouse performance.
Page 6
➢ There are five types of warehouses as described below
Private Warehouses:
The warehouses which are owned and managed by the
manufacturers or traders to store, exclusively, their own stock of goods are known as
private warehouses. Generally these warehouses are constructed by the farmers near
their fields , by wholesalers and retailers near their business centres and by
Manufactures near their factories. The design and the facilities are provided there
according to the nature of products to be stored.
Public Warehouses
The warehouses which are run to store goods of the general

public are known as public warehouses. Anyone can store his goods in these
warehouses on payment of rent. An individual, a partnership firm or a company may
own these warehouses. To start such warehouses a licence from the government is
required. The government also regulates the functions and operations of these
warehouses. Mostly these warehouses are used by manufacturers, wholesalers,
exporters,importers,government,agency,etc.
Bonded Warehouses
These warehouses are owned, managed and controlled by
government as well as private agencies. Private bonded warehouses have to obtain
licence from the government. Bonded warehouses are used to store imported goods
for which import duty is yet to be paid. In case of imported goods the importers are
not allowed to take away the goods from the ports till such duty is paid. These
warehouses are generally owned by dock authorities and found near the ports.
Government Warehouses
These warehouses are owned, managed and controlled

by central or state governments or public corporations or local authorities. Both
government and private enterprises may use these warehouses to store their goods.
Central Warehousing Corporation of India, State Warehousing Corporation and Food
Corporation of India are examples of agencies maintaining government warehouses.
Co-operative Warehouses
These warehouses are owned, managed and controlled
by co-operative societies. They provide warehousing facilities at the most economical
rates to the members of their society.
Page 7
• Background
❖ Front End
ASP.NET
ASP.NET is an open-source server-side web application framework Designed for
web development to produce dynamic web pages developed by Microsoft to allow programmer
to built dynamic web sites,applications and services.
The ASP.NET application

codes can be written in any
of the following languages:
✓ C#
✓ Visual Basic.Net
✓ Jscript
✓ J#
Visual Basic.Net
Visual basic.Net (VB.NET) is a multiparadigm,object-oriented programming
language,implemented on the .NET Framework.Microsoft launched VB.NET in 2002 as the
successor to its original Visual Basic language.
Page 8
❖ Back End
SQL Server
SQL Server is Microsoft's relational database
management system (RDBMS). It is a full-
featured database primarily designed to compete
against competitors Oracle Database (DB) and
MySQL.
SQL Server is sometimes referred to as MSSQL

and Microsoft SQL Server.
• Objective of WMS
➢ provide timely customer service.

➢ Keep track of items so they can be found readily & correctly.
➢ Minimize the total physical effort& thus the cost of moving goods into & out of storage.
➢ Provide the communication links with a customer.
➢ To maintain the flow of goods throughout the system, these goods may be raw materials or
finished products.
• Purpose of WMS
➢ WMS provide a set of computerized procedures for management of

Warehouse inventory , space , equipment , and people with the goal of
Minimizing cost and fulfillment time.
➢ To make easy for Tracking Stock in warehouse. This System helps for their time
management, Customer expectations, Redundant Processes, Globalization, etc. this type of
problems are arise.
➢ We can manage stock as per their requirements. We can modify as per customer
requirement, their all data store in database and we can fetch data from database and show
to user and admin.
➢ A warehouse management system’s primary purpose is to maintain the proper balance of

inventory.
Page 9
• Scope of WMS
➢ To implement visual basic .net languages.

➢ To help the student information in its efficient management.
➢ To store the databases of the warehouse management.
➢ All registration details are stored in files on stable storage.
➢ To store the shop’s information.
➢ To secure the internal database.
➢ To have a faster, easier to search a details.
➢ For doing work more accurately
• Applicability
➢ A warehouse management system (WMS) is a software application that helps control and
manage the day-to-day operations in a warehouse. WMS software guides inventory
receiving and put-away, optimizes picking and shipping of orders and advises on inventory
replenishment.
➢ This WMS website can be also providing information about the How many stock store in
warehouse.
➢ The WMS web application can be used by any customer to store stock in warehouse and
receiving stock in warehouse
Page
10
Chapter:-2
REQUIREMENT AND ANALYSIS
Page
11
• Problem Definition
o The seller will not have much of chose between buyers and the buyer also does not
get many options in getting a old product .if item does not sell them we can not get
our selected price.
o Currently their daily works on books and papers their monthly works such as stock
management, branch detail, daily stock, warehouse etc…
o Existing system is a time consuming process because it will take time for seller to
spread the news of its selling product to the near locality and this system is tough to
get the data and stock to be managed.
• Proposed System
o To make easy for Warehouse Management System to find to Find Stock in
Warehouse.
o To make easy for Tracking Stock in warehouse. This System helps for their time
management, Customer expectations, Redundant Processes, Globalization, etc. this
type of problems are arise.
o We can manage stock as per their requirements. We can modify as per customer
requirement, their all data store in database and we can fetch data from database and
show to user and admin.
o We can convert and move the stock from one warehouse to other warehouse and
this all details are stored and it is secure. And we must check all the data as per
stock in warehouse.
o Easy to store data of Product, Customer, Supplier, Stock etc. all this details are fetch
and it should show in the system as report and it shows to user the details of stock,
customer, supplier etc.
❖ Benefits of the proposed system
1. Easy to modify construction detail

2. Manage inquiry and stock
3. Time management
4. Manage Customer and supplier Product details easily.
Page
12
• Requirement Specification:
Functional Requirement:
The system aims at providing an efficient interface to the user for managing of warehouse;
it shall also provide the user varied options for managing the warehouse through various
functions at hand. The design is such that the user does not have to manually update the
warehouse every time, the system does it for the user.
The system calculates and predicts the amount of usage for specific set days that are pre-set
by admin. Therefore the user never has worry about the manually calculating the stock
because the system has done it automatically
The simple interface of the system has functions like adding a recipe, removing or updating
the recipe. It also extend to functions such as adding a item in a warehouse, removing the
item, checking threshold levels, processing orders, altering processed orders etc…
Nonfunctional Requirement:
➢ Usability
o The system must be quickly accessible by both manager and chefs.
o The menus of the system must be easily navigable by the users with buttons
that are easy to understand.
➢ Reliability
o The System must successfully add any recipe, ingredients, vendors or special
occasions given by the user and provide estimations and inventory status in
Relevance with the newly updated entities.
➢ Performance
o The system must not lag, because the workers using it don‟t have down time
to wait for it to complete an action
o All the functions of the system must be available to the user every time the
system is turned on.
➢ Supportability
o The system is designed such that it works even on systems having the minimum
configuration.
➢ Packaging
o The packaging must come with a manual that details the use of the system, and
also the instruction on how to use the program.
➢ Implementation
o The system user interface is built on Microsoft Visual Studio 2008.
o The programming is done in Microsoft Visual Studio 2008.
o The database implemented on the my SQL server 2008.
Page
13
• Hardware Software Requirement:
Software
Front End ASP.NET(Visual Studio 2008)
Back End Microsoft SQL Server
Programming language Visual basic.net
Operating system Window XP,Window 7,window 8,

window 10
Browser Opera,chrome,mozila firefox,

Internet explorer
Hardware
RAM 512MB and above
Processor Intel core2 dule
Free Space 2 GB Hard Disk and above
Page
14
• Planning and Scheduling:
Analysis
I have completed the analysis portion of my project within 10 of 15 days.
I have study different sites related of my project on academia online project.
Design
designing of forms and other design aspects will complete up to 20 days period I get
confused a lot in the case of choosing designing aspects such designing for homepages and
master pages.
Various type of tables I have arrange with its data types and fields.
Coding
Duration of coding consumes a huge time tack around 20 or 25 days.
I have complete home module, login form, master pages with validation and all form
validation complete in one month.
Testing
I have completed all testing of web sites with algorithms and query in time five days.
Scheduling the project task is an important project planning activities. it involves deciding
with task would be taken up when.
Page
15
Chapter:-3
SYSTEM DESIGN
Page
16
• OVER ALL SYSTEM DESIGN USING DESIGNING TOOLS
Systems design is the process of defining the architecture, modules, interfaces,

and data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems engineering.
System design implies a systematic approach to the design of a system.
System design then overlaps with system analysis, system engineering and systems
architecture.
In the warehouse management system we have define the different types of use case
diagrams and activity diagrams to design system.
Using this type of design you will definitely sure that easily understanding.
The following are the use case diagram for warehouse management system.
• Data flow diagram
➢ A data flow diagram (DFD) is a diagrammatic representation of the information

flows within a system
➢ Data flow diagram is graphical tool. it is used to describe and analyses the
movements of data through a system manually or automatically.
➢ They focus on the data flowing into the system between processes and in and out of
data stores.
➢ This central tool and the basis from which other components are developed.
➢ A full description of the system actually consists of a set of DFDs, which is
compared of various levels.
➢ An initial overview model is converted into lower diagram that show additional
features of the system.
➢ Further each process can be broken down into a more detailed DFD. This occurs
until sufficient details (lowest level) are described to allow the analyst to fully
understand that portion of the system.
Page
17
Why DFDs are useful?

When it comes to converting how information data flow through system and how that
data is transformed in the process, DFDs are the method of choice over technical descriptions
for three principle reasons.
1. DFDs are easier to understand by technical and non-technical audiences

2. DFDs can provide a high level system overview, complete with boundaries and
connections to other systems
3. DFDs can provide a detailed representation of system components.
A data flow diagram represents the following :
1. External entity sending and receiving data.

2. Process that change the data
3. Data flow themselves
4. Data storage locations
Notations/symbols 0f data flow diagram

There are only four symbols used to write the data flow diagram as follws:
Data flow:
➢ Data in any system moves in a specific direction (from source to destination) therefore
data flow indicates the movement of data in the system.
➢ Data flow must be inputs to and output from process.
Gane & Sarson Yourdon
Process:
➢ Process is the activities which are performed to transform inputs into output.
➢ Process are the action which are performed by people, machine or produced data.
Page
18
Entity:
➢ A person, machine or anything that performs process and either provides input or
receive the output is call an entity.
Data store:
➢ Data store is a file used to store data which user in the system. It is responsible for
storing as well as providing data as per user’s requirements.
Rules for data flow diagram:

➢ Arrow should not cross each other
➢ Squares, circle, and file must have the names.
➢ All data flow on the detailed diagram must reflect flow in the original diagram.
➢ No two flows, squares, or circles can have the same name.
➢ Draw all data flows around the outside of the diagram.
➢ Choose meaningful name for data flows, processes and data stores.
➢ Process must be transform data.
Advantages of DFDs:
➢ A simple but powerful graphic technique which is easily understood.
➢ Represents an information system from the viewpoint of data movements, which
includes the inputs and output to which people can easily read.
➢ The ability to represent the system at different level of details gives added advantage
➢ Helps to define the boundaries of the system.
➢ A useful tool to use during the interviews.
➢ Server to identify the information services the users require, on the basis of which the
future information system will be constructed.
Page
19
Disadvantage:
➢ When so many decision are to be made then DFD becomes complicated to understand
➢ The symbols are used differently by different person so to understand it is difficult for
other person.
DFD’S Diagrams:
Warehouse
management
Supplier Customer
management management
Warehouse
management
system
Purchasing
Payment
management
management
Receiving stock
management
Zero level DFD
Page
20
Stock management Generate stock report
Login management generate order report
Order management Warehouse generate payment

management report
system
User management Check login detail
Payment management Add new system user
FIRST LEVEL DFD – WAREHOUSE MANAGEMENT SYSTEM
Page
21
login Manage Add item

admin
modules
Show item
Change
password Add workers
Show workers
Release item
Manage order Available item Release workers
Second level DFD
Page
22
login Show there profile

user
Edit profile
Registration
in system
order item
Add to cart
Log out Cancel order
Second level DFD
Page
23
• Data Dictionary
➢ A data dictionary is a file or a set of files that contains a database’s metadata.

➢ The data dictionary contains records about other objects in the database, such as data
ownership, data relationships to other objects, and other data.
➢ The data dictionary is a crucial component of any relational database.
➢ Ironically, because of its importance, it is invisible to most database user. Typically,
only database administrators interact with the data dictionary.
➢ A data dictionary provides information about each attribute, also referred to as fields, of
a data model.
➢ An attribute is a place in the database that holds information.
➢ A data dictionary is typically organized in a spreadsheet format.
➢ Each attribute is listed as a row in the spreadsheet and each column labels an element of
information that is useful to know about the attribute.
➢ Let’s look at the most common elements included in a data dictionary.
➢ In a relational database, the metadata in the data dictionary includes the following.
➢ Name of all tables in the database and their owners.
➢ Names of all indexes and the columns to which the tables in those indexes related.
➢ Constraints defined on tables, including primary keys, foreign-key
➢ Relationships to other tables, and not-null constraints.
Admin login:-
Table Name :- alogin
Use: - It store the user name and password.
Filed Name Data Type Size Constraint Description
User_name Varchar 50 - Store the user name
Pass Varchar 50 - Store the password
Page
24
Add item :
Table Name :- Add item
Use: - Add the item in warehouse.
Primary Key :- prono
Prono Varchar 18 Not null It Store pro no
Procat Varchar 50 Not Null It store the product category
Proname Varchaer 50 Not null It store the name of the

product
Propicse Varchar 50 Not null It store the product picse
Pro price Varchar 50 Not null It store the prise of the

product
Photo varchar 50 Not null It store the image of the

product
Supplier master :-
Table Name :- Supplier_master
Use: - It store all Supplier Details.
Primary Key :- SuppId
worker_code Varchar 18 Primary key It Store Supplier Unique

Identifier
worker_Name Varchar 50 Not Null It Store Supplier Name.
Page
25
worker_no Varchar 50 Not Null It store Mobile Number of

Supplier.
Email Varchar 50 Not Null It store Email Id of

Supplier.
Address Varchar 50 Not null It sore the address of the

supplier
Pincode Numeric 18 Not Null It store the Pincode as per

Address.
User register:
Table Name :- u_regester
Use: - It use to regester a new user for the warehouse.
First_name Varhcar 50 - It store the first name of the

user
Last_name Varchar 50 - It store the last name of the

user
Address_of_shop Varchar 50 - It store the address
E-mail Varchar 50 - Store the e-mail address
Mobile_no Varchar 50 - Store the mobile number
User_name Varchar 50 Not Null Store the user name
Password Varchar 50 Not Null Store the password
Conform_pass Varchar 50 Not null Store the conform password
Page
26
Final order:-
Table Name :- f_order
Use: - It use to store the order data.
Proid Varhcar 50 - It store the product id
Username Varchar 50 - It store the username
Pro_quantity Varchar 50 - It store the quantity of product
Date Varchar 50 - It store the date
Status Varchar 50 - It store the status of the order
Add to cart:-
Table Name :- addtocart
Use: - It use to add product on the cart
Proid Varhcar 50 - It store the id of the product
Pro_quantity Varchar 50 - It store the quantity of product
Username Varchar 50 - It store the user name
Date Varchar 50 - It store the order date
Page
27
• Input/output design:
Admin:-
➢ In this page the admin can enter there user id and password and login to system.
➢ And also give Change password facilities,in this page admin can change their password.
Page
28
Ars:-
➢ This page is use to perform above display operatons.like add item in warehouse,release
item, Show available item,add worker,release worker ,edit worker detail in Warehouse.
➢ Admin can show all Order of users and Also Admin can Approve order of user.
Page
29
Add item:-
➢ This page is use to add items in warehouse,With all details like Product no,product
Category,product name,product image,product quantity and product price.
Page
30
Release item:-
➢ This page is use to delete any items in the warehouse.
Page
31
Show item:-
➢ This page is use to show Available all item in the warehouse.
Page
32
Add worker:-
➢ This page is use to add new workers in the warehouse.With It’s all details like
name,address, E-mail id ,mobile number etc.
Page
33
Delete worker:-
➢ This page is use to release workers from the warehouse.
Page
34
Approve Order:-
➢ This page is use to the admin can approve the user order.
Page
35
Change password:-
➢ In this page use to Admin can Change Their Password.
Page
36
Show worker:-
➢ This page is use to show all Workers,Which is available in our Warehouse.
Page
37
Registration:-
➢ This page is used to user can Register,after login into system.
Page
38
Home:-
➢ This page is use to user can Login in System Otherwise see only about us and contact us
page, Contact us page is use to show warehouse location.
Page
39
Cart:-
➢ This page is used to add item into cart and also show all order price.
Page
40
Order item:-
➢ This page is used to show all Available item With order And add to Cart option.if we can
Click Add to cart button than which product stored into add to cart page.
Page
41
Pending:-
➢ This page use to show user pending order.
Page
42
Logout:-
➢ This page is used to user can logout in the system.
Page
43
Chapter:-4
TESTING AND
IMPLEMENTATION
Page
44
• Testing approach used:
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. Testing represents an interesting anomaly
for the software. The testing Phase involves testing of the system using various test data.
Preparation of test data plays a vital role in system testing. After preparing the test data, the
system under study is tested using those test data. If testing is conducted successfully, it
uncovers the errors in the software. Secondly, testing demonstrates the software function
appears to be working according to specification and performance requirements appear to have
been met in, addition data collected as testing is conducted provides a good indication of
software reliability and some indication of software quality as a whole
Testing plan
Activities at each level are planned well in advance and it has to be formally
documented based on the individual plans only, the individual test levels are carried out.
In all test plans, the ETVX[entry-task-validation-exit] criteria are to be mentioned. Entry

means the entry point to that phase. For example, for unit testing, the coding must be complete
and then only one can start unit testing. Task is the activity that is performed. Validation is the
way which the progress and correctness and compliance and verified for that phase. Exits tell
the completion criteria of that phase, after the validation id done.
A sample test plan outline along with their description is as shown

below:
BACKGROUND – This item summarizes the functions of the application system and
the tests to be performed.
INTRODUCTION-Indicates introduce of system.
ASSUMPTION – Indicates any anticipated assumption which will be made while

testing the application.
Page
45
TEST ITEMS – List each of the items (programs) to be tested.
FEATURES TO BE TESTED – List each of the features (function or requirements)

which will be tested or demonstrated by the test.
APPROACH –Describe the data flows and test philosophy. Simulation or Live
execution, Etc. This section also mentions all the approaches which will be followed at
the various stages of the test execution.
ITEM PASS/FAIL CRITERIA Blanket statement – Itemized list of expected output
and tolerances.
SUSPENSION/RESUMPTION CRITERIA – Must the test run from start to

completion? Under what circumstances it may be resumed in the middle? Establish
check-point in long tests.
Testing strategy:
Before starting any testing activities, the team lead will have to think to think a lot &
arrive at a strategy. This will describe the approach, which is to be adopted for carrying out test
activities including the planning activities. This is a formal document regarding the testing area
and is prepared at very early stage in SDLC. This document must provide generic test approach
as well as specific details regarding the project.
To be most effective testing should be an in dependent third party. By “most effective”,

we mean testing that has highest probability of finding errors (primary objective of testing).
The software engineer who created the system is not the best person to conduct all tests for the
software. Here, the testing is performed by our project guide and then it’s approved only by
him. Finally, the whole system successfully implemented and tested by the users of different
departments and application is updated based on suggestion or the bug reported from them.
Test levels:
The test strategy must talk about what are the test levels that will be carried out for the
particular project. Unit, Integration & system testing will be carried out in our projects.
Page
46
Risks and Mitigation:

Any risks that will affect the testing process were listed along with the mitigation. By
documenting the risks in this document, we could anticipate the occurrence of it well ahead of
time and then were able to proactively prevent it from occurring.
Regression Test Approach:
When a particular problem is identified, the programs will be debugged and the fix will
be done to the program. To make sure that the fix works, the program will be tested again for
those criteria. Regression test will make sure that one fix does not create some other problems
in that program or in any other interface. So, a set of related test cases may have to be repeated
again, to make sure that nothing else is affected by a particular fix.
The following steps summarize our testing strategy approach:

The content model for the web application is reviewed to uncover errors.
The interface model is reviewed to ensure that all user-cases can be accommodated.
The design model is reviewed to uncover navigational errors.
The user interface is tested to uncover errors in presentation and/or navigation
mechanics.
Selected function components are unit tested.
Navigation throughout the architecture is tested.
Performances tests are conducted.
The web application is tested by a controlled and monitoring population of end-user; the results
of their interaction with the system are evaluated for content and navigation errors, usability
concerns, compatibility concerns, and web application reliability and performance
Testing method:
LOAD TESTING:-
A system that works well with one user may completely break down with
several hundred or more users. Load testing helps to evaluate how well a system holds up
under light, medium and heavy use.
Page
47
BLACK BOX TESTING:-
It takes an external perspective of the test object to derive test cases. These tests
can be functional or non-functional, though usually function. The test designer selects valid and
invalid input and determines the correct output. There is no knowledge of the internal workings
of the item being tested. For this reason, the tester and the programmer can be independent of
one another, avoiding programmer bias toward his own work. Due to the nature of black box
testing, the test planning can begin as soon as the specifications are written. This method of test
design is applicable to all levels of software testing: Unit, Integration, Functional testing,
WHITE BOX TESTING:
The opposite of black box testing would be glass box testing, where test data are
derived from direct examination of the code to be tested. For glass box testing, the test cases
cannot be determined until the code has actually been written. Both of these testing techniques
have advantages and disadvantages, but when combined, they help to ensure through testing of
product. Software testing approaches that examine the program structure and derive test data
from the program logic. Structural testing is sometimes referred to as clear-box testing since
white boxes are consider opaque and do not really permit visibility into the code.
Page
48
UNIT TESTING:
In Unit testing each module is tested module is tested alone in an attempt to discover
any errors in the code, i.e. all executable source code will be subject to test. It verifies that
certain parts of the code are working properly. Unit testing tool will be used to perform the unit
testing.
PERFORMANCE TESTING:
This will be performed to test the entire system to see whether all driving
requirement are satisfied. Allowing multiple users log into the system and perform the
operation at the same time using the J Meter testing tool will do this. This test verifies that the
components of the systems meet the stated requirements for speed.
• Test cases:
In software engineering, the most common definition of a test case is a set of condition
or variables under which a tester will determine if a requirement or use case upon an
application is partially or fully satisfied. It may take many test cases to determine that a
requirement is fully satisfied. In order to fully test that all the requirements of an application
are met.
Page
49
Common Tests:
SR NO. TEST CASE EXPECTED RESULT ACTUAL

RESULT
1. Check Test Box Text, with all validations is inserted PASS
for validation
2. Check tab It should be in proper logical order and it PASS

order should move though all the fields
3. Check field’s It should be as per program specs. PASS
name ,type
size ,screen
layout etc.
against
program
4. Check field’s Fields name, type and size should be PASS
name, type and consistent throughout the database for a
size for each particular field.
database table
and against
database
design
5. Check There should be no grammatical mistake or PASS
heading/titles spelling mistake. All heading and titles
of all the forms should be consistent throughout the system.
and pages
6. Field Proper validation should be placed PASS

validation according to the program specification to
validation the required fields and to check
the type of allowed character
7. Select value The dynamic values from the database PASS

from the should be filled in the drop down
dropdown
8. Delete record Record must be deleted from the database PASS

and try to find and should not be available there
it in the
database
Page
50
• Implementation approaches:
When a particular problem is identified, the programs will be debugged and the fix will be
done to the program. To make sure that the fix works, the program will be tested again for
those criteria. Regression test will make sure that one fix does not create some other problems
in that program or in any other interface. So, a set of related test cases may have to be repeated
again, to make sure that nothing else is affected by a particular fix.
The following steps summarize our testing strategy approach:
▪ The content model for the web application is reviewed to uncover errors.
▪ The interface model is reviewed to ensure that all use-cases can be accommodated.
▪ The design model is reviewed to uncover navigational errors.
▪ The user interface is tested to uncover errors in presentation and/or navigation

mechanics.
▪ Selected functional components are unit tested.
▪ Navigation throughout the architecture is tested.
▪ Performance tests are conducted.
The web application is tested by a controlled and monitored population of end-

users; the results of their interaction with the system are evaluated for content and
navigation errors, usability concerns, compatibility concerns, and web application
reliability and performance.
Page
51
Chapter:-5
Conclusion
Page
52
• Conclusion:
➢ Warehouse is the very important part of any supply chain industry.
➢ Warehouse management provide many benefits these may include real time inventory.
➢ The Indian warehousing sector is progressively getting redefine from the traditional
concept of “godowns” to modern days set up with technology but it need up gradation.
➢ To implementing a warehouse business intelligence initiatives are not project, but a
long term commitment to implement continuously improving business intelligence
practices.
➢ The goal of the warehouse management system is to provide management with the
information it need to efficiently control the movement of materials within a warehouse
➢ A cart design must be accompanied with the user-friendly shopping cart application
logic.
➢ It should be convenient for supplier to view the contain of their cart and to be able to
remove or add item in their cart.
➢ This projects help to understanding the creation of an interactive tachnologies user to
implement it.
➢ The project has been appreciated by all the user in the organization.
Page
53
• Limitation of system:
➢ The software we have developed has some limitation.
➢ We are trying to fulfill all requirements, but some tasks are not done here.
➢ Real time services like bar code label printing are not done here.
➢ In this warehouse the other person cannot store there goods.
➢ Upcoming product stock will display only in website nut not added messaging service
that when any product will come send message to customer mobile that new product
stock are available.
➢ We cannot send any types of email to the system user.
➢ We cannot send the stock location to the supplier.
• Future Scopes of System:
➢ If Its Limitation can be solved then it would be more effective.
➢ In future we will try to develop our project so that we able to give theses facilities and
hardcopy provide book.
➢ The administrator of the website can be given more functionality. Looking Specific
supplier generate invoice from admin panel of supplier till.
➢ In future we will add many facilities in our project like we can add label printing,
storage location of the product.
Page
54
➢ To make easy for tracking stock in ware house this system helps for their time
management.
➢ Adding SMS gateway to confirm that supplies order successful. Submitted, and also the
current sates of order that means any state change of order customer will get a
notification.
➢ Have accurate planning to stay ahead of demand curve keep right amount of products.
➢ Can respond to the customer’s need in a consistent way, right across your organization.
➢ Manager the accurate of the rampancy like what is receivable and pay able status.
➢ We will manage all the reports like, Invoice or History of supplier, vendors and
inventory also.
• Bibliography:-
➢ hariti Study Hub-Easy Learn-youtube
➢ www.freeprojectz.com
➢ www.youtube.com
➢ www.google.com
➢ software testing techniques book-Boris Beizer
➢ www.onlineproject.com
Page
55

Warehouse Management System

Uploaded by

Document Information

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

Warehouse Management System

Uploaded by

Copyright:

Available Formats

Warehouse Management System

Warehouse Management System

Shree Adarsh bca College-BOTAD

2 Requirement and Analysis 11

4 Testing And Implementation 44

Our grateful thanks go to our Department, which provides me an opportunity as a project

With sincere regards,

• Arranging the warehouse and its inventory.

• Having and maintaining the appropriate equipment.

• Managing new stock coming into the facility.

• Picking, packing and shipping orders.

• Tracking and improving overall warehouse performance.

➢ There are five types of warehouses as described below

The warehouses which are run to store goods of the general

These warehouses are owned, managed and controlled

The ASP.NET application

SQL Server is sometimes referred to as MSSQL

➢ provide timely customer service.

➢ WMS provide a set of computerized procedures for management of

➢ A warehouse management system’s primary purpose is to maintain the proper balance of

➢ To implement visual basic .net languages.

REQUIREMENT AND ANALYSIS

❖ Benefits of the proposed system

1. Easy to modify construction detail

• Hardware Software Requirement:

Back End Microsoft SQL Server

Programming language Visual basic.net

Operating system Window XP,Window 7,window 8,

Browser Opera,chrome,mozila firefox,

Processor Intel core2 dule

Free Space 2 GB Hard Disk and above

• Planning and Scheduling:

I have study different sites related of my project on academia online project.

• OVER ALL SYSTEM DESIGN USING DESIGNING TOOLS

Systems design is the process of defining the architecture, modules, interfaces,

System design implies a systematic approach to the design of a system.

• Data flow diagram

➢ A data flow diagram (DFD) is a diagrammatic representation of the information

Why DFDs are useful?

1. DFDs are easier to understand by technical and non-technical audiences

A data flow diagram represents the following :

1. External entity sending and receiving data.

Notations/symbols 0f data flow diagram

Gane & Sarson Yourdon

Gane & Sarson Yourdon

Gane & Sarson Yourdon

Gane & Sarson Yourdon

Rules for data flow diagram:

Zero level DFD

Stock management Generate stock report

Login management generate order report

Order management Warehouse generate payment

Payment management Add new system user

FIRST LEVEL DFD – WAREHOUSE MANAGEMENT SYSTEM

login Manage Add item

Second level DFD

login Show there profile

Log out Cancel order

Second level DFD

➢ A data dictionary is a file or a set of files that contains a database’s metadata.

Table Name :- alogin

Use: - It store the user name and password.

Filed Name Data Type Size Constraint Description

User_name Varchar 50 - Store the user name