Requirements Management and Traceability (15%)

Question 1

What is a pre-requisite to requirements management

Answer 1

Requirements validation (requirements baselined)

Question 2

Why is requirements management helpful?

Answer 2

Business Change
Ownership
Origins
Traceability

Question 3

What are the fundamentals of requirements management?

Answer 3

1. Identification (via unique ID)
2. Cross-referencing (does this change impact other req?)
3. Origin/ownership
4. Software support (to enhance the management)
5. Change control (DACDIR)
6. Configuration management (version control)

Question 4

Once baselined, all changes have to be…

Answer 4

1. governed by change control process
2. subject to approval

Question 5

Change Control Process

Answer 5

DACDIR

Document (any change request needs to be documented)
Analyse (strategy alignment/impact on other req/timeframe/budget etc)
Consult (relevant stakeholders - owner/source of req)
Decide
Implement/Reject

Question 6

Sources of change

Answer 6

Change of key stakeholder(s)
Change in project scope
Changed or new legislation
Altered business priorities
Competitor action
Compatibility with new technology
Users change their minds
Users develop better understanding of need

Question 7

What is vertical traceability ?

Answer 7

Traceability to the business objectives
Objectives (constrain)
Biz req (constrain)
Solution requirements

Question 8

What is horizontal traceability?

Answer 8

Traceability, from origin to delivery and back.
- ‘Backwards from’ (what was the source/who raised this)
- ‘Forwards to’ (what happened to this requirement)