1

ELECTRONIC SHOP SYSTEM

Project submitted to the

CENTRAL BOARD OF SECONDARY EDUCATION

in partial fulfilment of the requirement for the

GRADE XII

By
HEMAPRIYAN.T

[Reg.No. ]

Under the Guidance and supervision of

MRS.M.AROCKIA PRINCYA MCA, B.Ed.,

(Department of COMPUTER SCIENCE)

St. Joseph International School (CBSE)

(Affiliated to CBSE, New Delhi Affiliation no. 1931084)
Mother virgin garden, Rameshwaram Highway, Kodikottai
2023-2024
 2

BONAFIDE CERTIFICATE

This is to certify that MR.HEMAPRIYAN.T of Class XII

(Roll No: )has prepared the project report

entitled ELECTRONIC SHOP SYSTEM.

” Further this is a bonafide project work, done under the guidance

of the subject teacher. This bonafide project work is the result of
the student’s individual efforts and endeavours. The report is
worthy of acceptance as final project report for the subject
chemistry of class XII. And it has been prepared as per the
guidelines issued by CBSE.

SIGNATURE OF THE PRINCIPAL SIGNATURE OF THE TEACHER

MR.MARIA CHARLIE M.A., M.Ed., MRS.M.AROCKIA PRINCYA, MCA, B.Ed.,

SIGNATURE OF THE EXTERNAL

 3

DECLARATION

I hereby declare that the project work entitled "ELECTRONIC SHOP

SYSTEM" submitted to department of COMPUTER SCIENCE,
ST. JOSEPH INTERNATIONAL SCHOOL (CBSE) is prepared by me.
All the information, analysis and observations are the result of my personal
efforts and my indebtedness to the related publications, project works and
references, if any have been duly acknowledged.

Name of the Candidate : MR.HEMAPRIYAN.T

Signature of the Candidate :

Reg. No :
 4

ACKNOWLEDGEMENT

Firstly, I would like to thank God for being able to complete this
computer science project with success.

I am very grateful to everyone who supported me to complete my

projecteffectively and moreover on time. My deep acknowledgment
and gratitude go to all those who helped me present these ideas
well.

I would like to express my whole hearted thanks to our campus

superior Rev. Sr. PUNITHA ROSELINE M.com., B.Ed. or providing
best facilities and technical environment which helped me to
complete this project work.

I express my sincere thanks to my principal MR.MARIA CHARLIE

M.A., M.Ed. for her support and for all the facilities provided for
the preparation of thisproject work

I extend my sincere thanks to my teacher MRS. M.AROCKIA

PRINCYA MCA, B.Ed., who guided me to the successful completion of
this project. I take this opportunity to express my deep sense of
gratitude for their individual guidance, constantencouragement and
immense motivation which have sustained my effortsat all stages of
this project work.

Secondly, I would also like to thank my parents and friends who

helpedme a lot in finalizing this project within the limited time frame.
 5

TABLE OF CONTENTS [ T O C ]

C.NO DESCRIPTION PAGE NO

01 INTRODUCTION 06

02 OBJECTIVES OF THE PROJECT 06

03 PROPOSED SYSTEM 07

04 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 08

05 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 09

06 FLOW CHART 17

07 SOURCE CODE 18

08 OUTPUT 23

09 TESTING 27

10 HARDWARE AND SOFTWARE REQUIREMENTS 30

11 INSTALLATION PROCEDURES 31

12 BIBLIOGRAHPHY 32
 6

PROJECT ON ELECTRONIC SHOP SYSTEM

INTRODUCTION

Basically this software is a user friendly which can be used by both admin and

the customers. This software is used to update the electronic items list, the list of

workers working in this shop and the list of customers of this shop. For administrative

works such as entry of various lists there is a password .And for other activities such as

viewing of list there is no password. So this software is a admin as well as customer

friendly software.

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.

 7

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 out dated 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.

 8

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, concept-development, 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.
 9

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 outlines 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.
 10

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 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,
onetime 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.
 11

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 planning, concept of
operations, system security, verification and validation, and systems engineering
management planning.
 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.
● 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 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
 13

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.
● 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.
 14

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

● 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 reviewedand 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 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 on going. 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.
 16

START
FLOW CHART

CONNECT MYSQL, CREATE

TABLE-ITEM,
LABOURS,CUSTOMER

PRINT’1.CUSTOMER’P
RINT’2.ADMIN’

INT(INPUT(‘CHOICE’)

FALSE IF CHOICE
==1:
TRUE

ELIF CHOICE==2’ FALSE

PRINT’1.ITEM LIST’
TRU

PRINT’2.LABOURLIST’
PRINT’CUSTOMER LIST’

INPUT ENTER
PASSWORD

INPUT (‘ENTER THE CHOICE’)

IF PASSWD==
FALSE

WHYSOOSERIOUS

IF CHOICE==1:
TRUE

TRUE

FALSE

ELIF
ENTRY PRINT’1.ITEM’ SHOW ‘ITEM LIST’ FALSE
CHOICE=2
PRINT’2.LABOUR’
PRINT’3.CUSTOMER’
TRU

SHOW ‘LABOUR LIST’

INPUT ‘ENTER THE
CHOICE’
 17

IF CHOICE==1: FALSE
TRU

FALSE

TRU
INPUT ‘NAME OF ELIF CHOICE==3:
ITEM’ ELIF
‘AVAILABILITY’ CHOICE FALSE SHOW
‘PRICE OF ITEM’ ==2
‘CUSTOMER LIST’
TRUE

INSERT THE VALUES INTO

ITEM LIST
INPUT ‘ENTER THE ELIF
NAME OF CHOICE
LABOUR’ ‘AGE:’ ==3:
‘PLACE:’
‘DEPARTMENT:’
TRU

INPUT ‘ENTER THE

INSERT THE VALUES INTO NAME OF LABOUR’
ITEM LIST ‘AGE:’ ‘PLACE:’
‘DEPARTMENT:’

INSERT THE VALUES INTO

ITEM LIST

STOP
 18

SOURCE CODE

FOR CONNECTING MYSQL AND CREATING FIRST TABLE :

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',passwd='manager',d

atabase='electronic_shop')

