Requirements Analysis and Design Definition

Question 1

RADD Tasks

Answer 1

Specify and model requirements
vErify requirements
vAlidate requirements

define Requirements architecture
define design Options
Analyze potential value and Recommend solution

Question 2

Purpose of Specify and Model Requirements task

Answer 2

to transform elicitation results into requirements and designs by refining them through analysis and synthesis.

Question 3

Inputs to Specify and Model Requirements task

Answer 3

Elicitation Results (any state)

Question 4

Elements of Specify and Model Requirements task

Answer 4

Model Requirements
Analyze Requirements
Represent Requirements and Attributes
Implement the Appropriate Levels of Abstraction

Question 5

Guidelines and Tools for Specify and Model Requirements task

Answer 5

Modelling Notations/Standards
Modelling Tools
Requirements Architecture
Requirements Life Cycle Management Tools
Solution Scope

Question 6

Stakeholders for Specify and Model Requirements task

Answer 6

Any stakeholder

Question 7

Outputs of Specify and Model Requirements task

Answer 7

Requirements (specified and modelled)

Question 8

Purpose of Verify Requirements task

Answer 8

to ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve.

Question 9

Tasks using Requirements (specified and modelled)

Answer 9

Verify Requirements

Validate Requirements

Question 10

Inputs to Verify Requirements task

Answer 10

Requirements (specified and modelled)

Question 11

Elements of Verify Requirements task

Answer 11

Characteristics of Requirements and Designs Quality
Verification Activities
Checklists

Question 12

Guidelines and Tools for Verify Requirements task

Answer 12

Requirements Life Cycle Management Tools

Question 13

Stakeholders of Verify Requirements task

Answer 13

All stakeholders

Question 14

Outputs of Verify Requirements task

Answer 14

Requirements (verified)

Question 15

Purpose of Validate Requirements task

Answer 15

to ensure that all requirements and designs align to the business requirements and support the delivery of needed value.

Question 16

Inputs to Validate Requirements task

Answer 16

Requirements (specified and modelled)

Question 17

Tasks using Requirements (verified) output

Answer 17

Approve Requirements

Question 18

Elements of Validate Requirements task

Answer 18

Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope

Question 19

Guidelines and Tools for Validate Requirements task

Answer 19

Business Objectives
Future State Description
Potential Value
Solution Scope

Question 20

Stakeholders of Validate Requirements task

Answer 20

All stakeholders

Question 21

Outputs of Validate Requirements task

Answer 21

Requirements (validated)

Question 22

Tasks using Requirements (validated) output

Answer 22

Define Design Options

Measure Solution Performance

Question 23

Purpose of Define Requirements Architecture task

Answer 23

is to ensure that the requirements collectively support one another to fully achieve the objectives

Question 24

Inputs to Define Requirements Architecture task

Answer 24

Information Management Approach
Requirements (any state)
Solution Scope

Question 25

Elements of Define Requirements Architecture task

Answer 25

Requirements Viewpoints and Views Template Architectures Completeness Relate and Verify Requirements Relationships Business Analysis Information Architecture

Question 26

Guidelines and Tools for Define Requirements Architecture task

Answer 26

Architecture Management Software Legal/Regulatory Information Methodologies and Frameworks

Question 27

Stakeholders of Define Requirements Architecture task

Answer 27

Domain Subject Matter Expert, Implementation Subject Matter Expert, Project Manager, Sponsor, Tester Any Stakeholder

Question 28

Outputs of Define Requirements Architecture task

Answer 28

Requirements Architecture

Question 29

Tasks using Requirements Architecture output

Answer 29

Prioritize Requirements Assess requirements Changes Specify and Model Requirements Define Design Options

Question 30

Purpose of Define Design Options task

Answer 30

to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state.

Question 31

Inputs to Define Design Options task

Answer 31

Change Strategy Requirements (validated, prioritized) Requirements Architecture

Question 32

Elements of Define Design Options task

Answer 32

Define Solution Approaches Identify Improvement Opportunities Requirements Allocation Describe Design Options

Question 33

Guidelines and Tools for Define Design Options task

Answer 33

Existing Solutions Future State Description Requirements (traced) Solution Scope

Question 34

Stakeholders of Define Design Options task

Answer 34

``` Domain SME Implementation SME Operational Support Project Manager Supplier ```

Question 35

Outputs of Define Design Options task

Answer 35

Design Options

Question 36

Tasks using Design Options output

Answer 36

Define Change Strategy | Analyze Potential Value and Recommend Solution

Question 37

Purpose of Analyze Potential Value and Recommend Solution task

Answer 37

to estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements.

Question 38

Inputs to Analyze Potential Value and Recommend Solution task

Answer 38

Potential Value | Design Options

Question 39

Elements of Analyze Potential Value and Recommend Solution task

Answer 39

Expected Benefits Expected Costs Determine Value Assess Design Options and Recommend Solution

Question 40

Guidelines and Tools for Analyze Potential Value and Recommend Solution task

Answer 40

Business Objectives Future State Description Risk Analysis Results Solution Scope

Question 41

Stakeholders for Analyze Potential Value and Recommend Solution task

Answer 41

``` Customer Domain SME End User Implementation SME Project Manager Regulator Sponsor ```

Question 42

Outputs of Analyze Potential Value and Recommend Solution task

Answer 42

Solution Recommendation

Question 43

Tasks using Solution Recommendation output

Answer 43

Define Change Strategy

Question 44

Model Categories (RAP CD)

Answer 44

``` Rationale Activity Flow People & Roles Capability Data & Information ```

Question 45

Quality Characteristics of Requirements (FACt CUP CUT)

Answer 45

``` Feasible Atomic Complete Consistent Unambiguous Prioritized Concise Understandable Testable ```

Question 46

Verify Requirements Techniques (AIM-R)

Answer 46

Acceptance and Evaluation Criteria Item Tracking Metrics and KPIs Reviews

Question 47

"Representations"

Answer 47

A tangible business deliverable resulting from clarifying either the need (requirements) or the solution (designs).

Question 48

Two types of requirements models

Answer 48

Matrices (mostly text) | Diagrams (graphical with some text)

Question 49

Verification activities to be done

Answer 49

``` Completeness checks Comparison checks Correctness checks Compliance checks Terminology checks Examples to clarify ```

Question 50

Quality criteria used to examine requirements relationships (DUNCC)

Answer 50

``` Defined Unambiguous Necessary Correct Consistent ```

Question 51

Examples of ways to improve current state

Answer 51

Increased efficiencies Increased access to information Additional capabilities

Question 52

Design Option elements (BABOSO)

Answer 52

``` business policies and business rules affected stakeholders business processes operational business decisions software applications organizational structures ```

Question 53

Types of expected costs

Answer 53

``` schedule and effort support purchase and/or implementation resources opportunity ```

Question 54

Considerations when assessing design options | A RODeO

Answer 54

``` Available resources Relationships with proposed vendor Other constraints Dependencies between requirements Other factors ```