Scribd
Upload
187 views

Software Requirements Document

The document discusses requirements specification for software systems. It explains that a requirements document defines what is expected from system developers and includes both user and system requirements. While agile methods argue requirements documents are outdated due to frequent changes, they are still useful for large, critical systems developed by multiple teams. The document also outlines best practices for writing requirements, including using consistent templates and avoiding technical jargon. It provides examples of structured and tabular specifications that can reduce ambiguity compared to natural language requirements.

Uploaded by

gim688
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
187 views

Software Requirements Document

The document discusses requirements specification for software systems. It explains that a requirements document defines what is expected from system developers and includes both user and system requirements. While agile methods argue requirements documents are outdated due to frequent changes, they are still useful for large, critical systems developed by multiple teams. The document also outlines best practices for writing requirements, including using consistent templates and avoiding technical jargon. It provides examples of structured and tabular specifications that can reduce ambiguity compared to natural language requirements.

Uploaded by

gim688
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

Software Requirements Document

The software requirements document is the


official statement of what is required of the
system developers.

Should include both a definition of user


requirements and a specification of the
system requirements.

Agile methods and requirements

Many agile methods argue that producing a


requirements document is a waste of time as
requirements change so quickly.

The document is therefore always out of date.

Methods such as XP use incremental requirements


engineering and express requirements as user stories.

This is practical for business systems but problematic for


systems that require a lot of pre-delivery analysis (e.g.
critical systems) or systems developed by several
teams.

User stories

(discussed in chap. 3)

Users of a requirements document

The structure of a requirements document

Chapter

Description

Preface

This should define the expected readership of the document and describe
its version history, including a rationale for the creation of a new version
and a summary of the changes made in each version.

Introduction

This should describe the need for the system. It should briefly describe the
systems functions and explain how it will work with other systems. It
should also describe how the system fits into the overall business or
strategic objectives of the organization commissioning the software.

Glossary

This should define the technical terms used in the document. You should
not make assumptions about the experience or expertise of the reader.

User requirements
definition

Here, you describe the services provided for the user. The nonfunctional
system requirements should also be described in this section. This
description may use natural language, diagrams, or other notations that
are understandable to customers. Product and process standards that
must be followed should be specified.

System architecture

This chapter should present a high-level overview of the anticipated


system architecture, showing the distribution of functions across system
modules. Architectural components that are reused should be highlighted.

The structure of a requirements document

Chapter
System
requirements
specification

Description
This should describe the functional and nonfunctional requirements in more
detail. If necessary, further detail may also be added to the nonfunctional
requirements. Interfaces to other systems may be defined.

System models

This might include graphical system models showing the relationships between
the system components and the system and its environment. Examples of
possible models are object models, data-flow models, or semantic data models.

System evolution

This should describe the fundamental assumptions on which the system is


based, and any anticipated changes due to hardware evolution, changing user
needs, and so on. This section is useful for system designers as it may help them
avoid design decisions that would constrain likely future changes to the system.

Appendices

These should provide detailed, specific information that is related to the


application being developed; for example, hardware and database descriptions.
Hardware requirements define the minimal and optimal configurations for the
system. Database requirements define the logical organization of the data used
by the system and the relationships between data.

Index

Several indexes to the document may be included. As well as a normal


alphabetic index, there may be an index of diagrams, an index of functions, and
so on.

Requirements specification

The process of writing down the user and system


requirements in a requirements document.

User requirements have to be understandable by endusers and customers who do not have a technical
background.

System requirements are more detailed requirements


and may include more technical information.

The requirements may be part of a contract for the


system development

It is therefore important that these are as complete as


possible.

Ways of writing a system


requirements specification

Notation

Description

Natural language

The requirements are written using numbered sentences in natural


language. Each sentence should express one requirement.

Structured
language

natural The requirements are written in natural language on a standard form or


template. Each field provides information about an aspect of the
requirement.

Design description This approach uses a language like a programming language, but with more
languages
abstract features to specify the requirements by defining an operational
model of the system. This approach is now rarely used although it can be
useful for interface specifications.
Graphical notations

Graphical models, supplemented by text annotations, are used to define the


functional requirements for the system; UML use case and sequence
diagrams are commonly used.

Mathematical
specifications

These notations are based on mathematical concepts such as finite-state


machines or sets. Although these unambiguous specifications can reduce
the ambiguity in a requirements document, most customers dont
understand a formal specification. They cannot check that it represents what
they want and are reluctant to accept it as a system contract

Guidelines for writing requirements


in natural language

Invent a standard format and use it for all


requirements.

Use language in a consistent way. Use shall for


mandatory requirements, should for desirable
requirements.

Use text highlighting to identify key parts of the


requirement.

Avoid the use of computer jargon.

Include an explanation of why a requirement is


necessary.

Example requirements for the insulin


pump software system

10

3.2 The system shall measure the blood sugar


and deliver insulin, if required, every 10 minutes.
(Changes in blood sugar are relatively slow so
more frequent measurement is unnecessary; less
frequent measurement could lead to
unnecessarily high sugar levels.)
3.6 The system shall run a self-test routine every
minute with the conditions to be tested and the
associated actions defined in Table 1. (A self-test
routine can discover hardware and software
problems and alert the user to the fact the
normal operation may be impossible.)

Problems with natural language

Lack of clarity

Requirements confusion

Precision is difficult without making the document


difficult to read.
Functional and non-functional requirements tend to
be mixed-up.

Requirements amalgamation

Several different requirements may be expressed


together.

Structured specifications

12

An approach to writing requirements where


the freedom of the requirements writer is
limited and requirements are written in a
standard way.

This works well for some types of


requirements e.g. requirements for embedded
control system but is sometimes too rigid for
writing business system requirements.

Form-based specifications

Definition of the function or entity.

Description of inputs and where they come from.

Description of outputs and where they go to.

Information about the information needed for the


computation and other entities used.

Description of the action to be taken.

Pre and post conditions (if appropriate).

The side effects (if any) of the function.

14

A structured specification of a
requirement for an insulin pump

14

A structured specification of a
requirement for an insulin pump

15

Tabular specification

Used to supplement natural language.

Particularly useful when you have to define a


number of possible alternative courses of
action.

For example, the insulin pump systems


bases its computations on the rate of change
of blood sugar level and the tabular
specification explains how to calculate the
insulin requirement for different scenarios.

17

Tabular specification of
computation for an insulin pump
Condition

Action

Sugar level falling (r2 < r1)

CompDose = 0

Sugar level stable (r2 = r1)

CompDose = 0

Sugar level increasing and rate of increase


decreasing
((r2 r1) < (r1 r0))

CompDose = 0

Sugar level increasing and rate of increase


stable or increasing
((r2 r1) (r1 r0))

CompDose =
round ((r2 r1)/4)
If rounded result = 0 then
CompDose = MinimumDose

17

You might also like