Gathering, Analyzing, and Documenting Software Requirements discusses the requirements engineering process. It involves gathering requirements from stakeholders, analyzing them to understand the problem being solved, and documenting the requirements in a structured format. Effective requirements engineering is essential to develop software that meets stakeholder needs. It ensures the software solves the right problem by aligning with what customers want.

1. Gathering, Analyzing, and
Documenting Software
Requirements
Dikshant Acharya

2. Introduction of Requirements Engineering
Feasibility study : Find out the current needs and budget.
Requirement analysis : What the stack holders require from
the system.
Requirement Definition : Define the requirement in the form
understandable to the customer.
Requirement document : Official statement, include both
definition and specification

3. Requirement Engineering Process
It help software engineer to better understand the
problem.
 Participants involved in required engineering process
 Software engineer : Person who solve the problem.
 Manager : Person who is going to guide everything.
 Customers : Who brings the problem.
 Users : Who views the solution.

4. Understanding requirement
Collecting needs from customer (what customer want)
Managing the process.

5. Task involved in (REP)
 Inception means Beginning
 Identify stakeholders
 Multiple viewpoint
 Initiate communication
Inception is nothing but starting step of your task in REP
Elicitation means Extraction
 Problem of scope
 Problem of understanding
 Problem of volatility (requirement may change over time)

6.  Elaboration means Explanation
• Analyzing phage
It is going to be define about the functional, Informational and behavioral
consent of domain.
 Negotiation means Cooperation between customer and software developer
 Specification means final work product
 Validation means error detected in SRS has to be corrected

7. Requirement Gathering
 What is being done ?
 How is it being done ?
 What is the frequency of the task ?
 What is the volume of decisions or transactions ?
 What are the problem being encountered ?
1. Clients or user may not able to clearly define their problem or
requirement.
2. System developer gather client requirement to understand the
problem that need to be solved.

8. Requirement Analysis
1. Requirement analysis is significant and essential activity after
elicitation.
2. This activity reviews all requirement and may provide graphical
view of the entire system.
3. After the completion of the analysis, the understandability of
the project may improve significantly.

9. Documenting Requirements
1. Use a Structured Format: Utilize a structured format such as a requirements
document template to ensure consistency and clarity in documenting the
requirements.
2. Clearly Define Functional Requirements: Clearly define the specific behavior or
functions the software system must perform.
3. Document Non-Functional Requirements: Include non-functional requirements
such as performance, security, usability, and scalability constraints.

10. Conclusion
Thorough requirements engineering, involving effective gathering,
analysis, and documentation, is essential for aligning software
systems with stakeholder needs and ensuring successful
development.