Documentation On Warehouse Management Sy

Documentation on
Warehouse Management
System
SUPERVISED BY:
MD.MAHBUBUR RAHMAN
Assistant Professor
Department of CSE
SUBMITTED BY
NName
ID No
Intake
Section
Avrojit Das
13143103073
27th
02
BANGLADESH UNIVERSITY OF BUSINESS AND

TECHNOLOGY (BUBT)
Plot # 77-78, Road # 9, Rupnagar, Mirpur-2, Dhaka-1216
Submitted Date: 15th Oct, 2016
About the Developers :
Avrojit Das:
Avrojit Das is a student of Bangladesh University of Business & Technology
(BUBT). Study in B.Sc. in Computer Science & Engineering at 27 th intake, Section
2 and bearing university ID:- 13143103073
DECLARATION
I hereby declare that the project entitled Warehouse Management System
submitted in partial fulfillment of the requirements for the Course of Software
development-2 in the Faculty of Computer Science & Engineering of Bangladesh
University of Business & Technology in our own work and that it contains no
material which has been accepted for the award to the candidates of any other
degree or diploma, except where due reference is made in the text of the project to
the best of our knowledge. It contains no materials previously published or written
by any other person except where due references made in this project.
Signature
______
Avrojit Das
~2~
ABSTRACT
The project Warehouse Management System provides us a simple interface for
maintenance of Shops information. Achieving this objects is difficult using manual
system has information is scattered can be redounded and collecting relevant
information may be very time consuming. All this problems are solved using this
project.
Throughout the project , the focus has been on presenting information in an easy
and intelligible manner. The project is very useful for those who want to know
about Warehouse Management System and want to develop software /websites
based on the same concept.
~3~
ACKNOWLEDGEMENTS
First and foremost we are grateful to the God, the Almighty, the Merciful without
whose patronage and blessing this project would not been successfully completed.
He gave us zeal, confidence, power of determination and courage and vanquished
all the burrier, that we faced on the way. It is an auspicious occasion for us as
students of Department of Computer Science and Engineering, one of the
prestigious academic centers of the Bangladesh University of Business and
Technology, to express my deep feelings of gratitude to the department and
especially to our supervisor, Head of the department, all the teachers and also to
the departmental staff. I am immensely indebted to my supervisor,
MD.MAHBUBUR RAHMAN, Assistant professor, Department of Computer
Science and Engineering , for his wonderful guidance, inspiration , encouragement
and also for through review and correction of this dissertation work that could not
be finalized without his astute supervision .
I pay profound regard to all of our teachers of the department for their very
valuable directives and special attention. My parents are very much keen and
hopeful in the best performance of the dissertation I am going to submit. I wish i
could fulfill their aspiration. I also pay regard to my friends in the department who,
through their interest and work, are my contestant source of inspiration.
With Best Regards,

Avrojit Das
~4~
Table of Contents
Sl. No.
Chapter
Content
Introduction of The Project
2
3
4
5
6
7
8
9
1.1 Project Objectives

1.2 Features of the project
1.3 Scope of Project
2
2.1 Overview
2.2 History of Java Language
2.3 Features of Java
3
10
11
12
13
14
15
Platform/Technology
Used
System Requirement Study

3.1 User Characteristics
3.2 Hardware Requirement
3.3.Software Requirement
3.4.Functional Requirements
3.5.Non-Functional Requirements
System Analysis
16
4.1 Study of Current System
17
4.2 Problems And Weakness of Current

System
18
4.3 Life Cycle
~5~
19
20
21
22
23
24
25
26
27
28
System Design
5.1. Introduction
5.2.Logical Design
5.3.Physical Design
5.4.Design/Specification activities
5.5.Database Design
Implementation Planning &

Testing
6.1 Implementation Environment
6.2 Testing
Diagrams
29
30
31
7.1 Context Level Diagram

7.2 0-Level Data Flow Diagram
7.3 Use Case Diagram
32
7.4 E-R Model Diagram
33
34
Screen Short And User Manual

Appendix
35
36
37
38
39
9.1 Advantage of Project

