Requirement Gathering (Finals)

Question 1

• 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

Answer 1

Requirement

Question 2

is a crucial phase in the software development life cycle
(SDLC) and project management.

Answer 2

Requirements Gathering

Question 3

It involves collecting, documenting, and managing the requirements that define the
features and functionalities of a system or application.

Answer 3

Requirements Gathering

Question 4

The success of a project often depends on the accuracy and completeness of the
gathered requirements in software.

Answer 4

Requirements Gathering

Question 5

This focuses specifically on how data is collected during the requirement gathering
process.

Answer 5

Data Gathering Procedure

Question 6

Steps in data gathering procedure:

Answer 6

1. Planning
2. Preparation
3. Exection
4. Recording
5. Analysis

Question 7

Data Gathering Techniques

Answer 7

Interviews
Wokshops
Prototyping
Survey and Questionnaires
Observation
Use Case Scenarios

Question 8

Crucial component of Requirement Gathering

Answer 8

Interviews

Question 9

transform abstract ideas to tangible models

Answer 9

Prototyping

Question 10

provides a scalable approach at gathering stakeholder insights

Answer 10

Survey and Questionnaires

Question 10

They define the functions or features that the system must have.

Answer 10

Functional requirements

Question 11

Classification of Software Requirements

Answer 11

Functional requirements
Non-functional requirements
Domain requirements

Question 12

They define the quality attributes, performance criteria, and constraints.

Answer 12

Non-functional requirements

Question 13

These are specific to the domain or industry in which the software operates. They include terminology, rules, and standards relevant to that particular domain.

Answer 13

Domain requirements

Question 14

Types of Non-functional requirements

Answer 14

Execution qualities
Evolution qualities

Question 15

Execution qualities

Answer 15

Non-func requirement that consist of thing like security and usability, which are observable at run time.

Question 16

Evolution qualities

Answer 16

Non-func requirement that consist of things like testability, maintainability, extensibility, and scalability that are embodied in the static structure of the software system.

Question 17

Common Obstacles in Software
Requirements Gathering

Answer 17

Unclear Objectives
Ambiguous Requirements
Poor Stakeholder Involvement
Changing Requirements
Communication Barriers
Overreliance on Documentation
Lack of User Involvement

Question 18

• 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.

Answer 18

User Stories

Question 19

play a crucial role in streamlining the process of collecting, documenting, and managing project requirements.

Answer 19

Requirements gathering tools

Question 20

often include features like task assignment, progress tracking, and discussion forums, enabling teams to collaboratively gather, discuss, and manage requirements in real-time.

Answer 20

Collaboration Tools

Question 21

• Help organize and store
  project documentation.
• These tools provide a centralized repository for requirements, ensuring easy access, version control, and collaboration.

Answer 21

Document Management Tools

Question 22

These are useful for gathering structured data from a large audience, such as feedback, preferences, or specific information required for project requirements.

Answer 22

Survey and Form Builders

Question 23

• Allow the creation of visual or
  interactive prototypes.
• These tools are valuable for translating requirements into tangible representations

Answer 23

Prototyping Tools

Question 24

• help visualize and organize complex
  ideas and relationships.
• these tools can be used to create visual
  representations of interconnected requirements.

Answer 24

Mind Mapping Tools

Question 25

These tools track revisions, allowing teams to review, revert, or merge changes
seamlessly.

Answer 25

Version Control Systems

Question 26

are designed specifically for capturing, tracking, and managing requirements throughout the project lifecycle.

Answer 26

Requirements Management Software

Question 27

• Facilitate collaborative diagramming and
  visual representation of ideas.
• These tools can be used for creating flowcharts, diagrams, or visual models that help communicate complex requirements in a more intuitive and accessible way.

Answer 27

Visual Collaboration Tools