Requirement Analysis is a fundamental phase in the Software Development Life Cycle (SDLC) that involves identifying, analyzing, documenting, and validating the needs and expectations of users or stakeholders for a new or modified software system.
Purpose of Requirement Analysis:
-
Understand what the client truly wants
-
Define the scope of the software
-
Identify functional and non-functional requirements
-
Lay a strong foundation for system design and development
-
Avoid misunderstandings and costly rework later
Purpose of Requirement Analysis:
-
Understand what the client truly wants
-
Define the scope of the software
-
Identify functional and non-functional requirements
-
Lay a strong foundation for system design and development
-
Avoid misunderstandings and costly rework later
-
Functional Requirements:
-
Describe what the system should do.
-
Examples:
-
User login
-
Data entry
-
Report generation
-
-
-
Non-Functional Requirements:
-
Define how the system should perform.
-
Examples:
-
Performance
-
Security
-
Usability
-
Reliability
-
-
-
Domain Requirements:
-
Specific to the industry or domain (e.g., banking, healthcare)
-
Might include regulations, standards, or constraints
Process of Requirement Analysis:
-
Requirement Elicitation (Gathering):
-
Techniques: Interviews, questionnaires, observations, brainstorming
-
Stakeholders: Clients, users, business analysts, developers
-
-
Requirement Analysis and Negotiation:
-
Clarify and resolve conflicts in requirements
-
Prioritize features
-
-
Requirement Specification:
-
Create documents such as Software Requirements Specification (SRS)
-
Should be clear, complete, consistent, and testable
-
-
Requirement Validation:
-
Ensure requirements meet the stakeholder’s needs
-
Techniques: Reviews, walkthroughs, prototyping
-
-
Requirement Management:
-
Handle changes in requirements throughout the project
-
