Download as PDF, PPTX
![Break the model
[Chris Matts]
examples -> model -> more examples](https://image.slidesharecdn.com/refactoryour-specs2017-170615104645/75/Refactor-your-Specs-2017-Edition-70-2048.jpg)
![Credit
score
OK?
Compute
Credit
Limit
References
Check
Record
Outcome
credit application
[]
Optional step
Systematic](https://image.slidesharecdn.com/refactoryour-specs2017-170615104645/75/Refactor-your-Specs-2017-Edition-98-2048.jpg)
![Compute
Credit
Limit
References
Check
Record
Outcome
Manual step
Systematic
[ ]](https://image.slidesharecdn.com/refactoryour-specs2017-170615104645/75/Refactor-your-Specs-2017-Edition-101-2048.jpg)
![Living documentation
[Gojko Adzic]
Examples
Intent
(Free comments)](https://image.slidesharecdn.com/refactoryour-specs2017-170615104645/75/Refactor-your-Specs-2017-Edition-175-2048.jpg)
![Visible Workings
[Brian Marick]
Custom Doclet
Runtime export
LaTex export...](https://image.slidesharecdn.com/refactoryour-specs2017-170615104645/75/Refactor-your-Specs-2017-Edition-180-2048.jpg)
Uploaded byCyrille Martraire
Refactor your Specs - 2017 Edition
The document discusses the importance of refactoring specifications in software development to enhance clarity and align with business needs. It emphasizes the value of collaboration among team members during specification processes and the transition from traditional documentation to living documentation that evolves with the project. Various patterns in software design are explored to facilitate a better understanding of domain concepts and improve testing and implementation efficiency.
More Related Content
Similar to Refactor your Specs - 2017 Edition
![[DSBW Spring 2009] Unit 04: From Requirements to the UX Model](https://cdn.slidesharecdn.com/ss_thumbnails/unit04-starting-090328141241-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Refactor your Specs - 2017 Edition
- 1.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9. Software Craftsmanship "Raising the bar" "Workingcode is not enough"
- 10. Software Craftsmanship What about the waywe specify?
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. (with BDD) Given afloating rate bond on EURIBOR 3M And a nominal of 15M EUR And an issue date of 2011/06/15 And an end date of 2012/06/14 And an SEMI_ANNUAL calculation period When the EURIBOR 3M evolves: | 2011/09/15 | 3.5% | | 2012/03/15 | 4.0% | Then the cash-flows are: | 2011/12/13 | 23000 | | 2012/06/14 | 25500 |
- 18. DONE double sum =0; for (CashFlow cf : cashflows){ double df = 1 + rate * t; sum += cf.getAmount() / df; } return sum;
- 19.
- 20.
- 21. DONE double sum =0; for (CashFlow cf : cashflows){ double df = pow(1 + rate), t); sum += cf.getAmount() / df; } return sum;
- 23. double sum =0; for (CashFlow cf : cashflows){ double df = pow(1 + rate), t); sum += cf.getAmount() / df; } return sum; double sum = 0; for (CashFlow cf : cashflows){ double df = 1 + rate * t; sum += cf.getAmount() / df; } return sum; Spot the difference
- 24. double sum =0; for (CashFlow cf : cashflows){ double df = pow(1 + rate), t); sum += cf.getAmount() / df; } return sum; double sum = 0; for (CashFlow cf : cashflows){ double df = 1 + rate * t; sum += cf.getAmount() / df; } return sum; Spot the difference
- 25.
- 26.
- 27.
- 28. pow(1 + rate),t) double sum = 0; for (CashFlow cf : cashflows){ double df = sum += cf.getAmount() / df; } return sum; Cases 1 or 2 1 + rate * t *
- 29.
- 30.
- 31.
- 32.
- 33. Oh, I seewhat you mean...
- 34. This is the ‘conventionfor interests calculation’
- 35. Thx, we can growour Ubiquituous Language now!
- 36.
- 37.
- 38.
- 39. We call thatthe ‘coupon’, or just ‘cashflow’
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51. pattern 1 Systematic Combination large varietyfrom a few primitives
- 52.
- 60.
- 61.
- 62. 4+4 -> 4*4 Lesscode Less bugsYou win!
- 63.
- 64.
- 65. Technically: - Strategy pattern appliedseveral times - A (rigid) domain- specific language
- 66.
- 67.
- 68.
- 69.
- 70. Break the model [ChrisMatts] examples -> model -> more examples
- 71. Beware! Don’t go too generic Don’tbe smarter than business peopleMust make business sense (or just a little bit...) Not just for fun
- 72. And now for somemore patterns...
- 73. pattern 2 Contextual Symmetry same purpose,same thing, locally
- 74. 1. Concrete examples 2.visualize 3. Recognize refactoring opportunities
- 75. Plain Text "On eachanniversary date, the bond pays a coupon" "At the end of each period, the swap pays a cashflow"
- 76. Recognize opportunities "On each anniversarydate, the bond pays a coupon "At the end of each period, the swap pays a cashflow" Same scenario!?
- 77.
- 78.
- 79.
- 80. Tip: Focus onone context = ≠ ≠
- 81. Systematic in thiscontext = ≠ ≠ Legal Money Management
- 82. Systematic in thiscontext = ≠ Transport Regulation Cargo Shipping
- 83. Systematic in thiscontext = ≠ Transport Regulation Cargo Shipping DDD Bounded Contexts
- 84.
- 85. One Book. ManyViews. Book To Read Buyable Catalog Shopping Cart Searchable Search Billable Billing Recommendable Recommandation Priceable Pricing Shippable Shipping Capabilities!
- 86. Same capability Same thingin this context ”A book is a shippable like any other” Like any other shippable: • Books • DVDs • Little toys
- 87.
- 88. 88 Stuff you canclimb on
- 89. pattern 3 Degenerate Case Nothing isjust a special case of something
- 90. Tax calculation VAT VAT onnet price Not Applicable Calculation ?
- 91. Introduce Special Case Do-Nothing isa special case of calculation
- 92. Systematic VAT VAT on netprice Not Applicable Calculation
- 93. Technically: - Null Objectpattern (Fowler)
- 94.
- 95. pattern 3 bis Optional Element Systematicthanks to an optional element
- 96. Workflows Credit score OK? Compute Credit Limit References Check Record Outcome UK/US credit application France credit applicationCredit score OK? Compute Credit Limit Record Outcome
- 97.
- 98.
- 99. pattern 3 ter Manualas special case of automatic Systematic thanks to a alternate element
- 100.
- 101.
- 102. Of course youcould end up there by code refactoring…
- 103.
- 104. pattern 5 Principles over rules Systematicat the underlying principle level
- 105.
- 106.
- 107. 3 for $1 (whatif I buy 4, or 5?) $1.99/pound (cost for 4 ounces?) $0.65
- 108. $0.65 1 2 34 $0.65 $1.00 $1.65 + suggest buy 6 $1.30 + suggest buy 3 $1.30 Pricing by quantity decision tree
- 109.
- 110. $0.65 Principle: "What’s best for the customer" Couldbe implemented literally...
- 111. Don’t act asa HUMAN COMPILER
- 112. Technically: - Declarative code (bruteforce): compute each case & select best - Rules engine...
- 113.
- 114.
- 116.
- 117.
- 118. each pattern = opportunity to turnMANY into ONE
- 119. Need to seethe MANY at once
- 120. Feature 1 Feature2 Feature N User Story User Story User Story User Story User Story User Story User Story User Story User Story Ordering work
- 121. Feature 1 Feature2 Feature N User Story User Story User Story User Story User Story User Story User Story User Story User Story Ordering work DEPTH-FIRST -> FINISH :(
- 122. Feature 1 Feature2 Feature N User Story User Story User Story User Story User Story User Story User Story User Story User Story Ordering work INITIAL DESIGN ON 1 SINGLE CASE :(
- 123. Feature 1 Feature2 Feature N User Story User Story User Story User Story User Story User Story User Story User Story User Story Ordering work BREADTH-FIRST -> EXPLORE
- 124. Feature 1 Feature2 Feature N User Story User Story User Story User Story User Story User Story User Story User Story User Story Ordering work BREADTH-FIRST -> EXPLORE User Story?
- 125. Feature 1 Feature2 Feature N User Story User Story User Story User Story User Story User Story User Story User Story User Story Ordering work A LITTLE UPFRONT THINKING ?
- 126. LIKE IN TDD! Drivingthe implementation and its design by ordering the tests strategically
- 127. - e-commerce: kindof product sold (book, dvd, jewelries, vod…) - finance: asset class - insurance: health, life, motor… Frequent axis of opportunities:
- 128.
- 129.
- 130.
- 131.
- 132.
- 133. User Stories As anew visitor I want to register In order to receive spam points: 10 15
- 134. Conversations I want thisbutton more to the left ...
- 135. BDD scenarios Given I’mlogged in When I click the Logoff button Then I’m logged off
- 136.
- 137.
- 138.
- 139. Rules ”Taxes shall not bechanged retroactively”
- 140.
- 141.
- 142. Common situation + more details GivenI’m logged in When I click the Logoff button Then I’m logged off
- 143. Often far fromperfect
- 144.
- 145.
- 146.
- 148. So How to Really improvethis specs thing?
- 149.
- 150. Refactor your specs the wayyou think about
- 151.
- 152. Just tell me whatto do
- 153. No, we needyour skills to simplify and suggest abstractions TDD, refactoring, patterns...
- 154. Just gimme examples, I’ll reverseit all in TDD
- 155. No, we needa true business perspective DDD Ubiquitous Language
- 156. I can only helponce it’s done
- 157. No, you’re evenmore useful along the road, with your skills on challenging everything 3 amigos & specification workshops
- 158.
- 159.
- 160. I need specs toderive test cases
- 161. Why not collaborateduring the workshops? We’ll do the test cases at the same time Specifications by Example
- 162. Why not collaborateduring the workshops? We’ll do the test cases at the same time Specifications by Example scenarios
- 163.
- 164. My job isto solve problems & tell what to do
- 165.
- 166. Your job isto challenge the problem in-depth Feature Injection, Impact Mapping
- 167. If I don’twrite a document I’m useless!
- 168. Relax! The documentis always late to the party
- 169. Real work ishappening informally, while we talk.
- 170. And you alsohave to facilitate and explain the business domain to everyone
- 171.
- 172.
- 173. Specs -> Conversations earlyand frequent between all 3 amigos
- 174. Specs -> conversations earlyand frequent But what about documentation then?
- 175.
- 176.
- 177.
- 178. Living documentation Free comments Formulas,Rules, Principle
- 179.
- 180. Visible Workings [Brian Marick] CustomDoclet Runtime export LaTex export...
- 181. - Annotate domain-relevantclasses - Custom Doclet to export Excel- formatted glossary of every domain concept Source code as reference
- 182. Living Glossary Sent directlyto end customers
- 183.
- 184. Runtime exports sum_{i=0}^{n}frac{ }{} 1+rt (1+r)^{t} (1+r)^{frac{t_1 - t_0}{360}} 1+r.frac{t_1 - t_0}{365}
- 185.
- 186.
- 187. Refactor at thedomain level too
- 188. Exploit opportunities As longas it’s in line with the business domain
- 189. Provoke opportunities Explore earlyenough & order your work strategically!
- 191.
- 192.