Essay: Warehouse management system

Essay details:

  • Subject area(s): Engineering essays
  • Reading time: 10 minutes
  • Price: Free download
  • Published on: August 28, 2019
  • File format: Text
  • Number of pages: 2
  • Warehouse management system
    0.0 rating based on 12,345 ratings
    Overall rating: 0 out of 5 based on 0 reviews.

Text preview of this essay:

This page of the essay has 2610 words. Download the full version above.

Chapter 1


Warehouse Management System website is useful for the suppliers and the retailers to view their orders and details of the stocks easily without much paper work. It provides the facility to order new stocks and update the details of the new arrivals of the products for the customers.

1.1 Preamble

This project is very helpful for suppliers as they can give the orders to the retailers easily and the details will be stored. The retailers can assign the rates of the products directly through the website and need not go to the store every now and then.

1.2 Motivation

The warehouse Management system is very useful as the details of all the products and the orders will be updated and will not have paper works. When new products arrive it will be updated in the database. All the details about the products can be obtained without any difficulty.

1.3 Goal and Objectives of the Project Report

• To develop general purpose tool to maintain stock and order details and customers can easily view the products via online.

• This project intends to introduce more user friendliness in the various activities such as stock updating, maintenance, and searching.

• Accepting user details and updating details about the users and the stocks.

• Easy to order the stocks/products.

• Authentication of administrative users is done using proper user name and password. So that other users cannot retrieve administrative data.

1.4 Problem Statement

• In an existing System, all process are Handled manually. The admin should refer all the records kept for years ago to simply know the details. This is time consuming.

• This process is very difficult when the number of users increases. There are many limitations for the existing systems. In manual system all the work is done by human intervention due to which there are maximum chances of errors.

• Suppliers had to visit again and again to know about the order details and when the products will be completed and delivered.

• The files were not stored in hierarchical format. Hence searching was big problem. Due to this the updating was difficult. This leads to duplication of records.

1.5 Scope of the Dissertation Report

As the growing demands and heterogeneity of applications are continuously challenging the architectural aspects of the Internet, it becomes necessary to devise an architecture which is flexible in terms of any modification or update of applications or protocols.

• No data duplication

• No Paper Work Required

• Time Efficient

• Cost Efficient

• Automatic data validation

• User friendly environment

• Data security and reliability

• Fast data insertion & retrieval

• Easy performance check

• Format report generation

1.6 Outline of Dissertation Report

The Project Report is encompassed with six chapters in total and it is organized as follows:

Chapter – 1: Introduction:

It gives the details about the research work and the scope and objective of the project report. It also gives the information about the overview of the project report starting with the project explanation such as the introduction. It also briefs the feelings of the authors.

Chapter – 2: Literature Survey:

Determine the relevant background information such as the Internet design goals & principles, initiative towards the OSI reference model, architectural principles, a critical review of Internet dealing with its limitations and issues, future research approaches, and finally the need of net- work architecture.

Chapter-3: Requirement Analysis:

The main goal of the requirements phase is to produce the software requirements specification(SRS), which accurately captures the client’s requirement and forms the basis of the software development and validation. The main basic activity in the requirements phase is requirement analysis.

Chapter -4: System Design:

Deciding which module are needed for the system, the specification of these module should be interconnected is called “SYSTEM DESIGN”. System design is also called Top Level design. The design of a system is a plan for solution for the system here we consider a system to be set of components with clearly defined behavior that interact with each in a fixed manner to produce some behavior.


Implementation forms an important phase in the system development life cycle. It is a stage of the project work that transforms the design into a work module.

Chapter-6: Testing:

Testing can be stated as the process of validating and verifying that a software program/application is behaving just as expected during the designing phase. Track the errors to understand their causes and any patterns that may exist.

Chapter 2

Literature Survey

Literature survey is a text of a scholarly paper, which includes the current knowledge including substantive findings, as well as theoretical and methodological contributions to a particular topic.

Literature survey use secondary sources and do not report new or original experimental work.

During literature survey, we found the information about the warehouse management system that the products in the system will be very easy to find out if it is categorized. Hence categorization of the products will be easier for the customers to find the required products.


• New information about the proposed system

• Techniques used for user interactions

• How the users wish to have the proposed system and its functionality


• Lengthy Modules

• User accessibility

