Requirements Elicitation in Software Engineering
18 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

During requirements elicitation, technical staff work with ______ to find out about the application domain.

customers

Requirements elicitation involves ______ such as end-users, managers, engineers, and domain experts.

stakeholders

The process of requirements elicitation is influenced by ______ factors.

organisational and political

During requirements prioritization, ______ and negotiation take place.

<p>requirements</p> Signup and view all the answers

The requirements elicitation process involves ______ with stakeholders to discover their requirements.

<p>interacting</p> Signup and view all the answers

The system requirements may change due to ______ stakeholders emerging and the business environment changing.

<p>new</p> Signup and view all the answers

Requirements classification and organisation involves grouping related requirements and organising them into coherent ______.

<p>clusters</p> Signup and view all the answers

The process of gathering information about the required and existing systems and distilling the user and system requirements from this information is known as ______.

<p>requirements discovery</p> Signup and view all the answers

During interviewing, being open-minded and avoiding pre-conceived ideas about the ______ is crucial.

<p>requirements</p> Signup and view all the answers

______ involves prioritising requirements and resolving requirements conflicts.

<p>Prioritisation and negotiation</p> Signup and view all the answers

Requirements are documented and input into the next round of the spiral during the ______ phase.

<p>requirements specification</p> Signup and view all the answers

Stakeholders are involved in ______ to understand their needs and how they might interact with the system.

<p>interviews</p> Signup and view all the answers

Interviewers need to be open-minded without preconceived ideas of what the system should ______.

<p>do</p> Signup and view all the answers

[Blank] specialists may use language to describe their work that isn’t easy for the requirements engineer to understand.

<p>Application</p> Signup and view all the answers

Ethnography involves a social scientist spending a considerable time ______ and analysing how people actually work.

<p>observing</p> Signup and view all the answers

Requirements that are derived from the way that people actually work rather than the way in which process definitions suggest that they ought to ______.

<p>work</p> Signup and view all the answers

Awareness of what other people are doing leads to changes in the ways in which we ______.

<p>do</p> Signup and view all the answers

You need to prompt the user to talk about the system by suggesting ______ rather than simply asking them what they want.

<p>requirements</p> Signup and view all the answers

Study Notes

Requirements Elicitation Overview

  • Technical staff collaborates with customers to understand application domains, required services, and operational constraints.
  • Involves a diverse group of stakeholders such as end-users, managers, engineers, domain experts, and trade unions.

Stakeholders in Requirements Engineering

  • Stakeholders are individuals or groups that have an interest in the system and its requirements.
  • Effective engagement with stakeholders is crucial for comprehensive requirements gathering.

Stages of the Requirements Elicitation Process

  • Requirements Discovery: Interacting with stakeholders to identify desired system features and performance.
  • Requirements Classification and Organization: Grouping similar requirements into coherent categories for better understanding.
  • Requirements Prioritization and Negotiation: Ranking requirements and addressing conflicts among different stakeholder needs.
  • Requirements Specification: Documenting the gathered requirements as a foundational step for further development.

Challenges in Requirements Elicitation

  • Stakeholders often have unclear or poorly formulated requests for system functionality.
  • Varied terminology from different stakeholders can complicate understanding.
  • Conflicting requirements may arise between different stakeholders.
  • External factors, such as organizational politics, can influence stated requirements.
  • Requirements can evolve throughout the analysis phase due to new stakeholder emergence or changing business environments.

Requirements Discovery Process

  • Involves gathering insights from both existing and desired systems.
  • Requires interactions that include a wide range of stakeholders, from managers to regulators.

Interviewing Techniques

  • Interviews can be formal or informal and are integral to the requirements engineering process.
  • Types of Interviews:
    • Closed Interviews: Use a fixed set of questions to gather information.
    • Open Interviews: Allow for broader exploration of issues with stakeholders.
  • Effective interviewing necessitates openness, active listening, and the ability to encourage discussion through questions or prototypes.

Practical Interviewing Tips

  • A combination of closed and open-ended interviews yields the best results.
  • Interviewers should approach discussions without preconceived notions about system requirements.
  • Suggesting potential requirements can prompt stakeholders to elaborate on their needs.

Limitations of Interviews

  • Domain-specific language may hinder clear communication.
  • Interviews may not effectively uncover domain requirements due to complexity and familiarity bias among stakeholders.

Ethnographic Approach

  • Involves observing and analyzing real-world work contexts over an extended period.
  • Provides insights into social and organizational factors without requiring direct stakeholder explanation.
  • Highlights that actual work practices are often more intricate than simplified models suggest.

Importance of Ethnography in Requirements Gathering

  • Requirements derived from real-world practices rather than idealized process definitions.
  • Observations of social interactions lead to a better understanding of shared activities among users.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Quiz Team

Description

Learn about the process of gathering requirements from stakeholders in software engineering, involving technical staff, end-users, and domain experts. Understand the importance of identifying operational constraints and services required by the system.

More Like This

Software Engineering: Requirements Engineering Lecture
10 questions
Requirements Engineering Chapter 3
38 questions
Use Quizgecko on...
Browser
Browser