The document outlines a requirements analysis and specification process, aiming to understand and organize customer requirements effectively. It covers requirement gathering methods, analysis techniques, and the importance of clear communication among stakeholders. The final software requirements specification (SRS) document is crucial for advancing to the software design phase in the software development life cycle.

1. Requirement Analysis
and Specification
Prepared By
Pratik R Detroja
131060753005

2. Outline
• Introduction
• Requirement Gathering (Elicitation)
• Requirement Analysis
• Key point for Requirement Analysis
• Requirement Specification
• References

3. Introduction
• The goal of the Requirements Analysis and Specification is to
clearly understand customer requirements and to
systematically organize these requirements in a specification
document.
• This is consists of the following two activities:
• Requirements Gathering And Analysis
• Requirements Specification

4. RequirementGathering
• Interview
• Users are interviewed to gather the different functionalities
required by them
• Task analysis
• Users view the software as services provided by it – service as
task
• Form Analysis
• Analyse different data input and output of the system

5. RequirementsAnalysis
• The analyst starts requirements gathering and analysis
• By collecting all information from the customers
• Analyst should clearly understand to obtain good gasp on
problem
• What is the problem?
• Why is it important to solve the problem?
• What are the possible solutions to the problem?
• What exactly are the data input to the system and what exactly
are the data output by the system?
• What are the likely complexities that might arise while solving the
problem?

6. Key point for Requirement Analysis
• Working knowledge of software technology
• Computer programming experience and expertise
• General business knowledge
• Problem solving and problem reduction skills
• Interpersonal relation skills
• Be flexible and adaptable

7. RequirementSpecification
• Need of it
• There may not be clear understanding of what a system is
expected to do and its limitations
• System development process might lose focus over time
• Many people with variety of backgrounds are involved
• Different people might have different interpretations
• No clear communication between stakeholders and the
development team
• Requirements of the system might change
• Main Goal
• It provides feedback to the customer
• It decomposes the problem into component parts
• It serves as an input to the design specification
• It serves as a product validation check

8. Cont…
• Contains all the user requirement in structured though
informal form
• Important parts consist of
• Functional Requirements
• The functional requirements discuss the functionality required by
the users from the system.
• Non-Functional Requirements
• deal with the characteristics of the system which can not be
expressed as functions - such as the maintainability of the system,
portability of the system, usability of the system
• Goals of Implementation
• Documents some general design goals

9. At last…
• A very well mannered SRS (Software Requirement
Specification) document let you move to the next phase of
SDLC which is ‘Software Design’ but only after the proper
Requirement Analysis and Specification.

10. References
• http://myrajendrak.blogspot.in/2011/03/software-
requirement-specificationsrs.html
• http://www.sei.cmu.edu/productlines/frame_report/req_eng.
htm
• http://www.b2ttraining.com/course/requirements-analysis-
techniques/
• Fundamentals of Software Engineering
By Rajib mall

11. Thank You