[Date]

Computer
science
Investigatory project

Powered by
DILLIES V.A
ADITHYAN NS
 JAWAHAR NAVODAYA VIDYALAYA, KANNUR

ACADEMIC YEAR:2023-24

PROJECT REPORT ON
MANAGEMENT SYSTEM

NAME& ROLL NO. : DILLIES V.A

CLASS : XII – SCI
SUBJECT : COMPUTER SCIENCE
SUB CODE : 083
PROJECT GUIDE : Mrs.JISNA.C.K PGT (IT)

JAWAHAR NAVODAYA VIDYALAYA

KANNUR

1
 JAWAHAR NAVODAYA VIDAYALA,KANNUR

CERTIFICATE

This is to certify that Cadet has successfully completed the

project Work entitled Scientific Calculator using python in the

subject Computer Science(083) laid down in the regulations of CBSE for

the purpose of Practical Examination to be held in Jawahar Navodaya

Vidyalaya, Kannur on ____________.

Internal Examiner:
Name: _______________
Signature: Principal
External Examiner:
Name: _______________
Signature

2
 DECLARATION

We hereby declare that the project work entitled “

Scientific calculator “Submitted to JAWAHAR
NAVODAYA VIDYALAYA, KANNUR for the subject
of COMPUTER SCIENCE Under the guidance of Mrs.
Jisna.C.K, PGT (IT) is a record of original work done
by us. We further declare that this project record or any
part of this has not been submitted elsewhere for any
class.

Date name 1

Place

3
 TABLE OF CONTENTS [ T O C ]

PAGE
SER DESCRIPTION
NO

01 ACKNOWLEDGEMENT 05

02 INTRODUCTION 06

03 OBJECTIVES OF THE PROJECT 06

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 07

PHASES OF SYSTEM DEVELOPMENT LIFE

06 08
CYCLE

07 FLOW CHART 15

08 SOURCE CODE 17

09 OUTPUT 28

10 TESTING 29

11 HARDWARE AND SOFTWARE REQUIREMENTS 32

12 BIBLIOGRAPHY 32

4
 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 gratefully
acknowledge the contribution of the individuals who contributed in
bringing this project up to this level, who continues to look after me
despite my flaws, I express my deep sense of gratitude to the luminary
The Principal Jawahar Navodaya Kannur who has been continuously
motivating and extending their helping hand to us.I am overwhelmed to
express my thanks to The Administrative Officer for providing me an
infrastructure and moral support while carrying out this project in the
school. My sincere thanks to Jisna.C.K, 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

5
Introduction:
In this project ,we are going to create GUI scientific calculator using python
.As you can see, calculating large numbers nowadays is difficult and time
consuming .We have created a simple scientific calculator GUI using Python that
allows you to perform simple and complex calculations. To implement GUI we
use the thinker module of python.

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 ability to conduct a research or applied computer

science project , require writing and presentation skills which exemplify scholarly
style in computer science

Proposed system:
The proposed system is error free. Trivial concepts of Python language
are implemented into the system. As, the usage of Python Tkinter as the GUI
provided various controls, such as buttons, labels, and text boxes to build a user
friendly application. The rapid expansion and use of the internet, confirms the
splendid future and scope of the project.

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

7
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

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

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

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

DEVELOPMENT PHASE

12
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
assesses 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
13
 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 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.

14
flowchart

15
16
Source code
from tkinter import *
import math
import tkinter.messagebox

root = Tk()
root.title("Scientific Calculator")
root.configure(background = 'white')
root.resizable(width=False, height=False)
root.geometry("480x568+450+90")
calc = Frame(root)
calc.grid()

class Calc():
def __init__(self):
self.total=0
self.current=''
self.input_value=True
self.check_sum=False
self.op=''
self.result=False

def numberEnter(self, num):

self.result=False
firstnum=txtDisplay.get()
secondnum=str(num)
if self.input_value:
self.current = secondnum
self.input_value=False
else:
if secondnum == '.':
if secondnum in firstnum:
return
self.current = firstnum+secondnum
self.display(self.current)

def sum_of_total(self):
self.result=True
self.current=float(self.current)
if self.check_sum==True:
self.valid_function()
17
 else:
self.total=float(txtDisplay.get())

def display(self, value):

txtDisplay.delete(0, END)
txtDisplay.insert(0, value)

def valid_function(self):
if self.op == "add":
self.total += self.current
if self.op == "sub":
self.total -= self.current
if self.op == "multi":
self.total *= self.current
if self.op == "divide":
self.total /= self.current
if self.op == "mod":
self.total %= self.current
self.input_value=True
self.check_sum=False
self.display(self.total)

def operation(self, op):

