Combining Requirements Engineering and Testing, QA&TEST Bilbao 2013

429 views

Published on

Projects that use agile have small, multidisciplinary teams. When every discipline has its own specialist in the team, the team becomes bigger and bigger leading to more communication, coordination and more need for documentation. Combining programming and testing is not a wise decision but combining requirements engineering and testing is very well possible. It even turns out that a lot of communication, documentation and coordination is not necessary. So a lot of time and effort can be saved. During his presentation Jan Jaap tells why testers are excellent requirements engineers (and vice versa) and what the advantages of combining requirements engineering and testing can be. He also addresses what testers should do to get this combined role. With agile becoming more and more popular this can be a possible future for testers.

The idea of combining requirements engineering and testing started with a vision. By now we have enough practical experience to show that is actually works! During the presentation Jan Jaap shares vision and practical experiences.

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
429
On SlideShare
0
From Embeds
0
Number of Embeds
84
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Combining Requirements Engineering and Testing, QA&TEST Bilbao 2013

  1. 1. Combining requirements engineering and testing The presentation can be downloaded from: http://www.sysqa.com/qatest2013 Password:qatest2013 Jan Jaap Cannegieter – Vice President SYSQA B.V.  jcannegieter@sysqa.nl  @jjcannegieter
  2. 2. Agenda © SYSQA Almere • The outline of the idea • Combining the requirements and testing tasks • Consequences of combining requirements engineering and testing • Consequences for testers 3
  3. 3. Outline of the idea
  4. 4. V-model Production Wish Acceptance test Requirements Functional design System realisation Integration test Program test © SYSQA Almere Technical design System test
  5. 5. Tester and agile Traditional Agile User Developing Testing © SYSQA Almere Requirements engineering
  6. 6. Tester in an agile team User © SYSQA Almere Developing
  7. 7. Tester in an agile team User © SYSQA Almere Developing
  8. 8. Consequences - Effort - Knowledge - Techniques
  9. 9. RE-tester and effort
  10. 10. Effort requirements engineering Requirements management Start project End project © SYSQA Almere Requirements validation Elicitation and documentation requirements Effort
  11. 11. Effort tester Test strategy Start project End project © SYSQA Almere Test design Test Execution Effort
  12. 12. Effort RE-tester Start project End project © SYSQA Almere Effort RE-tester Effort
  13. 13. RE-tester and knowledge
  14. 14. Knowledge (and time) Knowledge Testing Start project End project © SYSQA Almere Requirements engineering 20
  15. 15. Knowledge RE-tester Knowledge Begin project End project © SYSQA Almere Requirements engineering testing 21
  16. 16. RE-tester and test documentation
  17. 17. RE – tester and documentation User requirement • System requirement • System requirement © SYSQA Almere • System requirement 23
  18. 18. RE – tester and documentation User requirement • System requirement • Test case • Test case • Test case • System requirement Test Test Test Test case case case case • System requirement • Test case • Test case © SYSQA Almere • • • • 24
  19. 19. © SYSQA Almere RE - tester and documentation 25
  20. 20. © SYSQA Almere Or mindmaps 26
  21. 21. RE-tester and techniques
  22. 22. Techniques – an overview Requirements eng. Testing • • • • • • • • • • • • • • • • Boundary analysis Dataflow test Control flow test Cause and effect graphing Decision table State-transition test Equivalence class test Test charter: test points © SYSQA Almere Use cases Class diagram Activity diagram Status diagram Entity relation diagram Dataflow diagram Problem frames User stories 28
  23. 23. Techniques – system requirements The system <name> Should Provide <whom?> with the ability to <process> Will When? Condition? <process> Be able to <object> <details about object> On request of the client the system shall show the delivery status of an ordered book © SYSQA Almere Shall 29
  24. 24. Techniques – system requirements On request of the client the system shall show the delivery status of an ordered book © SYSQA Almere Does 30
  25. 25. Techniques – system requirements Does the system show the delivery status of an ordered book on request of the client shall © SYSQA Almere Priority 1 31
  26. 26. Will RE-testing be the future?
  27. 27. © SYSQA Almere Advantages and disadvantages 33
  28. 28. Advantages and disadvantages © SYSQA Almere € 34
  29. 29. Advantages and disadvantages © SYSQA Almere € 35
  30. 30. What does this mean for you?
  31. 31. © SYSQA Almere Can you do it? 37
  32. 32. © SYSQA Almere What does this mean for you? 39
  33. 33. Jan Jaap Cannegieter – Vice President SYSQA B.V.  jcannegieter@sysqa.nl  @jjcannegieter © SYSQA Almere The presentation can be downloaded from: http://www.sysqa.com/qatest2013 Password:qatest2013 40

×