soft wa re requirement analysis and software requirement specification n.
Skip this Video
Loading SlideShow in 5 Seconds..
Soft wa re requirement analysis and software requirement specification PowerPoint Presentation
Download Presentation
Soft wa re requirement analysis and software requirement specification

Loading in 2 Seconds...

play fullscreen
1 / 16

Soft wa re requirement analysis and software requirement specification - PowerPoint PPT Presentation

  • Uploaded on

Soft wa re requirement analysis and software requirement specification. Presented by: Nikita Acharya Rumisha Shakya Sunita Singh Yadav. Requirements Analysis.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

Soft wa re requirement analysis and software requirement specification

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
soft wa re requirement analysis and software requirement specification

Softwarerequirement analysisand software requirement specification

Presented by:

Nikita Acharya


Sunita Singh Yadav

requirements analysis

Requirements Analysis

Requirement analysis is the process of studying and analyzing the customer and the user/stakeholder needs to arrive at a definition of software requirements.

Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders such as beneficiaries or users.


Requirements analysis is critical to the success of a development project.

  • Requirements must be documented, actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design
  • Requirements can be architectural, structural, behavioral, functional, and non-functional.

Requirements analysis is the first stage in the systems engineering process and software development process.

Requirements analysis is the first stage in the system engineering project and software development process

why requirements analysis
Why Requirements Analysis?
  • One of the primary reasons why software projects fail is because requirements of the project were not captured properly. Current software applications often operate over multiple platforms and across many locations around the globe. Often during the project lifecycle the demands keep varying and this can also have an impact in eliciting proper requirements.
  • Requirement analysis covers those tasks to determine the needs of a proposed software solution or product, often involving requirements of various stakeholders associated with the solution. Requirement analysis is a key component in the software development lifecycle and is usually the initial step before the project commences.
common errors in requirements analysis
Common errors in requirements analysis
  • Problem 1: Customers don't (really) know what they want
  • Problem 2: Requirements change during the course of the project
  • Problem 3: Customers have unreasonable timelines
  • Problem 4: Communication gaps exist between customers, engineers and project managers
  • Problem 5: The development team doesn't understand the politics of the customer's organization
what vs how dilemma
What vs. How Dilemma

User Needs


System Requirements


System Design





software requirement specification srs
  • Organization's understanding of a client‘s system requirements and dependencies.
  • Second stage of software requirement
  • Two-way insurance policy
  • Referred to as the "parent" document
  • Should contain functional and non-functional requirements only
  • Doesn’t offer design suggestions
  • Doesn’t offer possible solutions to technology
goals of system requirement specification
Goals of System Requirement Specification
  • Provides feedback to the customer.
  • Decomposes the problem into component parts.
  • Serves as an input to the design specification
  • Serves as a product validation check.
information included in srs
Information included in SRS
  • Interfaces
  • Functional Capabilities
  • Performance Levels
  • Data Structures/Elements
  • Safety
  • Reliability
  • Security/Privacy
  • Quality
  • Constraints and Limitations
ingredients included by srs document
Ingredients included by SRS document
  • A template
  • A method for identifying requirements and linking sources
  • Business operation rules
  • A traceability matrix

What makes an SRS "good?"

  • How do we know when we've written a "quality" specification?

quality specification

  • fully addresses all the customer requirements for a particular product or system
  • many quality attributes of an SRS are subjective, we do need indicators or measures that provide a sense of how strong or weak the language is in an SRS
  • A "strong" SRS is one in which the requirements are tightly, unambiguously, and precisely defined in such a way that leaves no other interpretation or meaning to any individual requirement.
consequence of poor srs
Consequence of poor SRS
  • Failure of the project.
  • Results in the dissatisfaction of the customer.