Chapter 12: Validating and Managing Requirements (5%)

Question 1

steps in formal requirements validation

Answer 1

review group (representatives from key stakeholder groups)

collating review comments

review outcomes (3 possible outcomes:
- needs significant rework
- needs amendment
- confirmed as satisfactory)

Question 2

2 stages to Agile requirements validation

Answer 2

• when initiating project:
  outline solution confirmed, backlog established
• when maintaining backlog:
  work items refined until ‘ready’ for development

Question 3

activities in Agile requirements validation process

Answer 3

• ensure individual requirements align with models developed to represent a solution
• produce initial prototypes
• develop use case or user stories
• build models to represent workflow/ specific task (e.g. swimlane, activity diagram)
• define acceptance criteria

Question 4

elements in requirements management [6]

Answer 4

requirements identification

cross-referencing

origin + ownership

configuration management (2 key areas: config identification + config control)

change control

software support

Question 4

3 possibilities for baselining prototypes during Agile software developing

Answer 4

baselining:
- every prototype before demo
- daily
- at end of timebox

Question 5

stages of a change control process

Answer 5

• documenting the proposed change
• analyse proposed change
• consult stakeholders
• decide on change