Requirement Gathering (Finals) Flashcards
- A condition or capability needed by a user to solve a problem or achieve an
objective - A condition or capability that must be met or possessed by a system or system
component to satisfy a contract, standard, specification or other formally imposed
documents
Requirement
is a crucial phase in the software development life cycle
(SDLC) and project management.
Requirements Gathering
It involves collecting, documenting, and managing the requirements that define the
features and functionalities of a system or application.
Requirements Gathering
The success of a project often depends on the accuracy and completeness of the
gathered requirements in software.
Requirements Gathering
This focuses specifically on how data is collected during the requirement gathering
process.
Data Gathering Procedure
Steps in data gathering procedure:
- Planning
- Preparation
- Exection
- Recording
- Analysis
Data Gathering Techniques
Interviews
Wokshops
Prototyping
Survey and Questionnaires
Observation
Use Case Scenarios
Crucial component of Requirement Gathering
Interviews
transform abstract ideas to tangible models
Prototyping
provides a scalable approach at gathering stakeholder insights
Survey and Questionnaires
They define the functions or features that the system must have.
Functional requirements
Classification of Software Requirements
Functional requirements
Non-functional requirements
Domain requirements
They define the quality attributes, performance criteria, and constraints.
Non-functional requirements
These are specific to the domain or industry in which the software operates. They include terminology, rules, and standards relevant to that particular domain.
Domain requirements
Types of Non-functional requirements
Execution qualities
Evolution qualities
Execution qualities
Non-func requirement that consist of thing like security and usability, which are observable at run time.
Evolution qualities
Non-func requirement that consist of things like testability, maintainability, extensibility, and scalability that are embodied in the static structure of the software system.
Common Obstacles in Software
Requirements Gathering
Unclear Objectives
Ambiguous Requirements
Poor Stakeholder Involvement
Changing Requirements
Communication Barriers
Overreliance on Documentation
Lack of User Involvement
- is a concise, informal description of a feature told from the end-user’s
perspective.
*focus on the user and their goals, helping to capture the essence of the
required functionality.
User Stories
play a crucial role in streamlining the process of collecting, documenting, and managing project requirements.
Requirements gathering tools
often include features like task assignment, progress tracking, and discussion forums, enabling teams to collaboratively gather, discuss, and manage requirements in real-time.
Collaboration Tools
- Help organize and store
project documentation. - These tools provide a centralized repository for requirements, ensuring easy access, version control, and collaboration.
Document Management Tools
These are useful for gathering structured data from a large audience, such as feedback, preferences, or specific information required for project requirements.
Survey and Form Builders
- Allow the creation of visual or
interactive prototypes. - These tools are valuable for translating requirements into tangible representations
Prototyping Tools
