1. Define Requirements Approach and Project Scope (5%) Flashcards

1
Q

What is a Requirement?

A
  1. A feature that the business users needs the new system (business or IT) to provide
  2. A documented representation of a condition or capability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Origin of Requirements - Provide the 4 Main Origins

A
  1. Strategic Change
  2. Business Change
  3. New Business, Products, Business Rules and Regulations
  4. Opportunities for Improvement, enhancements etc.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Provide 2 types of business changes

A
  1. Operational Changes
  2. Business Process Changes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Name 5 Common Problems with Requirements Engineering

A
  1. Problems are not well defined
  2. Users Unsure what is needed
  3. Ambiguous Expressions
  4. Contradiction between requirements
  5. Conflict between requirements
  6. Overlapping and duplicate requirements
  7. Unrealistic requirements
  8. Not testable
  9. Solutionising
  10. Missing Requirements
  11. Not Lined to the business objective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

what % of errors found in UAT are due to poor requirements capture?

A

60%

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

How to avoid high costs during requirements capture stage?

A

Ensure that the requirements are correct, well explained, no issues / conflicts or duplicates. This will reduce costs as it will prevent major issues in UAT which will have to be re-worked which could have been avoided at the start of the project.

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

In terms of planning and estimating on a project, how does requirements engineering help with this? Provide 3 reasons

A
  1. Form the basis of project estimates
  2. Clarify Scope
  3. Reveal more about the problem, the people, the processes and the business rules
  4. Rationalise at a task level why the problem needs addressing
  5. Take time to uncover
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Why do Project Managers rely on requirements gathering?

A
  1. It helps to provide with the estimates for the costings of the project
  2. If done correctly, it can avoid re-work. If re-work is needed then the PM’s project will run over budget and will reflect poorly on them.
  3. Project constraints such as budget, resource availability and time are likely to be considered as criteria for shaping the project.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the job of a Business Analyst during the Requirements Gathering stage?

A

It is the business analysts job to help the stakeholders to communicate and clarify their understanding of the requirements as efficiently as possible. The Business Analyst needs time to do this properly.

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