self.current = float(self.current)
if self.check_sum:
self.valid_function()
elif not self.result:
self.total=self.current
self.input_value=True
self.check_sum=True
self.op=op
self.result=False

def Clear_Entry(self):
self.result = False
self.current = "0"
self.display(0)
self.input_value=True

def All_Clear_Entry(self):
self.Clear_Entry()
self.total=0
18
def pi(self):
self.result = False
self.current = math.pi
self.display(self.current)

def tau(self):
self.result = False
self.current = math.tau
self.display(self.current)

def e(self):
self.result = False
self.current = math.e
self.display(self.current)

def mathPM(self):
self.result = False
self.current = -(float(txtDisplay.get()))
self.display(self.current)

def squared(self):
self.result = False
self.current = math.sqrt(float(txtDisplay.get()))
self.display(self.current)

def cos(self):
self.result = False
self.current = math.cos(math.radians(float(txtDisplay.get())))
self.display(self.current)

def cosh(self):
self.result = False
self.current = math.cosh(math.radians(float(txtDisplay.get())))
self.display(self.current)

def tan(self):
self.result = False
self.current = math.tan(math.radians(float(txtDisplay.get())))
self.display(self.current)

def tanh(self):
19
 self.result = False
self.current = math.tanh(math.radians(float(txtDisplay.get())))
self.display(self.current)

def sin(self):

self.result = False
self.current = math.sin(math.radians(float(txtDisplay.get())))
self.display(self.current)

def sinh(self):
self.result = False
self.current = math.sinh(math.radians(float(txtDisplay.get())))
self.display(self.current)

def log(self):
self.result = False
self.current = math.log(float(txtDisplay.get()))
self.display(self.current)

def exp(self):
self.result = False
self.current = math.exp(float(txtDisplay.get()))
self.display(self.current)

def acosh(self):
self.result = False
self.current = math.acosh(float(txtDisplay.get()))
self.display(self.current)

def asinh(self):
self.result = False
self.current = math.asinh(float(txtDisplay.get()))
self.display(self.current)

def expm1(self):
self.result = False
self.current = math.expm1(float(txtDisplay.get()))
self.display(self.current)

def lgamma(self):
self.result = False
20
 self.current = math.lgamma(float(txtDisplay.get()))
self.display(self.current)

def degrees(self):
self.result = False
self.current = math.degrees(float(txtDisplay.get()))
self.display(self.current)

def log2(self):
self.result = False
self.current = math.log2(float(txtDisplay.get()))
self.display(self.current)

def log10(self):
self.result = False
self.current = math.log10(float(txtDisplay.get()))
self.display(self.current)

def log1p(self):
self.result = False
self.current = math.log1p(float(txtDisplay.get()))
self.display(self.current)

added_value = Calc()

txtDisplay = Entry(calc, font=('Helvetica',20,'bold'),

bg='black',fg='white',
bd=30,width=28,justify=RIGHT)
txtDisplay.grid(row=0,column=0, columnspan=4, pady=1)
txtDisplay.insert(0,"0")

numberpad = "789456123"
i=0
btn = []
for j in range(2,5):
for k in range(3):
btn.append(Button(calc, width=6, height=2,
bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,text=numberpad[i]))
btn[i].grid(row=j, column= k, pady = 1)
21
 btn[i]["command"]=lambda
x=numberpad[i]:added_value.numberEnter(x)
i+=1

btnClear = Button(calc, text=chr(67),width=6,

height=2,bg='powder blue',
font=('Helvetica',20,'bold')
,bd=4, command=added_value.Clear_Entry
).grid(row=1, column= 0, pady = 1)

btnAllClear = Button(calc, text=chr(67)+chr(69),

width=6, height=2,
bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,
command=added_value.All_Clear_Entry
).grid(row=1, column= 1, pady = 1)

btnsq = Button(calc, text="\u221A",width=6, height=2,

bg='powder blue', font=('Helvetica',
20,'bold'),
bd=4,command=added_value.squared
).grid(row=1, column= 2, pady = 1)

btnAdd = Button(calc, text="+",width=6, height=2,

bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.operation("add")
).grid(row=1, column= 3, pady = 1)

btnSub = Button(calc, text="-",width=6,

height=2,bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.operation("sub")
).grid(row=2, column= 3, pady = 1)

btnMul = Button(calc, text="x",width=6,

height=2,bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.operation("multi")
).grid(row=3, column= 3, pady = 1)
22
btnDiv = Button(calc, text="/",width=6,
height=2,bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.operation("divide")
).grid(row=4, column= 3, pady = 1)

btnZero = Button(calc, text="0",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.numberEnter(0)
).grid(row=5, column= 0, pady = 1)