9.2 Features
9.3 Project Limitation
9.4 Difficulty faced during development
9.5 Scope of Future Application
40
41
9.6 Lessons Learned
42
43
44
10
Conclusion & Discussion

10.1 Conclusion
10.2 Discussion
10.3 Problem Encountered and Possible
~6~
Solutions
45
46
References
Code
Chapter-1
Introduction of the Project
1.1 Objective:
The objective of warehouse Management System is to allow the administrator of any
organization to edit and find out the details of a product, and allows the authority to maintain this
system. Itll also facilitate keeping all the records of workers, such as their id, name etc. So all
the information about a product and workers will be available in a few seconds.
1.2. Features of Project:

The features of this project are following:
View product
Add information of new product.
Update the information of products.
Delete the information.
Searching of products/workers marks by index no.
Easy access of saved data inside the system.
It is highly secure and less time consuming: hence time wastage can be avoided
1.3 Scope of Project:
To implement C# 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 shops information.
To secure the internal database.
To have a faster, easier to search a details.
~7~
For doing work more accurately.
Chapter-2
PLATFORM/TECHNOLOGY USED
2.1 Overview :
C# (pronounced as see sharp) is a multi-paradigm programming language encompassing strong
typing, imperative,declarative, functional, generic, object-oriented (class-based), and componentoriented programming disciplines. It was developed by Microsoft within its .NET initiative and
later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270:2006). C# is one
of the programming languages designed for the Common Language Infrastructure.
C# is a general-purpose, object-oriented programming language. Its development team is led
by Anders Hejlsberg. The most recent version is C# 6.0 which was released in 2015.
2.2 History of C# Language:

During the development of the .NET Framework, the class libraries were originally written using
a managed code compiler system called Simple Managed C (SMC). In January 1999, Anders
Hejlsberg formed a team to build a new language at the time called Cool, which stood for "C-like
Object Oriented Language". Microsoft had considered keeping the name "Cool" as the final
name of the language, but chose not to do so for trademark reasons. By the time the .NET project
was publicly announced at the July 2000Professional Developers Conference, the language had
been renamed C#, and the class libraries and ASP.NET runtime had been ported to C#.
~8~
C#'s principal designer and lead architect at Microsoft is Anders Hejlsberg, who was previously
involved with the design of Turbo Pascal, Embarcadero Delphi (formerly CodeGear Delphi,
Inprise Delphi and Borland Delphi), and Visual J++. In interviews and technical papers he has
stated that flaws in most major programming languages (e.g. C++, Java, Delphi, and Smalltalk)
drove the fundamentals of the Common Language Runtime (CLR), which, in turn, drove the
design of the C# language itself.
James Gosling, who created the Java programming language in 1994, and Bill Joy, a co-founder
of Sun Microsystems, the originator of Java, called C# an "imitation" of Java; Gosling further
said that "[C# is] sort of Java with reliability, productivity and security deleted." Klaus Kreft and
Angelika Langer (authors of a C++ streams book) stated in a blog post that "Java and C# are
almost identical programming languages. Boring repetition that lacks innovation," "Hardly
anybody will claim that Java or C# are revolutionary programming languages that changed the
way we write programs," and "C# borrowed a lot from Java - and vice versa. Now that C#
supports boxing and unboxing, we'll have a very similar feature in Java." In July 2000, Anders
Hejlsberg said that C# is "not a Java clone" and is "much closer to C++" in its design.
Since the release of C# 2.0 in November 2005, the C# and Java languages have evolved on
increasingly divergent trajectories, becoming somewhat less similar. One of the first major
departures came with the addition of generics to both languages, with vastly different
implementations. C# makes use of reification to provide "first-class" generic objects that can be
used like any other class, with code generation performed at class-load time. Furthermore, C#
has added several major features to accommodate functional-style programming, culminating in
the LINQ extensions released with C# 3.0 and its supporting framework of lambda
expressions, extension methods, and anonymous types. These features enable C# programmers to
use functional programming techniques, such as closures, when it is advantageous to their
application. The LINQ extensions and the functional imports help developers reduce the amount
of "boilerplate" code that is included in common tasks like querying a database, parsing an xml
file, or searching through a data structure, shifting the emphasis onto the actual program logic to
help improve readability and maintainability.
~9~
C# used to have a mascot called Andy (named after Anders Hejlsberg). It was retired on January
29, 2004.
C# was originally submitted to the ISO subcommittee JTC 1/SC 22 for review, under ISO/IEC
23270:2003, was withdrawn and was then approved under ISO/IEC 23270:2006.
2.3 Features of C#:

