Your SlideShare is downloading. ×
Requirements are Boring, and other Myths (EclipseCon 2013 Lightning talk)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Requirements are Boring, and other Myths (EclipseCon 2013 Lightning talk)

176
views

Published on

Published in: Technology, Art & Photos

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
176
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. MichaelJastram... and I do requirementsmy Blog &Newsletter:formalmind.com/blogImage (Post-it) courtesy of Master isolated images / FreeDigitalPhotos.net
  • 2. Requirements areboringImage courtesy of graur codrin / FreeDigitalPhotos.net
  • 3. Image courtesy of David Castillo / FreeDigitalPhotos.net
  • 4. Do you remember…… and JUnit?ImagecourtesyofMasterisolatedimages/FreeDigitalPhotos.net
  • 5. Understand why requirements matterMeasure whether requirements are realizedTry to Automate as much as possibleImage courtesy of photostock / FreeDigitalPhotos.net
  • 6. Joel Spolsky on requirements (1)Images courtesy of sheelamohan, koratmember and Ambro / FreeDigitalPhotos.netSpeedy, at Hasty BananasSoftware, never writesspecsMr. Rogers, at The Well-Tempered SoftwareCompany, refuses to writecode without specv1.0v2.0Task: Word Processor Migration FeaturePainless Functional Specifications: http://www.joelonsoftware.com/articles/fog0000000036.htmlUnderstand
  • 7. Joel Spolsky on requirements (2)Speedy, at Hasty BananasSoftware, never writesspecsMrs. Rogers, at The Well-Tempered SoftwareCompany, refuses to writecode without specUnderstandWrites Converter1.0 → 2.0Duration: 2 weeksCustomerUnhappyWrites Converter2.0 → 1.0Duration: 2 weeksCustomerSatisfiedResult:MediocreDuration: 4 weeks
  • 8. Joel Spolsky on requirements (3)Speedy, at Hasty BananasSoftware, never writesspecsMrs. Rogers, at The Well-Tempered SoftwareCompany, refuses to writecode without specUnderstandWrites Converter1.0 → 2.0Duration: 2 weeksCustomerUnhappyWrites Converter2.0 → 1.0Duration: 2 weeksCustomerSatisfiedResult:MediocreDuration: 4 weeksWrites Converter1.0 → 2.0CustomercommentsWrites Spec v.1“When opening a file createdwith an older version of theproduct, the file is convertedto the new format”Duration: 20 minutesBosscommentsWrites Spec v.2Duration: 20 minutes
  • 9. Joel Spolsky on requirements (4)Speedy, at Hasty BananasSoftware, never writesspecsMrs. Rogers, at The Well-Tempered SoftwareCompany, refuses to writecode without specUnderstandWrites Converter1.0 → 2.0CustomercommentsWrites Spec v.1“When opening a file createdwith an older version of theproduct, the file is convertedto the new format”Duration: 20 minutesBosscommentsResult:GreatDuration: 3 weeks, 1 hourWrites Spec v.2Duration: 20 minutesWrites Spec v.3Duration: 20 minutesImplemen-tationWrites Converter1.0 → 2.0Duration: 2 weeksCustomerUnhappyWrites Converter2.0 → 1.0Duration: 2 weeksCustomerSatisfiedResult:MediocreDuration: 4 weeks
  • 10. MeasureHow to write good requirements (1)#1 Use the right approach#2 KISSImages courtesy of Master isolated images / FreeDigitalPhotos.net
  • 11. MeasureHow to write good requirements (3)#3 Requirements: WhatSpecification: How#4 Define Scope!Images courtesy of renjith krishnan / FreeDigitalPhotos.net
  • 12. MeasureHow to write good requirements (3)#5 Quantify if you can(If you cant know why)#6 Atomic and IdentifiableImages courtesy of David Castillo Dominici / FreeDigitalPhotos.net
  • 13. complete, clear, realizable,understandable,no contradictions,no redundancy,traceability to sourceMeasureHow to write good requirements (4)Images courtesy of Master isolated images / FreeDigitalPhotos.net
  • 14. AutomateAutomate through ModelingImage courtesy of nokhoog_buchachon / FreeDigitalPhotos.net
  • 15. AutomateDomain PropertiesSpecificationRequirementsWhat?How the world behavesImage courtesy of anankkml, Felixco, Inc and Baitong333 / FreeDigitalPhotos.netHow?realizerealizeAutomate through Modeling (2)realize
  • 16. AutomateDomain PropertiesSpecificationRequirementsWhat?How the world behavesHow?Automate through Modeling (3)realizerealizejustifyjustify
  • 17. AutomateDomain PropertiesSpecificationRequirementsImplementationWhat?How the world behavesHow?realizerealizerefineAutomate through Modeling (4)justifyjustify
  • 18. AutomateAutomate through Modeling (5)What models?- UML- SysML- B / Event-B- VDM- Design by Contract… and many more.Image courtesy of nokhoog_buchachon / FreeDigitalPhotos.net
  • 19. What about …● Requirements vs. Goals vs. Specification?● Use Cases?● Traceability?● Testing?...?
  • 20. Visit my talk:6 June (Thu)14:15 – 14:50Room DiamantThankyou!... and requirements arenot boring!Image (Post-it) courtesy of Master isolated images / FreeDigitalPhotos.net