Super Market Automation

Super Market Automation
1. ABSTRACT OF THE PROJECT
The information revolution is creating sweeping changes in our present working

environment. The computer is transforming an industrial society to an information
society. Computers have become the driving force behind the information explosion.
Computers can store a vast amount of data & retrieve it as and when required. This
relieves the organization from the problem of maintaining & storing records in the
form of paper files that involves wastage of money and time.
The project automation of SUPER MARKET aims at the automation of SHOPPING
COMPLEX (JALANDHAR). This shopping complex is situated in the Gulmarg
Avenue near Rama Mandi chownk, jalandhar city.
PROCESSED AREAS FOR COMPUTERIZATION
The project automation of SUPER MARKET aims at the automation
of SHOPPING COMPLEX (JALANDHAR). This shopping complex is situated in the
Gulmarg Avenue near Rama Mandi chownk, jalandhar city. The project automation of
SUPER MARKET aims at the automation of:
 Sales handling
 Purchase handling
 Stock transfer
 Supplier maintenance
 Generating bills.
All modules will be automated and organization of the super market will
be just a click away.
Details of modules:-
Billing:-billing module produces the net bill of the items purchased by the customer by
also adding the whole taxes etc.
Inventory:-inventory has whole records of the present stock, purchasing items, selling
items etc.
The project helps to add new records, delete existing records, modify
Existing records, and search for some records. The project provides a user friendly
interface that the user gets timely and correct information.
1
2. BRIEF OVERVIEW OF THE ORGANISATION
The “SUPER MARKET “is a big shop which was established in year in 1997. This shop is
situated at Gulmarg Avenue near at PAP chownk, jalandhar city. The name of the owner of
the super market is Mr. Anvil thakur.
This super market sells various kind of product like toys, gifts, basic routine
food items, snacks of various kinds, daily routine products of various kind and many more
. The super market does work according to the fix time schedule. This super market is
associated with function and like selling, purchasing, payroll and inventory. The
minimum turnover of this super market is nearly about 2, 000 annually.
2
3. PROFILE OF PROBLEM ASSIGNED
The existing manual system has various problems. Due to large volume of data a lot of
complicities are involved in the maintaining of up to date data.
PROBLEM OF REDUNDANCY
In the existing system all the data is maintained is diff files and register. This often
leads to considerable tine hostage and some data is duplicated at various places.
PROBLEM OF DATA UPDATIONS
Since data is stored in various register, it is very difficult and time consuming to update
the data.
PROBLEMS IN LOCATING DATA
It is very difficult to locate data at times.
PROBLEM OF STORAGE
As the data is voluminous, more space is required to store it. Everything is stored on
paper so it is primarily to damage with time and also due to accidental factors.
PROBLEM OF INCONSISTENCY
It is very difficult to make same changes at all places. Sometime some entries are
misplaced so it introduces redundancy.
3
4. STUDY OF EXISTING SYSTEM

The existing system is studied in order to know and analyze the various degrees of
problem it has and how it is rectify. All the work relating to sale and purchase is done
manually. Big registers are maintained for this. There is also no such kind of
processing systems which calculate their daily sale and purchase, salary of workers.
Efforts have been made to develop the integrated system covering all the above-
mentioned sub modules.
 It was very difficult to maintain the ledgers, lists, trails and bulky bills
preparation.
 No automated tools like computer are used for the processing.
 It is difficult prompt case positions.
 Difficult to provide online information to the organization like suppliers,
customers and workers.
 More staff was required.
 It added to be voluminous paper work.
 It results in wastage of manpower, which could be better utilized for the
functioning of concerned organization.
 Data is scattered at various place. It is not centralized in nature.
 Bills are generated manually.
LIMITATIONS OF EXISTING SYSTEM:-
 Big register were used to keep daily record.
 It was less secure.
 Data duplicity was there.
 It was slow in process.
 Bills are generated manually
PURPOSED SOLUTION
A user- friendly GUI (graphical user interface) based software has been developed
for the SUPER MARKET keeping in view requirements of owner, employees and
customers. Possible precautions have been taken at each process involved in the
complex task of keeping records and performing calculations. By computerizing, it
implies that computer is entirely doing all the process handling. All the records are
stored in a computer based keeping system using a back end tool.
4
The most important facility is the report generation and printing which provides
user with hard copies of the data also.
By this solution, the existing system came out from the following problems:-
 As the SUPER MARKET became computerized, lot of time of the organization
is saved.
 Easy to maintain the ledgers, balance sheets, bills and bill receipt and
payments.
 Since the overall system is under the control of the data base administrator
