Jan Jaap Cannegieter – Vice President SYSQA B.V. jcannegieter@sysqa.nl @jjcannegieter

Combining requirements engineering and testing

The presentation can be downloaded from:http://www.sysqa.com/qatest2013Password:qatest2013

© S

YS

QA

Alm

ere

3

Agenda

• The outline of the idea• Combining the requirements and testing tasks• Consequences of combining requirements

engineering and testing• Consequences for testers

Outline of the idea

© S

YS

QA

Alm

ere

Wish

Functional design

Requirements

Technical design

System realisation

Acceptancetest

Systemtest

Integration test

Program test

Production

Testen

V-model

© S

YS

QA

Alm

ere

Tester and agile

Requirements engineering

User

Developing Testing

TraditionalAgile

© S

YS

QA

Alm

ere

Tester in an agile team

User

Developing

© S

YS

QA

Alm

ere

Tester in an agile team

User

Developing

RE-testing

Consequences

- Effort- Knowledge- Techniques

RE-tester and effort

© S

YS

QA

Alm

ere

Effort requirements engineering

Effort

Startproject

Endproject

Elicit

ati

on

an

d

docu

men

tati

on

re

qu

irem

en

ts

Req

uir

em

en

ts

valid

ati

on

Requirements management

© S

YS

QA

Alm

ere

Effort tester

Effort

Start project

End project

Test strategy

Test design

Test

Execu

tion

© S

YS

QA

Alm

ere

Effort RE-tester

Effort

Start project

Endproject

EffortRE-tester

RE-tester and knowledge

© S

YS

QA

Alm

ere

Requirements engineering

Knowledge (and time)

20

Knowledge

Start project

End project

Testing

© S

YS

QA

Alm

ere

Knowledge RE-tester

21

Knowledge

Begin project

End project

Requirements engineering -

testing

RE-tester and test documentation

© S

YS

QA

Alm

ere

RE – tester and documentation

User requirement• System requirement

• System requirement

• System requirement

23

© S

YS

QA

Alm

ere

RE – tester and documentation

User requirement• System requirement

• Test case• Test case• Test case

• System requirement• Test case• Test case• Test case• Test case

• System requirement• Test case• Test case

24

© S

YS

QA

Alm

ere

RE - tester and documentation

25

© S

YS

QA

Alm

ere

Or mindmaps

26

RE-tester and techniques

© S

YS

QA

Alm

ere

Requirements eng.

• Use cases• Class diagram• Activity diagram• Status diagram• Entity relation diagram• Dataflow diagram• Problem frames• User stories

Testing

• Boundary analysis• Dataflow test• Control flow test• Cause and effect graphing• Decision table• State-transition test• Equivalence class test• Test charter: test points

28

Techniques – an overview

© S

YS

QA

Alm

ere

Techniques – system requirements

29

On request of the client the system shall show the delivery status of an ordered book

The system

<name>Should <object>

<details about

object>

Will

Shall

Provide <whom?> with the ability to <process>

Be able to

<process>

When?Condition?

© S

YS

QA

Alm

ere

30

shall

Does

the system show the delivery status of an ordered bookOn request of the client

Techniques – system requirements

© S

YS

QA

Alm

ere

31

Does the system show the delivery status of an ordered book on request of the client

High level te

stcase

shall

Priority 1

Techniques – system requirements

Acceptance criteriu

m

Will RE-testing be the future?

© S

YS

QA

Alm

ere

Advantages and disadvantages

33

© S

YS

QA

Alm

ere

34

€

Advantages and disadvantages

© S

YS

QA

Alm

ere

Advantages and disadvantages

35

€

What does this mean for you?

© S

YS

QA

Alm

ere

Can you do it?

37

© S

YS

QA

Alm

ere

What does this mean for you?

39

© S

YS

QA

Alm

ere

40

Good luck withthe future

Jan Jaap Cannegieter – Vice President SYSQA B.V. jcannegieter@sysqa.nl @jjcannegieter

The presentation can be downloaded from:http://www.sysqa.com/qatest2013Password:qatest2013