Requirements Engineering: Full Review

This comprehensive review quiz covers all major topics from the chapter: the definition and scope of requirements engineering, user vs. system requirements, functional vs. non-functional requirements and their classification, the software requirements document structure, requirements specification notations, the RE process spiral, elicitation techniques (interviewing, scenarios, use cases, ethnography), requirements validation checks and techniques, and requirements management including change management. Use this quiz to consolidate your understanding of the entire chapter

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 223

Questions #: 21

Time: 20 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Requirements Engineering Definition

1 pts

volume_mute

Which of the following best defines requirements engineering (RE)?

The process of testing a delivered system against user expectations

The process of writing source code based on a system design

The process of designing and building the architecture of a software system

The process of finding out, analyzing, documenting and checking the services and constraints of a system

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

User vs. System Requirements

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Level

User Requirements

System Requirements

Description

Detailed descriptions of the software system's functions, services, and operational constraints; may form part of the development contract

High-level abstract statements in natural language plus diagrams, describing services and constraints for non-technical readers

Match each requirement level to its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Functional vs. Non-Functional Classification

2 pts

volume_mute

options

×The system shall generate a monthly report showing the cost of drugs prescribed by each clinic.

×The system shall be available to all clinics Mon–Fri, 08:30–17:30, with no more than 5 seconds downtime per day.

×Each staff member shall be uniquely identified by an eight-digit employee number.

×The system shall implement patient privacy provisions as set out in HStan-03-2006-priv.

Functional

Non-Functional

Classify each of the following requirements as Functional or Non-Functional.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three NFR Categories

1 pts

volume_mute

The three main categories of non-functional requirements are:

Product, Organizational, External

Functional, Structural, Behavioural

Speed, Reliability, Security

User, System, Domain

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

NFR Metrics

1 pts

volume_mute

Which of the following metrics are used to measure Reliability as a non-functional system property? Select all that apply.

Percentage of target-dependent statements

Mean time to failure

Training time

Number of ROM chips

Rate of failure occurrence

Probability of unavailability

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

SRS Document Purpose

1 pts

volume_mute

True or False: The Software Requirements Specification (SRS) is an official statement of what the system developers should implement, and it should include both user requirements and a detailed specification of the system requirements.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Requirements Document Users

1 pts

volume_mute

Which user of the requirements document uses it primarily to develop validation tests for the system?

System Engineers

System Test Engineers

System Maintenance Engineers

Managers

System Customers

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Requirements Specification Notations

2 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Notation

Natural Language Sentences

Structured Natural Language

Graphical Notations

Mathematical Specifications

Key Characteristic

Unambiguous but often not understood by customers; used mainly in safety- or security-critical systems

Most widely used; expressive, intuitive, and universal but potentially vague and ambiguous

Requirements written on standard forms or templates; maintains expressiveness while imposing uniformity

UML use case and sequence diagrams; most useful for showing state changes or sequences of actions

Match each notation to its key characteristic.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Mandatory vs. Desirable in Natural Language

1 pts

volume_mute

Fill in the blanks:

"In natural language requirements writing, (1) requirements use the keyword 'shall', while (2) requirements use the keyword 'should'."

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

The RE Process Is Iterative

1 pts

volume_mute

True or False: In practice, requirements engineering is a strictly sequential process — each of the four high-level activities (feasibility study, elicitation and analysis, specification, validation) is fully completed before the next one starts.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Feasibility Study Questions

2 pts

volume_mute

A feasibility study must answer three key questions before a project proceeds. Which of the following are those three questions? Select all that apply.

Does the system contribute to the overall objectives of the organization?

Will the system generate a positive return on investment within two years?

How many developers are needed to build the system?

Can the system be integrated with other systems that are used?

Can the system be implemented within schedule and budget using current technology?

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Elicitation and Analysis Cycle

2 pts

volume_mute

Please drag and drop the options to sort them

The requirements elicitation and analysis process has four activities that cycle iteratively. Sort them in the correct order.

Requirements Discovery

Requirements Classification and Organization

Requirements Prioritization and Negotiation

Requirements Specification

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Interview Limitations

2 pts

volume_mute

Interviews are good for gaining an overall understanding of a domain but are NOT effective for eliciting domain knowledge for two specific reasons. Which are those two reasons?

Interviews can only be conducted face-to-face and never remotely

Domain specialists use precise, subtle jargon that requirements engineers may misunderstand

Stakeholders are always unavailable for interviews

Some domain knowledge is so familiar to stakeholders that they assume it is obvious and don't mention it

Interviews are always too expensive for most projects

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Scenarios vs. Use Cases

1 pts

volume_mute

True or False: There is a clear, hard-and-fast distinction between scenarios and use cases — they are fundamentally different techniques that cannot be used interchangeably.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Ethnography — Unique Value

1 pts

volume_mute

What is the unique value of ethnography as a requirements elicitation technique compared to interviews or use cases?

It eliminates the need for any other elicitation technique

It produces formal mathematical models of work processes that can be directly compiled

It is the fastest and cheapest elicitation technique available

It discovers implicit requirements that reflect how people actually work — things so obvious to workers that they would never think to mention them in an interview, including social and cooperative aspects of work

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Five Validation Checks

3 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Check

Validity

Consistency

Completeness

Realism

Verifiability

Description

Requirements should always be written so that tests can demonstrate the delivered system meets them

The requirements document should define all functions and constraints intended by the user

Requirements should not contain contradictory constraints or conflicting descriptions of the same function

Requirements should be technically and economically feasible to implement within budget and schedule

Analysis may identify additional or different functions required beyond what users initially thought was needed

Match each validation check to its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Cost of Requirements Errors

1 pts

volume_mute

True or False: The cost of fixing a requirements error is usually much greater than fixing a design or coding error, because requirements changes ripple into design, implementation, and re-testing.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Validation Techniques

1 pts

volume_mute

Which of the following are the three main requirements validation techniques?

Interviews, Scenarios, Ethnography

Requirements Reviews, Prototyping, Test-Case Generation

Feasibility Study, Specification, Traceability Analysis

Static Analysis, Code Review, Unit Testing

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Requirements Management Definition

1 pts

volume_mute

Requirements management is the process of:

Understanding and controlling changes to system requirements throughout the system's lifetime

Initially writing the requirements specification for a system

Testing requirements for completeness and verifiability

Eliciting requirements from stakeholders through interviews and observation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Change Management Three Stages

2 pts

volume_mute

Please drag and drop the options to sort them

Sort the three stages of requirements change management in the correct order.

Problem Analysis and Change Specification

Change Analysis and Costing

Change Implementation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Key Points — True or False

3 pts

volume_mute

Which of the following are correct key points from the chapter? Select all that apply.

Ethnography is a complete elicitation approach that can replace all other techniques

Requirements validation is important because errors in requirements are expensive to fix once the system is being implemented

Requirements engineering is the process of finding out, analyzing, documenting and checking the services and constraints of a system

Non-functional requirements often apply to the system as a whole and are often more critical than individual functional requirements

Business, organizational, and technical changes inevitably lead to requirements changes — requirements management is needed to control this

Requirements elicitation and analysis is a strictly sequential process with no iteration

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Requirements Engineering Definition

Correct Answer

Explanation

User vs. System Requirements

Level

Description

Correct Answer

Explanation

Functional vs. Non-Functional Classification

Correct Answer

Explanation

Three NFR Categories

Correct Answer

Explanation

NFR Metrics

Correct Answer

Explanation

SRS Document Purpose

Correct Answer

Explanation

Requirements Document Users

Correct Answer

Explanation

Requirements Specification Notations

Notation

Key Characteristic

Correct Answer

Explanation

Mandatory vs. Desirable in Natural Language

Correct Answer

Explanation

The RE Process Is Iterative

Correct Answer

Explanation

Feasibility Study Questions

Correct Answer

Explanation

Elicitation and Analysis Cycle

Correct Answer

Explanation

Interview Limitations

Correct Answer

Explanation

Scenarios vs. Use Cases

Correct Answer

Explanation

Ethnography — Unique Value

Correct Answer

Explanation

Five Validation Checks

Check

Description

Correct Answer

Explanation

Cost of Requirements Errors

Correct Answer

Explanation

Three Validation Techniques

Correct Answer

Explanation

Requirements Management Definition

Correct Answer

Explanation

Change Management Three Stages

Correct Answer

Explanation

Key Points — True or False

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: