0% found this document useful (0 votes)
841 views32 pages

Super Market Project

1. The document discusses a proposed Super Market Management System project that aims to computerize manual activities in a supermarket. 2. The key aspects covered include maintaining daily purchase and sales details, updating product stock information, generating reports, and maintaining large volumes of data without difficulty. 3. The system is described as being user-friendly and efficiently carrying out purchase and sales processes without interruptions.

Uploaded by

AB Arthur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
841 views32 pages

Super Market Project

1. The document discusses a proposed Super Market Management System project that aims to computerize manual activities in a supermarket. 2. The key aspects covered include maintaining daily purchase and sales details, updating product stock information, generating reports, and maintaining large volumes of data without difficulty. 3. The system is described as being user-friendly and efficiently carrying out purchase and sales processes without interruptions.

Uploaded by

AB Arthur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 32

1.

INTRODUCTION

1.1 ABOUT THE PROJECT

This project report entitled “SUPER MARKET MANAGEMENT SYSTEM”


main goal of this project is to computerize all the manual activities involved in super
market.

Since the existing system is a manual one, lot of paper work and manpower are
needed, A large number of ledgers, papers, records, etc have to be kept for future use.
Searching and finding a particular detail of a customer from a large number of records
needs a large amount of time. Also the data can be lost in future. The main aim of this
project maintains the daily purchase, sales details and maintains the satisfaction of the
customer details.

