Chapter 12: Validating and Managing Requirements (5%) Flashcards

1
Q

steps in formal requirements validation

A

review group (representatives from key stakeholder groups)

collating review comments

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

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

2 stages to Agile requirements validation

A
  • when initiating project:
    outline solution confirmed, backlog established
  • when maintaining backlog:
    work items refined until ‘ready’ for development
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

activities in Agile requirements validation process

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

elements in requirements management [6]

A

requirements identification

cross-referencing

origin + ownership

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

change control

software support

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

3 possibilities for baselining prototypes during Agile software developing

A

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

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

stages of a change control process

A
  • documenting the proposed change
  • analyse proposed change
  • consult stakeholders
  • decide on change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly