RADD Multiple-Choice Questions

Hi, Bhuvanesh. When you submit this form, the owner will see your name and email address.

1. Which of the following is NOT a purpose of the Requirement Analysis and Design
Definition knowledge area?

To define and analyze stakeholder requirements

To ensure solutions align with business needs

To implement the solution into production

To specify and model requirements

2. What is the primary objective of verifying requirements?

To determine whether requirements are high quality and usable

To ensure stakeholder agreement on all requirements

To confirm the feasibility of the solution

To create test cases for the development team

3. Which technique is most commonly used for modeling requirements?

 SWOT Analysis

Use Case Diagrams

Stakeholder Analysis

PESTLE Analysis

4. What does "design" refer to in the context of RADD?

The process of gathering business requirements

The conceptualization of a solution that meets business needs

The technical implementation of a system

The documentation of business policies

5. Which of the following is a key characteristic of good requirements?

Ambiguous

Complete

Optional

Assumptive

6. What is the primary purpose of validating requirements?

 To ensure they align with the business need

To ensure all stakeholders approve them

To create a project budget

To finalize a project charter

7. What is the purpose of defining solution options?

To analyze various ways to meet business requirements

To select the cheapest solution available

To approve the project budget

To replace business case analysis

8. Which technique is NOT typically used for analyzing requirements?

Data Flow Diagrams

Prototyping

Benchmarking

Role-playing

9. What is the role of prioritization in requirements analysis?

 To ensure all requirements are implemented at once

To determine the order in which requirements should be addressed

To remove unnecessary requirements from the backlog

To ensure all stakeholders agree on every requirement

10. Which of the following is a technique for defining requirements architecture?

Business Process Model

Focus Group

MoSCoW Prioritization

SWOT Analysis

11. A requirement is considered testable if:

It is clearly documented

It can be measured and verified

It is related to a business goal

It is aligned with stakeholder expectations

12. Which type of model is best for defining user interactions with a system?
 Decision Tree

Use Case Diagram

SWOT Matrix

RACI Matrix

13. What is the key output of requirement verification?

A set of approved requirements

A business case document

A project charter

A test case list

14. What does a requirement traceability matrix help with?

Ensuring each requirement is linked to business objectives

Documenting project financials

Creating a project plan

Managing communication among stakeholders

15. Which of the following best describes a functional requirement?

 The ability of the system to handle 1,000 concurrent users

A rule specifying that users must log in using two-factor authentication

The system shall allow users to reset their passwords

The system should be available 99.9% of the time

16. Non-functional requirements typically address which of the following?

User authentication

Performance and reliability

Business rules

Data validation

17. What does "elicitation" focus on?

Gathering, documenting, and analyzing stakeholder needs

Writing technical design documents

Managing project risks

Approving financial estimates

18. What is an example of a constraint?

 The system must process payments securely

The project budget is limited to $100,000

Users should be able to update their profile

The system should be user-friendly

19. What does MoSCoW prioritization stand for?

Must Have, Should Have, Could Have, Won’t Have

Mandatory, Optional, Standard, Conditional

Measurable, Observable, Specific, Clear, Organized, Worthwhile

Model-Oriented Systematic Compliance Workflow

20. What is a common technique used in stakeholder analysis?

RACI Matrix

SWOT Analysis

Cost-Benefit Analysis

Decision Trees

21. The purpose of defining requirements architecture is to:

 Determine the order of requirement implementation

Describe how requirements interact with each other

Prioritize stakeholder feedback

Validate business processes

22. What is an example of a transition requirement?

The system must support 500 concurrent users

Users should be trained before go-live

The database should store customer information

The website must be mobile-friendly

23. What is the best approach to documenting ambiguous requirements?

Use clear, precise, and measurable language

Use general terms for flexibility

Allow stakeholders to interpret freely

Skip documentation and focus on verbal communication

24. Which diagram is useful for mapping business processes?

 Flowchart

Ishikawa Diagram

SWOT Matrix

Affinity Diagram

25. What is the purpose of requirement validation?

To confirm requirements support business objectives

To collect stakeholder signatures

To finalize project contracts

To estimate project budgets

This content is created by the owner of the form. The data you submit will be sent to the form owner. Microsoft is not responsible
for the privacy or security practices of its customers, including those of this form owner. Never give out your password.
Microsoft Forms | AI-Powered surveys, quizzes and polls Create my own form
Privacy and cookies | Terms of use