Complete Final Bhaumik

4th sem D.C.
E Inventory management 086400307543
INVENTORY MANAGEMENT
Created By: - Bhaumik Patel

Jay Patel
Rutvik Patel
Rishita Patel
Neha Patel
Daxa Rathva
Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

1
4th sem D.C.E Inventory management 086400307543
Inventory Definition
Inventory management system is used to keep information about
products, supplier and customers. This system is also useful for
display message when the product quality is below its level and
also display message when the product is expired. This system is
also used to know the detail about demanded products in market.

2
Visibility Plan:-
i) Meeting with the client:-
- After developing the whole objective meet with the

client, on which time and also tell the duration of
time of meeting.
ii) Group Meeting:-
- The group meeting will follow the pattern of

communication.
1) The all group member will inform about the

meeting. First decide the particular venue & time of
meeting.
2) The one group member will pass the message in
circular manner through mail, phone or personally.
3) The next meeting will be planned in the same
meeting only, the routine notes data will be
maintain by all members.
4) The progress reports and notes will maintain by the
one member for the document and forward to all
through mail or in written note form.
5) Discuss some brief ideas for this application
between the team members.
6) Determine which functionality of our system will
provide to the client and design that way.

3
SYSTEM REQUIREMENTS
HARDWARE REQUIREMENTS:-
1. 40 GB Hard Disk
2. 256 MB Ram
3. Floppy Drive 1.44MB
4. Monitor
5. Keyboard
6. Processor PIV
SOFTWARE REQUIREMENTS:-
1. Visual Basic 6.0
2. Windows 2000/XP
3. MS Access

4
STRUCTURE TABLE

5
DRAWBACKS OF OLD MANAGEMENT:-
As we know the manual processing is quite tedious,

time consuming, less accurate in comparison to
computerized processing. Obviously the
Present system is not is exception consultant encountering
all the above problems.
1. Time consuming.
2. It is very tedious.
3. All information is not placed separately.
4. Lot of paper work.
5. Slow data processing.
6. Not user-friendly environment.
7. It is difficult to found records due file

a. Management system.

6
CAPABILITIES OF NEW MANAGEMENT SYSTEM:-
In new computerized system I tried to give these facilities.
1. Manually system changes into computerized

a. System.
2. Friendly user interface.
3. Time saving.
4. Save paper work.
5. Connecting to database so we use different type of

queries, data report.
6. Give facility of different type of inquiry.
7. Formatted data.
8. Data’s are easily approachable.

7
Iterative Waterfall Model
ITTERATIVE WATERFALL MODEL
For model:-
1).It suggests a systematic sequential approach to s/w
development that begins with customer specification of
requirement and progress through planning, modeling,
construction and deployment.
2).The entire requirements for the reporting are known

before so this process model suits Inventory management.

8
Risk Analysis:-
1) Problem of electricity power:
Solution: Use the UPS in spare for solving the problem of
electricity.
2) Employee who are dummy and actually not the employee of
company and trying to login.
Solution:-Display the message if type mismatched.
3) Something is missing in software and we knew after completion
of software.
Solution: - With the feedback policy of development, it can been
modified.

9
1. Introduction
1.1 Purpose
Inventory Management must be designed to meet the
dictates of market place and support the company’s Strategic
Plan. The many changes in the market demand, new
opportunities due to worldwide marketing, global sourcing of
materials and new manufacturing technology means many
companies need to change their Inventory Management approach
and change the process for Inventory Control.
1.2 Document Conventions
Main Headings:
Font: Calibri Face: Bold Size: 26
Sub – sections:
Font: Calibri Face: Bold Size: 20
Other Text Explanation:
Font: Calibri Face: Normal Size Size: 16

10
1.3 Intended Audience and Reading Suggestions

 This document is used by developers, project managers,
users, testers during the subsequent software engineering
activities and is written by Software Analysts. The Business
Analyst can review this document to verify that the
development team has a correct understanding of the
requirements stated in the Business Requirements
Specification.
 Customer: The user of the system will get a clear idea of the
software requirements to be developed.
Developers: Project developers get a clear and quick
understanding of the methodology involved.
Tester: Testers would have a clear understanding of what
each requirement stands for and how the code should
perform in order for the requirement to be satisfied.
 Authors of this document suggest customer to go through
the requirements section thoroughly to gain a better
understanding of the process flow. Developers and Testers
can use this documentation as a resource for developing the
new product.

11
1.4 Project Scope

This document will be confined to a set of Software
Requirements that are used to develop a tool that is used to
reserve resources of an organization. The tool developed
will be user friendly and would require minimal entry. This
document covers the high level descriptions of all the
functionalities that the RRS tool will provide. The scope of
this document is limited to describing what features will be
made available. This is a foundation for all the engineering
activities that would take place. It covers every minute detail
of the project’s requirements; however it will not cover any
details on specific programming languages or development
tools that will be used later in this process.
1.5 References
RAJIB MALL
ROJER.S.PRESSMAN
MADULIKA JAIN
www.w3schools.com
www.google.com