(DBA) hence the system is centralized one.
 The level of security is more in case of new system.
 Now bill is generated automatically with help of computer.
 Stock is updated automatically during any sale or purchase of items.
5
5. SYSTEM REQUIREMENTS
5.1) REQUIREMENT ANALYSIS:-

Requirement analysis involves the determination of
what exactly the user want form the system. Often the user may want
“Computerization” but this is not precise enough for anyone to build the system. The
main concern of requirement analysis is on defining the problem is that what the
problem is and what the solution is rather than how the solution is implemented.
5.1.1) PRODUCT DEFINITION

5.1.2)PROBLEM STATEMENT:
One must know what the problem is before it can be solved. The basis for candidate
system is recognition of need which is the first step to develop any kind of system.
Once we know what actually the problem is, only then we can think for the solution.
The following problem is associated with this project is:-
 Financial costs and the funds available for the system work.
 To keep the billing system automated.
 To keep proper utilizations of resources of the organization.
 To maintain the stock in order during any kind of sale and purchase.
 To keep record of customer,vendor and various items or products that are
supplied by supermarket.
5.1.3)FUNCTION TO BE PROVIDED
The main objectives for developing the fully automated system for a filling station
are as follows:
 To make Super Market totally computerized.
 To have better interaction with the customers.
 To avoid wastage of time.
 To make the effective use of present technology and implement it.
 To provide security.
 To make the Super Market work faster and easier to provide security.
 To make the billing system automated.
 To maintain the stock automatically with the help of computer.
6
5.1.4)PROCESSING ENVIRONMENT
HARDWARE AND SOFTWARE PROFILE:-
SOFTWARE REQUIRED:-
Visual basic 6.0(V.B 6.0)
Oracle 8i
HARDWARE REQUIRED:-
A Pentium 3 or Pentium 4 processor
At least 128 MB RAM
At least 1028kb cache memory
Zip drive (for the data backup and recovery)
7
5.1.5) SOLUTION STRATEGY
The problem of security of data in case of manual system can be solved in the
Computerized system by providing and requiring hierarchies of passwords and Lock
words that allow access to the stored information only to authorized users Or person that
have knowledge of the passwords. This prevents the unauthorized Users from accessing
important information of the organization.
The maintenance of records of large number of transaction regarding sale and purchase
becomes a less tedious task in the computerized work system. The retrieval and uploading
of stored information is relatively easy in the computerized system. As less labor and time
is involved in the maintaining the records, it leads to reduction in the cost involved.
In the computerized Requiring system the use of passwords that can prevent unauthorized
users from accessing important information can also provide adequate security. The
billing system is automated which provide good interaction to the customer and time
management is done in efficient way.
8
5.1.6)ACCEPTANCE CRETERIA
Acceptance criteria for this project is based on these main things:-

 If the bill is generated automatically with the help of computer.
 If the stock is maintained in efficient way.
 If the customer and manager of supermarket satisfy with the services of
supermarket.
Moreover, Acceptance criteria of this project is based on this following
advantages.
1. FAST AND EFFICIENT: - As compared to existing manual system, in proposed

system the user can get the information fast, easily and efficiently from the
computer since information is a single click away from the user.
2. RELIABLE AND ACCURATE:- As in proposed system the information is stored
and processed in computers so that data will be more reliable and accurate.
3. CENTRALIZED DATA: - In the existing system most of data records are kept in
registers and some data is maintained in Microsoft Excel due to this system the
placement of the data is not at one particular place. But in proposed system each
and every record is maintained on computer, which leads to the centralization of
data and every user who has the access to system can retrieve the data at ease.
4. LOW OPERATION AND MAINTENANCE COST: - The proposed system is
not very costly as it doesn’t includes many costs and overhead expenses like file
management, stationary charges etc.
5. NON-REDUNDANT INFORMATION: - As in proposed system data is
maintained on the computers so inconsistency doesn’t occurs. As in our system
most of the inventory codes are Auto Generated hence there is no chance of
duplication of the master records.
6. USER FRIENDLY: - Proposed system is very user friendly. We have applied
many check and balances (i.e. validation rules) in the proposed system so that a
less knowledgeable person can also enter the data error free and at a ease.
7. EASY TO ACCESS: - As compared to existing system, in proposed system the
user can easily and efficiently access the information from the computer only if the
user is given the right of the same. In the proposed system we have used the
concept of level of access. We have created the different kind of users i.e. Super
9
User, Normal User & operator. So depending upon the type of hierarchy we can
assign different rights for the user.
8. NO DOCUMENTATION: - As everything is stored on the computer so there is
no need of documentation or maintaining the files or registers.
10
5.2)FEASIBILITY ANALAYSIS
Feasibility study is a test of the system proposal according to its