The advantages of the proposed system is easily calculated for daily sales and
purchase details. In retrieval data maintained and easily updated to the user. The product
stock information updated for purchase and sales times. Generating reports and
maintaining large volume of data is accomplished without any difficulty.
[

It includes forms like sales, purchase, purchase return, staff details, customer
details, supplier details, product details and report. It covers all aspects of transaction that
comes in process of managing super market.

This system is one of the most important functions of the maintaining data activity.
It depends upon the level of the user. It product purchase and sales process should be
efficiently carried out without any interruption. It is sure that the operations efficiency is
increasing due to the existing system. Various options become easier as there is no need
to have lot of introduction regarding the software because it is so user friendly.

1
1.2 SYSTEM SPECIFICATION

1.2.1 HARDWARE SPECIFICATION

MONITOR : LCD MONITOR 15” COLOR


PROCESSOR : INTEL
HARD DISK : 250 GB
MOUSE : OPTICAL MOUSE
KEYBOARD : 1. 4 MULTIMEDIA
RAM : 2 GB

1.2.2 SOFTWARE SPECIFICATION

OPERATING SYSTEM : WINDOWS XP


FRONT-END : VISUAL BASIC 6.0
BACK-END : ORACLE

2
SOFTWARE DESCRIPTION

VISUAL BASIC 6.0

Microsoft Visual Basic is most successful to provide a real high level windows
programming language. Visual basic let's to add menus, textboxes, list boxes, scroll bars
file and directory boxes to blank windows. The grids are used to handle important data.
The visual basic offers more internet features, better support for database development,
more language features to make programming jobs easier with more wizards.

All versions of visual basic are useful, powerful and therefore require a machine
to match. Realistically, even the learning edition of VB requires around 50 MB of free
hard disk space, a fast Pentium class chip and at least 16 MB of RAM. A full installation
of the most powerful version of Visual Basic, the enterprise edition could require more
than 300MB of hard disk space.

FEATURES OF VISUAL BASIC


 Visual Basic is a powerful, windows based professional client/server
application development too, which allows creating quickly and easily
accesses windows application for PC without being an expert in C++ or other
programming language.
 It is more user friendly and easy to learn commands.
 It has excellent facility for the file handling and manipulation.
 Programs and data are largely independent of each other.
 Online and offline help facility available.
 The user can modify the structure of the database without making many
program changes.
 It provides graphics facilities.
 It has easily interfaced with other software system such as word processor,
spreadsheet.
 Support for Active user interactive.

3
 Custom controls are the building blocks of a visual Basic application. Controls
allow your form to do more than just sit empty on a screen. Some controls,
such as labels, list boxes give users’ feedback, which others, command buttons
and textboxes, message responses.
 Other controls sit quickly invisible to the user, and perform some of the
difficult work that makes your application useful.
 The timer control is one example of an invisible control. Controls are easy to
use and when used properly, can add significant functionally to your
programs.
 Visual Basic is user friendly and it is very powerful language with features of
ADO, RDO, and OLE, Visual Basic 6.0 has powerful report generating
features.

BACK-END

ORACLE

Data in a database. A data model describes the logical relationship


between There are three major data models.

1. Hierarchical data model


2. Networking data model
3. Relational model
Hierarchical data model:
In 1968 IBM has developed the information management system (IMS), which is
the first hierarchical database model. It is a simple parent child structure. In this closely
related information in the parent child structure are stored together as logical units. A
parent unit may have child units, but each child is restricted to have only one parent.
Retrieving information from a hierarchical model database requires the knowledge

on the patent child structure. Knowing the structure navigation can be done through

records moving up or down hierarchy or parent child and side ways (that is child record

of a particular parent).

4
Networking model:
Networking model is an improvement model of the hierarchical model. Here the
multiple parent-child relationship is allowed. Rapid and easy access to information is
possible due to multiple access path. The relationship is called sets in the network model.
They are named and used for relating various data records. Retrieving information from a
networking made database requires accessing specific parent moving down to the
first/last child record from these and then navigating sequentially through individual child
records or moving up to the next parent record in the set.
Relational database management system:
A relational database management system is one, which relates the data implicitly.
A RDBMS has eliminated explicit parent-child relationships. In a fully relational database
there is no physical connection between relations (tables) that is, no pointers are
maintained. They contain only logical connections made by duplicate values.
In RDBMS, the interaction is in units of set of records. In this data is organized in
tables consisting of rows and columns. To identify a particular row in a table, a column or
combinations of columns, are used. This is called primary key.

A foreign key is an attribute or a combination of two or more attributes in one


relation that is defined on the same logical range of data values as the primary key in
some other relation (table), they need only logically equivalent data.

NEED FOR RDBMS:

As due to the following features they are employed widely.

 Ability to create multiple relations (tables) and data items.


 An interactive query language
 Ability to logically index and sort the data stored in more than one table.
 Ability to answer queries that require data stored in more than one table.
 A built in report generator.

In addition some package may provide


 An application generator
 A test editor for using writing an application program

5
 An interpreter to run the application program

Oracle is a relational database management system, which is a collection of tools,


utilities and applications that let you to manipulate and oracle database.

DATA ACCESS IN ORACLE


Oracle accesses and manipulates the data stored in a relational database using the
structured query language (SQL). SQL commands are used to access and manipulate
the stored data in the relational database.

The standard set of SQL commands fall in to four categories:


 The data definition language commands for creating and altering the structure of
database.
 The data manipulation commands for adding and modifying data.
 The data control commands for controlling access to database.
 The query commands to extract data from the database. SQL commands are the
base set of commands upon which ORACLE is built.

Security Control
Oracle has several features that ensure the integrity of the database. If an
interruption occurs in processing, a role back can reset the database to the point before
disaster. GRANT and REVOKE commands limits access to information down to the
row and column levels. Views are a valuable feature for limiting access to the primary
levels in the database. Oracle has unique clustering techniques for storing data on the
disk. Oracle store the DBMS in kernel in extended memory, so main memory is
available for other applications.

Data Access and Manipulation Tools

 SQL * PLUS: This allows users, depending on their grants, to create,


manipulate or to drop tables from the database. It permits generation of simple

6
reports, capturing the result from a query and formatting them. It is one of the
easiest languages to us.
 SQL * FORMS: SQL * FORMS provides a convenient and easy method for
non-experts to query a database and update, delete or add information. SQL *
FORMS offers a facility of incorporating PL/SQL statements and block in
triggers.
 SQL * REPORT WRITER: This tool is a menu-driven report formatting tool
uses SQL to create professional looking reports and merged speciality output.
 PL/SQL: While SQL is the natural language of the DBA, it does not have any
procedural capabilities such as looping and branching. For this, oracle
provides the PL/SQL language. PL/SQL bridges the gap between the database
technology and procedural programming languages. It can be thought of as a
development tool that extends the facilities of oracle data manipulation
statement as well as transaction processing and the cursor operations.

7
2. SYSTEM STUDY

2.1 EXISTING SYSTEM

The project entitled “Super Market Management System” is developed to


maintain a consistent transaction which links the fields of both purchase and sales of
products the new system is designed to solve almost all problem faced by existing system.
Reports were produced for the purchase details, sales details and staff details.

The study of the system deals with needed to carry out preliminary investigation.
The study proposal should be produced by the user super market and the study can be
performed only of the existing system. Since it give the structure and functioning of the
system.

The methods used in the system analysis were interviews, observation and
discussion. The existing system is manual one. But user found out some problem in the
existing system. There is no provision for maintain the staffs in the super market.
Moreover there is no provision for giving discount to customer while sales are made.
Similarly there is no provision for giving commission while purchases are made.

DRAWBACKS OF EXISTING SYSTEM

 There is no provision for giving discount while sales and purchases.


 There is chance for loss of record due to mishandling.
 There is possibility for error while updating details.
 There is no staff information.
 The time required to process data and generate the reports is very high.
 Stock products are not updated very well.

8
2.2 PROPOSED SYSTEM

The basic for the proposed system is the recognition of the need for improving the
existing system or procedure. The proposed system aims at overcoming the drawbacks of
the existing system. The proposed system is coded and designed using the visual basic
concept. The concept of visual basic helps in providing the better security and faster
access to data stored in the database of the proposed system.

Thus the proposed system maintains a huge database, which records all the details
pertaining to customers and also keeps track of all the details which are necessary for the
organization. The basis of the system lies in capturing and analyzing the information at
various levels and effective decision making.

FEATURES OF THE PROPOSED SYSTEM

 Completely menu-driven and user friendly.


 Provides faster and efficient information processing.
 Supports efficient data management.
 Highly flexible.
 Valid and secure.
 Provides timely information.
 Add the new facility type of discount for both the purchase and sales amount.
 Also stock updation for every transaction process.

9
3. SYSTEM DESIGN AND DEVELOPMENT
The design of the system is essentially a blue print or plan for solution of the
system to be developed. A part of the system or subsystem of a whole system can itself be
considered a system with its own complements.

FILE DESIGN
The file design is the last phase that indicates the final system and process of the
final system. In the design phase of ‘SUPER MARKET MANAGEMENT SYSTEM’,
the database tables, input screen design and output design etc. are designed.

 The database tables were designed by using all the necessary fields in compact
manner.
 All the input screens in this system are user-friendly and understandable format.
Also the sizes of all the screens are standardized.
 Icons designed in this system are brief, compact and self-explanatory. The icons
are sharp and the user can invoke the system.
 Reports generated here give the minute information, which helps the manager to
take vital decisions.

The importance of software design can be stated with a single word “QUALITY”.
Design is a lace where quality is fostered in software development. Design is the only
way where their requirements are accurately translated into finished software product or
system.

INPUT DESIGN

Input design is the process of converting user-originated inputs to a computer-


based format.

The system takes input from the users, processes it and produces an output. Input
design is link that ties the information system into the world of its users. The system
should be users friendly to gain appropriate information to the user.

10
Forms for input design in this project are:

 Product Details
 Supplier Details
 Staff Details
 Customer Details
 Purchase Details
 Stock Details
 Purchase Return Details
 Sales Details

OUTPUT DESIGN

Output design generally refers to the results and information that are integrated by
the system for many end users. Output is the main reason for developing the system and
the basis on which they evaluate the usefulness of the application. The objective of a
system finds its shape in terms of output; Output of a system can face various forms. The
most command are the reports, screen displays, printed forms, graphical, drawings etc.
The basic requirements of output are that, it should be accurate, timely and of content,
medium and layout for its in tented purpose.

 Staff Report
 Purchase Report
 Sales Report
 Stock Report

DATABASE DESIGN
The Database Management System (DBMS) consists of a collection of
interrelated data and a set of programs to access that data. The collection of data usually
referred to as database. The primary key goal of DBMS is to provide an environment that
is both convenient and efficient to use in retrieving and storing data information.

11
The term database design can be used to describe many different parts of the
design of an overall database system. Principally and most correctly, it can be thought of
as the logical design of the base data structures used to store the data. In the relational
model these are the tables and views. In an object database the entities and relationships
map directly to object classes and named relationships. However, the term database
design could also be used to apply to the overall process of designing, not just the base
data structures, but also the forms and queries used as part of the overall database
application within the database management system (DBMS).

The process of doing database design generally consists of a number of steps


which will be carried out by the database designer.

3.1 SYSTEM DEVELOPMENT

A system development project encompasses all the activities undertaken from the
time at which a potential requirement is identified until the resulting system is fully
implemented and accepted by the end user. The process can involve many stages over a
long period. The following section highlights some fundamental issues to be considered,
outlines the main stages in development and procuring new systems and indicates when
and how the auditor should be involved.

An information system acquired today must not only satisfy present business
needs; it must also be flexible and capable of being enhanced to meet changing
circumstances well into the future. Thus a pre-requisite to the introduction of a new
system is for management to identify and understand their organization’s mission and its
related information needs. Writing this down helps to ensure common understanding and
direction, and provides a yardstick against which achievement can be measured.

The first step in which the analyst must undertake is to understand the current
system by gathering all information about it. The required data are collected by several
methods like:

 Study of the current manuals

 Observation of the functioning

 Sampling and Research

12
3.2 DESCRIPTION OF MODULES
The project classified into the following modules and sub modules namely :

MASTER MODULE
It can be used to maintain the product details, supplier details, staff details and
customer details.

Product Details

This sub module deals with product details. It stores the details regarding the
product name, product code, rate, quantity and amount.

Supplier Details

This sub module deals with supplier details. It stores the details regarding the
supplier name, address, supply item, product price, quantity and amount.

Staff Details
This sub module deals with details regarding the staff. It stores the details like the
name, id number, address, designation, salary and experience of the staff.

Customer Details

This sub module deals with customer details. It stores the details regarding the
customer ID, customer name, address and phone number.

TRANSACTION MODULE
It can be used to maintain the purchase, stock, purchase return and sales details.

Purchase Details

This sub module used to products are purchased from supplier information. To
store the purchase id, date, product id, product name, supplier name, price, quantity, total
amount, discount amount and net amount.

13
Stock Details

This sub module is used to view the current product stock information.

Purchase Return Details


This sub module used to damage products return to suppliers. To store the return
id, date, purchase id, product name, price, quantity, supplier company name, address, total
amount and reason.

Sales Details
This sub module used to products sales to the customer information. To store the
bill number, date, customer name, product id, product name, price, quantity, total amount,
discount amount and net amount details.

REPORT MODULE

Product Report
Using report we can view the details about the products. It gives all the details
about the products data.

Purchase Report
Using report we can view the details about what are the goods are purchased. It
gives all the details about the purchase transaction.

Sales Report
Using report we can view the details about what are the goods are sold. It gives all
the details about the sales transaction.

Stock Report
Using report we can view the details about the product stock. It gives all the
details about the products stocks information.

14
4. SYSTEM TESTING AND IMPLEMENTATION

4.1 SYSTEM TESTING

All the modules of this system were successfully implemented and testing of the
project completed using test data as well as real data collected from the company. All the
reports and the screens are tested for their validity and values in the data tables are
checked for their correctness and consistency. After successful testing of the system, it
was ready for implementation.

Unit Testing

In this testing, we have to test the programs making up the system. The software
units in a system are the modules and routines that are assembled and integrated to
perform a specific function. Unit testing focuses first on the modules, independently of
one another, to locate errors. This enables, to detect errors in coding and logic that are
contained within that module alone.

Integration Testing

The constituents of the entire project are split into individual module and were
linked together, and until the maximum level for each transaction type was reach. This
modules have its individual programs, these program were tested individually. At last all
these programs were combined together.

Validation Testing

At the culmination of integration testing, software is assembled as a package;


interface errors have been uncovered and corrected and a final series tests- validation test
begin. Validation testing can be defined in many ways, but a simple definition is that

15
validation succeeds when the software functions in a manner that can be reasonably
expected by the customer.

Security Testing

During this testing, the tester plays the role of the individual who desires to
penetrate the system. The tester may also over when the system there by denying service
to others.

Whitebox Testing

It is a test case design method that uses the control structure of the procedural
design to derive test cases. Using white box test methods. Guarantee that all independent
paths within a module have been exercised at least one. Exercise all logical decisions on
their true and false sides. Execute all loops at their boundaries and within their
operational bounds.

Blackbox Testing

It is not an alternative to white box techniques. It is attempts to find errors in the


following categories. Incorrect or missing functions. Interface errors. Errors in data as
structures or external database access. Performance errors.

4.2 SYSTEM IMPLEMENTATION


Implementation is the stage of the project when the theoretical design is turned
into a working system. It can be considered to be the most critical stage in achieving a
successful new system and in giving the user confidence that the new system will work
and be effective.

Every developed system must be implementing to fulfill the mode of


development. There, are many software implementation methods. After designing of the
system is over, the user was consulted with a demonstration. This is done to find if any
logical error occur in the system.

16
A crucial phase in the system life cycle is the successful implementation of the
new candidate system design. Implementation simply means converting a new system
design into operational one. This involves creating compatible, training the operating
user, and installing the necessary hardware and terminals before the system is up running.

Therefore implementation is the process of converting a new or revised system


design into an operational one. Thus during this stage the theoretical design is turned into
a working system. If the implementation stage is not carefully planned and controlled, it
can cause chaos. Generally, there are three types of implementation as follows :

 Implementation of a computer system to replace a manual system.

 Implementation of a new computer system to replace an existing one.

 Implementation of a modified application to replace the existing one using the


same existing system.

17
5. CONCLUSION AND SUGGESTIONS

CONCLUSION
The developed system is flexible and changes can be made whenever necessary
speed and changes and accuracy are enhanced computer outputs are obtained more
quickly in desired formats.

The project entitled “Super Market Management System”, describe so far has
designed, tested and documented completely. The package has been developed to
overcome the problems with the existing system. The software produced is so useful that
the system efficiency provides the required information at any time, regarding super
market.

All the transactions of the super market are computerized, which can be upgraded
time to time as per requirements of the changing time.

SUGGESTIONS

Any project which is done is having room for development. It can be enhanced
with various options according to the customer satisfaction in future.

This project is making into online for the future, so that the management can
known the activities of other branches if the company has branches in somewhere.

18
APPENDICES
A) DATA FLOW DIAGRAM

