4.5.2 Flashcards

1
Q

What is the competence of requirements and objects?

A
This competence describes the
‘why’ of the project – which goals
are to be achieved, which
benefits are to be realised, which
objectives are to be reached and
which stakeholders’ requirements
are to be fulfilled. These are
derived from needs, expectations,
requirements and strategic
organisational goals from the
stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is a requirement?

A

A requirement is a clear statement of what is required from the
project.

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

What is functional, non-functional and “not a requirement”?

A
  • What something will do
  • How well it will do it
  • How it will do it
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the measures of requirement and projects?

A
• Projects deliver services / products
(solutions)
• Customers and users want capabilities
and the resultant benefits
• Requirements articulate those capabilities
to enable the correct products (solutions)
to be produced
• Emphasis should be on WHAT is required
rather than on HOW it will be achieved.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the requirement management process?

A

Capture , analyse,justify, documents and baseline then requirements test before handback.

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

What are the ways to capture requirement ?

A
Idea generation
Stakeholder analysis
interviews 
user analysis
product analysis
workshops 
assumptions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the acceptance criteria ?

A

To what quality specification must the deliverable be produced,
and what quality measurements will be applied by those
inspecting the finished deliverable?

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

What are the measures of change and configuration management?

A
• The agreed requirements are
used as a baseline for
change control
• All change requests should
be analysed to see if and how
they affect the requirements
• Requirements themselves
must be subject to formal
change control and
configuration management
• Tools are available and useful
to assist in managing
requirements.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the measures for benefits of requirements management?

A
• Better information on
performance, cost and risk
• Improved requirements and
acceptance criteria
• Reduced costs and risks
• Reduced time into
service/operations
• Increased likelihood
stakeholder will accept the
deliverable
• Satisfied customers!
How well did you know this?
1
Not at all
2
3
4
5
Perfectly