workability impact on the organization, ability to meet user needs, to make effective use of
resources. depending on the initial investigation of the Super market the survey is
expended more to a feasibility study .various kind of questions which are considered in
this phase while developing the project on Super market are given below:-
 What are the needs of the Super market and how does the candidate system meets
them?
 What are the various available resources for the automation of the Super market
system?
 What is the impact of the given candidate system on the Super market?
Feasibility study is focus on these three factors:-

During feasibility study the economical, technical,
behavioral viability of the product is examined.
 ECONOMICAL FEASIBILITY:-
The cost of acquiring the proposed system is not to high. The super
market already has the suitable hardware with them. Even the software is already available
with them. So that creates no extra burden of cost on the super market. System is
developed in Visual Basic and in oracle which is both advances in feature.
 TECHNICAL FASIBILITY-:
The necessary technologies that are required to implement the proposed system are
available easily in the software market. The main hardware equipments such as computers,
printers, etc. are readily available. As system is developed in VB. Visual Basic is a tool
that allows you to develop Windows (Graphical User Interface –GUI) applications. It
provide similar environment as other Graphical User Interface. So user feels very comfort.
The applications have a familiar appearance to the user. Oracle is a powerful program to
create and manage your databases. It has many built in features to assist you in
constructing and viewing your information. Oracle is much more involved and is a more
genuine database application than other programs such as Microsoft Works.
11
 BEHAVIORAL FEASIBILITY:-
The main objective here is to determine whether the system will work after it is
developed and installed. A proper investigation was done in this regard and as a result, the
following conclusions were derived:
There was sufficient support from the owner of supermarket and the personnel involved.
The current manual system is too cumbersome and takes lot of time and includes repetitive
works. The important data regarding books was not available as and when desired.
It takes a lot of time to gather the important information required related to sale and
purchase, workers etc. The persons involved in the current working of the system were
met and discussions were held with them to evolve a system with which they had good
support and participation.
12
5.3) PROGRAMING LANGUAGE & DEVELOPMENT TOOLS
The project was developed on a Windows NT platform. Microsoft Visual 6.0

is used as the front-end language and Oracle is used as back-end :case. ♦ VIS U A L
BASIC
What is Visual Basic?

 Visual Basic is a tool that allows you to develop Windows (Graphical User
Interface -GUI) applications. The applications have a familiar appearance to the
user. A s you develop as a Visual Basic programmer, you will begin to look at
Windows applications in a different light. You will recognize and understand how
various elements of MS- Word, Excel, Access and other applications work. You
will develop a new vocabulary to describe the elements of Windows applications.
 Visual Basic is event-driven; meaning code remains idle until called upon to
respond to some event (button pressing, menu selection...). An event processor
governs Visual Basic. Nothing happens until an event is detected. Once an event is
detected, the code corresponding to that event (event procedure) is executed.
Program control is then returned to the event processor.
EVENT ? Event processor
Basic Basic Basic

code code Code Event
13
Visual Basic is not just a language. I t ' s an Integrated moment Environment (IDE) in
which one can develop, run, test and debug nations. With Visual Basic, cone can create the
following types of rations:
Standard EXE Visual Basic is not just a language. I t ' s an Integrated moment
Environment (IDE) in which one can develop, run, test and debug nations.
FOLLOWING ARE THE TOOLS OF VISUAL BASICS WHICH WE ARE USED

IN THIS PROJECT:-
• MSHFLEXGRID:- We use this tool in bill form to display the bill format in a grid
form.also this tool is used in to view bill details.
• LIST BOX:-We use this component to show the various details or record of the
particular field which is associated with that list box.with the help of list box we show the
list of items available in the supermarket in product detail form.
• OPTIONS BUTTON:-This option button specify either true or false value.this button
is used in the where either discount is allowed or not.
• COMBO BOX:-When more than one option specified for any field there we used
combo box.in this project we used this tool in different places.
• TIMER:-The timer is used with splash form whose value is set or predefined fixed by
the developer.
• TEXT BOXES:-text boxes is used to display the records.
• LABELS :- It represent what type of data is ?
• DTPICKER:-It shows the current date of the system.this tool is used while
generating bills.
• PROGRESS BAR:-This tool is used in splash form which describe the status of
opening of the MDI form.
14
15
AUTOMATION OF PETROL PUMP
16
ORACLE8i
Oracle is the most widely used database in the world, it runs on virtually every kind of
computer. It functions virtually every identically on all these machines, so when you learn it
on one, you can use it on other.
Oracle was simply a data server, delivering state of the art

