Вы находитесь на странице: 1из 32

SOFTWARE DEVELOPMENT LIFE CYCLE

SRS

SOFTWARE DEVELOPMENT LIFE CYCLE

REQUIREMENT

A condition or a capability to
which the system must conform

SOFTWARE DEVELOPMENT LIFE CYCLE

Steps in SRS preparation


Requirements elicitation
Requirements management
Requirements analysis and specification

SOFTWARE DEVELOPMENT LIFE CYCLE

Software Requirement
Specification
Requirement analysis is the first step in
software engineering process
Software scope refined into a concrete
specification
Foundation for all future activities

SOFTWARE DEVELOPMENT LIFE CYCLE

Requirements management

Documenting requirements
Documenting changes
Controlling changes in the baseline
Project plans current with requirements
Version control
Tracking status of requirements in
baseline
5

SOFTWARE DEVELOPMENT LIFE CYCLE

Requirements Management
Procedures
Version control of requirements
specification
Change control
Requirements trace ability

SOFTWARE DEVELOPMENT LIFE CYCLE

Role of SRS
Bridge the communication gap between
the client, the user and the developer
Help clients to understand their own needs
The SRS must correctly define all of the
software requirements but no more
The SRS should not describe any design,
verification or project management details
except design constraints
7

SOFTWARE DEVELOPMENT LIFE CYCLE

Characteristics of a good SRS

Complete
Consistent
Correct
Modifiable
Ranked
Testable
Traceable
Unambiguous
Valid
Usable during operation and maintenance phase
8

SOFTWARE DEVELOPMENT LIFE CYCLE

Complete
A complete requirements specification
must precisely define all the real world
situations that will be encountered and the
capability's responses to them

SOFTWARE DEVELOPMENT LIFE CYCLE

Consistent
A consistent specification is one where
there is no conflict between individual
requirement statements that define the
behavior of essential capabilities and
specified behavioral properties and
constraints do not have an adverse impact
on that behavior

10

SOFTWARE DEVELOPMENT LIFE CYCLE

Correct
For a requirements specification to be
correct it must accurately and precisely
identify the individual conditions and
limitations of all situations that the desired
capability will encounter and it must also
define the capability's proper response to
those situations

11

SOFTWARE DEVELOPMENT LIFE CYCLE

Modifiable
In order for requirements specifications be
modifiable related concerns must be
grouped together and unrelated concerns
must be separated

12

SOFTWARE DEVELOPMENT LIFE CYCLE

Ranked
Ranking specification statements
according to stability and/or importance is
established in the requirements
document's organization and structure

13

SOFTWARE DEVELOPMENT LIFE CYCLE

Testable
In order for a requirement specification to
be testable it must be stated in such as
manner that pass/fail or quantitative
assessment criteria can be derived from
the specification itself and/or referenced
information

14

SOFTWARE DEVELOPMENT LIFE CYCLE

Traceable
Each requirement stated within the SRS
document must be uniquely identified to
achieve traceability

15

SOFTWARE DEVELOPMENT LIFE CYCLE

Unambiguous
A statement of a requirement is
unambiguous if it can only be interpreted
one way

16

SOFTWARE DEVELOPMENT LIFE CYCLE

Valid
To validate a requirements specification all
the project participants, managers,
engineers and customer representatives,
must be able to understand, analyze and
accept or approve it

17

SOFTWARE DEVELOPMENT LIFE CYCLE

Software requirements
specification (IEEE 830)
The SRS is a specification for a particular
software product program or set of
programs that does certain things.
The SRS is a means of translating the
ideas in the minds of the client (the input)
into a formal document (the output) pf the
requirements phase
18

SOFTWARE DEVELOPMENT LIFE CYCLE

Major Components of SRS


Functional
Requirements

Performance
Requirements

Software Requirements
Specification document

Design
Constraints

External
Interfaces

19

SOFTWARE DEVELOPMENT LIFE CYCLE

Introduction

Purpose

Scope

Definition, Acronyms and abbreviation

References

Overview

General description

Product perspective

Product functions

User characteristics

General constraints

Assumption and dependencies

20

SOFTWARE DEVELOPMENT LIFE CYCLE

SPECIFIC REQUIREMENTS

Functional requirements

Functional requirements 1

Introduction
Inputs
Processing
Outputs

Functional requirements 2
Functional requirements 3
Functional requirement 4

External Interface requirements

User Interface
Hardware Interface
Software interfaces
Communication interface
21

SOFTWARE DEVELOPMENT LIFE CYCLE

SPECIFIC REQUIREMENTS
Performance requirements
Design constraints

Attributes

Standard compliance
Hardware limitations
Security
Maintainability

.

Other Requirements

Database
Operation
Site adaptation

Appendix
Glossary
22

SOFTWARE DEVELOPMENT LIFE CYCLE

Functional requirements
Introduction
Inputs
Processing
Outputs

23

SOFTWARE DEVELOPMENT LIFE CYCLE

Functional requirement Inputs

Sources of inputs
Quantity
Units of measurement
Timing
Ranges of valid inputs to include accuracy
and tolerances

24

SOFTWARE DEVELOPMENT LIFE CYCLE

Functional requirements Processing


Valid checks on the input data.
Exact sequence of operations to include timing of
events.
Responses to abnormal situations i.e overflow,
communication failure, error handling.
Parameters affected by the operations.
Any methods i.e equations, mathematical algorithms,
logical operations etc used to transform system inputs
into corresponding outputs.
Validity checks on the outputs data.

25

SOFTWARE DEVELOPMENT LIFE CYCLE

Functional Requirements Outputs

Destination of the outputs


Quantity
Units of Measurements
Timing
Range of valid outputs to include accuracy
and tolerances
Error messages
26

SOFTWARE DEVELOPMENT LIFE CYCLE

Performance Requirements
Static Performance Requirements

Number of terminal to be supported


Number of simultaneous users to be supported
Number of files and records to be handled
Sizes to tables and files

Dynamic Performance Requirements


Number of transactions and tasks
Amount of data to be processed within certain time
period for both normal and peak workload conditions
All these requirements should be stated in
measurable terms
27

SOFTWARE DEVELOPMENT LIFE CYCLE

Design Constraints

Standard Compliance
Report Format
Data naming conventions.
Accounting procedures.
Audit tracing

28

SOFTWARE DEVELOPMENT LIFE CYCLE

Hardware Limitations
Hardware configuration characteristic (no
of ports, instruction sets. etc)
Limits on primary and secondary memory.

29

SOFTWARE DEVELOPMENT LIFE CYCLE

Attributes
Availability

Security
Restrictions on use of certain commands.
Control access to data
Provide different kinds of access requirements for different
people.
Require the use of pass words cryptography
Keep specific log or history data sets
Maintainability
Transferability / Conversion (from one environment to another)

30

SOFTWARE DEVELOPMENT LIFE CYCLE

Hardware Interfaces
Logical characteristics of each interface
between software product and the
hardware components of the system.
Devices supported and protocols.

31

SOFTWARE DEVELOPMENT LIFE CYCLE

Software Interfaces
Details of required software products to be
used i.e data management system and
operating systems and other applications.
Purpose of interfacing software.
Define in terms of message content and
format

32

Вам также может понравиться