Admin

Staff Customer Product Supplier


details details details details

Employee_details Customer_details Product_details

Supplier_details

Purchase_details

Purchase
details

Purchase
return
details
Stock
details

Stock_details

Sales
details 19 Purchasereturn_details
Customer
Sales_details
B) TABLE STRUCTURE

Table name : Login


Purpose : This table is used to store the user name and password for admin.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Uid Text 15 Primary key User ID
Pword Text 15 Not Null Password

Table name : Supplier_details


Purpose : This table is used to store the supplier details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Supid Number 8 Primary key Supplier id
Supname Text 20 Not Null Supplier name
Pname Text 20 Not Null Product name
Scompname Text 20 Not Null Supplier company name
Addrs Text 30 Not Null Address
Phno Number 12 Not Null Phone number
Emid Text 20 Not Null Email id

Table name : Product_details


Purpose : This table is used to store the product details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

20
Pno Number 10 Primary key Product number
Pname Text 20 Not Null Product name
Comname Text 20 Not Null Company name
Usageto Text 15 Not Null Usage to
Unit Text 10 Not Null Unit
Purprice Number 8 Not Null Purchase Price
Salprice Number 8 Not Null Sales Price
Table name : Staff_details
Purpose : This table is used to store the staff details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Stid Number 8 Primary key Staff id
Stname Text 30 Not Null Staff name
Gen Text 8 Not Null Gender
Dob Date 10 Not null Date of birth
Qulif Text 20 Not Null Qualification
Exp Text 20 Not Null Experience
Desi Text 20 Not Null Designation
Doj Date 10 Not Null Date of joining
Sal Number 8 Not Null Salary
Addrs Text 25 Not Null Address
Phone Number 10 Not Null Phone number
Emid Text 20 Null Email id

