Sample Billing Market
Sample Billing Market
Sample Billing Market
Bachelor of Engineering
In
Computer Science and Engineering
Submitted by,
POOJA S G 22CSE112
POORNA CHANDRA TEJASWI L 22CSE113
External Viva
1.
1.
2. 2.
ACKNOWLEDGEMENT
We sincerely convey our regards and thanks to Dr. B N Shobha, Principal, BGSIT,
BG Nagar, Mandya, for giving us a chance to carry out and present our mini project
work.
Finally, we would also extend our heartfelt thanks to our family members,
classmates, friends and well-wishers for their support and encouragement
throughout this effort.
i
ABSTRACT
The CAPTCHA Generator project aims to develop a web-based application using HTML, CSS,
and JavaScript to generate and implement CAPTCHA (Completely Automated Public Turing
test to tell Computers and Humans Apart) challenges. CAPTCHA is widely used on websites to
prevent automated bots from accessing or interacting with certain features, such as submitting
forms or creating accounts. This project focuses on creating a customizable and user- friendly
CAPTCHA generation system to enhance web security.The HTML component of the project
provides the structure for the web interface. It includes elements such as input fields, buttons,
and placeholders for the generated CAPTCHA images. The structure is designed to be intuitive
and accessible to users, allowing them to interact seamlessly with the CAPTCHA generation
process.CSS is employed to enhance the visual appeal of the application and ensure a responsive
and aesthetically pleasing design. Styling elements such as colors, fonts, and layout contribute
to a user-friendly experience, making the CAPTCHA generation interface more engaging and
accessible.JavaScript is the core programming language for the CAPTCHA generation logic.
The project leverages JavaScript's capabilities to create random and dynamic CAPTCHA
challenges.
ii
lOMoARcPSD|42436405
TABLE OF CONTENT
SL NO TOPICS PAGE NO
1 INTRODUCTION 5
2 LITERATURE SURVEY 6
3 SYSTEM ANALYSIS
3.1 EXISTING SYSTEM 8
3.1.1 BOTTLENECK OF EXISTING SYSTEM 8
3.2 PROPOSED SYSTEM 9
3.3 OBJECTIVE OF THE PROJECT 10
3.4 SCOPE OF STUDY 10
4 SYSTEM REQUIRED SPECIFICATION
4.1 SOFTWARE REQUIREMENT 11
4.2 HARDWARE REQUIREMENT 12
4.3 SYSTEM ARCHITECTURE 13
4.4 FEASIBILITY STUDY 14
5 SYSTEM DESIGN
5.1 USE CASE DIAGRAM 16
5.2 DATA FLOW DIAGRAM 17
5.2.1 LOW LVEL DATA FLOW DIAGRAM 17
5.2.2 HIGH LEVEL DATA FLOW DIAGRAM 18
6 SYSTEM IMPLEMENTATION
6.1 SAMPLE CODE 19
6.2 MODULE DESCRIPTION 21
7 DATABASE DESIGN 23
8 SYSTEM TESTING AND IMPLEMENTATION
8.1 TESTING OBJECTIVE 24
8.2 TEST PLAN 25
8.2.1 TESTING AND RESULT 25
LIST OF FIGURES
10.1 MENU 28
PRODUCT
ABSTRACT
In present days people are facing problem in shopping, this Supermarket Billing
System project in JAVA is a simple console application built without use of graphics. This
project will help us to understand basically two things- use of stream class and file handling
in JAVA language. This project is simple to understand, and the source code has been
presented in an understandable manner. To make software fast in processing with the good
user interface so that user can manage and change it, this should be used for long time
without error and maintenance.
This project is a traditional supermarket billing system with some added functionality.
This system is built for fast data processing and bill generation for supermarket customers.
The billing system consists of JAVA and file handling concepts. The billing database is a
vast collection of product name, price and other product specific data. A product when billed
is searched from the database and its price is added to the bill based upon the product
quantity. The system also contains discounted price while billing. The supermarket billing
system is built to help supermarkets calculate and display bills and serve the customer in a
faster and efficient manner.
CHAPTER 1
INTRODUCTION
Supermarket is the place where customers come to purchase their daily using products
and pay for that. So, there is a need to calculate how many products are sold and to generate
the bill for the customer. “Supermarket Billing System” aims at developing into software
that can be used at places like Shopping malls, Supermarkets to easily operates the daily tasks
of taking the order, calculating the bill etc.
The main advantage of this project is that it converts all the manual work is time
consuming and error prone to fully automated system which helps in eliminating all the paper
work, saves time, improves customer services. It also speeds up various processes such as
addition of new items to the menu, deletion of items from the menu, modification of details
of items and calculation of bills thus providing convenience to the workers as well as
customers. In the development of the project, selection of an appropriate programming
language and a platform is of primary importance.
This project is developed to manage the bill submission process in big organization.
Using this system user can submit their bill online and check the status of their bill. In this
system, we have two users. First one is the customer who can purchase the items available or
can make the bill for the customers. Second one is the administrator who will decide the
discounts on the products and can see the report of any report. In this project JAVA language
is used to maintain all the data. It provides many features like file handling data can be easily
maintained and many features that are required while doing a project. The system will
display all the items with prices and discount. Finally, a separate bill will be generated for
each customer. This will be saves in the database. Any periodic records can be viewed at any
time. Eventually, users will consume less time in the calculation and the sales activity will be
completed within a fraction of seconds whereas a manual system will make the user write it
down which is a long procedure and so paperwork will be reduced and the user can spend
more time on the monitoring the supermarket.
CHAPTER 2
LITERATURE SURVEY
A Supermarket is a large form of the traditional grocery store, it is a self-service shop
offering a wide variety of food and household products. It is larger in size an has a wider
selection than a traditional grocery, but is smaller and more limited in the range of
merchandise than a hypermarket or big-box market.
The concept of an inexpensive food market relying on large economies of scale was
developed by Vincent Astor. He founded the Astor Market in 1915, investing $750,000 of
this fortune into a 165 by 125 corner of in the famous 95 Manhattan avenue, creating in
effect, an open air mini-mall that sold meat, fruit, produce and flowers. The expectation was
that customers would come from great distances (“miles around”), but in the end even
attracting people from the ten blocks away was difficult, and the market folded in 1917. The
concept of a supermarket was developed by entrepreneur Clarence Saunders and his Piggly
Wiggly stores. His first store opened in 1916. Saunders was awarded a number of patents for
the ideas he incorporated into his stores. The stores were a financial success and Saunders
began to offer franchises. The Great Atlantic & Pacific Tea Company, which was established
in 1859, was another successful early grocery store.
Historically, there was a debate about the origin of the supermarket, with King Kullen
and Ralphs of California having strong claims. Other contenders included Weingarten’s Big
Food Markets and Henke & pillot. To the end the debate, the Food Marketing Institute in
conjunction with the Smithsonian Institution and with funding from H.J. Heinz, researched
the issue. It defined the attributes of a supermarket as “self-service product departments,
discount pricing, marketing and volume selling”.
It has been determined that the first true supermarket in the United States was opened
by a former Kroger employee, Michael J Cullen, on August 4, 1930 inside a 6,000-square-
foot (560m*) former garage in Jamaica, Queens in New York City. The store, King Kullen,
operated under the slogan “Pile it high. Sell it low”. At the time of Cullen’s death in 1936,
there were seventeen King Kullen stores in operation. Although Saunders had brought the
world self- service, uniform stores and nationwide marketing, Cullen built on this idea by
adding separate food departments, selling large volumes of food at discount prices and
adding a parking lot.
lOMoARcPSD|42436405
In the United Kingdom, self-service shopping took longer to become established even
in 1947, there were just ten self-service shops in the country. The UK’s first supermarket
under the new Premier Supermarkets brand opened in Streatham, South London, taking ten
times as much per week as the average British general store of the time.
According to Aggarwal, Sisodia to make the software fast in processing, there should
be good user interface so that user can change it and it should be used for long time without
error and maintenance. Many supermarkets use this type of billing system for a decade. It is
also improved many times according to requirements of sellers and customers. It does the
same work that is calculating the bill; gives it to the customer and maintain proper database.
They are accurate in calculation and printing they also generate records.
A new concept is also added in the billing system that also maintains relationships
with the customers who purchase more products from the store regularly. The system also
concerns their requirements and give them more discount and commission. It also shows the
overall profit on a particular product and reports on which items are required and which have
crossed their expiry date.
lOMoARcPSD|42436405
CHAPTER 3
SYSTEM ANALYSIS
System analysis is the first and foremost phase in the methodology of system
development because the development of and success of all the phases ahead are entirely
dependent on the successful development of this phase hence, system analysis in this
organization is taken as most crucial and done very carefully.
Every system has pros and cons so existing system also have many advantages and
disadvantages. So, the bottlenecks of the existing system are as follows:
User Interface: user interface is not so much good that operators feel some problem.
Graphical User Interface: GUI not good so the operators get bored by watching
screen.
Processing Speed: processing speed of the software is not so much good to operate
fast.
Flexible: existing system is not so much flexible that can be changed according to the
operators and customers.
To reduce the bottlenecks of the existing system there is a need to develop a new
system the new system could concern the requirements of the customer and the sellers. It has
following qualities:
Propose system has these qualities including the qualities of existing system.
Automation – The application automates each and every activity of the manual
system and increases its throughput. Thus, the response time of the system is very less
and it works very fast.
Accuracy – The application provides the user a quick response with very accurate
information regarding the bill calculation and customer detail etc. any details or
system in an accurate manner, as when required.
User Friendly – The application Supermarket Billing System has a very user friendly
interface. Thus, the users will fully very easy to work on it. The application provide
accuracy along with a pleasant interface. Make the present manual system more
interactive, speedy and user friendly.
Availability – All the Billing details stored permanently in the database admin can
see the data, whatever needed.
Maintain Cost – Reduce the cost of maintenance. It is standalone application so no
required of cost for maintain it.
CHAPTER 4
4.1SOFTWARE REQUIREMENTS
JAVA Language
JAVA has also been found useful in many other contexts, with key strengths being
software infrastructure and resource-constrained applications, including desktop
applications, video games, servers and performance-critical applications.
4.2HARDWARE REQUIREMENTS
The most common set of requirements defined by any operating system or software
application is the physical computer resources, also known as hardware. A hardware
requirements list is often accompanied by a hardware compatibility list (HCL), especially in
case of operating systems. An HCL lists tested, compatibility and sometimes incompatible
hardware devices for a particular operating system or application. The following sub-sections
discuss the various aspects of hardware requirements.
The Model View Controller (MVC) design pattern specifies that an application consist of a
data model, presentation information, and control information. The pattern requires that each
of these be separated into different objects.
The MODEL contains only the pure application data, it contains no logic describing
how to present the data to a user.
The VIEW presents the model’s data to the user. The view knows how to access the
model’s data, but it does not know what this data means or what the user can do to
manipulate it.
The CONTROLLER exists between the view and the model. It listens to events
triggered by the view (or another external source) and executes the appropriate
reaction to these events. In most cases, the reaction is to call a method on the model.
Since the view and the model are connected through a notification mechanism, the
result of this action is then automatically reflected in the view.
“Feasibility Study” is a test of the system according to its workability, impact of the
organization, ability to meet user needs and effective use of the resources.
We can test our system by different type of the feasibilities. There are 5 types of the
feasibilities which are discussed here. There are as follows:
1. Technical Feasibility:
A study of resource availability that may affect the ability to achieve an acceptable
system. This evaluation determines whether the technology needed for the proposed
system is available or not. This system can be made in any language that support good
user interface and easy database handling.
2. Economic Feasibility:
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economic feasibility, the development
cost in creating the system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any addition hardware or
software. Since the interface for this system is developed using the existing resources
and technologies. There is nominal expenditure and economic feasibility for certain.
3. Operational Feasibility:
Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organization’s operating requirements. Operational
feasibility aspects of the project are to be taken as an important issue raised are to test
the operational feasibility of a project includes the following:
Is there sufficient support for the management from the users?
Will the system be used and work properly if it is being developed and
implemented?
Will there be any resistance from the user that will undermine the possible
application benefits?
4. Schedule Feasibility:
Time evaluation is most important consideration in development of the project. So,
the project is concerned should be completed with fixed in scheduled time as far as
company is concerned. New system is not so much big so it is easy to make in few
days.
5. Behavioural Feasibility:
People are inherently resisted to change and a computer means “change is the only
certainty”. An estimate should be made of how strong a reaction the user staff in
going to have towards development of new system. Thus, special efforts can be made
to educate and train the staff.
lOMoARcPSD|42436405
CHAPTER 5
SYSTEM DESIGN
5.1USE CASE DIAGRAM
Use case diagram is a graph of actors, a hard and fast of use instances enclosed by
means of a deviceboundary, conversation associations among the actor and the use case.
The use case diagram describes how a gadget interacts with out of doors actors; each use
case represents a bit of functionality that a machine provides to its users. The use instances
are used at some point of the evaluation phase of a task to pick out and partition system
capability. They separate the device into actors and use case. Actors represent roles which
might be played by using person of the system. Those users may be people, different
computer systems, portions of hardware, or maybe other software structures.
CHAPTER 6
SYSTEM IMPLEMENTATION
This chapter is the part that puts a planned system into action and examine in details
the analysis and design of the Skillmad supermarket system. The present chapter discusses
the implementation of the system, highlighting the testing exercise and describing some of
the main components of the system’s Graphical User Interface. It will give an output from
programming language and other tools used to develop our system. According to this plan,
the activities are to be carried out, discussions made regarding the equipment and resources
and the additional equipment has to be acquired to implement the new system.
while (true) {
System.out.print("Enter item name: ");
String itemName = scanner.next();
if (itemName.equalsIgnoreCase("exit")) {
break;
}
System.out.print("Enter item quantity: ");
int itemQuantity = scanner.nextInt();
System.out.print("Enter item price: ");
double itemPrice = scanner.nextDouble();
Item item = new Item(itemName, itemQuantity, itemPrice);
items.add(item);
subTotal += itemQuantity * itemPrice;
System.out.println("Item: " + itemName + ", Quantity: " + itemQuantity + ", Price: Rs " + itemPrice);
}
class Item {
private String name;
private int quantity;
private double price;
1. Customer
2. Administrator
3. Exit
1. CUSTOMER:
Customer is one of the modules in our project. They can purchase the available
product. The product number will be shown by the administrator. Using the product number,
they can purchase and they can enter the amount of quantity they required after completion
the admin will generate the total price of the product with discount and he also generate the
bill of the particular product to the customer. The steps involved are:-
2. ADMINISTRATOR:
Administrator plays a major role in our project. They are responsible to create a
product and delete new product and they can modify the product and view and they can
check the product after modification or altering the project.
Initially the administrator of the system will add the amount of the particular product
after entering the details of the product and he can also add the discount of a particular
product. The administrator module consists of the following options:
1. Create a product.
2. Modify a product.
3. Delete a product.
4. View product menu.
5. Back to the main menu.
1. createpr() – This function is used to create new product, with name, price and
discount by the administrator.
2. showpr() – This function is used by the administrator to see the product list, with
description and price.
3. writepr() – This function writes the information about the product in the file.
4. disp() – This function is used to display all record from the file.
5. dispsp() – This function is used to read specific data/records based on the product
number entered by the file.
6. modifypr() – This function is used modifies the product details by entering the
product number.
7. deletepr() – This function is used to delete the product by entering the product
number.
8. menu() – Display all product price list.
9. placeorder() – Function to place order and generating bill for product.
10. into() – This function displays the project name.
11. admin() – This function displays a list of function to be operated by administrator
to modify/update product details.
12. main() – This is the main function which just the MAINMENU from where the
control is transferred to other functions.
CHAPTER 7
DATABASE DESIGN
The data in the system has to be stored and retrieved from database. Designing the
database is part of system design. Data elements and data structures to be stored have been
identified at analysis stage. They are structured and put together to design the data storage
and retrieval system. A database is a collection of interrelated data stored with minimum
redundancy to serve many users quickly and efficiently. The general objective is to make
database access easy, quick, inexpensive and flexible for the user. Relationships are
established between the data items and unnecessary data items are removed. Normalization is
done to get an internal consistency of data and to have minimum redundancy and maximum
stability. This ensures minimizing data storage required, minimizing chances of data
inconsistencies and optimizing for updates. The MS Access database has been chosen for
developing the relevant databases.
1. ADMINISTRATION TABLE
2. CUSTOMER TABLE
Field Name Data Type Description
Customer Char Primary key
3. PRODUCT TABLE
CHAPTER 8
SOFTWARE TESTING
It is the process of testing the functionality and correctness of software by running it.
Process of executing a program with the intent of finding an error.
A good test case is one that has a high probability of finding an as yet undiscovered
error. A successful test is one of that uncovers an as yet undiscovered error.
Defect detection
Reliability estimation
Knowing the internal working i.e., to test if all internal operation is performed
according to program structure and data structures.
The main aim of testing is to uncover a host of errors, systematically and with
minimum effort and time. Starting formally, we can say, Testing is process of executing a
program with the intent of finding an error. A successful test is one that uncovers an as yet
undiscovered error. Good case test is one that has a high probability of finding errors, if it
exists. But there is one thing that testing cannot do testing cannot show the absence of defects
it can only show that software defects are present. As the test results are gathered and
evaluated, they begin to give a qualitative indication of the reliability of the software.
The process of testing is to discover the errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub-assemblies. It is the process of exercising software with
the intent of ensuring that the software system meets its requirements and user expectations
and does not final in an unacceptable manner.
TYPES OF TESTING
1. UNIT TESTING
The first level of testing is called unit testing. In this, different modules are tested against
the specification produced during design for the modules. Unit testing is essentially for
verification of the code produced during the coding phase, and hence the goal is to test the
internal logic of the modules. It is typically done by the programmer of the module. A
module is considered for integration and use by others only after it has been unit tested
satisfactorily.
2. INTEGRATION TESTING
The next level of testing is often called integration testing. In this, many units tested
modules are combined into subsystems, which are then tested. The goal here is to see if the
modules can be integrated properly. Hence, the emphasis is on testing interfaces between
modules. This testing activity can be considered testing the design.
3. SYSTEM TESTING
Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal is to see if the software meets its requirements. This is
essentially a validation exercise, and in many situations, it is the only validation activity.
System testing is also known as black box testing and it is conducted to test the functionality
of the system that is behaving as expected
lOMoARcPSD|42436405
4. ACCEPTANCE TESTING
Acceptance testing is sometimes performed with realistic data of the client to demonstrate
that the software is working satisfactorily. Testing here focuses on the external behaviour of
the system. The internal logic of the program is not emphasized. Mostly functional testing is
performed at these levels.
Field testing will be performed manually and functional tests will be written in detail.
Test Objectives:
Features to be tested:
CHAPTER 9
SNAPSHOTS OF RESULT
CONCLUSION
After we have completed the project, we are sure the problems in the existing system
world overcome. The “Supermarket Billing System” process made computerized to reduce
human errors & to increase the efficiency. The main focus of this project is to fewer human
efforts. The maintenance of the records is made efficient, as all the records are stored in the
access database, through which data can be retrieved easily. The navigation control is
provided in all the forms to navigate through the large number of records. If the numbers of
records are very large than user has to just type in the search string & user gets the results
immediately. The editing is also made simples. The user has to just type in the required field
& process the modify button to update desired field. Our main aim of the project is to get the
correct bills and maintain the data of the supermarket.
lOMoARcPSD|42436405
REFERENCES
www.google.com
www.wikipedia.com
www.youtube.com
some resources are from few text books and other websites.