A PYTHON Project

ON
GUI CALCULATOR

Submitted By:
Ayushi(1709710034)

Anurag Chaudhary(1709710022)

Submitted To:

Mr. Rajwantbir Singh Kohli

Mr. Himanshu Pathak

(Dept. Of Computer Science)

SOFTWARE REQUIREMENTS SPECIFICATION
(SRS)
GUI CALCULATOR
1. INTRODUCTION

THE GUI CALCULATOR IS AN AUTOMATIC TOOL BENEFICIAL FOR PER-

FORMING ARITHMETIC CALCULATIONS AND LOGICAL OPERATIONS
FAST AND EASILY. WITH FEW CLICKS ON BUTTONS USER CAN
EASILY GET HIS WORK DONE.

1.1 PURPOSE

This SRS Document contains the complete software and graphical re-
quirements for making arithmetical operations and describes the design
decisions ,architectural design and detailed design required to imple-
ment the GUI calculator. It provides visibility in design and provides in-
formation needed for software support. This setup basically helps to
make your calculations quick and set you free from paperwork.

1.2 SCOPE
GUI Calculator helps to provide efficient ,quick and accurate result of the
given input. It tends to make the performance better and reliable. It saves
time and reduces human efforts by performing arithmetic operations fast
and accurate.

1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

IEEE - The Institute of Electrical and Electronics Engineers, Inc.

SRS - Software Requirements Specification

OS - Operating System
1.4 REFERENCES

(a) IEEE Recommended Practice for Software Requirements Specifica-

tions – IEEE Std 830-1998.
(b) IEEE Standard for Software Test Documentation – IEEE Std. 829-
1998.

2. Overall Description
THE GRAPHICAL USER INTERFACE CALCULATOR ALLOWS AUTHOR-
ISED ADMIN TO MAKE CALCULATIONS. IT CAN BE USED IN VARIOUS
COMPUTERS ACROSS THE GLOBE AND SIMPLIFIES WORKING OF
USER.

2.1. Product Perspective

The proposed system shall be developed using client/server architecture

and be compatible with Microsoft Windows as Well as Macintosh Operating
System.

2.1.1. System Interfaces

GUI using Tkinter library in python.

2.1.2. User Interfaces

The Calculator will have following user-friendly and menu driven interfaces

a) Screen: to display numbers ; buttons with number on them.

2.1.3. Hardware Interfaces

a) Screen resolution of at least 640 x 480 or above.

b) Support for printer (dot matrix, deskjet, laserjet)
2.1.4. Software Interfaces

a) MS-Windows Operating System

b) PLATFORM : PYTHON LANGUAGE

2.1.5. Communication Interfaces

None

2.1.6. Memory Constraints

At least 512 MB RAM and 500 MB space of hard disk will be required to run
the software.

2.1.7. Operations

None

2.1.8. Site Adaptation Requirements

The terminal at client site will have to support the hardware and software
interfaces specified in the section 2.1.3 and 2.1.4 respectively.

2.2. Product Functions

The admin will be able to access all the modules of the system.
No modification can be done according to personal life.

2.3. User Characteristics

·Qualification :Simple Knowledge of performing arithmetic calculations

·Technical Experience: Elementary knowledge of computers

2.4. Constraints

·There will only be screen for displaying score and buttons with numbers
on them.
- To clear the screen backspace is used.
2.5 Assumptions and Dependencies

·The GUI Calculator must be created by system administrator and commu-

nicated to the concerned user confidentially to avoid unauthorised access
to the system.

2.6 Apportioning of Requirements

Not Required

3. External Interface Requirements

3.1 Hardware Interfaces

As stated in Section 2.1.3

3.2 Software Interfaces

As stated in Section 2.1.4

3.3 Communication Interfaces

None

4. Functional Requirements

A. Use Case Description

1 Introduction

This use case documents the steps that must be followed in order to use
the GUI calculator.

2 Actors Administrator
3 Pre-Condition

None.

4 Post Condition

If the use case is successful, the actor is able to perform arithmetic opera-
tions.
If not, the system state remains unchanged.

5 Basic Flow

Starts when actor wishes to use the calculator.

i. The system requests that the actor choose the operation
he/she would like to perform.
ii. The result is thus shown on the screen as output.

Use Case Diagram

5. Non-Functional Requirements

5.1 Performance

The system must be interactive and the delays involved must be less .So in
every action-response of the system, there are no immediate delays. In
case of opening windows forms, of popping error messages and saving the
settings or sessions there must be a delay of less than 2 seconds.

5.2 Reliability

As the system provide the right tools for discussion, problem solving it
must be made sure that the system is reliable in its operations and for se-
curing the sensitive details.

5.3 Software Quality Attributes

5.3.1 Security

The main security concern is for users account hence proper login mecha-
nism should be used to avoid hacking.

5.3.2 Usability

As the system is easy to handle and navigates in the most expected way
with no delays. In that case the system program reacts accordingly and
transverses quickly between its states.