There is given many features of c#. The C# Features given below are simple and easy to
understand.
Binary Literals
Digit Separators
Local Functions
Type switch
Ref Returns
Tuples
Out var
Pattern Matching
Arbitrary async returns
Records
~ 10 ~
Chapter 3
System Requirement Study
3.1 User Characteristics :
Administrator:
The administrator has all the rights to access the system. He is the one who has all rights to view
the all details, modify those details;the administrator also keeps a track of the file status of the
applicants.
3.2 Hardware Requirement
~ 11 ~
Hardware is a set of physical components, which performs the function of applying appropriate,
predefined instruction. In other words one can say that electronic or mathematical parts of
computer constitute of hardware.
The following are the minimum hardware specifications to run this package:
Processor: Pentium(R) Dual-Core CPU
RAM: 1.00 GB
System type: 32- bit or 64- Operating System
3.3.Software Requirement:
The software is a set of procedures of coded information or a program when fed into the
computer hardware enables the computer to perform various tasks. Software is like a current
inside the wire, which cannot be seen but its effect can be felt.
The following are the minimum software specifications to run this package:
Operating System: Windows 7 /Windows 8
Platform: C# language through Microsoft visual studio
Database : Database access
3.4.Functional Requirements:
Creation of New Record: This function creates a record for a new items.
Deletion of Record: This function is used to delete the existing record of any items.
Updating in Record: This function updates the information in a record of any items.
Display of Data in Record: This function displays the record of the items.
Searching a Record: This function search the record of the items.
3.5.Non-Functional Requirements:
Security: Only authorized users can access the system with user name and password.
Performance: Easy tracking of records and updating can be done.
User Friendly: The system is very interactive.
Maintainability: Backups for database are available.
~ 12 ~
CHAPTER-4
System Analysis
4.1 Study of Current System :

The current system for the Warehouse Management System deals with maintaining a
physical contact with the sales management for filling all the details and the documentation
work.
The admin also has to manage all the sites. He needs to maintain records of all the
products., The Manual process is more error prone and also slow. Moreover Books in the library
can interface his/her work area only. But if an online application is available then they can
communicate whole system. Thus a simulation of this entire process can be a boon to the
applicants as well as the admin.
~ 13 ~
4.2 Problems And Weakness of Current System :
The present system has certain major disadvantages. A few to be listed can be excessive
paperwork, time consuming process flow, laborious work environment for employees,
difficulty to access historical data and all these problems lead to inefficient working of
government sector causing dissatisfaction in the general public.
A part from the above stated problems there is lack of transparency in the existing
system. This being one of the major drawbacks in the system needs special attention.
The following listed are the problems or weaknesses of the current system:
So much time consume in preparing registers which is having replicated data

It is difficult to prepare report for decision making.
Attendance related module is not there.
4.3.Life Cycle:
Figure 1.1: Iterative and Incremental Life Cycle

The basic idea behind iterative enhancement is to develop a software system
incrementally, allowing the developer to take advantage of what was being learned during the
development of earlier, incremental, deliverable versions of the system. Learning comes from
both the development and use of the system, where possible. Key steps in the process were to
~ 14 ~
start with a simple implementation of a subset of the software requirements and iteratively
enhance the evolving sequence of versions until the full system is implemented.
Chapter-5
System Design
5.1. Introduction :
Design is the first step into the development phase for any engineered product or System. Design
is a creative process. A good design is the key to effective system. The term design is defined
as the process of applying various techniques and principles for the purpose of defining a
process or a system in sufficient detail to permit its physical realization. It may be defined as a
process of applying various techniques and principles for the purpose of defining a device, a
process or a system in sufficient detail to permit its physical realization. The system design
develops the architectural detail required to build a system or product. As in the case of any
systematic approach, this software too has undergone the best possible design phase fine tuning
all efficiency, performance and accuracy levels. The design phase is a transition from a user
oriented document to a document to the programmers or database personnel. System design goes
through two phases of development: Logical and Physical Design.
~ 15 ~
5.2.Logical Design:
The logical flow of a system and define the boundaries of a system. It includes the
Following steps:
Reviews the current physical system its data flows, file content, volumes, frequencies
etc.
Prepares output specifications that is, determines the format, content and frequency of
reports.
Prepares input specifications format, content and most of the input functions.
Prepares edit, security and control specifications.
Specifies the implementation plan.
Prepares a logical design walk through of the information flow, output, input,
Controls and implementation plan.
Reviews benefits, costs, target dates and system constraints.
5.3.Physical Design:
Physical system produces the working systems by define the design specifications that tell the
programmers exactly what the candidate system must do. It includes the following steps.
Design the physical system.

Specify input and output media.
Design the database and specify backup procedures.
Design physical information flow through the system and a physical design Walk
through.
Plan system implementation.
Prepare a conversion schedule and target date.
Determine training procedures, courses and timetable.
Devise a test and implementation plan and specify any new hardware/software.
Update benefits , costs , conversion date and system constraints
5.4.Design/Specification activities:
~ 16 ~
Concept formulation.
Problem understanding.
High level requirements proposals.
Feasibility study.
Requirements engineering.
Architectural design.
5.5.Database Design:
A database is an organized mechanism that has the capability of storing information through
which a user can retrieve stored information in an effective and efficient manner.
The data is the purpose of any database and must be protected. The database design is a two level
process. In the first step, user requirements are gathered together and a database is designed
which will meet these requirements as clearly as possible. This step is called Information Level
Design and it is taken independent of any individual DBMS.
In the second step, this Information level design is transferred into a design for the specific
DBMS that will be used to implement the system in question. This step is called Physical Level
Design, concerned with the characteristics of the specific DBMS that will be used. A database
design runs parallel with the system design. The organization of the data in the database is aimed
to achieve the following two major objectives.
Data Integrity
Data independence
Normalization is the process of decomposing the attributes in an application, which results in a
set of tables with very simple structure. The purpose of normalization is to make tables as simple
as possible. Normalization is carried out in this system for the following reasons.
To structure the data so that there is no repetition of data , this helps in saving.
To permit simple retrieval of data in response to query and report request.
To simplify the maintenance of the data through updates, insertions, deletions.
To reduce the need to restructure or reorganize data which new application requirements
arise.
~ 17 ~
Chapter 6
Implementation Planning & Testing
6.1 Implementation Environment:
The implementation view of software requirement presents the real world manifestation
of processing functions and information structures. This computerized system is specified in a
manner that dictates accommodation of certain implementation details.
The implementation environment of the developed system facilitates multiple users to use
this system simultaneously. The user interfaces are designed keeping in mind that the users of
this system are familiar to using GUI-based systems. Thus, we restricted ourselves to developing
~ 18 ~
a GUI-based system so that it becomes easier for the end user to get acquainted to the developed
system.
6.2 Testing :
Software Testing has a dual function; it is used to identify the defects in program and it is used to
help judge whether or not program is usable in practice. Thus software testing is used for
validation and verification, which ensure that software conforms to its specification and meets
need of the software customer.
Developer resorted Alpha testing, which usually comes in after the basic design of the program
has been completed. The project scientist will look over the program and give suggestions and
ideas to improve or correct the design. They also report and give ideas to get rid of around any
major problems. There is bound to be a number of bugs after a program have been created.
Unit
Testing
Modul
e
Testing
Subsystem
Testing
Syste
m
Testing
Acceptanc
e Testing
~ 19 ~
Fig6.2: Testing Step
Chapter -7
Diagrams
7.1 Context Level Diagram :
Manager
Control/production
Super Shop
Manageme
nt System
Purchase
~ 20 ~
Customer
Information
Product
Figure: Context Level Data Flow Diagram for Warehouse management system
7.2 0-Level Data Flow Diagram:
~ 21 ~
Fig: 0- Level Data Flow Diagram for Warehouse Management System
7.3 Use Case Diagram

