Requirement

analysis and
specification
Need of Requirement Analysis
and Specification

• Many software project fails:

We start implementation the software system without

understanding the requirement of user and product.

So we need requirement analysis and specification to

understand the system’s requirement in documented
form.
 Requirements analysis and
specification
• This is a phase of SDLC.
SDLC is a process followed for a
• Requirement analysis and software project, within a
software organization. It consists
requirement specification of a detailed plan describing how
to develop, maintain, replace and
these are two activities. alter or enhance specific
software.

• We use Requirement
analysis and Requirement Requirements gathering

specification technique to Design

understand the
Implementation
requirement and prepare
Testing
the specification
document. Maintenance
Goal of requirement analysis and
specification

Goal :

Fully understand the user requirements,

remove
in-consistencies , anomalies , etc. from
requirements and prepare document.
Activities of Requirement analysis and
specification

Two Activities involved in this phase

1) Requirement gathering and analysis.

2) specification (External design).

 Output of requirement analysis and
specification
SRS= software requirement
specification

WHAT IS SRS?
A documents use to describe the behavior of the software system, functional,
non-functional requirements of the software system.

Users of SRS
 Maintenance team
 Development team
 Client
 Technical writer’s
Contents of SRS
 Category: what kind of your software is (e.g.; Desktop application, web
application etc.

 Purpose: Describe what is the purpose of making this system(as nothing is

without any reason)

 Scope: what is the area is covering ,what is its range, to what limits it will help
you.

 Introduction : Define the existing system and proposed system.

 Advantages: define the advantage of the system(in every perspective)

 Functional requirements .

 Non-functional requirements.
 Functional or non-Functional
requirements

Functional requirement

 In one sentence “what the system should do”.

 This is the list of the actual services which a system
will provide.
 This is the list of the services/functions which a user
wants from the software.
 Features of software which the client demand.
 Non-functional Requirement
Non-Functional
requirement

 How a system should behave while performing the operation.

 These are the constraints on the services which system is

offering (e.g. timing of operation ,way to response in
particular condition.
For example :
 Response time
 Recoverability
 Database get ready after update 2 minutes
 EXAMPLE
BOOKSHOP AUTOMATION SOFTWARE
Functional requirement

Check for availability of book:

Description:
Once the customer
selects this option the system will ask to enter the ISBN no. of
books sold. And the system will take the prices of books from inventory and
generates the bills and updates the stock and generate the sales receipt for the
book.

View request:
Description:
Once the employee selects this option, he would be asked to enter the list of new book name.

.
 Update stock:
Description: Once the employee selects this option, he would be
asked to enter the list of new book name
 Purchase Book:
Description:
Once the customer selects this option the system will ask to enter
the ISBN no. of books sold. And the system will take
the prices of books from inventory and generates the bills and
updates the stock and generate the sales receipt for the book.

 Generate Sales Statistics:

Description: Once the manager selects this option, he will be
informed about exact business done over any period of time. It
also calculates inventory level required for various books
 Non-Functional
requirement

Performance Requirements:

Safety Requirements:

Security Requirements:

Software quality:

Business Rules:
(Customer : The one who purchases books from the bookshop. He must have the very
limited access to the system.
Sales Clerk: The one who enters purchase details in the bookshop. He must have the next
higher level of access to the system after the customer.
Employee: The one who updates the inventory. He must the have next higher level of access
to the system after the clerk.
Manager: The person who views the current demand of different books. He must have the
next higher level of access to the system after the employee.
Book Shop Owner: The owner of the shop. He must have access to the entire system.)
THANKS