Cs Projec Final
Cs Projec Final
NORTH LAKHIMPUR
(AFFILIATED TO CBSE )
SESSION : 2024-2025
COMPUTER SCIENCE PROJECT ON :
GROCERY MANAGEMENT SYSTEM
Submitted to: Mr. AVISHEK SINHA
PGT Computer Science,Teacher
LAKHIMPUR____________.
Examiner:
Name: _______________
Signature:
ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends largely on the
encouragement and guidelines of many others. I take this opportunity to express my
gratitude to the people who have been instrumental in the successful completion of this
project.
I express deep sense of gratitude to almighty God for giving me strength for the
successful completion of the project.
My sincere thanks to Mr. Avishek Sinha, Master In-charge, a guide, mentor all the
above a friend, who critically reviewed my project and helped in solving each and every
problem, occurred during implementation of the project
The guidance and support received from all the members who contributed and who are
contributing to this project, was vital for the success of the project. I am grateful for their
constant support and help
SOURCE CODE
print('grocery shop')
print('1.customer details')
print('2.product details')
print('3.worker details')
print('4.see all customer details')
print('5.see all product details')
print('6.see all worker details')
print('7.see one customer details')
print('8.see one product details')
print('9.see one worker details')
print('10.stocks')
print('11.pie chart for avalibility of stock')
choice=int(input('enter the choice'))
if choice==1:
cust_name=input('enter your name=')
phone_no=int(input('enter your phone
number='))
cost=float(input('enter your cost='))
sql_insert="insert into customer_details
values("+str(phone_no)+",'"+(cust_name)+"',"+str(cost)+
")"
c.execute(sql_insert)
conn.commit()
print('data is updated')
elif choice==2:
product_name=input('enter product name=')
product_cost=float(input('enter the
cost='))
sql_insert="insert into product_details
values(""'"+(product_name)+"',"+str(product_cost)+")"
c.execute(sql_insert)
conn.commit()
print('data is updated')
elif choice==3:
worker_name=input('enter your name=')
worker_work=input('enter your work=')
worker_age=int(input('enter your age='))
worker_salary=float(input('enter your
salary='))
phone_no =int(input('enter your phone
number='))
sql_insert="insert into worker_details
values(" "'"+(worker_name)+"',"
"'"+(worker_work)+"',"+str(worker_age)+","+str(worker_s
alary)+","+str(phone_no)+ ")"
c.execute(sql_insert)
conn.commit()
print('data is updated')
elif choice==4:
t=conn.cursor()
t.execute('select*from customer_details')
record=t.fetchall()
for i in record:
print(i)
elif choice==5:
t=conn.cursor()
t.execute('select*from product_details')
record=t.fetchall()
for i in record:
print(i)
elif choice==6:
t=conn.cursor()
t.execute('select*from worker_details')
record=t.fetchall()
for i in record:
print(i)
elif choice==7:
a=input('enter your name')
t='select*from customer_details where
cust_name=("{}")'.format(a)
c.execute(t)
v=c.fetchall()
for i in v:
print(v)
elif choice==8:
a=input('enter your product_name')
t='select*from product_details where
product_name=("{}")'.format(a)
c.execute(t)
v=c.fetchall()
for i in v:
print(v)
elif choice==9:
a=input('enter your name')
t='select*from worker_details where
worker_name=("{}")'.format(a)
c.execute(t)
v=c.fetchall()
for i in v:
print(v)
elif choice==10:
print('******************************************')
f=open('test.txt','r')
data=f.read()
print(data)
f.close()
print('******************************************')
elif choice==11:
import matplotlib.pyplot as plt
items=('shoes','stationary','watch','house
use','food items')
avalibility=[156,200,103,206,196]
colors=['red','yellowgreen','blue','gold','lightcoral']
plt.pie(avalibility,labels=items,colors=colors)
plt.title('avalibility of items in shop')
plt.show()
else:
print('wrong password, try again ')
if choice==2:
exit()
OUTPUT
TESTING
SPECIFICATION-BASED TESTING
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, 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)
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.
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. mysql
.
BIBLIOGRAPHY
***