Requirements Document-Software Requirement-Lecture Slides, Slides of Software Project Management

Download Requirements Document-Software Requirement-Lecture Slides and more Slides Software Project Management in PDF only on Docsity!

1

Requirements Document

Lecture # 24

2

Recap

• Writing requirements and different

aspects of writing requirements

4

Requirements Document - 2

• The services and functions which the

system should provide

• The constraints under which the system

must operate

• Overall properties of the system i.e.,

constraints on the system’s emergentproperties

5

Requirements Document - 3

• Definitions of other systems which the

system must integrate with

• Information about the application domain of

the system, e.g., how to carry out particulartypes of computation

• Constraints on the process used to develop

the system

7

Requirements Document - 5

• Typically, requirements documents are

written in natural languages (like, English,Japanese, French, etc.)

• Natural languages, by their nature, are

ambiguous

• Structured languages can be used with the

natural languages to specify requirements

8

Requirements Document - 6

• For software systems, the requirements

document may include a description of thehardware on which the system is to run

• The document should always include an

introductory chapter which provides anoverview of the system and the businessneeds

10

Requirements Document - 8

• Structure of requirements document is

also very important and is developedon the basis of following information– Type of the system– Level of detail included in requirements– Organizational practice– Budget and schedule for RE process

11

Users of Requirements

Documents

• System customers• Managers• System engineers• System test engineers• System maintenance engineers

13

Users of Requirements

Documents - 3

• System engineers
  • Use the requirements to understand what

system is to be developed

• System test engineers
  • Use the requirements to develop

validation tests for the system

14

Users of Requirements

Documents - 4

• System maintenance engineers
  • Use the requirements to help understand

the system and the relationships betweenits parts

16

Six Requirements for RS - 2

• It should record forethought about the

lifecycle of the system

• It should characterize acceptable

responses to undesired events– Heninger (1980)

17

How to Organize an SRS?

• Clients/developers may have there own

way of organizing an SRS

• US Department of Defense• NASA• IEEE/ANSI 830-1993 Standard

19

1. Introduction

1.1 Purpose of the requirements

document

1.2 Scope of the product1.3 Definitions, acronyms, and

abbreviations

1.4 References1.5 Overview of the remainder of the

document

20

2. General Description

Product perspective

Product functions

User characteristics

General constraints

Assumptions and dependencies