complete final bhaumik

8/8/2019 Complete Final Bhaumik

1/52

4th

sem D.C.E Inventory management 086400307543

Bhaumik H.Patel GUIDED BY: - DHARMISHTHA SINHA

1

INVENTORY MANAGEMENT

Created By: - Bhaumik Patel

Jay Patel

Rutvik Patel

Rishita Patel

Neha Patel

Daxa Rathva


2/52

4th



2

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 isalso used to know the detail about demanded products in market.


3/52

4th



3

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 incircular 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 applicationbetween the team members.

6)Determine which functionality of our system will

provide to the client and design that way.


4/52

4th



4

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


5/52

4th



5

STRUCTURE TABLE


6/52

4th



6

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.


7/52

4th



7

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. Datas are easily approachable.


8/52

4th



8

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.


9/52

4th



9

Risk Analysis:-1) Problem of electricity power:

Solution:Use the UPS in spare for solving the problem ofelectricity.

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.


10/52

4th



10

1. Introduction1.1 Purpose

Inventory Management must be designed to meet the

dictates of market place and support the companys Strategic

Plan. The many changes in the market demand, new

opportunities due to worldwide marketing, global sourcing of

materials and new manufacturing technology means manycompanies need to change their Inventory Management approach

and change the process for Inventory Control.

1.2 Document ConventionsMain 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


11/52

4th



11

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 RequirementsSpecification.

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.


12/52

4th



12

1.4 Project ScopeThis 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 projects 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 ReferencesRAJIB MALL

ROJER.S.PRESSMAN

MADULIKA JAIN

www.w3schools.com

www.google.com
http://www.w3schools.com/http://www.w3schools.com/http://www.google.com/http://www.google.com/http://www.google.com/http://www.w3schools.com/


13/52

4th



13

2. Overall Description

2.1 Product PerspectiveThe 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 FeaturesThis Software will allow three levels of users

(Administrators, Managers, and Users) to reserve resources.

Additionally Managers will be able to manage the Userssubordinate 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 CharacteristicsThe three different user classes are administrators,

managers, and basic users. Administrators have full rights tomanage 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 ownreservations.


14/52

4th



14

2.4 Operating EnvironmentThis Application will run on a 32-bit Windows XP/Vista

Operating system. It requires vb6.0 and ms access.

2.5 Design and Implementation ConstraintsThis Application Design in vb 6.o And Data Base Create in ms

access

2.6 User DocumentationThis Application will have a user manual delivered with the

software in pdf format.


15/52

4th



15

DATA DICTIONARY

TABLE:- USERLOG

FIELD

NAME

DATA

TYPE

Null? Pkey? Fkey? Ref table DESCRIPTION Domain

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

FIELD

NAME

DATA

TYPE


SDATE TEXT N N N NA SALE DATE 4 digit integer

greater than 50

CNAME TEXT N N N NA CUSTOMER

NAME

4 digit integer

greater than 50

CADDRESS TEXT N N N NA CUSTOMER

ADDRESS

4 digit integer

greater than

100

ITEMGROUP

TEXT N N N NA ITEM GROUPNAME

4 digit integergreater 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

ITEM

4 digit integer

greater than 50

TOTAL

AMOUNT

NUMBER N N N NA TOTAL

AMOUNT OF

ITEM

4 digit integer

greater than 50


16/52

4th



16

TABLE:- PURCHASE

FIELD

NAME

DATA

TYPE


PDATE TEXT N N N NA PURCHES

DATE

4 digit integer

greater than 50

DEALER

NAME

TEXT N N N NA DEALER

NAME

4 digit integer

greater than 50

ITEM

GROUP

TEXT N N N NA ITEM GROUP

NAME

4 digit integer

greater than 50


greater than 50


greater than 50


greater than 50

QTY NUMBER N N N NA ITEM

QUANTITY

4 digit integer

greater than 50

TOTAL

AMOUNT

NUMBER N N N NA TOTAL PRICE 4 digit integer

greater than 50

TABLE:- ITEM MASTER

FIELD

NAME

DATA

TYPE


SERIAL_NO TEXT N Y N NA ITEM SERIAL

NUMBER

4 digit integer

greater than 50


greater than 50

GROUP

NAME


NAME

4 digit integer

greater than 50CODE NO NUMBER N N N NA ITEM CODE 4 digit integer

greater than 50


greater than 50

QTY NUMBER N N N NA ITEM

QUANTITY

4 digit integer

greater than 50


17/52

4th



17

TABLE:- BILL

FIELD

NAME

DATA

TYPE


SDATE TEXT N N N NA SALE DATE 4 digit integer

greater than 50

CNAME TEXT N N N NA CUSTOMER

NAME

4 digit integer

greater than 50

CADDRESS TEXT N N N NA CUSTOMER

ADDRESS

4 digit integer

greater than

100

ITEM

GROUP


NAME

4 digit integer

greater than 50


greater than 50


greater than 50


greater than 50

QTY NUMBER N N N NA QUANTITY OF

ITEM

4 digit integer

greater than 50

