GROCERY SHOPPING MANAGEMENT

SYSTEM USING PYTHON

Register No. : XIIG45

Under the guidance of

Mrs.LAVANYA G MICHAEL

M.Sc, M.Phil, B.Ed

A Project work submitted to

CENTRAL BOARD OF SECONDARY EDUCATION

INDIA

In partial fulfilment of the requirement for

Class– XII 2024-25

1
 VELAMMAL
VIDYALAYA
PARUTHIPATTU

ACADEMIC YEAR 2024-25

PROJECT REPORT ON

GROCERY MANAGEMENT SYSTEM

USING PYTHON
REGISTER NO. :

NAME : M.NIKITHA

CLASS : XII G

SUBJECT : COMPUTER SCIENCE

SUB CODE : 083

PROJECT GUIDE: Mrs LAVANYA G MICHAEL

M.Sc, M.Phil, B.Ed

2
 VELAMMAL VIDYALAYA

PARUTHIPATTU,AVADI

VELAMMAL VIDYALAYA
PARUTHIPATTU

CLASS–XII PROJECT

Register No.:

CERTIFICATE
This is to certify that M.NIKITHA of class XII-G,

Register no: has successfully completed the project work entitled

GROCERY MANAGEMENT SYSTEM in the subject Computer science (083)

and submitted it to Central Board of Secondary Education.

During the academic year: 2024-25

INTERNAL EXAMINER EXTERNAL EXAMINER

3
 INDEX

S.NO. DESCRIPTION PAGE NO.

01 ACKNOWLEDGEMENT 05

02 INTRODUCTION 06

03 OBJECTIVES OF THE PROJECT 06

04 PROPOSED SYSTEM 07

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 08

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 09

07 FLOW CHART 17

08 SOURCE CODE 17

09 OUTPUT 20

10 TESTING 28

11 HARDWARE AND SOFTWARE REQUIREMENTS 31

12 BIBLIOGRAPHY 32

ACKNOWLEDGEMENT

4
 First and foremost my grateful thanks to the almighty for his divine
blessing and grace in making this project successful and I thank my parents
for giving me all this life and opportunity. I acknowledge my sincere thanks
to The Chairman and The Correspondent of Velammal Educational Trust for
providing me with this opportunity and the necessary facilities for
completing this study.

My profound gratitude and heartfelt thanks to Mr.Prithviraj, Senior

Principal Velammal Vidyalaya, Paruthipattu. Sir, thank you for your
expertise,enthusiasm, and especially for your precious time and for the
kind help in all situations throughout the academic year.

It is a proud privilege to express my sincere gratitude to my guide

Mrs.LAVANYA G MICHAEL , Faculty of Computer Science for constant
guidance for the entire study duration. Always looking ahead with new
ideas, guiding with patience and support in all situations.

I gladly extend my sincere thanks to my class in-charge and all Faculty

members for their support. Last but not least, I would like to show my
humble gratitude to my family members and all my friends who were the
back bone for me to complete this study successfully.

5
INTRODUCTION

This project is all about software for COVID vaccination. It helps

the Government to have a full-fledged control over his/her state .

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the

programming knowledge into a real- world situation/problem and exposed

the students how programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when

developing small to medium sized projects.

3. Write effective procedural code to solve small to medium sized

problems.

4. Students will demonstrate a breadth of knowledge in computer

science, as exemplified in the areas of systems, theory and software

development.

5. Students will demonstrate ability to conduct a research or applied

Computer Science project, requiring writing and presentation skills

which exemplify scholarly style in computer science.

6
PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be

really wants to stand against today’s merciless competition where not to

wise saying

“to err is human” no longer valid, it’s outdated to rationalize your mistake.

So, to keep pace with time, to bring about the best result without

malfunctioning and greater efficiency so to replace the unending heaps of

flies with a much sophisticated hard disk of the computer.

One has to use the data management software. Software has been an

ascent in atomization various organisations. Many software products working

are now in markets, which have helped in making the organizations work

easier and efficiently. Data management initially had to maintain a lot of

ledgers and a lot of paper work has to be done but now software product on

this organization has made their work faster and easier. Now only this

software has to be loaded on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully

automated and any information regarding the organization can be obtained

by clicking the button. Moreover, now it’s an age of computers of and

automating such an organization gives the better look.

7
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management

