These are the slides for my Specification by example presentation. This particular version was given as part of my "I'm telling you for the last time"-series (see http://www.marcusoft.net/2013/11/ImTellingYou.html).

1. Specification by example
What? How? When?
Marcus Hammarberg

15. http://www.youtube.com/aptitudsthlm

16. Bandung

19. Theory of
Constraints

20. Where is our
bottleneck?

22. http://images.nationalgeographic.com/wpf/media-live/photos/000/212/cache/sinkholes-holes-ground-2007-guatemala-sinkhole_21282_600x450.jpg

24. Deliberate
Discovery

26. Gojko Adzic

28. ... it’s no silver
bullet, but it seems
like a good start
Dan North

29. http://manning.com/adzic/
From Specification by Example
Used with permission

30. http://www.wallpaperpimper.com/wallpaper/Military/F_16_Fighting_Falcon/F-16-Fighting-Falcon-20-9XTZMAN20G-1280x1024.jpg

31. http://www.wallpaperpimper.com/wallpaper/Military/F_16_Fighting_Falcon/F-16-Fighting-Falcon-20-9XTZMAN20G-1280x1024.jpg

32. Who sets scope?
http://2.bp.blogspot.com/-mJ8gPBlBRjY/TcYv9xOuWlI/AAAAAAAAKvY/0JniIDxlBjY/s1600/how-to-get-your-boss-off-your-back.jpg

33. How do they know
what they want?

34. How do they know
what they want?

35. Don’t let
the customer
limit
themselves
http://www.realestateradiousa.com/blog/wp-content/uploads/2008/09/straitjacket.jpg

36. Derive scope from
business goals
http://cojent7.files.wordpress.com/2010/04/business-goals1.jpg

37. Build the right thing!

44. §

47. 1. Start with wide end of it on your right and
extending a foot below the narrow end
2. Cross wide end over narrow and turn back
underneath
3. Bring up and turn down to loop
4. Pass wide end around frong from left to right
5. Then, up through loop ...
6. And down through knot in front. Tigthen carefully
and draw up to collar.

49. Go concrete with examples
http://www.flickr.com/photos/bensutherland/3961418687/

50. Scenario 1: Account is in credit!
Given the account is in credit!
And the card is valid!
And the dispenser contains cash!
When the customer requests €50!
Then !
ensure the account is debited €50!
And ensure €40 is dispensed!
And ensure the card is returned

51. Key examples

52. Key examples
http://www.bigideastobigresults.com/wp-content/uploads/2009/09/good_enough.jpg

53. Let’s try that, shall we?

54. Customers who buys three
books gets free shipping

55. Customers who buys three
books gets free shipping
Number of books
Free shipping?

56. Customers who buys three
books gets free shipping
Number of books
1
Free shipping?
-

57. Customers who buys three
books gets free shipping
Number of books
1
2
Free shipping?
-

58. Customers who buys three
books gets free shipping
Number of books
1
2
3
Free shipping?
X

59. Customers who buys three
books gets free shipping
Number of books
1
2
3
4
Free shipping?
X
X

60. To get a loan you need to
be older than 18

61. To get a loan you need to
be older than 18
Age of applicant
Can take loan?

62. To get a loan you need to
be older than 18
Age of applicant
17
Can take loan?
-

63. To get a loan you need to
be older than 18
Age of applicant
17
18
Can take loan?
X

64. To get a loan you need to
be older than 18
Age of applicant
17
18
19
Can take loan?
X
X

65. To get a loan you need to
be older than 18
Age of applicant
17
18
19
null?
Can take loan?
X
X
eeeeh?

68. Text
http://www.flickr.com/photos/toastytreat/4555895229
Who writes this
stuff anyway?

69. Refactor the
specification

71. Examples should be
precise and testable

72. Examples should be
precise and testable
Scripts are not specifications

73. Examples should be
precise and testable
Scripts are not specifications
Specifications should be about business
functionality, not software design

74. Examples should be
precise and testable
Scripts are not specifications
Specifications should be about business
functionality, not software design
Specifications should
be self-explanatory

75. Examples should be
precise and testable
Scripts are not specifications
Specifications should be about business
functionality, not software design
Specifications should
be in domain language
Specifications should
be self-explanatory

77. Shared
understanding

78. Shared
understanding
Testing

79. Shared
understanding
Testing
Documentation

87. Automation
http://jbehave.org/reference/stable/images/jbehave-logo.png
http://lh6.ggpht.com/_X3kaawac_g4/SuoT1Yd67pI/AAAAAAAAArU/
dhE-WLR0VKE/Unbenannt.png?imgmax=800
http://lh5.ggpht.com/_X3kaawac_g4/S0nxyUKaIYI/AAAAAAAAAu0/
CtKaMavsxoM/cucumber.jpg?imgmax=800

88. A Cucumber Scenario
Scenario 1: Account is in credit!
Given the account is in credit!
And the card is valid!
And the dispenser contains cash!
When the customer requests €50!
Then !
ensure the account is debited €50!
And ensure €50 is dispensed!
And ensure the card is returned

94. http://1.bp.blogspot.com/-3yjyeeTpRFI/Tea15VHttaI/AAAAAAAAC3w/YXoTDAv9tx8/s1600/hard_work.png

98. One document to rule them all ...

99. http://www.questpartnership.co.uk/blog/uploaded_images/restructuring-775119.jpg

101. “... features are an executable
map of the current
functionality of the system.”
Andrew Premdas (BDD Google Group)

103. ToC and
Specification by example

104. ToC and
Specification by example
• Better communication

105. ToC and
Specification by example
• Better communication
• Concrete examples

106. ToC and
Specification by example
• Better communication
• Concrete examples
• Frequent validation

107. ToC and
Specification by example
• Better communication
• Concrete examples
• Frequent validation
• Living documentation

108. Learn more

109. Learn more

110. Learn more

111. Learn more

112. Learn more

113. Learn more

115. www.marcusoft.net
@marcusoftnet
marcus.hammarberg@aptitud.se

116. www.marcusoft.net
@marcusoftnet
marcus.hammarberg@aptitud.se

117. Recording of this talk
http://www.youtube.com/
aptitudsthlm