solution to corporate business communities version 3 is the 1 st many of us saw in the mid
1980,s. It ran in the ram the 1st 640 kb of memory attached to the personal computers strew
all over many companies offices. Versions 3 alongside some early tool offering by oracle
Systems Corporation had some heavy competitions with like of Ashton Tate, dbase2 to
mention one of many.
Oracle is the most widely used database in the world. It runs on virtually
every kind of computer. It functions virtually every identical on all these machines, so when
you learn it on one, you can use it on any other.
Oracle was simply a data server, delivering state of the art solutions to corporate business
communities version 3 in the 1 st many of the raw in the mid 1980,s .it ran in the ram the 1 st
640 kb of memory attached to personal computers strewn all the over many companies
offices. Version 3 alongside some early tool offerings by oracle System Corporation had some
heavy competitions with likes of Aston tats dbase2 to mention one of many.
In this project we used oracle for creating tables .following are the tables which are
developed in the oracle are:-
 Sale table
 Customer table
 Purchase table
 Vendor table
 Item detail table
17
6. SYSTEM REQUIREMENT SPECIFICATION
6.1)DEVOLPING OPERATIONAL/MAINTENNACE ENVIRNOMENT
This is concluded that, this project of Inventory Management System

for supermarkets House for helpful to them as they are going go save tremendous of time as
well as energy for day to day activity related to maintaining the Inventory levels, making
bills, procuring materials etc.
1) Using this software, super market can maintain the stock, daily sale, and invoicing
records.
2) Manager will need not to search large books or ledgers to see the stock of the finished
reels of particular date, he will just have to enter the product id and whole information
regarding stock will be displayed.
So this project will definitely help them to do their work more efficiently and fast.
6.2)EXTERNAL INTERFACE AND DATAFILES
18
Grid Chart:-
Process Stock Sale Purchase Billing

Files availibilty process process process
Stock detail U,T m,T m,T m
Sale detail U,D M,D
Purchase U,m M,u

detail
Supplier detail u
U- Used
m-Master file
T-Transaction file
D-Daily Created
DESCRIPTION:-
The grid chart specify the various files that are used in the process that are involved in the
Automation of supermarket.
6.2.1) USER DISPLAY AND REPORT FORMAT
19
Following are the various forms or user displays which is associated with the automation of
supermarket system
These are the forms:-
Login form
Change password form
Product detail form
Bill generation form
Purchased item form
View old bill form
MDI form(multiple document interface form)
Follwing are the reports which are associated with project:-
Static reports:-
Dealer report
Product detail report
Sale report
Purchased item report
Dynamic reports:-
Sale report of a particular bill_no.
Purchased report of a particular order_no
Product detail report of a particular product_code
20
6.2.2) HIGH LEVEL DFD AND DATA DICTIONARY
DATA FLOW DIAGRAM

Data flow diagrams (also known as data flow graphs) are
commonly used during problem analysis it is a way of expressing system requirement in a
graphical form. This leads to a modular design.
HIGH LEVEL DFD
DESCRIPTION:-
This is the level-0 DFD or context level Diagram.it specifies the various
entity that are associated with the Super Market Automation Process. Here the entites are
shown in the rectangle box. As customer place the orders and according to it supply of item is
take place by giving bill to the customer.Orders for the product is given to the
Suppliers/Vendors .
21
LEVEL-1
DESCRIPTION:-
This is the level 1 DFD which specify the various process like sale
process,purchase process,inventory management process.for thesale process various files are
viewed like sal file,product files ,for purchase process vendors and product details files are
linked.
22
6.2.2)DATA DICTIONARY
LOGIN DETAILS:
=[username]+[password]
PRODUCT DETAILS:
=[P_CODE]+p_name+mrp+quantity_in_stock+min_quantity
SALE DETAILS:
=[bill_no+pro_code]+p_name+mrp+cust_name+cust_address+sale_qty+total
PURCHASE DETAILS:
[order_no+pro_code]+date+pur_price+pur_qty++supp_no+total
SUPPLIER DETAILS:-
[s_no]+name+(description)+phone no.+email id+ address
23
7. DESIGN
7.1)DETAILED DFD AND STRUCTURE DAIGRAM
LEVEL-2
DESCRIPTION:-
The level-2 DFD describes the sale process in detail with the bill
generation and stock updation.as for every sale of product the stock is updated automatically
by decreasing the sale quantity of the product from stock quantity of the product.
24
LEVEL-3
DESCRIPTION:-
The level-3 DFD describes the purchase process in detail with the
creation of order and stock updation according to it .As for every purchase of product the
stock is updated automatically by increasing the quantity of the product purchased in the
stock quantity of the product.
25
LEVEL-4
DESCRIPTION:-
The level 4 DFD illustrates the Stock Process. For every sale and purchase of
products stock is updated automatically.
26
7.2)DATA STRUCTURE
TABLE: LOGIN
SR NO. FIELD DATA TYPE SIZE OF DESCRIPTION CONSTRAINT

NAME DATA
TYPE
1 username Varchar2 22 It contained the Not null
username
password Varchar2 22 It contained the Not null
password
DESCRIPTION:-
This is a login table which has two fields username and password. Here primary key consist
of both username and password fields as for every user there is unique password to access the
system.
27
TABLE:-ITEM
SR NO. FIELD NAME DATA TYPE DESCRIPTION CONSTRAINT

1 P_code Varchar2(20) For product no. Primary key
2 P_name Varchar2(30) Product name
3 Item_cat Varchar2(20) Category of item
4 Weight Number(5) Product weight
5 Mrp_pri Number(5) Marked price
6 Quantity _in_stock Number(5) Quantity of the
product
7 Reorder_qty Number(6) Reorder level of
product
DESCRIPTION:-
This is the item detail table which stores information corresponding to the items
that are available in the supermarket.
28
TABLE:-CUSTOMER
SR.NO Fieldname Data type description constraints

1 cust_id Number(5) Customer no. Primary key
2 cust_name Varchar2(30) Cust omer name
3 Address Varchar2(30) Customer address
4 cust_no Number(10) Customer Phone no.
DESCRIPTION:-
This is the customer detail table which stores information corresponding to the various
customers that purchases some items that are available in the supermarket.
29
TABLE:- SALE

1 Bill_no Number(2) Bill number Primary key
2 date date Bill Date
3 P_code Varchar2(5) Product code Reference key
5 Sale_pri Number(20) Selling price
6 Cust_no. Varchar2(5) Customer name Reference key
7 Pro_qty Number(20) Quantity of product
sold
8 discount Number(2) Discount on product
9 total Number(20,2) Total value of sale
DESCRIPTION:-
This is the sale detail table which stores information corresponding to the sale of various
items to the customers .
30
TABLE:-PURCHASE

1 order_no Number Id number
(20,2)
2 date date Order date
3 Pro_code Varchar2(20) Description of Reference key
purchased product
4 Pro_qty Number Quantity of product
(20,2) puchased
5 Pur_price Number Product purchase
(20,3) price
6 discount Number (2) Discount on
purchased product
7 Vendor_id number(20) Vendor no. Reference key
8 vat Number(20) Vat tax
9 total Number2(40) Total purchase value
DESCRIPTION:-
This is the purchase detail table which stores information corresponding to the purchase of
various item with their vendor id and product code .
31
TABLE:-VENDOR
Fieldname Data type description constraints

ven_id Number(5) Vendor no. Primary key
ven_name Varchar2(30) Vendor name
Address Varchar2(30) Vendor address
Phone_no Number(10) Vendor Phone no.
Em_id Varchar2(30) Vendor Email_id
DESCRIPTION:-
This is the vendor detail form which stores the information related to the
vendors that are supplying products to the supermarket.
32
7.3) FORM DESIGNING
LOG IN SCREEN: This screen prompt the user to enter user name to enter password after
entering information enter and it will authenticate the user to work .
33
DESCRIPTION:-
This is a splash form which specifies the platform version ,front end &
back end that are used. It also specify the developer name and the software which is
developed.
34
DESCRIPTION:-
This is look of bills form. When you choose the receive payments from
the invoices menu yow will see this form. You can create the invoice.
35
DESCRIPTION:-
This form is used to place, save the orders according to the choice you
select the product id of the product which you want to be purchased.
36
DESCRIPTION:-
This form is active when you select products edit option from products menu.
In this form we can add, edit and delete the information about any product. We can also
browse the products to know details of a particular product.
37
DESCRIPTION:-
This is change password form if we user want to change password then
he/she can press on change password button.
38
DESCRIPTION:-
This is a veiw sold stock form.if the user want to know what is the quantity
that is sold of an product and what is the quantity in hand and according to it balance stock is
show by simply deducting quantity in hand from quantity sold out.
39
DESCRIPTION:-
This form is active when we choose check stock option from products menu.
This form will display the products which are less than the minimum stock value.
40
DESCRIPTION:-
This is the form which is used to view old bill details . just the user select
the bill no. from the form and according to it all the details of that bill no. is shown.
41
DESCRIPTION:-
This form is active when we choose Products information option from
the products menu. We can check detail of any product from this form.
42
DESCRIPTION:-
This form is used to add, edit , delete browse the information about the
purchase parties as options selected from the purchase parties menu.
43
DESCRIPTION:-
This form is used to open dynamic reports corresponding to bill no. wise,
ordered no. wise and product code wise.
44
DATA REPORTS
DESCRIPTION:-
This is item detail report which shows information regarding the item that is
available
In the supermarket with the item name, quatity, weight, price etc.
45
DESCRIPTION:-
This is sale information report of the product . it describe what type of product is sold and
what is the quantity sold product,discount,customer_name,total etc.
46
DESCRIPTION:-
This is the purchased detail report which describes the various product that are purchases
from the dealer.
47
DESCRIPTION:-
This the vendor detail report which shows the information regarding the various vendors
which sold different types of product to the supermarket.
48
DESCRIPTION:-
This is the dynamic report which show the information regarding the particular item that is
available in the super market.
49
DESCRIPTION:-
This is the dynamic report which show the information regarding the sale of item that is
available in the super market.
50
DESCRIPTION:-
This is the dynamic report which show the information regarding the particular ordered no. of
item that is purchase from the vendor.
51
8. TESTING
Testing is vital to the success of the system. System testing makes a logical assumption that if
all parts of the system are correct, the goal will be successfully achieved. A small error can
conceivably explode into a much larger problem. Effective testing early in the process
translates directly into long-term cost savings from a reduced number of errors. The best
program is worthless if it does not meet the user needs. Often the software developer and the
users have communication barriers due to different backgrounds, interests, priorities and
perhaps languages.
NATURE OF TEST DATA

The proper choice of data is as important as the test itself. If test data as input is not valid or
representative of the data to be provided by the user, then the reliability of the output is
suspect. Test date may be artificial or live. Unlike live data, which are biased towards typical
values, artificial data provide extreme values for testing the limits of the candidate system.
THE TEST PALN

The first step in system testing is to prepare a plan that will test all aspects of the system in a
way that promotes its credibility among users. Its features are: -
1) Programmers document and report on the method and extent of their testing.
2) Users are involved, which means communication is improved between users and the
designer.
3) Programmers are involved when they become aware of user problems and expectations.
The user also becomes aware of the complexity of programming and testing.
WHY DO WE TEST?
The first test of a system is to see whether it produces the correct outputs. Following this step,
a variety of other tests are conducted as: -
52
FUNCTIONAL TESTING
In functional testing the structure of the program is not considered. Test cases are decided
solely on the basis of requirements or specifications of the program or module and the
internals of the module or the program are not considered for selection of test cases. It is
often called Black Box testing. Test cases are generated based on the actual code of the
program or module to be tested. For the entire system test cases are designed from the
requirements specification document for the system. For modules create during design, test
case for functional testing are decided from the module specifications produced during
testing.
STRUCTURAL TESTING
Structural testing is concerned with testing the implementation of the program. The intent of
structural testing is not to exercise all the different input or output conditions but to exercise
the different programming structures and data structures used in the program. Structural
testing aims to achieve test cases that will force the desired coverage of different structures.
The criteria for structural testing are generally quite precise as they are based on the program
structures, which are formal and precise.
UNIT TESTING
Unit testing is a dynamic method for testing and verification, where the program is actually
compiled and executed. It is one of the most widely used methods and the coding phase is
sometimes called the ‘coding and unit testing phase’. Unit testing involves executing the code
with some test cases and then evaluating the results. Its goal is to test modules or ‘units’, not
the entire software system. The programmer often does it. After finishing the coding of a
module, it is tested with some test data. Then this module is delivered for system integration
and further testing.
53
INTEGRATED TESTING
The next level of testing is called ‘Integration Testing’. In this many unit-tested modules are
combined into subsystems, which are then tested. The goal here is to see if the modules can
be integrated properly. Hence, emphasis is on testing interfaces between modules. This
testing activity can be considered testing the design.
We have adopted very good technique for implementing and giving training to the End Users.
Initially we have separated the peoples of Super Market into three groups and we have
stated the theoretically classes to them i.e. we taught them that how they were working in
their previous system and how they are going to get benefits from this new system.
After giving them training to them for the proposed system we have also taken the test
from them with the dummy data. And at last they are quite satisfied with the performance of
the system.
METHODOLOGY USED IN TESTING
Testing is done in three ways :
1.First a dummy data is input in the data base.
2.Then username and password of the project is given access is given only to those who are
authenticated to it.
3.User documentation is very important , because the procedure written in it helps user to
solve certain problem.
4. At last when vehicles are sold after inserting in new stock , the invoice comes as the
output , which finally marks the end of testing.
5. At last when spare parts are sold after inserting in new stock , the voucher comes as
the output , which finally marks the end of testing.
6.Software also provides the facility to check the details of the employees.
7.At last reports are generated to check the functioning of the software.
54
Unit Testing of Information Modules
1) Sub Module: Supplier, Customer

