NEW
Font size
WorksheetsRequirements Engineering Quiz Chap 3
Total questions: 30
Worksheet time: 15mins
What is described as a core activity of Requirements Engineering (RE)?
System testing
Elicitation of requirements
Writing code
Project management
Which of the following is NOT listed as a primary source for requirements?
Stakeholders
Marketing trends
Documents
Systems in operation
What is a significant consequence of failing to identify relevant stakeholders?
Programmers have more creative freedom.
Change requests during system operation, leading to additional costs.
The project finishes faster.
Requirements documents become shorter.
According to the rules for collaboration, what is a key duty of a stakeholder?
To write the code for the system.
To create the requirement document.
To prioritize the requirements.
To speak the language of the requirements engineer.
In the Kano Model, which category describes features that customers explicitly request?
Delighters
Satisfiers
Dissatisfiers
Basic
A hotel guest expects their room to be clean. In the Kano Model, this is a:
Delighter
Satisfier
Dissatisfier
Performance need
The main goal of all elicitation techniques is to:
Write the final software documentation.
Support requirements engineers in ascertaining the knowledge and requirements of the stakeholders.
Replace the need for stakeholder interviews.
Finalize the project budget.
Which of the following is an influencing factor when choosing an elicitation technique?
The favorite color of the project manager.
The distinction between conscious and subconscious requirements.
The brand of computers used by the development team.
The age of the stakeholders.
What is a major WEAKNESS of the interview technique?
It is low cost.
It allows for immediate follow-up on new topics.
The result depends heavily on the experience of the moderator.
It reaches a large, distributed audience.
An interview technique that involves asking "What is a typical step-by-step process of your day?" is known as:
The "Dive into" technique
The "Yesterday" technique
The "Summarize" technique
The "Concern" technique
What is a key STRENGTH of using questionnaires?
They are excellent for exploring completely unknown topics.
They can gather a lot of information from a large audience quickly and at a low cost.
They allow for deep, follow-up questioning during the process.
They guarantee high motivation and response rates.
During a brainstorming session, what is a fundamental rule?
Criticism of ideas should be immediate.
Only the most experienced person should speak.
Ideas should be analyzed as they are suggested.
Criticism should be deferred until the end.
The "Brainstorming Paradox" technique primarily helps in:
Generating as many ideas as possible without filter.
Identifying risks by focusing on events that must NOT happen.
Creating detailed requirement specifications.
Solving problems by mimicking nature.
In the "6 Thinking Hats" technique, the Blue Hat is responsible for:
Stating intuitive feelings and emotions.
Focusing on facts and data.
Managing the process and agenda.
Identifying risks and difficulties.
What is a major WEAKNESS of the "6 Thinking Hats" technique?
It is not effective for persuading stakeholders with strong opinions.
It is not suitable for eliciting fine-grained, detailed requirements.
It does not allow for different perspectives.
It requires a very large number of participants.
The creativity technique that maps project problems to analogous situations in nature is called:
Brainstorming Paradox
6 Thinking Hats
Bionics
Perspective-based Reading
"System Archaeology" is a technique used to:
Extract requirements from the documentation or code of a legacy system.
Study ancient computing methods.
Observe users in their natural environment.
Brainstorm ideas for a completely new, innovative system.
A key STRENGTH of "Requirements Reuse" is:
It guarantees that all requirements will be perfectly suited to the new project.
It is the best technique for discovering delighters.
It can significantly reduce elicitation costs by using pre-existing requirements.
It requires no validation or checking.
Observation techniques are particularly helpful when:
Developing brand new processes that have never been used before.
Domain specialists are unable to spend time in interviews.
The project has an unlimited budget.
All stakeholders are located in the same office.
What is a key STRENGTH of field observation?
It is ideal for designing future, non-existent workflows.
It is well-suited for eliciting subconscious "dissatisfiers" that stakeholders take for granted.
It eliminates the need for any other elicitation technique.
It is the fastest technique available.
In the "Apprenticing" technique, the requirements engineer:
Teaches the stakeholder how to code.
Actively learns and performs the stakeholder's procedures.
Only observes the stakeholder from a distance.
Manages the project timeline.
A graphical representation used to show relationships between terms, often supporting brainstorming, is called:
A Gantt Chart
A Pie Chart
Mind Mapping
Use Case Modeling
What is the primary purpose of a workshop in requirements elicitation?
To write the final code for the system.
For the requirements engineer and stakeholders to jointly elaborate system goals and details.
To conduct performance testing.
To approve the project budget.
CRC Cards are used to model:
Project schedules and deadlines.
Class, Responsibility, and Collaboration in a system.
Client satisfaction levels.
The cost and revenue of a project.
A key WEAKNESS of using audio/video recordings is:
They are too cheap to implement.
They capture too much irrelevant data.
Stakeholders may feel supervised and give biased statements.
They cannot capture fast-paced processes.
Use Case Modeling is primarily used to:
Document the internal code structure.
Manage the project budget.
Document the external view of the system and its interactions.
Create the user interface design.
Prototypes are especially useful when:
Stakeholders have a very vague understanding of what is to be developed.
The requirements are completely fixed and cannot change.
The project is in its final testing phase.
The development team has no experience.
Which factor is considered a "Human Influence" on elicitation?
Given budget
System complexity
Domain knowledge of stakeholders
Availability of resources
Which factor is considered an "Organizational Influence" on elicitation?
Communication skills of the team
Cultural differences
Whether it is a new system or an extension
Group dynamics
The Kano Model demonstrates the relationship between:
Project cost and timeline.
Fulfillment of requirements and client satisfaction.
Number of stakeholders and project complexity.
Developer skill and code quality.