technique that divides complex projects into smaller, more easily managed
segments or phases. Segmenting projects allows managers to verify the
successful completion of project phases before allocating resources to
subsequent phases.
Software development projects typically include initiation, planning,
design, development, testing, implementation, and maintenance phases.
However, the phases may be divided differently depending on the
organization involved.
For example, initial project activities might be designated as request,
requirements-definition, and planning phases, or initiation,
conceptdevelopment, and planning phases. End users of the system under
development should be involved in reviewing the output of each phase to
ensure the system is being built to deliver the needed functionality.

8
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an

opportunity.
The purpose of the Initiation Phase is to:
Identify and validate an opportunity to improve business
accomplishments of the organization or a deficiency related to a
business need.
Identify significant assumptions and constraints on solutions to that
need.
Recommend the exploration of alternative concepts and methods to
satisfy the need including questioning the need for technology, i.e., will
a change in the business process offer a solution?
Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is
documented in a Concept Proposal. The Concept Proposal includes
information about the business process and the relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal
results in a Project Management Charter which outline the authority of
the project manager to begin the project.

Careful oversight is required to ensure projects support strategic

business objectives and resources are effectively implemented into an
organization's enterprise architecture. The initiation phase begins when an
opportunity to add, improve, or correct a system is identified and formally
requested through the presentation of a business case. The business case
should, at a minimum, describe a proposal’s purpose, identify expected
benefits, and explain how the proposed system supports one of the
organization’s business strategies. The business case should also identify
alternative solutions and detail as many informational, functional, and
network requirements as possible.

9
SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership and
the Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.
Identify basic functional and data requirements to satisfy the business
need.
Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
Evaluate the costs and benefits of alternative approaches to satisfy the
basic functional requirements
Assess project risks
Identify and initiate risk mitigation actions, and Develop high-level
technical architecture, process models, data models, and a concept of
operations. This phase explores potential technical solutions within the
context of the business need.
It may include several trade-off decisions such as the decision to use
COTS software products as opposed to developing custom software or
reusing software components, or the decision to use an incremental
delivery versus a complete, one-time deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves as an important reference document to support the
Information Technology Project Request (ITPR) process.
The ITPR must be approved by the State CIO before the project can
move forward.

10
PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing

development, acquisition, and maintenance projects. Careful planning,
particularly in the early stages of a project, is necessary to coordinate
activities and manage project risks effectively. The depth and formality of
project plans should be commensurate with the characteristics and risks of a
given project. Project plans refine the information gathered during the
initiation phase by further identifying the specific activities and resources
required to complete a project.
A critical part of a project manager’s job is to coordinate discussions
between user, audit, security, design, development, and network personnel
to identify and document as many functional, security, and network
requirements as possible. During this phase, a plan is developed that
documents the approach to be used and includes a discussion of methods,
tools, tasks, resources, project schedules, and user input. Personnel
assignments, costs, project schedule, and target dates are established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality assurance

11
planning, concept of operations, system security, verification and validation,
and systems engineering management planning.
REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements

using high-level requirements identified in the Initiation, System Concept,
and Planning phases. It also delineates the requirements in terms of data,
system performance, security, and maintainability requirements for the
system. The requirements are defined in this phase to a level of detail
sufficient for systems design to proceed. They need to be measurable,
testable and relate to the business need or opportunity identified in the
Initiation Phase. The requirements that will be used to determine acceptance
of the system are captured in the Test and Evaluation Master Plan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and
document them in the Requirements Document,
Complete business process reengineering of the functions to be
supported (i.e., verify what information drives the business process,
what information is generated, who generates it, where does the
information go, and who processes it),
Develop detailed data and process models (system inputs, outputs,
and the process.
Develop the test and evaluation requirements that will be used to
determine acceptable system performance.

12
DESIGN PHASE

The design phase involves converting the informational, functional,

and network requirements identified during the initiation and planning
phases into unified design specifications that developers use to script
programs during the development phase. Program designs are constructed
in various ways. Using a top-down approach, designers first identify and link
major program components and interfaces, then expand design layouts as
they identify and link smaller subsystems and connections. Using a bottom-
up approach, designers first identify and link minor program components and
interfaces, then expand design layouts as they identify and link larger
systems and connections. Contemporary design techniques often use
prototyping tools that build mock-up designs of items such as application
screens, database layouts, and system architectures. End users, designers,
developers, database managers, and network administrators should review
and refine the prototyped designs in an iterative process until they agree on
an acceptable design. Audit, security, and quality assurance personnel
should be involved in the review and approval process. During this phase,
the system is designed to satisfy the functional requirements identified in
the previous phase. Since problems in the design phase could be very
expensive to solve in the later stage of the software development, a variety
of elements are considered in the design to mitigate risk. These include:

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new
system.
Determining the operating environment.
Defining major subsystems and their inputs and outputs.
Allocating processes to resources.
Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the
preliminary design for the system.

13
 Everything requiring user input or approval is documented and
reviewed by the user. Once these documents have been approved by
the Agency CIO and Business Sponsor, the final System Design
Document is created to serve as the Critical/Detailed Design for the
system.
This document receives a rigorous review by Agency technical and
functional representatives to ensure that it satisfies the business
requirements. Concurrent with the development of the system design,
the Agency Project Manager begins development of the
Implementation Plan, Operations and Maintenance Manual, and the
Training Plan.

DEVELOPMENT PHASE
The development phase involves converting design specifications
into executable programs. Effective development standards include
requirements that programmers and other project participants discuss
design specifications before programming begins. The procedures help
ensure programmers clearly understand program designs and functional
requirements. Programmers use various techniques to develop computer
programs. The large transaction oriented programs associated with
financial institutions have traditionally been developed using procedural
programming techniques. Procedural programming involves the line-by-
line scripting of logical instructions that are combined to form a program.
Effective completion of the previous stages is a key factor in the success
of the Development phase. The Development phase consists of:

Translating the detailed requirements and design into system

components.
Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.

14
INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing

is conducted during the integration and test phase. The user, with
those responsible for quality assurance, validates that the functional
requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system. OIT Security staff
assess the system security and issue a security certification and
accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly
supported by end users

Testing as a deployed system with end users working together with

contract personnel

Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing a final Independent
Verification & Validation evaluation is performed and all documentation
is reviewed and accepted prior to acceptance of the system.
IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and accepted
by the user. In this phase, the system is installed to support the intended
business functions. System performance is compared to performance
objectives established during the planning phase. Implementation includes
user notification, user training, installation of hardware, installation of
software onto production computers, and integration of the system into daily

15
work processes. This phase continues until the system is operating in
production in accordance with the defined user requirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for

continued performance in accordance with user requirements and needed
system modifications are incorporated. Operations continue as long as the
system can be effectively adapted to respond to the organization’s needs.
When modifications or changes are identified, the system may re-enter the
planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.
Conduct periodic assessments of the system to ensure the functional
requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or
retired SOURCE CODE

================================================================

import mysql.connector
db1 = None
def connect():
global db1

db1=mysql.connector.connect(host="localhost",user="root",password="shreya060620
0 5",database="covid") def
showusers(): c1=db1.cursor()
c1.execute("select * from covid")
res=c1.fetchall()
#print(res) print("list of covid") for val in res:
print("username="+val[0]+"password="+val[1])

def login():
print("-"*50)

16
 print("\t COVID VACCINATION RECORD") print("-"*50)
print("\t LOGIN") un=input("Enter User Name:")
pw=input("Enter Password:") q="select*from covid where
username=%s and pass=%s" val=(un,pw)
cursor2=db1.cursor() cursor2.execute(q,val)
result=cursor2.fetchall() print("-"*50) if
len(result)==0: print("invalid user name or
password") print("-"*50) return False else:
print("Access Granted!!!")
print("-"*50) return
True

def addmember():
ad=input("Enter character:")
name=input("Enter Name:")
address=input("Enter Address:")
phone=input("Enter phone number:")
email=input("Enter email:")
age=input("Enter age of member:")
aadhar=input("Enter Aadhar cardno:")
cursor1=db1.cursor()
q="insert into member values(%s,%s,%s,%s,%s,%s,%s)"
val=(ad,name,address,phone,email,age,aadhar)
cursor1.execute(q,val) db1.commit()
print("Member Added successfully")

def showmembers(): c1=db1.cursor()

c1.execute("select * from member")
res=c1.fetchall()
#print(res) print("List of Members") for val in res:
print("Name ="+val[1]+" Aadhar card="+val[6])

def addvaccination():
ad=input("Enter Aadhar no:") name=input("Enter
vaccination Name:") d=input("Enter 1 for Dose 1: and ")
dt=input("Enter the date of vaccination:") c2=db1.cursor()
if d=="1": q="insert into vaccination values(%s,%s,
%s,NULL)" val=(ad,name,dt) c2.execute(q,val)
db1.commit() print("Vaccination Record Added
Successfully")
elif d=="2":
q="update vaccination set dose=%s where ad=%s"
val=(dt,ad)
c2.execute(q,val)
db1.commit()
print("Vaccination Record Updated Successfully

") else:
print("invalid input,please try again")

17
 def showvaccine(): c1=db1.cursor()
c1.execute("select*from vaccination,member where
vaccination.ad=member.ad") res=c1.fetchall()
#print(res)
print("List of Vaccinated Members") print ("-"*40)
print("Name\tVaccine\tAadhar No\tDose1\tDose2") print
("-"*40) for val in res: print(val[5],"\t",val[1],"\t",val[0],"\
t",val[2],"\t",val[3]) def shownotvaccined():
c1=db1.cursor(); c1.execute("select*from member where ad
not in(select ad from vaccination)") res=c1.fetchall()
#print(res) print("List of Not Vaccinated Members")
print ("-"*40) print("Name\tAadhar\tphone\
tAddress\tEmail") print ("-"*40) for val in res:
print(val[1],"\t",val[0],"\t",val[3],"\t",val[2],"\t",val[4])
def showduevaccine(): c1=db1.cursor() c1.execute("select* from vaccination,member
where vaccination.ad=member.ad
and d is null") res=c1.fetchall()
#print(res) print("List of Members whose Dose2 is due")
print("-"*40) print("Name\tvaccine\tAadhar no\tDose1\
tDose 2") print ("-"*40) for val in res:
print(val[5],"t",val[1],"\t",val[0],"\t",val[2],"\t",val[3])
connect()
print("connected")
if login(): while
True: print("-"*50)
print("\t CHOOSE AN OPERATION")
print("-"*50) print("Press1-Add a New Society
Member")

print("Press2-Add a Vaccination Record")

print("Press3-Show all the Members") print("Press4-Show all
Vaccinated Members") print("Press5-Show whose Vaccination
is Due") print("Press6-Show who are not at all Vaccinated")
print("Press7-Quit")
ch=int(input("Enter Your Choice:")) if
ch==1: addmember() elif ch==2:
addvaccination()
elif ch==3:
showmembers() elif
ch==4: showvaccine()
elif ch==5: showduevaccine()
elif ch==6: shownotvaccined()

18
OUTPUT

20
21
22
23
24
25
25
26
27
TESTING

Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service
under test[1] , with respect to the context in which it is intended to operate.
Software Testing also provides an objective, independent view of the
software to allow the business to appreciate and understand the risks at
implementation of the software. Test techniques include, but are not limited
to, the process of executing a program or application with the intent of
finding software bugs.

It can also be stated as the process of validating and verifying that a

software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as
expected and can be implemented with the same characteristics. Software
Testing, depending on the testing method employed, can be implemented at
any time in the development process, however the most test effort is
employed after the requirements have been defined and coding process has
been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used to describe
the point of view that a test engineer takes when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairs testing, fuzz
testing, model-based testing, traceability matrix, exploratory testing and
specification-based testing.

28
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software

according to the applicable requirements.[16] Thus, the tester inputs data
into, and only sees the output from, the test object. This level of testing
usually requires thorough test cases to be provided to the tester, who then
can simply verify that for a given input, the output value (or behaviour),
either "is" or "is not" the same as the expected value specified in the test
case. Specificationbased testing is necessary, but it is insufficient to guard
against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the principle, "Ask
and you shall receive," black box testers find bugs where programmers
don't. But, on the other hand, black box testing has been said to be "like a
walk in a dark labyrinth without a flashlight," because the tester doesn't
know how the software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes
many test cases to check something that can be tested by only one test
case, and/or (2) some parts of the back end are not tested at all. Therefore,
black box testing has the advantage of "an unaffiliated opinion," on the one
hand, and the disadvantage of "blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester
has access to the internal data structures and algorithms (and the code that
implement these)

29
Types of white box testing:-
The following types of white box testing exist:
api testing - Testing of the application using Public and Private
APIs.
Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all statements
in the program to be executed at least once.
fault injection methods. mutation testing methods. static
testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the

completeness of a test suite that was created with black box testing
methods. This allows the software team to examine parts of a system that
are rarely tested and ensures that the most important function points have
been tested.

Two common forms of code coverage are:

FunctionCoverage: Which reports on functions executed and
StatementCoverage:Which reports on the number of lines
executed to complete the test.
They both return coverage metric, measured as a percentage

30
 HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUALCORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIAK8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo : (If back up required)

VII.FLOPPY DRIVE 1.44 MB : (If Backup required) VIII. MONITOR

: 14.1 or 15 -17 inch

IX. Key board and mouse : required

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python
III. MySqlClient

31
 BIBLIOGRAPHY

1. NCERT Textbook
2. Computer science With Python - Class XI By : SumitaArora
3. A Project Report On Space Invader Game and Gold Loan
Shop
Management (GLSM)
By :M.Kalanithi
4. Website: https://www.youtube.com

32