12
2. Overall Description
2.1 Product Perspective
The Software is a based interface which will replace the
existing method of reservation by way of human officer and
manual record keeping.
2.2 Product Features
This Software will allow three levels of users
(Administrators, Managers, and Users) to reserve resources.
Additionally Managers will be able to manage the Users
subordinate to them and Administrators will have full
authority to manage reservations, manage resources and
manage users. The RRS also includes secure login and usage
reports.
2.3 User Classes and Characteristics
The three different user classes are administrators,
managers, and basic users. Administrators have full rights to
manage the entire system including managing user,
managing resources, and managing reservations. Manager
create user accounts for users for which they manage.
Managers will be able to cancel one of their user's
reservations, modify the user's account and remove user
account for which they are responsible. Lastly, the basic
users will only have the ability to update their own account
information and to make reservations and cancel their own
reservations.

13
2.4 Operating Environment

This Application will run on a 32-bit Windows XP/Vista
Operating system. It requires vb6.0 and ms access.
2.5 Design and Implementation Constraints
This Application Design in vb 6.o And Data Base Create in ms
access
2.6 User Documentation
This Application will have a user manual delivered with the
software in pdf format.

14
DATA DICTIONARY
TABLE:- USERLOG
FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

NAME TYPE
NAME TEXT N N N NA USER NAME 4 digit integer
greater than 50
PASS TEXT N N N NA VLID PASS 4 digit integer
greater than 20
TABLE:- SALE

NAME TYPE
SDATE TEXT N N N NA SALE DATE 4 digit integer
greater than 50
CNAME TEXT N N N NA CUSTOMER 4 digit integer
NAME greater than 50
CADDRESS TEXT N N N NA CUSTOMER 4 digit integer
ADDRESS greater than
100
ITEM TEXT N N N NA ITEM GROUP 4 digit integer
GROUP NAME greater than 50
ITEM NAME TEXT N N N NA ITEM NAME 4 digit integer
greater than 50
ITEM SIZE NUMBER N N N NA ITEM SIZE 4 digit integer
greater than 50
PRICE NUMBER N N N NA ITEM PRICE 4 digit integer
greater than 50
QTY NUMBER N N N NA QUANTITY OF 4 digit integer
ITEM greater than 50
TOTAL NUMBER N N N NA TOTAL 4 digit integer
AMOUNT AMOUNT OF greater than 50
ITEM

15
TABLE:- PURCHASE

NAME TYPE
PDATE TEXT N N N NA PURCHES 4 digit integer
DATE greater than 50
DEALER TEXT N N N NA DEALER 4 digit integer
NAME NAME greater than 50
greater than 50
greater than 50
greater than 50
QTY NUMBER N N N NA ITEM 4 digit integer
QUANTITY greater than 50
TOTAL NUMBER N N N NA TOTAL PRICE 4 digit integer
AMOUNT greater than 50
TABLE:- ITEM MASTER

NAME TYPE
SERIAL_NO TEXT N Y N NA ITEM SERIAL 4 digit integer
NUMBER greater than 50
greater than 50
GROUP TEXT N N N NA ITEM GROUP 4 digit integer
NAME NAME greater than 50
CODE NO NUMBER N N N NA ITEM CODE 4 digit integer
greater than 50
greater than 50
QTY NUMBER N N N NA ITEM 4 digit integer
QUANTITY greater than 50

16
TABLE:- BILL

NAME TYPE
SDATE TEXT N N N NA SALE DATE 4 digit integer
greater than 50
CNAME TEXT N N N NA CUSTOMER 4 digit integer
NAME greater than 50
CADDRESS TEXT N N N NA CUSTOMER 4 digit integer
ADDRESS greater than
100
greater than 50
greater than 50
greater than 50
QTY NUMBER N N N NA QUANTITY OF 4 digit integer
ITEM greater than 50
TOTAL NUMBER N N N NA TOTAL 4 digit integer
AMOUNT AMOUNT OF greater than 50
ITEM
TABLE:- EXPENSE

NAME TYPE
EDATE TEXT N N N NA EXPENSE 4 digit integer
DATE greater than 50
DETAIL TEXT N N N NA EXPENSE 4 digit integer
DETAIL greater than 50
AMOUNT NUMBER N N N NA AMOUNT 4 digit integer
greater than 50

17
ERD Notations
ENTITY
RELATIONSHIP
ATTRIBUTE
KEY ATTRIBUTE
DATA FLOW

18
r ADMIN ER-DIAGRAM
MANAGE NAME
ID
ADDRESS
ORDER
CUSTOMER HAS SUPPLIER
PHONE
ID
PHONE
CHECK GOODS
MANAGE
NAME
ADDRESS
BILL NO.
SALES
ITEM
ID DATE
DISCOUNT
NAME
BILL AMOUNT
PRICE
COUSTOMER ID
STOCK
ID
SELECT QOH
19
SYSTEM DIAGRAM:-INVENTORY SYSTEM
INVENTORY SYSTEM
ADMIN
DATABASE SYSTEM
(WAREHOUSE) BILLING SYSTEM

20
DFD Notations
It represents a process or transform