if conn.is_connected:

print('ELECTRONIC SHOP SYSTEM')

print('1.items')

print('2.labours')

print('3.customers')

print('4.sales')

print('5.expenses')

cur=conn.cursor()

cur.execute('create table items(s_no int(10),item varchar(50)

primary key,availability_of_item int(10),price int(7))')

conn.commit()

FOR CREATING OTHER TWO TABLES :

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',passwd='manager',d

atabase='electronic_shop')

cur=conn.cursor()

cur.execute('create table labours(name varchar(25) primary

key,age int(10),place varchar(25),department varchar(25))')

 19

cur.execute('create table customer(customer_name varchar(50)

primary key,age int(10),place varchar(25),item_bought

varchar(25))

conn.commit()

MAIN SOURCE CODE :

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',passwd='manager',d

atabase='electronic_shop')

cur=conn.cursor()

if conn.is_connected:

print('ELECTRONIC SHOP SYSTEM')

print('1.admin')

print('2.customers')

choice=int(input('enter the choice:'))

if choice==1:

pw='whysoserious'

passwrd=input('enter the password:')

print('1.entry for item')

print('2.entry for labour')

print(‘3.entry for customer')

choose=int(input('enter the choice for entry:'))

if choose==1:

item=input('enter the name of item:')

availability=int(input('availability of the item:'))

 20

price=int(input('enter the price of item in rupees:'))

cur.execute("insert into items values('" + item + "'," +

str(availability) + "," + str(price) + ")")

print('entry succesful')

conn.commit()

elif choose==2:

name=input('enter the name of labour:')

age=int(input('enter the age:'))

place=input('enter the place of the labour:')

dept=input('enter the name of the department:')

cur.execute("insert into labours values('" + name +

"','" + str(age) + "','" + place + "','" + dept + "')")

print('entry sucessful')

conn.commit()

elif choose==3:

name=input('enter the name of the customer:')

age=int(input('enter the age:'))

place=input('enter the place of the customer:')

item=input('enter the item bought:')

cur.execute("insert into customer values('" + name +

"','" + str(age) + "','" + place + "','" + item + "')")

print('entry sucessful')

conn.commit()

elif choice==2:
 21

print('1.Display of item list')

print('2.Display of labour list')

print('3.Display of customer list')

ch=int(input('enter the choice'))

if ch==1:

print()

cur.execute("select * from items")

dataa=cur.fetchall()

print('list of items')

for row in dataa:

print()

print('item:',row[0])

print('availablity:',row[1])

print('price:',row[2])

elif ch==2:

print()

cur.execute("select * from labours")

data=cur.fetchall()

print('list of labours')

for row in data:

print()

print('name:',row[0])

print('age:',row[1])

print('place:',row[2])
 22

print('department:',row[3])

elif ch==3:

print()

cur.execute("select * from customer")

datas=cur.fetchall()

print('list of customer')

for row in datas:

print()

print('name:',row[0])

print('age:',row[1])

print('place:',row[2])

print('item bought:',row[3])
 23

OUTPUT
24
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.

SPECIFICATION-BASED TESTING
 28

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. 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)
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.
 29

⮚ 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
 30

HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)

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

K9MM-V VIA K8M800+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

X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python
III. Mysql
 31

INSTALATION PROCEDURE

Dental Management System :-

Pre-Requisites :-
1. You have to have the following softwares for the successful running of
this software; which are

I) Python (Only for the First time), it is downloadable from

'www.python.org'.

II) MySQL (Only for the First time), it is downloadable from

'www.mysql.org'.

Installation :-
1. There will be two folders namely 'Python Files' and 'EXE files'.

2. The folder 'Python Files' will contain the source code of the software in python
language. If you are running the software by the 3rd step mentioned below you have to
pre install the following modules :-

I) mysql.connector

II) matplotlib.

3. Open the files in any python editors and run it to start and work on the
software.

4. The folder 'EXE files' will contain two files namely 'main.exe' and
'Tables_in_mysql.exe'.

5. First run the 'Tables_in_mysql.exe' to create the tables in MySQL.

6. Then run the file 'main.exe' to start and work on the software.

CAUTION :-
If you are running the software through running the python files or by running the
.exe files ; first run the file named 'Tables_in_mysql'.

The .exe file will take a lot of time; so be PATIENT.

 32

BIBLIOGRAPHY

1. Computer science With Python - Class XI By : Sumita Arora

2. A Project Report On ELECTRONIC SHOP MANAGEMENT SYSTEM
By: B.K.SUKUNTHAN
3. Website: https://www.w3resource.com

***