TOTALAMOUNT

NUMBER N N N NA TOTALAMOUNT OF

ITEM

4 digit integergreater than 50

TABLE:- EXPENSE

FIELD

NAME

DATA

TYPE


EDATE TEXT N N N NA EXPENSE

DATE

4 digit integer

greater than 50DETAIL TEXT N N N NA EXPENSE

DETAIL

4 digit integer

greater than 50

AMOUNT NUMBER N N N NA AMOUNT 4 digit integer

greater than 50


18/52

4th



18

ERD Notations

ENTITY

RELATIONSHIP

ATTRIBUTE

KEY ATTRIBUTE

DATA FLOW


19/52

4th



19

r ER-DIAGRAMADMIN

MANAGE

CUSTOMER SUPPLIER

ITEM

SALES

ID

PHONE

ADDRESS

NAME

PRICE

BILL NO.

DISCOUNT

COUSTOMER ID

BILL AMOUNT

DATE

HAS

IDNAME

ADDRESS

PHONE

ORDER

GOODS

MANAGE

CHECK

ID

NAME

STOCK

ID

SELECT QOH


20/52

4th



20

SYSTEM DIAGRAM:-INVENTORY SYSTEM

ADMIN

DATABASE SYSTEM

(WAREHOUSE) BILLING SYSTEM

INVENTORY SYSTEM


21/52

4th



21

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.


22/52

4th



22

DFD

CONTEXT DIAGRAM

ENTER USRE NAME AND PASS

LOGIN SUCCESS

INVENTORY

SYSTEMADMIN

PURCHASE DETAIL

SALE DETAIL

SALE BILL

ADD NEW ITEM


23/52

4th



23

LEVEL 0

SALE DETAIL1 SALE

PURCHASE DETAIL

UPDATE DETAIL

ADMIN1.0

SALES

PROCESS

2.0

PURCHASE

PROCESS

3.0

UPDATE

PROCESS

2 BILL

STORE SALE DETAIL

PRINT BILL

BILL SLIP

3 PURCHASE

BILL DETAIL

STORE PURCHASE DETAIL

PURCHASE DETAILPURCHASE DETAIL

4 ITEM MASTER

ITEM DETAIL

ITEM DETAIL RETURN

ALL DETAIL RETUN TO

ADMIN


24/52

4th



24

LEVEL 1

ORDER APPROVAL

ENTER USERNAME / PASS

LOGIN TO ADMIN

ORDER

ITEM RECEIVE

AVAIABILITY

ITEAM RECEIVED SEARCH ITEAM

UPDATE STOCK

1 PURCHASE

2 SALE

ITEAMS SUPPLED

DEMAND ITEAM

BILL REQUEST 3 BILL

PRINT OUT BILL

ADMIN

1.2

PURCHASEORDER

DEALER

1.4

SEALE

PROCESS

COUSTOMER

1.5

CHECK

ITEM

1.1

LOGIN

1.6

BILL

PROCESS

1.3

SALE

ORDER

SUPLIER


25/52

4th



25

Activity Diagram

INPUT TRIES REMAIN

SELECT OTER OPTION ALSO

LOGIN

PROMPT

FOR RETRYSELECT MEJOR

FUNCTION

SELECT ORDER

OPTION

VERIFY ORDER

EXECUTE ORDER

SELECT TRADESEND FAIL NOTICE

CLOSE ORDER

NO INPUT TRIDE REMAIN

FAILURE


26/52


27/52

4th



27

Admin Login

Administrator Login

Login

(id)

Goods

Add

Goods

Remove

Goods

Supplier

Addsupplier

Delete

Supplier

Logout

Logout


28/52

4th



28

\

Sale

Register

Sales

Boundary

Register

Sales

Controller

Sales

History

Sales

Record

Register

Sales

Confirm

Confirm

RegisterSales

Create

RegisterSales


29/52

4th



29

Use Case Diagram

ADMIN


30/52

4th



30

GOI

Enter User Name and Pass


31/52

4th



31

When you click add item you add item detail


32/52

4th



32

Add new item

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


33/52

4th



33

When u click sale item you open sale detail


34/52

4th



34

Add sale detail and save data


35/52

4th



35

When you click purchase item you choice to purchase


36/52

4th



36

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


37/52

4th



37

When u click daily expense open daily expense detail


38/52

4th



38

When you click view detail you show detail menu


39/52

4th



39

When you click stock detail u show stock detail


40/52

4th



40

Show item detail


41/52

4th



41

When u click sale detail u show sale detail


42/52

4th



42

Show sale detail


43/52

4th



43

When u click purchase detail you show purchase detail


44/52

4th



44

Show purchase detail


45/52

4th



45

When you click reorder level u show all record


46/52

4th



46

Add reorder detail


47/52

4th



47

Show reorder detail


48/52

4th



48

When u click expense detail show expense detail


49/52

4th



49

Show expense detail


50/52

4th



50

When u click make a new bill you add detail


51/52

4th



51

Add bill detail and print bill


52/52

4th


complete final bhaumik

Documents