Requirement Management, Agile RE Lecture 9, DAT230, Requirements - - PowerPoint PPT Presentation

▶
requirement management agile re
SMART_READER_LITE
LIVE PREVIEW

Requirement Management, Agile RE Lecture 9, DAT230, Requirements - - PowerPoint PPT Presentation

Apr 01, 2023 24 likes •577 views

Requirement Management, Agile RE Lecture 9, DAT230, Requirements Engineering Robert Feldt, 2010-09-28 Notes about course Student course evaluators: We need 5 of you! Group assignment: Doodles on home page FAQ will collect

slide-1
SLIDE 1

Requirement Management, Agile RE

Lecture 9, DAT230, Requirements Engineering Robert Feldt, 2010-09-28

slide-2
SLIDE 2
  • Student course evaluators: We need 5 of you!
  • Group assignment:
  • Doodle’s on home page
  • FAQ will collect some common questions on home page
  • Don’t miss deadlines late next week
  • Rubric for PostMortem will be uploaded this week

Notes about course

slide-3
SLIDE 3

Recap from last lecture

slide-4
SLIDE 4
  • Req traceability to follow links to and from reqs
  • to = sources, reasons, versions, releases
  • from = design, implementation, tests, use, refinement
  • Need traceability for: Certification, Testing, Tracking, Changes
  • Links: Satisfies, Dependency, Rationale, Evolves-to
  • Prioritization = which into next release
  • Common techniques: 100 dollar, yes-no, 5-way, cost-value
  • Triage (MDRE)

Recap

slide-5
SLIDE 5

Triage (in MDRE)

slide-6
SLIDE 6

Triage (in MDRE)

New Reqs

slide-7
SLIDE 7

Triage (in MDRE)

Triage

New Reqs

slide-8
SLIDE 8

Triage (in MDRE)

Triage MUST SHOULD NOT

New Reqs

slide-9
SLIDE 9

Triage (in MDRE)

Triage MUST SHOULD NOT Estimate resources

New Reqs

slide-10
SLIDE 10

Triage (in MDRE)

Triage MUST SHOULD NOT Estimate resources

New Reqs

Value, Cost, Risk

slide-11
SLIDE 11

Triage (in MDRE)

Triage MUST SHOULD NOT Estimate resources

New Reqs

Value, Cost, Risk

Prioritize

slide-12
SLIDE 12

Triage (in MDRE)

Triage MUST SHOULD NOT Estimate resources

New Reqs

Value, Cost, Risk

Prioritize Refine

slide-13
SLIDE 13

Triage (in MDRE)

Triage MUST SHOULD NOT Estimate resources

New Reqs

Value, Cost, Risk

Prioritize Refine Select

slide-14
SLIDE 14

Triage (in MDRE)

Triage

Iteratively & Continuously!

MUST SHOULD NOT Estimate resources

New Reqs

Value, Cost, Risk

Prioritize Refine Select

slide-15
SLIDE 15

Change Management

  • Requirements baselining
  • Procedures for new and changed requirements
  • How to propose
  • How to process
  • How to negotiate
  • How to communicate
  • Impact analysis procedures
  • How changes are reflected in project plans & commitments
slide-16
SLIDE 16

Three main reasons for change

  • Changing market demands
  • Developers increased understanding
  • Organizational reasons - strategy change, scope reduction

[Nurmuliani2004]

slide-17
SLIDE 17

Taxonomy of Req Change

  • Type: Add, Delete, Modify
  • Reason: Defect fix, Func. Enhancement, Design

improvement, ...

  • Origin: Defect report, Marketing group, Review, ...

[Nurmuliani2004]

slide-18
SLIDE 18

Requirement Additions

slide-19
SLIDE 19

Requirement Deletions

slide-20
SLIDE 20

Requirement Modifications

slide-21
SLIDE 21

When are the changes?

2.3 2.1 2.0 1.9 1.8 1.4 1.9 1.6

slide-22
SLIDE 22

Preparing for change

  • Accept that changes are inevitable
  • Identify

Volatile Requirements

  • Establish single channel for change requests
  • Manage change hierarchically
slide-23
SLIDE 23

Change Management Process

slide-24
SLIDE 24

Measuring Change Activity

  • Assess stability of requirements
  • Identify improvement opportunities
  • Alerts to project planning
slide-25
SLIDE 25

“Agile” RE in practice

  • [Cao2008]
  • Interviews with 54 personer in 16 companies
  • All used XP or SCRUM, fully or partially
  • Questions:
  • How does “agile” developers work with RE?
  • Which advantages and disadvantages?
slide-26
SLIDE 26

What do they do?

slide-27
SLIDE 27

