RADD - Tasks and Elements

Question 1

Specify and Model Requirements

Answer 1

1. Model Requirements
2. Analyze Requirements
3. Represent Requirements and Attributes
4. Implement the Appropriate Levels of Abstraction

Question 2

Verify Requirements

Answer 2

1. Characteristics of Requirements and Designs Quality
   
   • Atomic, Complete, Consistent, Concise, Feasible, Unambiguous, Testable, Prioritized, and Understandable
2. Verification Activities
   
   • Compliance with standards, completeness, missing or inaccurate cross-references, clear terminology
3. Checklists
   
   • For quality control when verifying requirements / designs

Question 3

Validate Requirements

Answer 3

1. Identify Assumptions
   
   • Factors that are believe to be true but not configured, such as benefits a solution may bring
2. Define Measurable Evaluation Criteria
   
   • The criteria for assessing the success of a change after implementation
3. Evaluate Alignment with Solution Scope
   
   • Reconciling requirements to the solution in terms of benefit and taking appropriate action (remove or change scope / design)

Question 4

Define Requirements Architecture

Answer 4

1. Requirements Viewpoints and Views
   
   • A set of conventions that define how requirements will be represented
2. Template Architectures
   
   • Standards or templates applied when presenting business analysis information
3. Completeness
   
   • Structuring requirements through an architecture ensures that requirements sets are complete
4. Relate and Verify Requirements Relationships
   
   • Analyzing requirements against each other to define their relationships
5. Business Analysis Information Architecture
   
   • Describes how all of the business analysis information for a change relates

Question 5

Define Design Options

Answer 5

1. Define Solution Approaches
   
   • Create, Purchase, or Combination of both
2. Identify Improvement Opportunities
   
   • Increase Efficiencies, Improve Access to Information, Identify Additional Capabilities
3. Requirements Allocation
   
   • Allocating requirements to solution components and releases supported by assessing trade-offs between alternatives
4. Describe Design Options
   
   • Business processes, opperational decisions, organizational structures, software applications

Question 6

Analyze Potential Value and Recommend Solution

Answer 6

1. Expected Benefits
   
   • Intended positive value of the solution, such as: Benefits, reduces risk, compliance with policies and regulations, improved user experience
2. Expected Costs
   
   • Potential negative value of the solution, such as: Timeline, effort, and actual costs
3. Determine Value
   
   • Potential value based on the expected benefits and costs considered from stakeholders’ viewpoint
4. Assess Design Options and Recommend Solution
   
   • Based on the potential value the solution is expected to deliver