~ 22 ~
Log in
Select ypur
Brand
Add / Edit /
Delete / Update
products
view Items
Admin
View product
Details
Search items
Exit
Fig: Use Case Diagram For Warehouse Management System
7.4 E-R Model Diagram

~ 23 ~
Admin
product
Admin control
Add
Product store
Edit
Update
Product Store
delete
Item
name
Qty
Price
Fig: E-R Model Diagram For Warehouse Management System
Chapter 8
~ 24 ~
Screen Shot And User Manual
Fig 8.1: Screen shot showing First Page as login page
~ 25 ~
Fig 8.1: Screen shot showing next page
Fig 8.1: Screen shot showing manager page
~ 26 ~
Fig 8.1: Screen shot showing a brand of products
Fig 8.1: Screen shot showing add products
~ 27 ~
Fig 8.1: Screen shot showing update product page
Fig 8.1: Screen shot showing delete item
~ 28 ~
Fig 8.1: Screen shot showing Reset information
Fig 8.1: Screen shot showing view Item
~ 29 ~
Chapter 9
Appendix
9.1 Advantage of Project:
Following are the main advantages:
It provides better and efficient service to user.
Reduce the workload of user.
Reduce paper work.
All details will be available on single click.
Addition, deletion, searching is easy.
If user wants to know only marks then this facility is also provided separately and his
personal information is shown separately.
Reduced time consume.
9.2 Features:
It creates a user friendly environment, where a normal user can access through all the
benefits of the system.
It provides security from unauthorized system access, only admin or authorized users
are access granted to the system.
It increases efficiently and save the time.
No any danger and obstacles from external entities.
Easy access of saved data inside the system.
Complex Reservation operation and Billing operation are efficiently handled by
the application.
It is cost effective.
It is highly secure and less time consuming: hence time wastage can be avoided.
Up to date records of the customers are maintained by the authority.
~ 30 ~
9.3 Project Limitation:

The part of the system can be implemented using the current technology although some
modifications had to be done at various places. At various places some alterations with the
prototypes and functionalities would be done in order to work out the cost constraints and to
copy with the scheduling constraints.
In this system we have dont have facility for time schedule of workers.
There is no online connectivity.
Fast report generation is not possible.
9.4 Difficulty faced during development:

While developing this Application, we faced many difficulties as we newbie to developing
software. After start working day by day we overcome many difficulties we faced early staged in
development. The faced difficulties are listed below-
At initial stage, I waste lots of time to set up development environment for software
development. After trying some days, we successfully set up development environment.
Since Im not expert programmer in C# language. So I have to work hard to learn very
well about programming
At first my program did not ran. But after working few days I was able to successfully
run the program.
~ 31 ~
9.5 Scope of Future Application:
The SIMS has been developed with a main aim of making work easier and timesaving for
the human capital. The whole system is bi-lingual at present and can be extended to other
languages too with minor changes (not in coded).
The coding pattern is kept as dynamic as possible with minimum amount of static values
to make it easier for future extensions. As the current system is expected to add more
functionality and dependency according to requirement changes and technology, proper coding
standards and working platform have been kept in mind to produce a quality product.
One enhancement is that we can make this application in more than 1 language as
well.Adding attendance management is also one option for enhancement.
It can be made online

More security can be there.
Reusability is possible as and when require in this application.
The Warehouse Management System(WHMS) can be enhanced to include some other
functionality like time schedule management
9.6 Lessons Learned:

There were lots of lessons that we learned from throughout the time we spent for developing this
project. Most importantly we learned to work according to a time schedule and how to manage
the time to take the maximum benefit of the time we had. We faced lot of inconveniences while
engaging with the project development and those incidents gave us the experiences of facing the
problems and finding the appropriate solutions as necessary. This project also let me to get the
experience of working and how to do it with a team spirit. Now I have lot of experiments that i
did to get on to a better out come and those things impacted me to collect new things in to my
knowledge as well as to my lives.
~ 32 ~
Chapter 10
Conclusion and Discussion
10.1 Conclusion:
Warehouse management system will be helpful to perform paperless work and manage
all data.
This provides easy, accurate, unambiguous and faster data access.
Lesser learning curve - Consistent user interface, customized for the group of users,
statistical information in various graphical and tabular forms.
10.2 Discussion
10.2.1 Self Analysis of Project Viabilities
WHMS is a very efficient system for the management of buy and selling product. Most of
all the task of buy and sale can be easily done with this system. This can be used by any
organization.
It was easy enough to develop the project. If any changes in the system are to be made
then they can be done very easily.
~ 33 ~
10.3 Problem Encountered and Possible Solutions:

