0% found this document useful (0 votes)
75 views

System Requirement Specification

The document describes a system requirement specification (SRS), which defines what a software system will do, how it will perform, and what functionality it needs to satisfy stakeholders. An SRS contains descriptions of functional requirements, technical requirements, acceptance criteria, assumptions, and constraints. It establishes agreement between customers and developers on expected system behavior and functions. The SRS helps prevent project failure by documenting all necessary requirements upfront.

Uploaded by

Sahil Thakur
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
75 views

System Requirement Specification

The document describes a system requirement specification (SRS), which defines what a software system will do, how it will perform, and what functionality it needs to satisfy stakeholders. An SRS contains descriptions of functional requirements, technical requirements, acceptance criteria, assumptions, and constraints. It establishes agreement between customers and developers on expected system behavior and functions. The SRS helps prevent project failure by documenting all necessary requirements upfront.

Uploaded by

Sahil Thakur
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

System Requirement Specification

System Requirement Specification System


Requirement Specification(SRS) is also known as
System Requirement Document. System
requirements document is a set of documentation
that describes the behaviour and features of a
software or system. It comprises of various
elements that attempt to characterize the
functionality needed by the client to satisfy their
users. In other words, the system requirements
document (SRD) describes the system-level
performance and functional requirements for a
system. These points are needed for a SRS
Document:-
1. Introduction
2. Functional Description
3. Behavioural Description
4. Validation Criteria
5. Bibliography
INTRODUCTION
System Requirements Document or System
Requirements Specification is defined as a
document which defines what the software will do
and how it will be required to perform, and it also
defines the functionality the software needs to
satisfy all stakeholders (users, business)
requirements. System Requirement Document or
system requirement specification contains a
description of the system requirements, functional
requirements, technical requirements, acceptance
criteria, assumptions and constraints.

Functional Description
Functional requirements in an Software
Requirement Specification. indicate what a
software system must do and how it must function;
they are product features that focus on user needs.
An SRS document contains a detailed description
of software requirements and lays the groundwork
for technical teams, investors, managers, and
developers, delineating functional requirements is
a big part of writing it. This segment normally
comprises a hierarchical arrangement of
requirements, with the functional/business
requirements at the uppermost level and the
detailed system requirements are listed as their
child items. When the team agrees that functional
specification agreement is reached, the functional
specification is typically declared "complete" or
"signed off". After this, typically the software
development and testing team write source code
and test cases using the functional specification as
the reference.
While testing is performed, the behaviour of the
program is compared against the expected
behaviour as defined in the functional
specification. These are the function requirements
which will specify the relationship between input
and output of the system. They will verify the
behaviour of the system for invalid inputs and
invalid output. Functional requirements will
suggest the various outputs which are being
produced from the given input.
Behaviour Description
Behavioural requirements characterize what a
system's behaviour is to be. These requirements
are satisfied (or not) by what the system does
when it runs. Behaviour of a system is also depends
on its working or acknowledgement of a system
when it is gives an output. A system also have to be
user friendly and easy to use and understandable.

Validation Criteria

Validation is the process of checking requirements


for development, define the system that the
customer really wants. To check issues related to
requirements, we perform requirements
validation. We usually use requirements validation
to check error at the initial phase of development
as the error may increase excessive rework when
detected later in the development process.
The output of requirements validation is the list of
problems and agreed on actions of detected
problems. The lists of problems indicate the
problem detected during the process of
requirement validation. The list of agreed action
states the corrective action that should be taken to
fix the detected problems.

Bibliography
Software requirements specification establishes
the basis for an agreement between customers
and contractors or suppliers on how the software
product should function (roles may be played by
the marketing and development divisions).
Software requirements specification is a carefully
assessment of requirements before the more
specific system design stages, and its goal is to
reduce later redesign. It should also provide a
realistic basis for estimating product costs, risks,
and schedules.
Used appropriately, software requirements
specifications can help prevent software project
failure. The software requirements specification
document lists sufficient and necessary
requirements for the project development. To
derive the requirements, the developer needs to
have clear and thorough understanding of the
products under development. This is achieved
through detailed and continuous communications
with the project team and customer throughout
the software development process.
Data Flow Diagram

Gas
Admin
Admin Booking Admin
Agency

0 Level DFDs
E-R DIAGRAM
Data Flow Diagram

Customer Detail Booking Status


Report

Gas Agency
Management
System

Getting Stock Details


Current Stock Report
1 Level DFDs

1 Level Data Flow Diagram

You might also like