Table name : Purchase_details


Purpose : This table is used to store the purchase details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Date Date 10 Not Null Date
Bno Number 8 Primary key Bill number
Supid Number 8 Foreign key Supplier id
Supname Text 20 Not Null Supplier name
Addrs Text 25 Not Null Address
Pno Number 8 Foreign key Product number
Pname Text 20 Not Null Product name

21
Units Text 10 Not Null Units
Price Number 8 Not Null Price
Qty Number 8 Not Null Quantity
Gamt Number 8 Not Null Gross amount
Dstamt Number 8 Not Null Discount amount
Namt Number 8 Not Null Net amount

Table name : Purchasereturn_details


Purpose : This table is used to store the purchase return details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Bdate Date 10 Not Null Bill date
Prbno Number 8 Primary key Purchase return bill
number
Supname Text 20 Foreign key Supplier name

Addrs Text 30 Not Null Address


Rproduct Text 10 Not Null Return of product

Unit Text 10 Not Null Unit


Price Number 8 Not Null Price
Qty Number 8 Not Null Quantity

Gamt Number 8 Not Null Gross amount

Dis Number 8 Not Null Discount

Namt Number 8 Not Null Net amount

Table name : Customer_details


Purpose : This table is used to store the customer details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Date Date 10 Not Null Date
Cid Number 8 Primary key Customer id
Cname Text 20 Not Null Customer name