• User security

Literature Survey if very important as the users will be using the system and they will be using the system only if they are happy with the way the system is developed. Hence taking the information from the survey has become mandatory. It will also be helpful if we get to know the ideas how the users wish to have the system developed and the interface they wish to use.

Chapter 3

Hardware and software Requirements

3.1 Requirement Analysis

Software Requirement Specification is a technical specification of requirements for the software products. SRS represents an overview of products, features and summarizes the processing environment for development operation and maintenance of the product.

Software Requirement Specification completely describes what the proposed software is supposed to do, without explaining what it actually does. It contains all the basic requirements that are needed for the development of the software.

The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system. An SRS provides a reference for validation of the final product. The Warehouse Management System is useful for all the suppliers who wish to view the products online and give orders of the stocks quickly and in a easy way. It helps to keep the details of the records and can be viewed even after many years. It will be updated easily without any problem.

3.1.1 Software Requirement Specification

• Windows 7 Ultimate, Windows 8

• Browser Software like Microsoft Internet Explorer 4.0 or later.

• Visual Studio 2010 or later

• .Net as front end.

• SQL Server 2005 and above

3.1.2 Hardware Requirement Specification

• 256 MB of RAM or more.

• 2GB of hard disk space.

• VGA or higher monitor resolution.

• Mouse or other pointing devices.

• Network interface card or Modem.

• LAN Network.

• Processor Intel core i3 and above.

• Communication Devices such as Wi-Fi.

Chapter 4

System Design Architecture

Deciding which module are needed for the system, the specification of these module should be interconnected is called “SYSTEM DESIGN”. System design is also called Top Level design. The design of a system is a plan for solution for the system here we consider a system to be set of components with clearly defined behavior that interact with each in a fixed manner to produce some behavior.

4.1 E-R Diagram

An ER model is an abstract way to describe a database. Describing a database usually starts with a relational database, which stores data in tables. Diagrams created to design these entities and relationships are called entity–relationship diagrams or ER diagrams. E-R diagram depicts the various relationships among entities, considering each object as entity.Peter Chen developed ERDs in 1976.

4.2.1 Entity-Relationship Diagram Notation:

Entity: An entity is an object or concept about which you want to store information.

Weak Entity: A weak entity is an entity that must defined by a foreign key relationship with another entity as it cannot be uniquely identified by its own attributes alone.

Key attribute:A key attribute is the unique, distinguishing characteristic of the entity. For example, an employee’s social security number might be the employee’s key attribute.

Figure 4.1:E-R Diagram

4.2 Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the “flow” of data through an information system, modelling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design).

A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel.

4.2.1 Description of the Documents

The notations used in the diagram are:


A process transforms incoming data flow into outgoing data flow.

Data Store:

Data stores are repositories of data in the system. They are sometimes

also referred to as files.

External Entity:

External entities are objects outside the system, with which the system

Communicates. External entities are sources and destinations of the

system’s inputs and outputs.


Dataflow are pipelines through which packets of information flow. Label

the arrows with the name of the data that moves through it .

Level 0:

Fig 4.2:DFD Level 0

Level 1:

Fig 4.3: DFD Level 1

Level 2 User:

Fig 4.4:DFD Level 2 User

Level 2 Admin:

Fig 4.5: Level 2 DFD of Admin

4.3 Class Diagram

Fig 4.6: Class Diagram

4.4 Sequence Diagram

Fig 4.7: Sequence Diagram

4.5 UseCase Diagram

Fig4.8: UseCase for Admin

Fig4.9: UseCase for User

Fig4.10: UseCase for Retailers/suppliers

Chapter 5


5.1 Home Page

5.2 Registration Page

5.3 Login Page

5.4 Admin Page:

5.5 User Details

5.6Order Details

5.7 Customer Page:

5.8 Supplier Page:

5.9 Retailer Page:

Chapter 6


Software testing is the process of executing a program or system with the intent of finding errors. Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Although crucial to software quality and widely deployed by programmers and testers, software testing is still an art, due to limited understanding of the principles of software. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and validation or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing.

6.1 Testing approach

Testing is the penultimate step of software development. While testing is done, errors are noted and correction is made. Both hardware and software securities are made to run the developed system successfully.