Test cases Condition being Input Data Expected Result
tested
1 Name 123 Not Allowed
#$%”>< Not Allowed
Length>100characters Not Allowed
Left Blank Not Allowed
2 City 123 Not Allowed
3 State 123 Not Allowed
4 Mobile Abc Not Allowed
55
1) Sub Module: Product

tested
1 Name 123 Not Allowed
2 Product code Left Blank Not Allowed
3 Product color 123 Not Allowed

4 Capacity Abc Not Allowed

56
1) Sub Module: Purchase

tested
1 Product id #$%”>< Not Allowed
2 Supplier code Left Blank Not Allowed
3 Quantity Abc Not Allowed

4 Amount Abc Not Allowed

57
1) Sub Module: Sale Bill

tested
1 Product id #$%”>< Not Allowed
2 Customer code Left Blank Not Allowed
3 Quantity Abc Not Allowed

4 Amount Abc Not Allowed

5 Bill Abc Not Allowed

58
9. IMPLEMENTATION
Implementation means converting new system design into operational one. Certain
tasks are involved:-
 Certain of computer compatible files
 Training and operating of staff
 Installation of hardware
 Installation of communication network etc.
9.1 System Implementation

In system implementation user training is crucial for minimizing resistance to change.
 Certain of user friendly manuals
 Data dictionary
 Job performance aids
 Communication information about the system and help screens etc.
Types of Implementations
Implementation of computer system to replace the manual system. Problems encountered in
this implementation are as follows.
 Conversion of files
 Certain of accurate files
 Training of users
 Verifying printouts for integrity
 Implementation of new computer system to replace exsting one .
 The project and the system are same. We are not changing the whole system only
certain modules are changed.
59
9.2 Conversion
Conversion means change of one system to another .the objective of
conversion is to pue tested system into operational while holding three things:-
Cost
Risk(if corruption of file is there, no change should be made)
Personnel irritation(if people working in organization, do not want changes, then conversion
should not be done.)
Conversion involves following tasks:-

Creation of computer compatible files.
Successful installation of hardware
Successful training of the operating staff.(which involve cost, risk & personal irritation at
minimum)
60
Procedure for implementation
Project Plan
System Test implimentation
Implementation Plan
Conversion plan of the implementation

plan finalized
Perform file Conversion
Perform Parallel Processing
Log Result Of Conversion
Any Diagnose and correct

discrepencies discrepencies
?
Implementation Discontinue Parrallel

results Processing
Implementation Complete conversion

documents
Prepare plan for post

implementation
61
POST_IMPLEMENTATION AND MAINTENANCE
After the installation phase is completed and the user staff is adjusted to the changes created
by the candidate system , evaluation and maintenance begin. Like any system , there is an
aging process that requires periodic maintenance of hardware and software. If the new
information is inconsistent with the design specifications, then changes have to be made.
Hardware also requires periodic maintenance to keep in tune with design specifications. The
importance of maintenance is to continue to bring the new system to standards.
User priorities, changes in organizational Requirements, or environmental factors also call for
system enhancements.. The change requires evaluation, program modifications and further
testing.
62
10. PROJECT LEGACY

10.1 Current Status
The proposed system is concerned with following areas:-
• Contain information about supplier, customer, and products.
• Automatically maintain the inventory
• Generate reports according to user requirements.
10.2 Remaining Area of concern

Many more areas can be included in the proposed system such that it can handle multiple
areas. This will make the system multi purpose and more general.
Areas which can be included in the system are:-

• Accounting System
• Payroll system
10.3 Technical Lessons Learnt

As the proposed system uses vb6.0 as front end language, so I have learned a new language
i.e. VB6.0.
10.4 Managerial Lessons Learnt

As this project taught me may managerial skills are:-
Time management
Coordination
63
10.5) Future Enhancement
“SAINI’ S SUPERMARKET” is a project on the automation of the “SUPER MARKET”. While