Problem of creating control using C# language were faced during development. But with
help of internal guide and other team members problems were solved.
The problems encountered during the training undergone at Tata Consultancy Services
were purely due to lack of knowledge in various technical aspects. The lack of in depth
knowledge in various concepts of java script, database concepts, etc. was the problems
faced.
Moreover the lack of practical know-how of these aspects did cause a few hindrances in
early stages of training but later with the help and guidance of team members it became
easier to cope up with these concepts and applications.
References
[1] https://en.wikipedia.org/wiki/C_Sharp_(programming_language)
[2] http://net-wms.ercim.eu/images/pdf_documents/netwms%20brochure.pdf
[3] RaguRamakrishnan/ JohnesGehrke, Database Management Systems
3"edition. McGrow HILL,2003.
[4] https://www.youtube.com
www.google.com
www.sourcecodesworld.com
~ 34 ~
CODE
using
using
using
using
using
using
using
using
using
using
System;
System.Collections.Generic;
System.ComponentModel;
System.Data;
System.Drawing;
System.Linq;
System.Text;
System.Threading.Tasks;
System.Windows.Forms;
System.Data.OleDb;
namespace WindowsFormsApplication1
{
public partial class Form1 : Form
{
private OleDbConnection connection = new OleDbConnection();
public Form1()
{
InitializeComponent();
connection.ConnectionString = @"Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=F:\SD\Cosmetics.accdb;
Persist Security Info=False;";
}
private void button1_Click(object sender, EventArgs e)
{
foreach (Control c in this.Controls)
{
if (c.GetType() == typeof(TextBox))
{
((TextBox)(c)).Text = string.Empty;
}
}
}
{
connection.Open();
OleDbCommand command = new OleDbCommand();
command.Connection = connection;
command.CommandText = "select * from AdminPannel where
Username='"+txt_Username.Text+"' and Password='"+txt_password.Text+"'";
OleDbDataReader reader= command.ExecuteReader();
int count = 0;
while(reader.Read())
{
count++;
}
if(count==1)
{
~ 35 ~
MessageBox.Show("Username and Password is correct");

connection.Close();
connection.Dispose();
Welcome f = new Welcome();
f.Show();
this.Hide();
}
else if(count>1)
{
MessageBox.Show("Duplicate Username and Password");
Welcome frm = new Welcome();
frm.Show();
this.Hide();
}
else
{
MessageBox.Show("Username and Password is not correct");
}
connection.Close();
}
private void label1_Click(object sender, EventArgs e)
{
}
private void Form1_Load(object sender, EventArgs e)

{
try
{
connection.Open();
checkConnection.Text = "Connection Successful";
connection.Close();
}catch(Exception ex)
{
MessageBox.Show("Error"+ ex);
}
}
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
System.Data.OleDb;
~ 36 ~
{
public partial class Welcome : Form
{
public Welcome()
{
}
private void Welcome_Load(object sender, EventArgs e)
{
}
{
Main frm = new Main();
frm.Show();
this.Hide();
}
}
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
System.Data.OleDb;
{
public partial class Main : Form
{
//private OleDbConnection connection = new OleDbConnection();
public Main()
{
/*connection.ConnectionString = @"Provider=Microsoft.ACE.OLEDB.12.0;Data
Persist Security Info=False;";*/
}
{
Oxy o = new Oxy();
o.Show();
this.Hide();
~ 37 ~
}
{
Dulgon o = new Dulgon();
o.Show();
this.Hide();
}
{
Lipice o = new Lipice();
o.Show();
this.Hide();
}
{
Mua o = new Mua();
o.Show();
this.Hide();
}
{
Thebodyshop o = new Thebodyshop();
o.Show();
this.Hide();
}
{
Superdrug o = new Superdrug();
o.Show();
this.Hide();
}
{
Mothercare o = new Mothercare();
o.Show();
this.Hide();
}
{
Acnes o = new Acnes();
o.Show();
this.Hide();
}
}
~ 38 ~
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Thebodyshop : Form
{
public Thebodyshop()
{
}
private void thebodyshopBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
this.thebodyshopBindingSource.EndEdit();
this.tableAdapterManager.UpdateAll(this.cosmeticsDataSet3);
}
private void Thebodyshop_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet3.Thebodyshop' table. You
can move, or remove it, as needed.
this.thebodyshopTableAdapter.Fill(this.cosmeticsDataSet3.Thebodyshop);
}
{
{
{
}
}
}
{
Application.Exit();
}
~ 39 ~
Main m = new Main();

m.Show();
this.Hide();
}
{
this.Validate();
MessageBox.Show("Update successful", "Message", MessageBoxButtons.OK,
MessageBoxIcon.Information);
}
}
}
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Superdrug : Form
{
public Superdrug()
{
}
private void superdrugBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
this.superdrugBindingSource.EndEdit();
}
private void Superdrug_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet5.Superdrug' table. You
this.superdrugTableAdapter.Fill(this.cosmeticsDataSet5.Superdrug);
}
{
~ 40 ~

m.Show();
this.Hide();

{
this.Validate();
this.superdrugBindingSource.EndEdit();
}
{
{
{
}
}
}

{
Application.Exit();
}
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
System.Data.OleDb;
{
public partial class Oxy : Form
{
private OleDbConnection connection = new OleDbConnection();
public Oxy()
{
~ 41 ~
connection.ConnectionString = @"Provider=Microsoft.ACE.OLEDB.12.0;Data
Persist Security Info=False;";
}
private void btn_save_Click(object sender, EventArgs e)
{
this.Validate();
this.oxyBindingSource.EndEdit();
this.tableAdapterManager.UpdateAll(this.cosmeticsDataSet);
}
private void oxyBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
}
private void Oxy_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet.Oxy' table. You can move,
or remove it, as needed.
this.oxyTableAdapter.Fill(this.cosmeticsDataSet.Oxy);
}
private void btn_delete_Click(object sender, EventArgs e)
{
{
{
}
}
}
private void btn_view_Click(object sender, EventArgs e)
{
Application.Exit();
}
private void btn_update_Click(object sender, EventArgs e)
{
this.Validate();
}
{
~ 42 ~
m.Show();
this.Hide();
}
private void oxyBindingNavigator_RefreshItems(object sender, EventArgs e)
{
}
private void bindingNavigatorMoveFirstItem_Click(object sender, EventArgs e)
{
}
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Mua : Form
{
public Mua()
{
}
private void thebodyshopBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
}
private void Mua_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet4.Mua' table. You can
move, or remove it, as needed.
~ 43 ~
this.muaTableAdapter.Fill(this.cosmeticsDataSet4.Mua);
// TODO: This line of code loads data into the 'cosmeticsDataSet4.Mua' table. You can
this.muaTableAdapter.Fill(this.cosmeticsDataSet4.Mua);
// TODO: This line of code loads data into the 'cosmeticsDataSet3.Thebodyshop' table. You
}
{
{
{
}
}
}
{
m.Show();
this.Hide();
}
{
this.Validate();
this.muaBindingSource.EndEdit();
}