btnDot = Button(calc, text=".",width=6,

height=2,bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.numberEnter(".")
).grid(row=5, column= 1, pady = 1)
btnPM = Button(calc, text=chr(177),width=6,
height=2,bg='powder blue', font=('Helvetica',20,'bold'),
bd=4,command=added_value.mathPM
).grid(row=5, column= 2, pady = 1)

btnEquals = Button(calc, text="=",width=6,

height=2,bg='powder blue',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.sum_of_total
).grid(row=5, column= 3, pady = 1)
# ROW 1 :
btnPi = Button(calc, text="pi",width=6,
height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.pi
).grid(row=1, column= 4, pady = 1)

btnCos = Button(calc, text="Cos",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.cos
).grid(row=1, column= 5, pady = 1)

btntan = Button(calc, text="tan",width=6,

23
 height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.tan
).grid(row=1, column= 6, pady = 1)

btnsin = Button(calc, text="sin",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.sin
).grid(row=1, column= 7, pady = 1)

# ROW 2 :
btn2Pi = Button(calc, text="2pi",width=6,
height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.tau
).grid(row=2, column= 4, pady = 1)

btnCosh = Button(calc, text="Cosh",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.cosh
).grid(row=2, column= 5, pady = 1)

btntanh = Button(calc, text="tanh",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.tanh
).grid(row=2, column= 6, pady = 1)

btnsinh = Button(calc, text="sinh",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.sinh
).grid(row=2, column= 7, pady = 1)

# ROW 3 :
btnlog = Button(calc, text="log",width=6,
height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.log
).grid(row=3, column= 4, pady = 1)
24
btnExp = Button(calc, text="exp",width=6, height=2,
bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.exp
).grid(row=3, column= 5, pady = 1)

btnMod = Button(calc, text="Mod",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=lambda:added_value.operation("mod")
).grid(row=3, column= 6, pady = 1)

btnE = Button(calc, text="e",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.e
).grid(row=3, column= 7, pady = 1)

# ROW 4 :
btnlog10 = Button(calc, text="log10",width=6,
height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.log10
).grid(row=4, column= 4, pady = 1)

btncos = Button(calc, text="log1p",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.log1p
).grid(row=4, column= 5, pady = 1)

btnexpm1 = Button(calc, text="expm1",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd = 4,command=added_value.expm1
).grid(row=4, column= 6, pady = 1)

btngamma = Button(calc, text="gamma",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.lgamma
25
 ).grid(row=4, column= 7, pady = 1)
# ROW 5 :
btnlog2 = Button(calc, text="log2",width=6,
height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.log2
).grid(row=5, column= 4, pady = 1)

btndeg = Button(calc, text="deg",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.degrees
).grid(row=5, column= 5, pady = 1)

btnacosh = Button(calc, text="acosh",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.acosh
).grid(row=5, column= 6, pady = 1)

btnasinh = Button(calc, text="asinh",width=6,

height=2,bg='black',fg='white',
font=('Helvetica',20,'bold'),
bd=4,command=added_value.asinh
).grid(row=5, column= 7, pady = 1)

lblDisplay = Label(calc, text = "Scientific Calculator",

font=('Helvetica',30,'bold'),
bg='black',fg='white',justify=CENTER)

lblDisplay.grid(row=0, column= 4,columnspan=4)

def iExit():
iExit = tkinter.messagebox.askyesno("Scientific Calculator",
"Do you want to exit ?")
if iExit>0:
root.destroy()
return

def Scientific():
root.resizable(width=False, height=False)
root.geometry("944x568+0+0")
26
def Standard():
root.resizable(width=False, height=False)
root.geometry("480x568+0+0")

menubar = Menu(calc)

# ManuBar 1 :
filemenu = Menu(menubar, tearoff = 0)
menubar.add_cascade(label = 'File', menu = filemenu)
filemenu.add_command(label = "Standard", command = Standard)
filemenu.add_command(label = "Scientific", command = Scientific)
filemenu.add_separator()
filemenu.add_command(label = "Exit", command = iExit)

# ManuBar 2 :
editmenu = Menu(menubar, tearoff = 0)
menubar.add_cascade(label = 'Edit', menu = editmenu)
editmenu.add_command(label = "Cut")
editmenu.add_command(label = "Copy")
editmenu.add_separator()
editmenu.add_command(label = "Paste")

root.config(menu=menubar)

root.mainloop()

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

29
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)
30
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 percent

31
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
X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

BIBLIOGRAPHY
https://realpython.com/python-gui-tkinter/
https://ncert.nic.in/textbook.php?lecs1=0-13
computer science textbook for class 12 ncert

32
33
34