Scribd
Upload
20 views11 pages

1-Develop SRS Documents and Align Them With SDLC From The Requirement Phase To Maintenance Phase-23-07-2024

Uploaded by

krishna teja
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
20 views11 pages

1-Develop SRS Documents and Align Them With SDLC From The Requirement Phase To Maintenance Phase-23-07-2024

Uploaded by

krishna teja
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

SOFTWARE REQUIREMENTS

SPECIFICATION (SRS)
Software Requirements Specification
Software Requirement Specification (SRS) Format as the name suggests, is a
complete specification and description of requirements of the software that need to be
fulfilled for the successful development of the software system.

These requirements can be functional as well as non-functional depending upon the


type of requirement.

The interaction between different customers and contractors is done because it is


necessary to fully understand the needs of customers.

Depending upon information gathered after interaction, SRS is developed which


describes requirements of software that may include changes and modifications that is
needed to be done to increase quality of product and to satisfy customer demand.
Parts of SRS
The important parts of the Software Requirements Specification (SRS)
document are:
1. Functional requirements of the system
2. Non-functional requirements of the system, and
3. Goals of implementation
Functional Requirements
In this, possible outcome of software system which includes effects due to
operation of program is fully explained.
All functional requirements which may include calculations, data processing, etc.
are placed in a ranked order.
Functional requirements specify the expected behavior of the system-which
outputs should be produced from the given inputs.
They describe the relationship between the input and output of the system.
For each functional requirement, detailed description all the data inputs and their
source, the units of measure, and the range of valid inputs must be specified.
Interface Requirements
In this, software interfaces which mean how software program communicates
with each other or users either in form of any language, code, or message are
fully described and explained.

Examples can be shared memory, data streams, etc.


Performance Requirements
In this, how a software system performs desired functions under specific condition is
explained.
It also explains required time, required memory, maximum error rate, etc. T
he performance requirements part of an SRS specifies the performance constraints on the
software system.
All the requirements relating to the performance characteristics of the system must be
clearly specified.
There are two types of performance requirements: static and dynamic.
Static requirements are those that do not impose constraint on the execution
characteristics of the system.
Dynamic requirements specify constraints on the execution behaviour of the system.
Design Constraints
In this, constraints which simply means limitation or restriction are specified and
explained for design team.

Examples may include use of a particular algorithm, hardware and software limitations,
etc.

There are a number of factors in the client’s environment that may restrict the choices
of a designer leading to design constraints such factors include standards that must be
followed resource limits, operating environment, reliability and security requirements
and policies that may have an impact on the design of the system.

An SRS should identify and specify all such constraints.


Non-Functional Requirements
In this, non-functional attributes are explained that are required by software system for
better performance.

An example may include Security, Portability, Reliability, Reusability, Application


compatibility, Data integrity, Scalability capacity, etc.
Preliminary Schedule and Budget
In this, initial version and budget of project plan are explained which include
overall time duration required and overall cost required for development of project.
Appendices
In this, additional information like references from where information is
gathered, definitions of some specific terms, acronyms, abbreviations, etc.
are given and explained.
Uses of SRS
● Development team require it for developing product according to the need.
● Test plans are generated by testing group based on the describe external behaviour.
● Maintenance and support staff need it to understand what the software product is supposed
to do.
● Project manager base their plans and estimates of schedule, effort and resources on it.
● Customer rely on it to know that product they can expect.
● As a contract between developer and customer.
● For documentation purpose.

You might also like