A PROJECT REPORT

ON
“CALCULATOR”

PM SHRI KENDRIYA VIDYALAYA ARA

PATNA REGION

SUBMITTED BY
Name : Shivam Ojha
Enroll No.:
Class : XII
Group Members : Aditya, Shivam Ojha, Sahil

Under the Guidance of

Dr. Anu Aujla
PGT-CS
 DECLARATION

This is to certify that the Project Report entitled “CALCULATOR” which is

submitted to the department of computer science, PM SHRI Kendriya Vidyalaya
Ara , Patna region is prepared by us. All the coding is the result of our personal
effort and due acknowledgement has been made in the text to all other material
used.

Date: 11/28/2024
Name of Student: Shivam Ojha

APPROVED BY-
Name of Subject Teacher/Guide: Dr. Anu Aujla

TABLE OF CONTENT

1
SER DESCRIPTION PAGE NO

01 CERTIFICATE

02 ACKNOWLEDGEMENT

03 INTRODUCTION

04 OBJECTIVES OF THE PROJECT

05 PROPOSED SYSTEM

06 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

07 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

08 FLOW CHART

09 SOURCE CODE

10 OUTPUT

11 TESTING

12 HARDWARE AND SOFTWARE REQUIREMENTS

13 REFERNCES

2
 CERTIFICATE

This is to certify that the Project Report entitled “CALCULATOR” which is

submitted by Shivam Ojha and group in partial fulfillment of the requirement
for the award of practical marks for Computer Science, CBSE board
Examination is a record of the candidate’s own work carried out by her under my
supervision.

External Teacher Signature Internal Teacher Signature

ACKNOWLEDGEMENT

I pay my gratitude and sincere regards to Dr. Anu Aujla, our project guide for
giving me the cream of her knowledge. I am thankful to her as she has been a
constant source of advice, motivation and inspiration. I am also thankful to her
for giving her suggestions and encouragement throughout the project work.

I take the opportunity to express our gratitude and thanks to our Principal,
Teachers and library staff for providing us the opportunity to utilize their
resources for the completion of the project.

I am also thankful to my family and friends for constantly motivating me to

complete the project and providing me an environment which enhanced my
knowledge.

3
 PROJECT ON CALCULATOR

INTRODUCTION
• Purpose
• Perform mathematical operations (addition, subtraction, multiplication,
division, etc.).
• Store operation history and results in a MySQL database for
recordkeeping and analysis.
• Components:
• Python: The programming language used for creating the calculator's
logic and interacting with the database.
• MySQL: A relational database management system to store the operation
history (e.g., inputs, outputs, timestamps).
• Key Features:
• User Input Handling: Accept numeric inputs and operation choices from
the user.
• Computation: Perform calculations based on user input.

4
OBJECTIVES OF THE PROJECT

1. Mathematic operations: to perform basic mathematical operations

2. Integration : illustrate the use of Python libraries like mysql-connector to

interact with databases.

3. Application of Programming Concepts: Apply programming concepts

such as modular design, database connectivity, and error handling in a

realworld scenario

PROPOSED SYSTEM

• User Interface
• A text-based interface for user input, built using Python's input()

• Allows users to:

• Select operations (e.g., addition, subtraction, multiplication, division).

• Input values for calculations.
• View operation history

• Calculation Module:
• Implements arithmetic logic to perform operations.
• Validates user inputs (e.g., ensuring no division by zero)

• Database Module:
5
 • Manages connection to the MySQL database.
• Saves each operation, including inputs, results, and timestamps.
• Retrieves stored operations for user review.

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,

6
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.

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

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

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
8
 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.

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

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements using
highlevel requirements identified in the Initiation, System Concept, and Planning
phases. It also delineates the requirements in terms of data, system performance,
10
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

11
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.
• 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 byAgency technical and
functional representatives to ensure that it satisfies the business
12
 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
13
 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
14
 • 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 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.

15
 • Determine when the system needs to be modernized, replaced, or retired.

important about the code

• Operations function is for the table of mathematical operators

• Use this function only for one time

SOURCE CODE

import mysql.connector as m
import math as y

mydb=m.connect(host='localhost',user='root',password='adi@2007',port=3306,data
base='calculator')
mycursor=mydb.cursor()
mycursor.execute('create database if not exists calculator')

# FOR CALCULATOR DESIGN

mycursor.execute('create table if not exists CALCULATOR( VALUE_1 varchar(50)
,VALUE_2 varchar(50),MATHEMATICAL_OPERATION varchar(50),RESULT varchar(50))')
while True:

v1= eval (input('enter your VALUE_1(main value)--'))

v2= eval(input('enter your VALUE_2(side value)--'))
math=input('enter you MATHEMATICAL_OPERATION as per SQL TABLE ')
if math in
['lcm','hypot','add','sub','multiply','divide','remainder','percentage','power
']:

16
 if math=='add':
m1=v1+v2
mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,
MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1, v2,'add',m1))
mydb.commit()
if math=='sub':
m2=v1-v2
mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,
MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1, v2,'sub',m2))
mydb.commit()
if math=='lcm':
m3=y.lcm(v1,v2)
mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,
MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1, v2,'lcm',m3))
mydb.commit()
if math=='multiply':
m4=v1*v2
mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,
MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
v2,'multiply',m4))
mydb.commit()
if math=='divide':
if v2 ==0:
mj='infinity'
print('infinity')
mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,
MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1, v2,'divide',mj))
else:
m5=v1/v2
mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,
MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1, v2,'divide',m5))
mydb.commit()
if math=='remainder':
m6=v1%v2

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
v2,'remainder',m6))
mydb.commit()
if math=='percentage':
m7=v1//v2*100

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
v2,'percentage',m7))
mydb.commit()
if math=='power':

17
 m14=v1**v2

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','powery',m14))
mydb.commit()
else:

if math=='cube':
m16=v1**3

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','cube',m16))
mydb.commit()
if math=='square':
m15=v1**2

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','square',m15))
mydb.commit()
if math=='log':
m13=y.log(v1)

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','log',m13))
mydb.commit()
if math=='!':
m12=y.factorial(v1)

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','factorial',m12))
mydb.commit()
if math=='sqrt':
m11=y.sqrt(v1)

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1, 'NULL','square
root',m11))
mydb.commit()
if math=='floor':

18
 m10=y.floor(v1)

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','floor',m10))
mydb.commit()
if math=='ceil':
m9=y.ceil(v1)

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','ceil',m9))
mydb.commit()
if math=='cbrt':

m8=y.cbrt(v1)

mycursor.execute("INSERT INTO CALCULATOR (VALUE_1, VALUE_2,

MATHEMATICAL_OPERATION,RESULT) VALUES (%s, %s, %s,%s)", (v1,
'NULL','cuberoot',m8))
mydb.commit()
v3=input('enter yes/no for more execution--')
if v3=='no':

mycursor.execute('truncate table CALCULATOR ')

print('the calculator has cleared now ')
mydb.commit()
break

# USE OPERATORS FUNCTION FOR ONE TIME ONLY

def operators():
mycursor.execute('''create table if not exists operators($$ varchar(50) ,
$$$ varchar(50) ,$$$$ varchar(50) , $$$$$ varchar(50))''')
sml='insert into operators($$ , $$$ , $$$$ , $$$$$ ) values(%s,%s,%s,%s)'
mycursor.execute(sml,("add","sub","multiply",'divide'))
mycursor.execute(sml,("lcm","remainder","power",'cube'))
mycursor.execute(sml,("square","percentage","log",'fact!'))
mycursor.execute(sml,("floor","ceil","cbrt",'ADI'))
mydb.commit()

19
20
 OUTPUT
================================================================

Vs code output:

Sql output:

21
Sql output(2nd):

TESTING

22
Software Testing is an empirical investigation conducted to provide stakeholders
with information about the quality of the product or service under test, 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.

23
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. 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:-

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

HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : INTEL 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 ATHLON

IV. RAM : 512MB+

25
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. Keyboard and mouse

X. Printer : required

SOFTWARE REQUIREMENTS:

• Windows OS
• Python--
• MySQL

REFERENCES

26