developing the software various aspects have been taken into consideration like maintaining
stocks for products, product records, accessory details, material issued details, bill deposit,
maintaining record structure for various product use, keeping records of various dealers,
entering customer’s, purchaser’s, calculating the final output reports of the product and
generating various types other related product report used.
But, apart from this much work there are a few modules, which still remain to be developed.
These include, Accounts, and Attendance salary record etc.
While developing the project, due care has been taken to incorporate maximum functionality
in each and every module so that it is not only easy for a layman to use this software but also,
but also he should have necessary information at his disposal the time. There is a scope for
further improvement in the software. It can be done I the following manners: -
1.WEB ENABLED
The software can be made web enabled. That is, the user can access the information while
working on a remote computer. purchasing of the products,selling of the goods, billing to the
customer etc. all this information can be made available online.
2.IVR ENABLED
IVR stands for ‘Interactive Voice response’. This facility can be introduced in the software so
that it is possible for the consumer’s and for the dealer to obtain the information about the
product what they want to know can be through telephonic conversation.
64
BIBLIOGRAPHY
BOOKS REFER AUTHOR NAME

VISUAL BASIC BLACK BOOK BY STVEN HOLZER
SOFTWARE ENGINEERING BY PANKAJ JALOTE
SIMPLIFIED APPROACH TO ORACLE BY RANJIT SINGH
SIMPLIFIED APPROACH TO DBMS BY RANJIT SINGH
WEBSITE VISITED:-
www.google.com
www.hotbot.com
65

Super Market Automation

Uploaded by

Document Information

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Super Market Automation

Uploaded by

Copyright:

Super Market Automation

1. ABSTRACT OF THE PROJECT

The information revolution is creating sweeping changes in our present working

2. BRIEF OVERVIEW OF THE ORGANISATION

3. PROFILE OF PROBLEM ASSIGNED

4. STUDY OF EXISTING SYSTEM

5.1) REQUIREMENT ANALYSIS:-

5.1.1) PRODUCT DEFINITION

HARDWARE AND SOFTWARE PROFILE:-

5.1.5) SOLUTION STRATEGY

Acceptance criteria for this project is based on these main things:-

1. FAST AND EFFICIENT: - As compared to existing manual system, in proposed

Feasibility study is a test of the system proposal according to its

Feasibility study is focus on these three factors:-

5.3) PROGRAMING LANGUAGE & DEVELOPMENT TOOLS

The project was developed on a Windows NT platform. Microsoft Visual 6.0

What is Visual Basic?

EVENT ? Event processor

Basic Basic Basic

FOLLOWING ARE THE TOOLS OF VISUAL BASICS WHICH WE ARE USED

Oracle was simply a data server, delivering state of the art

6. SYSTEM REQUIREMENT SPECIFICATION

6.1)DEVOLPING OPERATIONAL/MAINTENNACE ENVIRNOMENT

This is concluded that, this project of Inventory Management System

6.2)EXTERNAL INTERFACE AND DATAFILES

Process Stock Sale Purchase Billing

Stock detail U,T m,T m,T m

Sale detail U,D M,D

Purchase U,m M,u

6.2.1) USER DISPLAY AND REPORT FORMAT

These are the forms:-

Change password form

Product detail form

Bill generation form

Purchased item form

View old bill form

MDI form(multiple document interface form)

Follwing are the reports which are associated with project:-

6.2.2) HIGH LEVEL DFD AND DATA DICTIONARY

DATA FLOW DIAGRAM

HIGH LEVEL DFD

[s_no]+name+(description)+phone no.+email id+ address

7.1)DETAILED DFD AND STRUCTURE DAIGRAM

SR NO. FIELD DATA TYPE SIZE OF DESCRIPTION CONSTRAINT

SR NO. FIELD NAME DATA TYPE DESCRIPTION CONSTRAINT

SR.NO Fieldname Data type description constraints

SR NO. FIELD NAME DATA TYPE DESCRIPTION CONSTRAINT

SR NO. FIELD NAME DATA TYPE DESCRIPTION CONSTRAINT

Fieldname Data type description constraints

7.3) FORM DESIGNING

NATURE OF TEST DATA

THE TEST PALN

1.First a dummy data is input in the data base.

Unit Testing of Information Modules

1) Sub Module: Supplier, Customer

1) Sub Module: Product

Test cases Condition being Input Data Expected Result

3 Product color 123 Not Allowed

4 Capacity Abc Not Allowed

1) Sub Module: Purchase

Test cases Condition being Input Data Expected Result

2 Supplier code Left Blank Not Allowed

3 Quantity Abc Not Allowed

4 Amount Abc Not Allowed

1) Sub Module: Sale Bill

Test cases Condition being Input Data Expected Result

2 Customer code Left Blank Not Allowed