that is applied to data.
________
________ It represents data store-stored
information that is used by software.
It represents one or more data items.
It represents external entities.

21
DFD
CONTEXT DIAGRAM
ADD NEW ITEM
SALE DETAIL
PURCHASE DETAIL
ENTER USRE NAME AND PASS
INVENTORY
ADMIN SYSTEM
LOGIN SUCCESS
SALE BILL

22
LEVEL 0
STORE SALE DETAIL
SALE DETAIL 1.0

ADMIN 1 SALE
SALES
BILL DETAIL
BILL SLIP PROCESS
2 BILL
PRINT BILL
2.0 STORE PURCHASE DETAIL

PURCHASE DETAIL
PURCHASE 3 PURCHASE
PROCESS PURCHASE DETAIL
PURCHASE DETAIL
ITEM DETAIL
UPDATE DETAIL 3.0
4 ITEM MASTER
UPDATE
PROCESS ITEM DETAIL RETURN
ALL DETAIL RETUN TO

ADMIN

23
LEVEL 1
ORDER APPROVAL
ADMIN ENTER USERNAME / PASS
LOGIN TO ADMIN
1.1
LOGIN
1.2 ORDER
PURCHASE DEALER
ORDER ITEM RECEIVE
1.5
AVAIABILITY
CHECK
ITEAM RECEIVED SEARCH ITEAM ITEM
UPDATE STOCK
1 PURCHASE
2 SALE
SUPLIER 1.3 1.4

SALE
SEALE
ORDER
PROCESS
ITEAMS SUPPLED
DEMAND ITEAM
COUSTOMER
1.6
BILL REQUEST BILL 3 BILL

PROCESS
PRINT OUT BILL

24
Activity Diagram
LOGIN
INPUT TRIES REMAIN
SELECT MEJOR PROMPT

FUNCTION FOR RETRY
SELECT OTER OPTION ALSO
SELECT ORDER
OPTION
NO INPUT TRIDE REMAIN
VERIFY ORDER
EXECUTE ORDER
FAILURE
SELECT TRADE
SEND FAIL NOTICE
CLOSE ORDER

25
Sequence Diagram
Purchase
Purchase Purchase
Boundary History
Register
Purchase
Register
Purchase
Confirm
Purchase
Record
Confirm

26
Admin Login
Administrator Login Goods Supplier Logout
or
s
Login
(id)
Add
Goods
Remove
Goods
Add
supplier
Delete
Supplier
Logout

27
Sale
Register Register Sales

Sales Sales History
Boundary Controller
Register
Sales
Register
Register Sales
Sales Create
Sales
Record
Confirm
Confirm

28
Use Case Diagram
ADMIN

29
GOI
Enter User Name and Pass

30
When you click add item you add item detail

31
Add new item
Add new item and when u click save data store in data base

32
When u click sale item you open sale detail

33
Add sale detail and save data

34
When you click purchase item you choice to purchase

35
Purchase new item and click in save all data save in data base

36
When u click daily expense open daily expense detail

37
When you click view detail you show detail menu

38
When you click stock detail u show stock detail

39
Show item detail

40
When u click sale detail u show sale detail

41
Show sale detail

42
When u click purchase detail you show purchase detail

43
Show purchase detail

44
When you click reorder level u show all record

45
Add reorder detail

46
Show reorder detail

47
When u click expense detail show expense detail

48
Show expense detail

49
When u click make a new bill you add detail

50
Add bill detail and print bill

51

52

Complete Final Bhaumik

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Complete Final Bhaumik

Transféré par

Droits d'auteur :

Formats disponibles

4th sem D.C.

E Inventory management 086400307543

Created By: - Bhaumik Patel

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

i) Meeting with the client:-

- After developing the whole objective meet with the

ii) Group Meeting:-

- The group meeting will follow the pattern of

1) The all group member will inform about the

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

3. Floppy Drive 1.44MB

1. Visual Basic 6.0

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

DRAWBACKS OF OLD MANAGEMENT:-

As we know the manual processing is quite tedious,

3. All information is not placed separately.

4. Lot of paper work.

5. Slow data processing.

6. Not user-friendly environment.

7. It is difficult to found records due file

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

CAPABILITIES OF NEW MANAGEMENT SYSTEM:-

In new computerized system I tried to give these facilities.

1. Manually system changes into computerized

2. Friendly user interface.

4. Save paper work.

5. Connecting to database so we use different type of

6. Give facility of different type of inquiry.

8. Data’s are easily approachable.

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

Iterative Waterfall Model

ITTERATIVE WATERFALL MODEL

2).The entire requirements for the reporting are known

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

1.2 Document Conventions

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

1.3 Intended Audience and Reading Suggestions

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

1.4 Project Scope

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

2.4 Operating Environment

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

TABLE:- ITEM MASTER

FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

FIELD DATA Null? Pkey? Fkey? Ref table DESCRIPTION Domain

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

SYSTEM DIAGRAM:-INVENTORY SYSTEM

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

It represents a process or transform

It represents one or more data items.

It represents external entities.

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA