4: RMC - Requirement Mng & Communication Flashcards

1
Q

What does Requirements Management and Communication Knowledge Area ensures?

A

These tasks are performed to ensure that all stakeholders have a shared understanding of the nature of a solution and to ensure that those stakeholders with approval authority are in agreement as to the requirements that the solution shall meet.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

How the requirement change are managed in Chang-driven approaches?

A

Change-driven approaches typically do not use a formal change control process, as requirements are prioritized and selected for implementation at the beginning of each
iteration and no changes to the requirements occur during an iteration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How the conflicts can be resolved during manage solution scope and requirement task?

A

Conflicts may be resolved

  • through formal meetings among affected stakeholders,
  • through research,
  • resolution by a third party,
  • or other methods as appropriate.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What should be the consideration when Presenting Requirements For Review during manage solution scope and requirement task?

A

When presenting requirements for review and approval, there needs to be enough formality to support the methodology and ensure that the stakeholders will review, understand, and approve them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the purpose of Manage Requirements Traceability?

A

Create and maintain relationships between business objectives, requirements, other team deliverables, and solution components to support business analysis or other activities.

The goal of tracing is to ensure that requirements (and ultimately, solution components) are linked back to a business objective.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the common relationships between/among requirements?

A

Common relationships include:

Necessity: This relationship exists when it only makes sense to implement a particular requirement if a related requirement is also implemented. This relationship may be unidirectional or bi-directional.

Effort: This relationship exists when a requirement is easier to implement if a related requirement is also implemented.

Subset: When the requirement is the decomposed outcome of another requirement.

Cover: When the requirement fully includes the other requirement. This is a special case of subset, where the top-level requirement is the sum of the sub-requirements.

Value: When including a requirement affects the desirability of a related requirement (either increasing or decreasing it).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

In what situation the coverage matrix will be used to manage tracing?

A

Coverage Matrix is typically used when there are relatively few requirements or when tracing is limited to high-level requirements (e.g. features or models).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the advantages of Maintain Requirement re-use?

A

Maintenance of requirements can facilitate

  • impact analysis of new, proposed changes to the business,
  • reduce analysis time and effort,
  • assist in maintenance of previously implemented solutions, and
  • support other activities, including training, corporate governance, and standards compliance.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Why requirements maintain for re-use and how long?

A

Requirements may be maintained for re-use as long as they describe information of use to the organization beyond the lifetime of an initiative. Requirements will usually be candidates for maintenance only if the describe the actual current state of an organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

In some cases if the requirement are not approved or implemented, can they be maintain for re-use?

A

In some cases a requirement that was not approved or implemented may be maintained for a possible future initiative.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is attributes of Requirement Structure?

A

A package should contain a consistent, cohesive, and coherent set of requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the difference between Requirement Workshop and Structured Walkthrough in relation to Communicate Requirements?

A

Requirements Workshops (9.23): Requirements may be presented as part of a requirements workshop to familiarize all parties with the existing solution scope and the current requirements.

Structured Walkthrough (9.30): A structured walkthrough often begins with a review of the requirements to be discussed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Which of the following tasks involves securing approval of requirements from those stakeholders who have the appropriate authority?

Select one:

a. Confirm Elicitation Results
b. Manage Solution Scope and Requirements
c. Allocate Requirements
d. Communicate Requirements

A

The correct answer is:
b. Manage Solution Scope and Requirements

Page Number(s)	64
Knowledge Area	Requirements Management & Comm

Correct Answer Feedback
BABOK 4.1.2. This is one of the aspects of managing solution scope and requirements. Approval of requirements may be sought at the end of a project phase or at a number of intermediate points in the business analysis process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When RFI and When RFQ/RFP is used?

A

An RFI is generally used when the issuing organization is open to a number of alternative solutions and is seeking information to evaluate possible options.

An RFQ or RFP is used when the issuing organization understands the nature of the solution options available to it and is seeking vendors who can implement an option. An RFQ generally follows a less formal review and selection process than an RFP.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Which one of the following statements best describes the Define Business Case task that is conducted as part of enterprise business analysis?

Select one:

a. To determine if an organization can justify the cost of providing a proposed solution.
b. To determine if an organization can implement the proposed solution successfully.
c. To identify new capabilities required by the enterprise to meet the business need.
d. To define which new capabilities a project or iteration will deliver.

A

The correct answer is:
a. To determine if an organization can justify the cost of providing a proposed solution.

Page Number(s)	94
Knowledge Area	Enterprise Analysis

Correct Answer Feedback
BABOK 5.5.1 The purpose of this task is to determine if an organization can justify the investment required to deliver a proposed solution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

When should the Risk Assessment be done, according to the BABOK Knowledge Recall Area?

Select one:

a. Enterprise Analysis
b. Business Analysis Planning and Monitoring
c. Stakeholder Analysis
d. Solution Assessment and Validation

A

The correct answer is:
a. Enterprise Analysis

page Number(s)	96
Knowledge Area	Enterprise Analysis

Correct Answer Feedback
BABOK 5.5.4.3. The purpose of the initial risk assessment is to determine if the proposed initiative carries more risk than the organization is willing to bear.

17
Q

What are common requirement relationships are?

A

Common relationships include:

Necessity: This relationship exists when it only makes sense to implement a particular requirement if a related requirement is also implemented. This relationship may be unidirectional or bi-directional.

Effort: This relationship exists when a requirement is easier to implement if a related requirement is also implemented.

Subset: When the requirement is the decomposed outcome of another requirement.

Cover: When the requirement fully includes the other requirement. This is a special case of subset, where the top-level requirement is the sum of the sub-requirements.

Value: When including a requirement affects the desirability of a related requirement (either increasing or decreasing it). This may occur because the related requirement is only necessary if the first requirement is implemented, or because only one of the requirements should be implemented.