PAGE | 1

AISSCE 2021-2022
Rabindra Vidya Niketan,
NH-49, Badahal, Keonjhar
PROJECT REPORT
ON
GROCERY SHOP

Submitted By: - Abhishek sandha

Class – XII Science (A)
Roll No. ----
Submitted To: - MR. K.Jagannath Reddy
 PAGE | 2

CERTIFICAT
E
This is to certify that the Computer Science project on

“GROCEREY SHOP”is a bonafide work done by

“ABHISHEK SANDHA”

OfClass –XII Science, Session 2021-2022 inthe complete

fulfilment of Central board of secondary education

(CBSE)AISSCE Examination 2021-2022

And has been carried out under my direct supervision and

guidance.

MR.K.JAGANNATH REDDY
(COMPUTER SCIENCE TEACHER)

DECLARATION
 PAGE | 3

I hereby declare that the project work entitled on

“GROCEREY SHOP”

Submitted to
DEPARTMENT OF COMPUTER SCIENCE

RABINDRA VIDYA NIKETAN,

NH-49, Keonjhar, Odisha

Is prepared by me.

All the coding is the result

Of my personal effort.

Name: - ABHISHEK SANDHA

Class: - XII Science

TABLE OF CON
 PAGE | 4

Page
S.no. Description
No
01 Acknowledgement 05
02 Preface 06
02 Introduction 07
03 Objectives Of The Project 07
04 Proposed System 08
05 System Development Life Cycle (Sdlc) 08
Phases Of System Development Life
06 09
Cycle
07 Flow Chart 15
08 Source Code 16
09 Output 19
10 Testing 26
11 Hardware And Software Requirements 29
12 Bibliography 30

ACKNOWLEDGEMENT
 PAGE | 5

As usual a large no people deserve my thanks for the

help they provided me for the preparation of this
project.

First of all I would like to thank my teacher

Mr K Jagannath Reddy

For his support during the preparation of this project

I am very thankful for his guidance.

I would like to thank my friend for the encouragement

and information about the topic they provided me
during my effort to prepare this topic.At last I would
also place on record, our sincere gratitude to one and
all who directly or indirectly have lent there helping
hand in this venue.

preface
 PAGE | 6

This project“GROCEREY SHOP”

is a specially designed program by me which
will help you add, list and delete product.

I have chosen this topic since this type of

program will help you perform menu driven
program which will also help you understand
the use of this beautiful program which has
been designed into small chunks of blocks.
PAGE | 7
 PAGE | 8

PROJECT ON GROCERY SHOP MANAGEMENT SYSTEM

INTRODUCTION

This software is used to maintain the shop customer detail, product,

details,workerdetail maintain the shop in updated and maintain records of in and out
data of shop

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.
 PAGE | 9

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 organizations. 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
 PAGE | 10

button. Moreover, now it’s an age of computers of and automating such an

organization gives the better look.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

 PAGE | 11

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’sjob 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 planning, concept
of operations, system security, verification and validation, and systems engineering
management planning.
 PAGE | 12

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.
 PAGE | 13

Develop the test and evaluation requirements that will be used to determine
acceptable system performance.

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 c 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
 PAGE | 14

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.
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.
 PAGE | 15

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.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is

conducted during the integration and test phase. The user, with those
 PAGE | 16

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.
 PAGE | 17

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 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 reenter the planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the
system.
Certify that the system can process
sensitive information.
 PAGE | 18

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.
 PAGE | 19

FLOW CHART

Python-MySQL
connecting

Software login with username &password

Ask user to enter his choice

Your need will be fulfilled by python by

interfacing with MySQL
 PAGE | 20

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.

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.

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
 PAGE | 21

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 behavior), either "is" or "is not" the same as the expected value
specified in the test case. Specification-based 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)
 PAGE | 22

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:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines executed to
complete the test?
They both return coverage metric, measured as a percentage
PAGE | 23
 PAGE | 24

CODING:
PAGE | 25
PAGE | 26
PAGE | 27
 PAGE | 28

Hardware and Software Requirements

Hardware:
Procedure- Intel(R) Core(TM) [email protected]
Processor speed – 3.10GHZ
Ram- 6 GB or more or less
Hard disk – 1TB
 PAGE | 29

Software:
Operating System-Windows11 or below
Python version:Python 3.7.2

bibliography
http://www.google.com

http://en.wikipedia.org

http://www.stackoverflow.com

https://pythonworld.in/practical-project/project-list/

https://www.shutterstock.com/search/grocery+store