Importance of Gathering User Requirements
- Project Clarity
- Cost and Time Efficiency
- Improved User Satisfaction
- Risk Reduction
- Basis for Testing
Describes what the system should do and defines the functionality, features, and behavior of the system.
Functional Requirements
Describes how the system should behave or perform, like performance, scalability, security, usability, and reliability.
Non-Functional Requirements
Defines high-level objectives and goals that the software must achieve to support business processes.
Business Requirements
Describes the tasks that users need to accomplish with the system.
User Requirements
Describes the hardware, software, and network configurations necessary for the system to function.
System Requirements
Conducted with stakeholders, end-users, and subject matter experts to gather detailed requirements.
Interviews
Types of Interviews
Structured Interviews and Unstructured Interviews
Used for gathering input from a large number of users. They are especially valuable when you need to collect quantitative data.
Surveys and Questionnaires
Involves a guided discussion with a group of stakeholders or users to gather feedback and opinions on the software requirements.
Focus Group
Analyzing users as they perform their daily tasks provides insights into their workflows, pain points, and needs.
Observation
Involve multiple stakeholders collaborating to identify and define requirements. They are interactive sessions that encourage brainstorming, problem-solving, and consensus-building.
Workshops
Allows users to visualize the proposed system, provide feedback, and refine requirements. This is particularly useful for capturing user interface requirements.
Prototyping
Analyzing existing documentation, such as business process documents, reports, or user manuals.
Document Analysis
Characteristics of Good Requirements
- Clear and Unambiguous
- Measurable and Testable
- Specific and Concise
- Relevant
- Achievable
Common Challenges in Gathering User Requirements
- Incomplete or Vague Requirements
- Changing Requirements
- Communication Barriers
- Conflicting Requirements
- Lack of Stakeholder Involvement
Strategies to Overcome Challenges in Gathering User Requirements
- Engage Stakeholders Early and Continuously
- Use Visual Aids
- Prioritize Requirements
- Facilitate Clear Communication
Requirements Management Tools
- JIRA
- Confluence
- IBM DOORS
- Trello
Wireframing and Prototyping Tools
- Figma
- Balsamiq
- Adobe XD
Survey and Feedback Tools
- Google Forms
- Survey Monkey
A detailed description of a software system that defines its intended functionality, features, and constraints.
Software Requirements Specification (SRS) Document
Purpose of an SRS Document
- Clarifies Requirements
- Serves as a Contract
- Facilitates Communication
- Guides Development and Testing
- Reduces Costs and Risks
Components of a Software Requirements Specification
- Introduction
- Overall Description
- Functional Requirements
- Non-Functional Requirements
- System Architecture
- Interface Requirements
- Data Requirements
- Acceptance Criteria
Best Practices for Writing an SRS Document
- Be Clear and Concise
- Use Consistent Terminology
- Prioritize Requirements
- Use Diagrams and Visuals
- Make It Testable
- Collaborate with Stakeholders