{
Application.Exit();
}
~ 44 ~
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Mothercare : Form
{
public Mothercare()
{
}
private void mothercareBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
this.mothercareBindingSource.EndEdit();
}
private void Mothercare_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet6.Mothercare' table. You
this.mothercareTableAdapter.Fill(this.cosmeticsDataSet6.Mothercare);
}
{
this.Validate();
this.mothercareBindingSource.EndEdit();
}
{
{
{
~ 45 ~
}
{
Application.Exit();
}

{
m.Show();
this.Hide();
}
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Lipice : Form
{
public Lipice()
{
}
private void lipiceBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
this.lipiceBindingSource.EndEdit();
}
private void Lipice_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet2.Lipice' table. You can
this.lipiceTableAdapter.Fill(this.cosmeticsDataSet2.Lipice);
}
~ 46 ~

{
this.Validate();
this.lipiceBindingSource.EndEdit();
}
{
m.Show();
this.Hide();
}
{
{
{
}
}
}
{
Application.Exit();
}
}
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Dulgon : Form
{
public Dulgon()
{
}
~ 47 ~
private void label3_Click(object sender, EventArgs e)

{
}
private void dulgonBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
this.dulgonBindingSource.EndEdit();
}
private void Dulgon_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet1.Dulgon' table. You can
this.dulgonTableAdapter.Fill(this.cosmeticsDataSet1.Dulgon);
}
{
m.Show();
this.Hide();
}
{
this.Validate();
this.dulgonBindingSource.EndEdit();
}
{
{
{
}
}
}

