Use-Case is Everything
Download as PPTX, PDF1 like2,227 views
The document emphasizes the critical role of gathering comprehensive use-cases in software development, highlighting historical examples like Alan Turing's work on breaking the Enigma code. It argues that understanding and prioritizing requirements can prevent failures in meeting project goals. The key takeaway is to gather and analyze use-cases thoroughly before proceeding with design and implementation.
Use-Case is Everything
- 1. Use-Case is EVERYTHING! Software Engineering 1Use-Case is Everything!
- 2. Disclaimer The purpose of this slide deck is to highlight the importance of a good requirements gathering process in software development. (~,~) Breaking the ENIGMA code was an amazing feat of reverse-engineering. The events described below are not meant to belittle the task in any way. 2Use-Case is Everything!
- 3. Remember Alan Turing? The guy who developed the system used to defeat the Nazi ENIGMA encryption. 3Use-Case is Everything!
- 4. Remember Alan Turing? • …actually, this is Alan Turing. • Pioneering… – computer scientist – Mathematician – Logician – Cryptanalyst – Philosopher – mathematical biologist – marathon runner Why enigma?... …because no one else is doing anything about it and I can have it to myself… 4Use-Case is Everything!
- 5. The Engineering Team 5 Project Manager Lead Executive Manager Software Engineers Use-Case is Everything! Guys! Requirement = Break ENIGMA!
- 6. The Engineering Team 6Use-Case is Everything! • Used £100,000 ($6Million in today’s terms). • Spent 30 man-months. • Result ? ummm… OK!
- 7. * operator not included. 7Use-Case is Everything!
- 8. The bombe ran . . . Use-Case is Everything! 8
- 10. . . . and ran . . . Use-Case is Everything! 10
- 11. . . . until it was switched-off. Use-Case is Everything! 11
- 12. Requirements? What requirements? (a.k.a. requirement = requirements) Use-Case is Everything! 12 Doesn’t work?? The bombe was still running, trying to break the code. Isn’t that what you wanted!!?? Yes. But the requirement was to break the code within a “reasonable” time-frame. Oh! Ok. Since code is changed daily, Time to break code < 24hrs.
- 13. So who gathers use-cases? 13 Project Manager Lead Executive Manager Software Engineers Use-Case is Everything!
- 14. So who gathers use-cases? 14Use-Case is Everything! …but did not prioritise this over other tasks. Only to end-up forgetting this when put under a strict deadline. In fact, Alan Turing did start gathering use-cases early-on…
- 15. Luckily, someone else was gathering use-cases ! Each message always starts with… Use-Case is Everything! 15 Not this guy Customer facing field engineer
- 16. Use-Case is Everything! 16
- 17. OK. So what? Use-Case is Everything! 17
- 18. * operator not included. Looks familiar? 18Use-Case is Everything!
- 19. 19 Is this block required? Use-Case is Everything!
- 20. Requirements “Features” What is possible to engineer within the feature What is actually required to be engineered within the feature What is not part of the feature (but requested by the customer) Supported Feature Customer Requirements 20Use-Case is Everything!
- 21. Requirements “Features” TODO. When I have a hammer, everything looks like a nail to me. Supported Features Customer Requirements 21Use-Case is Everything!
- 22. TL;DR • Gather use-cases before designing. – Prepare a comprehensive set of use-cases. • Know all the use-cases before starting out to implement the design. • Let the customer know what use-cases the system will handle once ready. – Essentially letting the customers know of any shortcomings in the input requirements provided by them. Use-Case is Everything! 22
- 23. References • http://en.wikipedia.org/wiki/Alan_Turing#Hut_8_and_Naval_Enigma • http://en.wikipedia.org/wiki/Cryptanalysis_of_the_Enigma • http://www.imdb.com/title/tt2084970/ Linkedin.com/in/chinmayvs TheCodeArtist.blogspot.com StackOverflow.com/users/319204/TheCodeArtist 23Use-Case is Everything!