Professional Documents
Culture Documents
Of
IGNOU
By
INDEX
Sr. Subject Page
No. No.
1 Project Title 3
2 Declaration 4
3 Acknowledgement 5
3 Introduction 6
4 Objective of the Project 7
5 Project Category 9
6 System Configuration 10
7 Brief Introduction About Visual 12
Basic 6.0
8 About The Structured Query 18
Language (SQL)
9 Entity Relationship diagram 22
10 Database Table 24
11 Process Model 28
12 Activity Diagram 30
13 Date Flow Diagram 42
DFD Level 0 43
DFD Level 1 44
DFD Level 2 45
DFD Level 3 46
DFD Level 4 46
14 Module 49
15 Report 49
15 Software Testing 50
16 Objectives 51
17 Timeline 52
18 Future Scope and Future Scope 54
19 Bibliography 55
2
Retail Store Management System
Project Definition This ‘Retail Store Management System VB 6.0 based application
Maintain Retail Store Stock.
Team size 1
Platform 6.0
Duration 6 months
3
Retail Store Management System
DECLARATION
Place: SURAT
Date: 25/12/2011
------------------------------
Signature of the Student
Mr. Srikant Surendra Rout
Enrolment No: 092001678
Course: BCA
Semester: VIth
4
Retail Store Management System
ACKNOWLEDGEMENT
5
Retail Store Management System
Introduction
Development of large software system is extremely complex activity full
of various opportunities to introduction errors. Software Engineering is the
discipline that attempts to provide method to handle this complexity,
enabling us to produce reliable system software with maximum productivity.
It was felt that it is important and very instructive, not only to learn
the principles of software engineering but also apply them to a software
development project so that all aspects of development and be clearly seen on
project.
Product Record,
Categories Detail,
Dealer Record,
6
Retail Store Management System
Customer Record,
Various types of Grocery products, its cost, price are such kind of
record. These records are used at the time of Sales of product to the
customer. When Customer paid their Payment then keep the record of Payment &
7
Retail Store Management System
update the record. If we want to a record of customer as their Product wise
then it was tedious job.
Same as this many other tasks are also available such as Sales record,
purchase record etc. So in manual system records maintain processes are more
difficult. With the use of this project store can maintain their customer
record easily.
Project Category
8
Retail Store Management System
This project Category is Expert System which are
managed the Retail store processes. In this system we
can store products record.
9
Retail Store Management System
System Configuration
Hardware Requirements
Software Requirements
10
Retail Store Management System
Screen, including its position and its color. However, In VB , you just need
to drag and drop any graphical object anywhere on the form, and you can
change its color any time using the properties windows.
11
Retail Store Management System
On the other hand, because the user may click on a certain object
randomly, so each object has to be programmed independently to be able to
response to those actions (events). Therefore, a VB Program is made up of
many subprograms, each has its own program code, and each can be executed
independently and at the same time each can be linked together in one way or
another.
Visual Basic was derived from BASIC and enables the rapid application
development (RAD) of graphical user interface (GUI) applications, access to
databases using Data Access Objects, Remote Data Objects, or ActiveX Data
Objects, and creation of ActiveX controls and objects. Scripting languages
such as VBA and VBScript are syntactically similar to Visual Basic, but
perform differently.
Language Features
Like the BASIC programming language, Visual Basic was designed to be
easily learned and used by beginner programmers. The language not only allows
programmers to create simple GUI applications, but can also develop complex
applications. Programming in VB is a combination of visually arranging
components or controls on a form, specifying attributes and actions of those
components, and writing additional lines of code for more functionality.
Since default attributes and actions are defined for the components, a simple
program can be created without the programmer having to write many lines of
12
Retail Store Management System
code. Performance problems were experienced by earlier versions, but with
faster computers and native code compilation this has become less of an
issue.
This runtime is included by default in Windows 2000 and later, but for
earlier versions of Windows like 95/98/NT it must be distributed together
with the executable.
Controls have attributes and event handlers associated with them. Default
values are provided when the control is created, but may be changed by the
programmer. Many attribute values can be modified during run time based on
user actions or changes in the environment, providing a dynamic application.
For example, code can be inserted into the form resize event handler to
reposition a control so that it remains centered on the form, expands to fill
up the form, etc. By inserting code into the event handler for a keypress in
a text box, the program can automatically translate the case of the text
being entered, or even prevent certain characters from being inserted.
13
Retail Store Management System
appropriate event handlers. For example, a drop-down combination box will
automatically display its list and allow the user to select any element. An
event handler is called when an item is selected, which can then execute
additional code created by the programmer to perform some action based on
which element was selected, such as populating a related list.
The Visual Basic compiler is shared with other Visual Studio languages
(C, C++), but restrictions in the IDE do not allow the creation of some
targets (Windows model DLLs) and threading models.
Characteristics
By default, if a variable has not been declared or if no type
declaration character is specified, the variable is of type Variant.
14
Retail Store Management System
However this can be changed with Deftype statements such as DefInt,
DefBool, DefVar, DefObj, DefStr. There are 12 Deftype statements in
total offered by Visual Basic 6.0. The default type may be overridden
for a specific declaration by using a special suffix character on the
variable name (# for Double, ! for Single, & for Long, % for Integer, $
For String, and @ for Currency) or using the key phrase As (type). VB
can also be set in a mode that only explicitly declared variables can be
used with the command Option Explicit.
15
Retail Store Management System
16
Retail Store Management System
database language. Although SQL is often described as, and to a great extent
is, a declarative language, it also includes procedural elements. SQL
became a standard of the American National Standards Institute (ANSI) in
1986, and of the International Organization for Standards (ISO) in 1987.
Since then the standard has been enhanced several times with added features.
However, issues of SQL code portability between major RDBMS products still
exist due to lack of full compliance with, or different interpretations of
the standard. Among the reasons mentioned are the large size, and incomplete
specification of the standard, as well as vendor lock-in.
17
Retail Store Management System
Statements, which may have a persistent effect on schemata and data, or
which may control transactions, program flow, connections, sessions, or
diagnostics.
Queries:-
The most common operation in SQL is the query, which is performed with
the declarative SELECT statement. SELECT retrieves data from one or
more tables, or expressions. Standard SELECT statements have no persistent
effects on the database. Some non-standard implementations of SELECT can have
persistent effects, such as the SELECT INTO syntax that exists in some
databases.
Queries allow the user to describe desired data, leaving the database
management system (DBMS) responsible for planning, optimizing, and performing
the physical operations necessary to produce that result as it chooses.
18
Retail Store Management System
The FROM clause which indicates the table(s) from which data is to be
retrieved. The FROM clause can include optional JOIN sub clauses to
specify the rules for joining tables.
The WHERE clause includes a comparison predicate, which restricts the
rows returned by the query. The WHERE clause eliminates all rows from the
result set for which the comparison predicate does not evaluate to True.
The GROUP BY clause is used to project rows having common values into a
smaller set of rows. GROUP BY is often used in conjunction with SQL
aggregation functions or to eliminate duplicate rows from a result set.
The WHERE clause is applied before the GROUP BY clause.
The HAVING clause includes a predicate used to filter rows resulting
from the GROUP BY clause. Because it acts on the results of the GROUP
BY clause, aggregation functions can be used in the HAVING clause
predicate.
The ORDER BY clause identifies which columns are used to sort the
resulting data, and in which direction they should be sorted (options are
ascending or descending). Without an ORDER BY clause, the order of rows
returned by an SQL query is undefined.
19
Retail Store Management System
Entity
Attribute
Flow
Line
DIAGRAM
20
Retail Store Management System
Database Tables
21
Retail Store Management System
22
Retail Store Management System
No. Column Name Data Type Description
1. Bill_No Smallint Primary Key (A.I.)
To Store Purchase
2. Bill_Date DateTime
Bill Date
Foreign Key of
3. ID Smallint
Dealer
To Store the Grand
4. Grand_Total Smallint
Total
1. No Smallint No Of Product
25
Retail Store Management System
Process Model
Unified Modeling Language Manage Purchase
Detail
Manage Sales
Detail
Manage Product
Detail
Manage Stock
Manage Customer
Record
Administrat
Manage Delear
or Record
Manage Purchase
Return
Manage Sales
Return
Manage Bill
Record
Manage Company
Record
26
Retail Store Management System
Process Model
Customer
Detail
Receive
Payment
Purchase
Product
Get
Information
About Product
Get Information
About Issue Bills
Get Information
About Sales Return
27
Retail Store Management System
Activity Diagram
2). Sales Process Diagram
Get Customer
Detail
Fill Sales
Details
Check Empty No
Field
Yes
Validate Data No
yes
28
Retail Store Management System
Get Customer
Id
Fill Customer
Details
No
Check Empty Field
Yes
No
Validate Data
Yes
Customer Detail
Process
Complete & Save the
Record
29
Retail Store Management System
Put Customer
Id
Click On Ok
Button
Validate Data No
& Check Empty
Field
Yes
30
Retail Store Management System
Input Customer
Id
Input Cheque
Amount, Cheque No,
Cheque Date
Click On Ok
Button
Validate Data No
& Check Empty
Field
Yes
31
Retail Store Management System
Fill Purchase
Form Details
Check Empty No
Field
Yes
No
Validate Data
Yes
Record Store
in System
32
Retail Store Management System
Input Product
Name
No
Check Record
Yes
Show Product
Details
Fill Required
Information
Click On Save
Button
No
Validate Data
Yes
Record Store
in System
33
Retail Store Management System
No
Check Password &
Confirm Password
Equal
Yes
34
Retail Store Management System
Option
Select User
Input current
password & New
Password Correctly
No
Validate Data
Yes
Change Password
35
Retail Store Management System
Click on Administrator
Menu and Select Edit
Product
Details
Fill Details of
Product as form
No
Validate the Data &
Check Empty Field
Yes
Record Stored
36
Retail Store Management System
Click on Administrator
Menu and Select Edit
Store
Fill Details of
Store as Form
No
Validate the Data
& Check Empty
Field
Yes
Record Stored
37
Retail Store Management System
Click on Report
Select Report
which you want
Print or Exit
38
Retail Store Management System
The main merit of DFD is that it can provide an overview of what data a system
would process, what transformations of data are done, what data are stored and which
stored data are used, and where the result flows.
A DFD shows what kinds of data 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 (which is shown on a flowchart).
39
Retail Store Management System
DFD Level 0
Retail
User Product
Store
Managemen
t
System
DFD Level 1
40
Retail Store Management System
Purchase
Payment Retail Customer Detail
Store Order Detail
Managemen Supply Detail
t Product Detail
System
User
DFD Level 2
User Search
41
Retail Store Management System
Order
Purchase
Search
User DFD Level 3 Product
Apply
Filter
42
View
Category
Retail Store Management System
Cosmetics
Grocery
Stationary
DFD Level 4
Purchase
Product
43
Purchase
Retail Store Management System
MODULES
Main Function module
Contain Main function. So , Program execution start from main function
REPORTS
Product List Report
Dealer List Report
Purchase Report
Purchase Return Report
Sales Report
Sales Return Report
44
Retail Store Management System
Expire Medicines Report
Stock Report
Software Testing
Testing
Once the program code is designed and implemented, some testing
technique will be used to ensure the program function correctly.
Unit Testing
Individual modules will be tested against the specification and design
to confirm their correct operation.
Integration Testing
Several units will be tested together to see how they interact and to
confirm whether their overall function is performed correctly. This testing
will apply to each of the main section of code; the use interface, data
processing, etc.
System Testing
45
Retail Store Management System
46
Retail Store Management System
Objective
Principles
47
Retail Store Management System
48
Retail Store Management System
49
Retail Store Management System
Week 7 Week8
4. System Design
3
Interface Design
Milestone Design Complete
Testing
Milestone : Testing
Complete
Bibliography
50
Retail Store Management System
Website Name:-
www.visual-basic-6.com
http://www.sqlcourse.com
www.visualbasicbooks.com
www.agilemodeling.com/artifacts/dataFlowDiagram.htm
www.w3schools.com/sql
Book Name:-
Introduction To Systems Analysis And Design.
A Complete Visual Basic 6 Training Course: How to Programme:
Package.
51
Retail Store Management System
52