{
Application.Exit();
}
~ 48 ~
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Drawing;
System.Linq;
System.Text;
{
public partial class Acnes : Form
{
public Acnes()
{
}
private void acnesBindingNavigatorSaveItem_Click(object sender, EventArgs e)
{
this.Validate();
this.acnesBindingSource.EndEdit();
}
private void Acnes_Load(object sender, EventArgs e)
{
// TODO: This line of code loads data into the 'cosmeticsDataSet7.Acnes' table. You can
this.acnesTableAdapter.Fill(this.cosmeticsDataSet7.Acnes);
}
private void acnesDataGridView_CellContentClick(object sender, DataGridViewCellEventArgs
e)
{
}
{
m.Show();
this.Hide();
}
{
this.Validate();
this.acnesBindingSource.EndEdit();
~ 49 ~
}
{
{
{
}
}
}
{
Application.Exit();
}
}
~ 50 ~

Documentation On Warehouse Management Sy

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

Documentation On Warehouse Management Sy

Uploaded by

Copyright:

Available Formats

Documentation on

BANGLADESH UNIVERSITY OF BUSINESS AND

Submitted Date: 15th Oct, 2016

About the Developers :

With Best Regards,

Introduction of The Project

1.1 Project Objectives

System Requirement Study

4.1 Study of Current System

4.2 Problems And Weakness of Current

4.3 Life Cycle

Implementation Planning &

7.1 Context Level Diagram

7.4 E-R Model Diagram

Screen Short And User Manual

9.1 Advantage of Project

9.6 Lessons Learned

Conclusion & Discussion

1.2. Features of Project:

Add information of new product.

Update the information of products.

Delete the information.

Searching of products/workers marks by index no.

Easy access of saved data inside the system.

1.3 Scope of Project:

For doing work more accurately.

2.2 History of C# Language:

2.3 Features of C#:

Arbitrary async returns

3.2 Hardware Requirement

4.1 Study of Current System :

4.2 Problems And Weakness of Current System :

So much time consume in preparing registers which is having replicated data

Figure 1.1: Iterative and Incremental Life Cycle

Design the physical system.

Fig6.2: Testing Step

7.2 0-Level Data Flow Diagram:

Fig: 0- Level Data Flow Diagram for Warehouse Management System

7.3 Use Case Diagram

Fig: Use Case Diagram For Warehouse Management System

7.4 E-R Model Diagram

Fig: E-R Model Diagram For Warehouse Management System

Screen Shot And User Manual

Fig 8.1: Screen shot showing First Page as login page

Fig 8.1: Screen shot showing next page

Fig 8.1: Screen shot showing manager page

Fig 8.1: Screen shot showing a brand of products

Fig 8.1: Screen shot showing add products

Fig 8.1: Screen shot showing update product page

Fig 8.1: Screen shot showing delete item

Fig 8.1: Screen shot showing Reset information

Fig 8.1: Screen shot showing view Item

9.3 Project Limitation:

9.4 Difficulty faced during development:

9.5 Scope of Future Application:

It can be made online

9.6 Lessons Learned:

10.3 Problem Encountered and Possible Solutions:

MessageBox.Show("Username and Password is correct");

private void Form1_Load(object sender, EventArgs e)

Main m = new Main();

Main m = new Main();

private void button3_Click(object sender, EventArgs e)