Agile RE Practices - Pro / Con

Face2Face communication & User stories Iterative req engineering

slide-28
SLIDE 28

Agile RE Practices - Pro / Con

Saves time

Face2Face communication & User stories Iterative req engineering

slide-29
SLIDE 29

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories Iterative req engineering

slide-30
SLIDE 30

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust

Iterative req engineering

slide-31
SLIDE 31

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented

Iterative req engineering

slide-32
SLIDE 32

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented Customer on site

Iterative req engineering

slide-33
SLIDE 33

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented Customer on site

Iterative req engineering

Clearer reqs

slide-34
SLIDE 34

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented Customer on site

Iterative req engineering

Clearer reqs Customer relation

slide-35
SLIDE 35

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented Customer on site

Iterative req engineering

Clearer reqs Customer relation Minimal docs when problems

slide-36
SLIDE 36

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented Customer on site

Iterative req engineering

Clearer reqs Customer relation Minimal docs when problems Cost & schedule estimation

slide-37
SLIDE 37

Agile RE Practices - Pro / Con

Saves time Customer drives

Face2Face communication & User stories

Requires trust Not all user groups represented Customer on site

Iterative req engineering

Clearer reqs Customer relation Minimal docs when problems Cost & schedule estimation Non-functional requirements

slide-38
SLIDE 38

Agile RE Practices - Pro / Con

“Extreme” Prioritization Managing Change through Constant replanning

slide-39
SLIDE 39

Agile RE Practices - Pro / Con

“Extreme” Prioritization Managing Change through Constant replanning

Clearer reasons

slide-40
SLIDE 40

Agile RE Practices - Pro / Con

“Extreme” Prioritization Managing Change through Constant replanning

Clearer reasons Re-prio is easier

slide-41
SLIDE 41

Agile RE Practices - Pro / Con

“Extreme” Prioritization

“Business Value” to narrow

Managing Change through Constant replanning

Clearer reasons Re-prio is easier

slide-42
SLIDE 42

Agile RE Practices - Pro / Con

“Extreme” Prioritization

“Business Value” to narrow

Managing Change through Constant replanning

Clearer reasons Re-prio is easier Instable with re-prio

slide-43
SLIDE 43

Agile RE Practices - Pro / Con

“Extreme” Prioritization

“Business Value” to narrow

Managing Change through Constant replanning

Fewer changes Clearer reasons Re-prio is easier Instable with re-prio

slide-44
SLIDE 44

Agile RE Practices - Pro / Con

“Extreme” Prioritization

“Business Value” to narrow

Managing Change through Constant replanning

Fewer changes Smaller changes Clearer reasons Re-prio is easier Instable with re-prio

slide-45
SLIDE 45

Agile RE Practices - Pro / Con

“Extreme” Prioritization

“Business Value” to narrow

Managing Change through Constant replanning

Fewer changes Smaller changes Architecture suffers Clearer reasons Re-prio is easier Instable with re-prio

slide-46
SLIDE 46

Agile RE Practices - Pro / Con

“Extreme” Prioritization

“Business Value” to narrow

Managing Change through Constant replanning

Fewer changes Smaller changes Architecture suffers “Refactoring” not enough Clearer reasons Re-prio is easier Instable with re-prio

slide-47
SLIDE 47

Agile RE Practices - Pro / Con

Prototypes Test-driven Development Reviews & Acceptance tests

slide-48
SLIDE 48

Agile RE Practices - Pro / Con

Prototypes Test-driven Development

Quicker feedback

Reviews & Acceptance tests

slide-49
SLIDE 49

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Quicker feedback

Reviews & Acceptance tests

slide-50
SLIDE 50

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Tests capture reqs Quicker feedback

Reviews & Acceptance tests

slide-51
SLIDE 51

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Tests capture reqs

Freedom to experiment

Quicker feedback

Reviews & Acceptance tests

slide-52
SLIDE 52

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Tests capture reqs

Freedom to experiment

Requires close customer collab Quicker feedback

Reviews & Acceptance tests

slide-53
SLIDE 53

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Tests capture reqs

Freedom to experiment

Requires close customer collab Developers resist Quicker feedback

Reviews & Acceptance tests

slide-54
SLIDE 54

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Tests capture reqs

Freedom to experiment

Requires close customer collab Developers resist Quicker feedback

Reviews & Acceptance tests

Status report to customers

slide-55
SLIDE 55

Agile RE Practices - Pro / Con

Prototypes

Unrealistic dev speed expectations

Test-driven Development

Tests capture reqs

Freedom to experiment

Requires close customer collab Developers resist Quicker feedback

Reviews & Acceptance tests

Status report to customers Hard to create acc.tests