Requirements Management Planning

This quiz covers why requirements always change, the concept of enduring vs. volatile requirements, the definition and purpose of requirements management, requirements management planning (identification, change process, traceability policies, tool support), and the three-stage requirements change management process (problem analysis, change analysis and costing, change implementation) — including how agile processes handle requirements changes differently

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 #: 225

Questions #: 13

Time: 10 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Why Requirements Always Change

2 pts

volume_mute

Requirements for large software systems are always changing. Which of the following are the main reasons why? Select all that apply.

The business and technical environment changes after installation — new hardware, legislation, and business priorities emerge

Requirements documents are always poorly written in the first place

The people who pay for the system and the users of the system are rarely the same, leading to organizational and budgetary constraints that may conflict with user needs

Large systems have a diverse user community with many users having different and conflicting requirements

Software engineers always make mistakes when writing requirements

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Enduring vs. Volatile 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

Requirement Type

Enduring Requirements

Volatile Requirements

Description

Associated with supporting activities that reflect how the organization does its work rather than the core work itself; more susceptible to change

Associated with the core, slow-to-change activities of an organization; derived from fundamental work activities

Match each type of requirement to its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Wicked Problems

1 pts

volume_mute

Large software systems are often developed to address 'wicked' problems. In this context, a 'wicked problem' means:

A problem that was deliberately specified incorrectly by stakeholders

A problem that is technically too difficult for current technology

A problem that is ethically unacceptable to solve

A problem that cannot be completely defined, meaning software requirements will always be incomplete

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Requirements Management — Definition

1 pts

volume_mute

Requirements management is the process of:

Eliciting requirements from stakeholders through interviews and observation

Writing the initial requirements specification for a system

Validating that requirements define what the customer wants

Understanding and controlling changes to system requirements

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

When to Start Requirements Management

1 pts

volume_mute

When should the formal requirements management process begin?

Only after the system has been deployed to production users

Only when stakeholders formally request a requirements change

As soon as a draft version of the requirements document is available

After the software has been fully implemented and tested

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Four Requirements Management Planning Decisions

2 pts

volume_mute

During requirements management planning, four key decisions must be made. Which of the following are those four decisions? Select all that apply.

A change management process — a set of activities that assess the impact and cost of changes

Requirements identification — each requirement must be uniquely identified for cross-referencing and traceability

The number of requirements engineers assigned to the project

The visual design and font choices for the requirements document

Tool support — selecting tools to manage the large amounts of requirements information

Traceability policies — defining the relationships between requirements and between requirements and system design

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Tool Support for Requirements Management

2 pts

volume_mute

Requirements management needs automated tool support for which three purposes? Select all that apply.

Traceability management — discovering related requirements and relationships between requirements and design

Acceptance testing — running test cases against the deployed system

Code generation — automatically converting requirements into source code

Requirements storage — maintaining requirements in a secure, managed data store accessible to everyone involved

Change management — simplifying the process of assessing and managing change proposals

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Stages of Change Management

2 pts

volume_mute

Please drag and drop the options to sort them

Sort the three principal stages of a requirements change management process 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

Stage 1: Problem Analysis and Change Specification

1 pts

volume_mute

In the first stage of change management, what happens after the change proposal is analyzed to check its validity?

The change is immediately implemented in the system code

The analysis is fed back to the change requestor, who may respond with a more specific change proposal or decide to withdraw the request

The change is sent directly to the testing team for evaluation

The change is automatically rejected if it affects more than three requirements

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Stage 2: Change Analysis and Costing

2 pts

volume_mute

During Change Analysis and Costing, which of the following are done? Select all that apply.

The effect of the proposed change is assessed using traceability information

A decision is made whether or not to proceed with the requirements change

The cost of making the change is estimated in terms of modifications needed to the requirements document

The cost is estimated in terms of any modifications needed to the system design and implementation

The change is immediately written into the source code

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Avoiding Emergency Bypasses of Change Management

1 pts

volume_mute

True or False: When a new requirement has to be urgently implemented, it is acceptable to change the system first and then retrospectively update the requirements document.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Document Modularity for Changeability

1 pts

volume_mute

To facilitate change management in the requirements document, you should organize the document so that:

Requirements are arranged alphabetically so changes can be found quickly

Individual sections are as modular as possible, minimizing external references, so individual sections can be changed without extensive rewriting or reorganization

Only the most senior stakeholders can modify any section of the document

All requirements are described in a single long unstructured chapter to avoid duplication

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Agile Requirements Change vs. Traditional Change Management

1 pts

volume_mute

How do agile development processes handle requirements changes differently from traditional formal change management?

The user submits a formal change request that goes through all three stages of the change management process

Changes are batched and reviewed only once a year at a formal change board

The user prioritizes the change and, if high priority, it replaces lower-priority features planned for the next iteration — no formal change management process is used

All requirements changes are automatically rejected to maintain system stability

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Why Requirements Always Change

Correct Answer

Explanation

Enduring vs. Volatile Requirements

Requirement Type

Description

Correct Answer

Explanation

Wicked Problems

Correct Answer

Explanation

Requirements Management — Definition

Correct Answer

Explanation

When to Start Requirements Management

Correct Answer

Explanation

Four Requirements Management Planning Decisions

Correct Answer

Explanation

Tool Support for Requirements Management

Correct Answer

Explanation

Three Stages of Change Management

Correct Answer

Explanation

Stage 1: Problem Analysis and Change Specification

Correct Answer

Explanation

Stage 2: Change Analysis and Costing

Correct Answer

Explanation

Avoiding Emergency Bypasses of Change Management

Correct Answer

Explanation

Document Modularity for Changeability

Correct Answer

Explanation

Agile Requirements Change vs. Traditional Change Management

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: