Software Requirements Specification

Calculator

pg$.1$

$1.$ Introduction

$1\mathrm{.}1.$ Purpose

$1\mathrm{.}2.$ Intended Audience

$2.$ Overall Description

$2\mathrm{.}1.$ Product Perspective

$2\mathrm{.}2.$ Product Functions

$2\mathrm{.}3.$ Operating Environment

$2\mathrm{.}4.$ Design and Implementation Constraints

$2\mathrm{.}5.$ Assumptions and Dependencies

$3.$ External Interface Requirements

$3\mathrm{.}1.$ User Interfaces

$3\mathrm{.}2.$ Hardware Interfaces

$3\mathrm{.}3.$ Software Interfaces

$3\mathrm{.}4.$ Communication Protocols and Interfaces

$4.$ System Features

$4\mathrm{.}1.$ System Feature $1$

$4\mathrm{.}1\mathrm{.}1.$ Description

$4\mathrm{.}2.$ System Feature $2$

$4\mathrm{.}2\mathrm{.}1.$ Description

$4\mathrm{.}3.$ System Feature $3$

$4\mathrm{.}3\mathrm{.}1.$ Description

$4\mathrm{.}4.$ System Feature $4$

$4\mathrm{.}4\mathrm{.}1.$ Description

$4\mathrm{.}5.$ System Feature $5$

$4\mathrm{.}5\mathrm{.}1.$ Description

$5.$ Non$-$functional Requirements

$5\mathrm{.}1.$ Performance Requirements

$5\mathrm{.}2.$ Safety Requirements

$5\mathrm{.}3.$ Security Requirements

$5\mathrm{.}4.$ Software Quality Attributes

Software Requirements Specification

Calculator

pg$.2$

Introduction

$1\mathrm{.}1.$ Purpose

This document will describe the functionality and constraints of the calculator program

that will be provided to students of the school division

$1\mathrm{.}2.$ Intended Audience

This document is intended for administrators of the school division, teachers, and

parents of the students who will use the program

Overall Description

$2\mathrm{.}1.$ Product Perspective

Elementary students will use this calculation program to test their knowledge of simple

math equations by allowing them to guess the result rather then just giving them the

answer.

$2\mathrm{.}2.$ Product Functions

The calculator will allow user input and $4$ math functions

$2\mathrm{.}3.$ Operating Environment

The application must be able to run on Windows

$2\mathrm{.}4.$ Design and Implementation Constraints

The program is to be used by young children so care in wording must be taken and all

system messages must be reviewed by school division administration

$2\mathrm{.}5.$ Assumptions and Dependencies

Dependency on the $.$Net Framework

Software Requirements Specification

Calculator

pg$.3$

External Interface Requirements

$3\mathrm{.}1.$ User Interfaces

The user interface will have $2$ fields for entering numbers, one for selecting the

operation, one field for entering an expected result, and one button to execute the

calculation test to display if they had the correct answer.

$3\mathrm{.}2.$ Hardware Interfaces

None defined as yet

$3\mathrm{.}3.$ Software Interfaces

None defined as yet

$3\mathrm{.}4.$ Communication Protocols and Interfaces

None defined as yet

System Features

$4\mathrm{.}1.$ Addition

$4\mathrm{.}1\mathrm{.}1.$ This will test the students$$ knowledge of addition facts

$4\mathrm{.}2.$ Subtraction

$4\mathrm{.}2\mathrm{.}1.$ This will test the students$$ knowledge of subtraction facts

$4\mathrm{.}3.$ Multiplication

$4\mathrm{.}3\mathrm{.}1.$ This will test the students$$ knowledge of multiplication facts

$4\mathrm{.}4.$ Division

$4\mathrm{.}4\mathrm{.}1.$ This will test the students$$ knowledge of division facts

Software Requirements Specification

Calculator

pg$.4$

Non$-$functional Requirements

$5\mathrm{.}1.$ Performance Requirements

Results of the calculation test should take less then $1$ second

$5\mathrm{.}2.$ Safety Requirements

There should be no tracking or usage logging of any kind

$5\mathrm{.}3.$ Security Requirements

There should be no requirement to reduce any security level or request security access

from a logged on windows user without administrative access.

$5\mathrm{.}4.$ Software Quality Attributes

Each feature should have automated tests ensuring that valid entry calculates properly

and that invalid entry doesn$$t cause exceptions. Invalid entry should prompt for re$-$entry ANALYSIS $($USER$-$LEVEL$)$ USE CASE

Author:$\_\_\_\_\_\_\_\_\_\_\_$ Date:$\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_$

USE CASE NAME:

ACTOR$($S$)$:

DESCRIPTION:

REFERENCES

TYPICAL COURSE OF EVENTS: Actor Action System Response

Step $1$

Step $2$

Step N: This use case concludes when $............$

ALTERNATE COURSES:

PRE$-$CONDITION:

POST$-$CONDITION:

ASSUMPTIONS: