Introduction

1
  An Overview:

“Provision Store Management System” is a highly

enhanced from the existing system. The owners of stores
are providing with user-friendly interactive system. Our
system will provide a best way to manage a provision
stores. It also provides a best service for selling process.

 Objectives of the system :

Automated Provision store management system

for provision store enhances the facilities with implement
latest technologies. This application enables instant access
of information for the items, customers, dealers, sells etc. ,
which increase the selling services, and satisfaction that
keeps building the personal skill towards.

In this system the owner of the store can Insert,

Update, Save, Search and delete operation for various fields
of the system and can also generate various reports.

 High level of security

2
  Instant data access

 Consistent Process Approach

 Easy reporting

 Disadvantages of old system:

As we know the manual processing is quite tedious,

time
Consuming and 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
management system.

 Need For New System:

3
1. Manually system changes into Computerized system
2. Friendly user interface
3. Time saving
4. Save paper work
5. Connecting database so we use different type of
quires, data report.
6. Give facility of different type of inquiry
7. Formatted data
8. Data’s are easily approachable
 Hardware Requirement :

1. Processor: Pentium-4
2. RAM: 512 MB or above
3. Hard disk: 80 MB or above
4. Monitor: 17’’ VGA
5. Mouse
6. CD Rom

 Software Requirement :

1. Operating System: Window XP

2. Front End : Microsoft Visual Studio 2008
3. Back End: Microsoft SQL Server 2005

4
 DATA
FLOW
DIAGRAMS
5
 Context Level Diagram (0 – Level):

6
7
 1 – level :

Bill Master

Stock Info.

3.0
Bill Info.
Report Generation

8
 ENTITY
RELATIONSHIP
DIAGRAMS

9
 C_na C_ad
C_ID
me d

CUSTOMER C_cn
o

C
S

Item_ID Item_Na
1
mee

Cat_ID STOCK Qty

D

R.P.U
. 1

S
D

M Dlr_Nam
Dlr_ID
e

DELAR

Dlr_Ad Dlr_Cn 10
d o
HIERARCHICAL
RELATIONSHIP
DIAGRAM

11
12
 P.S.M.S.

Purchas Sale
Master Stock Report Exit
er Item

Order Stock Sale Item Items

detail Entry

User Sell Info.

Master Order

Dealer
Master

Category
Master

Exit

13
 DATA
DICTIONARY

14
 Login Table :

 Dealer Master :

15
 Category Master :

16
  Order Master :

Item Master :

17
Stock Master :

Bill Master :

18
19
SCREEN
SHOTS

20
 Login Form :

21
 Master Form :

22
 User Master :

23
 User Master – Search :

24
 User Master – Update :

25
 User Master – Delete :

26
27
 Category Master :

28
 Category Master – Search :

29
 Dealer Master :

30
 Dealer Master – Search :

31
 Order Master :

32
 Order Master – Search :

33
34
 Item Master :

35
 Item Master – Search :

36
 Sell Item :

37
 Sell Info :

38
 Sell Info – Search :

39
REPORTS

40
 Bill :

41
 Item Report :

42
43
 Order Report :

44
 TESTING

The testing is most important thing in Project

Development. The Project which we implement is an
organization is first requiring the check all the module are
properly working or not. If any exception generated when
what happen, our project coding show those errors and
handle or not.

The testing of each and every module are more

important so we can check one by one module with divide
in tiny parts so we can easily find out error or mistakes
which are make more trouble in future.

With support of testing we finalized the project for

global market. Without testing we cannot give project to
any user because when error will be occur then at that time
we have no any proper idea about that. So at the time of
deliver project to user testing is the most important factor
before finalizing, and if some other idea occurs in their mind
than we can easily modify in project, so user may satisfy
with our service.

Testing take part in different level, like primary level

testing, in this level we only check the documentation which
provided by the company or organization. After completing
this testing we are going to the next phase of testing that is
called middle level testing. In this level of testing, we check
the flow of control in the system is correct or not. And in
the last phase called final level testing, here, we check the

45
coding of existing system. And also check each form, report
and utilities are working properly or not. Because after that
we will give this project to the user and it called software.

ENHANCEMENT OF THE PROJECT

 We will design this system online.

 We can also add Daily, Weekly and Monthly backup

utility.

 We can also add different utilities like cal c, calendar in

this system.

BIBLIOGRAPHY

 www.google.com

 www.scribd.com

 www.yahoosearch.com

 www.wikipedia.com

46