22
Addrs Text 25 Not Null Address
Phno Number 10 Not Null Phone number
Emid Text 20 Null Email id

Table name : Sales_details


Purpose : This table is used to store the sales details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Bno Number 8 Primary key Bill number
Bdate Date 10 Not Null Bill date
Cid Number 8 Foreign key Customer id
Cname Text 25 Not Null Customer name
Caddrs Text 30 Not Null Customer address
Pno Number 10 Foreign key Product number
Pname Text 20 Not Null Product name
Qty Number 8 Not Null Quantity
Price Number 8 Not Null Price
Tot Number 8 Not Null Total amount
Ded Number 8 Not Null Deduction amount
Namt Number 8 Not Null Net amount

Table name : Stock_details


Purpose : This table is used to store the stock details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION


Pno Number 8 Foreign key Product number
Pname Text 20 Not Null Product name
Price Number 8 Not Null Price
Qty Number 8 Not Null Quantity

23
Gamt Number 8 Not Null Gross amount
Disamt Number 8 Not Null Discount amount
Namt Number 8 Not Null Net amount

C) SAMPLE INPUT

LOGIN FORM

MDI FORM

24
STAFF DETAILS

PRODUT DETAILS

25
SUPPLIER DETAILS

CUSTOMER DETAILS

26
PURCHASE DETAILS

PURCHASE RETURN DETAILS

27
SALES DETAILS

STOCK DETAILS

28
DATEWISE SALES DETAILS

29
D) SAMPLE OUTPUT

PRODUCT REPORT

PURCHASE REPORT

30
SALES REPORT

STOCK REPORT

31
32

You might also like