System testing is aimed at ensuring the system works accurately before the live operation commences. Testing is vital to the system. System testing makes a logical assumption that if all parts of the system are correct, the goal will be successfully achieved. A series of testing are performed for the proposed system before the system is ready for user acceptance testing.

Normally, testing of any large systems will be in two parts: The functional verification and validation against the indicated requirements. Testing activity is involved right from the beginning of the project.

Characteristics of a Good test:

• Tests are likely to catch bugs

• No redundancy

• Not too simple or too complex

6.2 System Testing

When a system is developed, it is hoped that it performs properly. The main purpose of testing and information system is to find the errors and correct them.

The main objectives of system testing are:

• To ensure during operation the system will perform as per specification.

• To make sure that the system meets user’s requirements during operation.

• To verify that the controls incorporated in the system function as intended.

• To see that when correct inputs are fed to the system the outputs are correct.

• To make sure that during operation incorrect input and output will be deleted.

System testing is the process of checking if the developed system is working according to the original objectives and requirements.

6.3 Types of testing

Clearly, the success of testing is revealing errors in programs depend critically on the test cases. The two basic approaches are:

• Black box or Functional testing

• White box or Structural testing

6.3.1 Black box or Functional testing

A software testing technique whereby the internal workings of the item being tested are not known by the tester. The tester does not ever examine the programming code and does not need any further knowledge of the program other than its specifications.

6.3.2 White box or Structural testing

White box testing includes analyzing data flow, control flow, information flow, coding practices and exception and error handling within the system to test the intended and unintended software behavior.

6.4 Test Cases

6.4.1 Change Password:

Sl No Testing Condition Expected Result Test Result

1 If emailid is not entered Message box appears telling users to enter their emailid Success

2 If password and confirm password is not matching Message box appears telling users that password doesnot match Success

3 If usertype is not selected Message box appears telling users to select the usertype Success

Table6.1: Change Password Test case

6.4.2 Login:

Sl No Testing condition Expected Results Test Result

1 If the emailid and password is left blank Message box appears asking users to enter emailid and password Success

2 If emailid is typed wrong Message box appears telling users its invalid emailid Success

3 If password is typed wrong Message box appears telling users its invalid password Success

4 If user type is not selected Message box appears asking users to select user type Success

Table 6.2: Login Test Case

6.4.3 Register Page :

Sl No Testing Condition Expected Result Test Result

1 If user name is already available Message box appears telling users to select different username Success

2 If emailid is already available Message box appears telling users to select different emailid Success

3 If emailid and username are not available already Message box appears telling users to continue with their procedure Success

4 If usertype, country, state are not selected Message box appears telling users to select usertype, country and state Success

5 If phone number is not entered correctly Message box appears telling users to give valid phone number Success

Table 6.3: Register Test Case

7. Conclusion:

• Warehouse management system is developed successfully and has been tested successfully.

• This web based application can be used by the people without any problem and has user friendly interface.

• All the testing and validation has been successfully carried out.

Using the proposed system:

• Efficiency is improved

• Storage and maintenance of database is easy

• Paper work is reduced.

8. Future Enhancement:

• New modules can be added without affecting the existing model.

• The existing modules can be reused in future projects.

• Can be upgraded to include various products in which various categories will be included.

• Can be moved our vision through National Level.

• This Project can be extended with regional language support.

• If any user forgets the password, the new password will be sent to their registered email accounts.

• The delivery of the product will be reaching the customer within very short period of time.

• Every kind of products such as food, accessories etc will be available in our website in very short period of time.


[1] McGraw Bart De Smet: C# 4.0 Unleashed, Pearson Education- SAMS Series

[2] Hebert Shildt: Programming in C# 4.0, Tata Hill

[3]An Integrated Approach to Software Engineering by PankajJalote.

[4] ASP.NET reference- MSDN- microsoft

[5] Professional ASP.NET books in c#

[6] Software Testing : A practical approach

About Essay Sauce

Essay Sauce is the free student essay website for college and university students. We've got thousands of real essay examples for you to use as inspiration for your own work, all free to access and download.

...(download the rest of the essay above)

About this essay:

This essay was submitted to us by a student in order to help you with your studies.

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, Warehouse management system. Available from:<> [Accessed 21-09-20].

Review this essay:

Please note that the above text is only a preview of this essay.

Review Title
Review Content

Latest reviews: