Requirements Analysis Flashcards

1
Q

What are the tasks in Requirements Analysis?

A
  1. Prioritize Requirements
  2. Organize Requirements
  3. Specify and Model Requirements
  4. Define Assumptions and Constraints
  5. Verify Requirements
  6. Validate Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the purpose of Prioritize Requirements?

A

Ensure that analysis and implementation efforts focus on the most critical requirements

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

What are the inputs to Prioritize Requirements?

A
  1. Business Case
  2. Business Need
  3. Requirements
  4. Requirements Management Plan
  5. Stakeholder list, roles, and responsibilities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the elements of Prioritize Requirements?

A
  1. Basis for Prioritization - possible criteria: business value, business or technical risk, implementation difficulty, likelihood of success, regulatory or policy compliance, relationship to other requirements, stakeholder agreements, urgency
  2. Challenges - non-negotiable demands, unrealistic trade offs,
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What techniques can be used in Prioritize Requirements?

A
  1. Decision Analysis
  2. Risk Analysis
  3. Moscow Analysis - must, should, could, won’t
  4. Time boxing/Budgeting
  5. Voting needs more input here
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Who are the stakeholders for Prioritize Requirements?

A
  1. Domain SME
  2. Implementation SME
  3. Project Manager
  4. Sponsor
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the output of Prioritize Requirement?

A

Requirements[Prioritized], each requirement should have a priority at the completion of this task

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

What is the purpose of Organize Requirements?

A

Create a set of views of the requirements that are comprehensive, complete, consistent and understood by all stakeholders

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

What are the inputs to Organize Requirements?

A
  1. Organizational Process Assets
  2. Requirements[Stated]
  3. Solution Scope
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are the elements of Organize Requirements?

A
  1. Levels of Abstraction
  2. Model selection needs more work and input
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What techniques can be used in Organize Requirements?

A
  1. Business Rule Analysis
  2. Data Flow Diagrams
  3. Data Modeling
  4. Functional Decomposition
  5. Organization Modeling
  6. Process Modeling
  7. Scenario and Use Cases
  8. Scope Modeling
  9. User Stories
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Who are the stakeholders for Organize Requirements?

A
  1. Domain SME, End User, Implementation SME, Sponsor
  2. Project Manager
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the output of Organize Requirements?

A

Requirements Structure

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

What is the purpose of Specify and Model Requirement?

A

To analyze expressed stakeholder desires and or the current state of the organization using a combinaiton of textual statements, matrices, diagrams, and formal models

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

What are the inputs to Specify and Model Requirement?

A

Requirements[stated]

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

What are the elements of Specify and Model Requirement?

A
  1. Text
  2. Matrix Documentation
  3. Models
  4. Capture Requirements Attributes
  5. Improvement Opportunities
17
Q

What techniques can be used in Specify and Model Requirement?

A

Too many to list

18
Q

Who are the stakeholders for Specify and Model Requirement?

A

Any Stakeholder

19
Q

What is the output of Specify and Model Requirement?

A

Requirements[analyzed]

20
Q

What is the purpose of Define Assumptions and Constraints?

A

Identify factors other than requirements that may affect which solutions are viable

21
Q

What are the inputs to Define Assumptions and Constraints?

A

Stakeholder Concerns

22
Q

What are the elements of Define Assumptions and Constraints?

A
  1. Assumptions
  2. Business Constraints
  3. Technical Constraints
23
Q

What techniques can be used in Define Assumptions and Constraints?

A
  1. Problem Tracking
  2. Risk Analysis
24
Q

Who are the stakeholders for Define Assumptions and Constraints?

A
  1. Implementation SME
  2. Project Manager
  3. All Stakeholders
25
Q

What is the output of Define Assumptions and Constraints?

A

Assumptions and Constraints

26
Q

What is the purpose of Verify Requirements?

A

To ensure that requirements specifications and models meet the necessary quality standard to allow them to be used effectively to guide further work

27
Q

What are the inputs to Verify Requirements?

A

Requirements[Any except stated]

28
Q

What are the elements of Verify Requirements?

A
  1. Characteristics of requirements quality
  2. Verification Activities
29
Q

What techniques can be used in Verify Requirements?

A
  1. Acceptance and Evaluation Criteria Definition
  2. Problem Tracking
  3. Structure Walkthrough
  4. Check lists
30
Q

Who are the stakeholders for Verify Requirements?

A

All Stakeholders

31
Q

What is the output of Verify Requirements?

A

Requirements[Verified]

32
Q

What is the purpose of Validate Requirements?

A

To ensure that all requirements support the delivery of business value, fulfill its goals and objectives, and meet stakeholder needs

33
Q

What are the inputs to Validate Requirements?

A
  1. Business Case
  2. Stakeholder, Solution, or Transition Requirement[verified]
34
Q

What are the elements of Validate Requirements?

A
  1. Identify Assumptions
  2. Define Measurable Evaluation Criteria
  3. Determine Business Value
  4. Determine Dependencies for Benefits Realization
  5. Evaluate Alignment with Business Case and Opportunity cost
35
Q

What techniques can be used in Validate Requirements?

A
  1. Acceptance and Evaluation Criteria Definition
  2. Metrics and Key Performance Indicators
  3. Prototyping
  4. Risk Analysis
  5. Structured Walkthrough
36
Q

Who are the stakeholders for Validate Requirements?

A

All Stakeholders

37
Q

What is the output of Validate Requirements?

A

Requirements[validated]

38
Q

What are the objectives of Organize Requirements?

A
  1. Understand which models are appropriate for the domain
  2. Identify interrelationships and dependencies among requirements, organized requirements must clearly depict the relationships between requirements
39
Q
A