software requirement specification in the real world - tobias andersen - 2009 08 24
DESCRIPTION
Software requirements specification in the real world – The good, the bad & the ugly. Why do we need software requirements specification, where does it go wrong (samples), who can do it?TRANSCRIPT
![Page 1: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/1.jpg)
Software requirements specification in the real world – The good, the bad & the ugly
By Tobias Andersen
![Page 2: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/2.jpg)
??
![Page 3: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/3.jpg)
• A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed.
• It includes a set of use cases that describe all the interactions the users will have with the software.
• In addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
Definition according to wikipedia...
![Page 4: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/4.jpg)
Why do we need a SRS...
Why?
![Page 5: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/5.jpg)
At a glance...Where REQUIREMENTS can help
![Page 6: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/6.jpg)
What often happens...Ba
d Re
quire
men
ts
Bad
Assi
gnm
ent
![Page 7: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/7.jpg)
You cannot build what you do not understand
![Page 8: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/8.jpg)
No amount of SPIN can replace a quality product
![Page 9: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/9.jpg)
Starting off wrong, leads to a short lifeBa
d Re
quire
men
ts
Bad
Exec
ution
Bad
Valu
e
Bad
Long
evity
![Page 10: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/10.jpg)
Bad Input leads to Bad outputBa
d Re
quire
men
ts
![Page 11: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/11.jpg)
So what is a better way?
The SRS lifecycle
![Page 12: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/12.jpg)
Its not a science
Can I do it?
![Page 13: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/13.jpg)
The Good (Case 1)
• Project brief: Substitute X resource with Y resource on the clients corporate website. UX have created a ”resource map”, which is located on our internal project server.
• Projected duration: 1 business day.
• Estimated rate of success: >75%.
![Page 14: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/14.jpg)
The Good (case 1) it was a piece of cake.
• Technical brief: Substitute X resource with Y resource on the clients corporate website at ftp://mysite.com.
See sitemap from UX @ \\{server}\{project} for further details on the resource-2-page mappings.
• Actual development time: 1½ business day.
• Actual rate of success: 100%.
![Page 15: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/15.jpg)
The BAD (case 2)
• Project brief: Substitute X resource with the document we uploaded last month to our clients corporate website.
• Projected duration: ½ - 1 business day.
• Estimated rate of success: 75% <> 50%.
![Page 16: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/16.jpg)
The Bad (case 2) we got lucky...
• Technical brief: Substitute X resource with its predecessor (unknown document, ask Claus he worked on it a month ago) on the clients corporate website at ftp://mysite.com.
See sitemap from UX @ \\{server}\{project} for further details on the resource-2-page mappings.
• Actual development time: ½ business day.
• Actual rate of success: 50%.
![Page 17: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/17.jpg)
The UGLY (case 3) it’s not a science, it’s black magic
• Project brief: Hi Tobias. ”Your account manager asked me to forward you this email discussion that describes our change requests. If you have any questions feel free to contact me (p.s: I might be busy, but leave a message and I will get back to you ASAP.). Have a nice day! ”
• Projected duration: ? business day.
• Estimated rate of success: <25%.
![Page 18: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/18.jpg)
The Ugly (case 3) not even the Beauty could love this Beast
• Technical brief: Read this email thread and do the needful!
• Actual development time: Just bill the client by the hour. Job nr. is 00911.
• Actual rate of success: 0%.
![Page 19: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/19.jpg)
What have we learned
• A well-crafted SRS document mitigates risk.• SRS does not have to be 50 page documents.
It can be something as simple as a set of use cases defining the clients needs.
![Page 20: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/20.jpg)
How to convert the Ugly into the Good
• When in doubt ask your client. If they don’t know, chances are you don’t need to know.
• Express your needs in a form that a 5 year old could understand!
![Page 21: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/21.jpg)
Good Input enables Beautiful output
![Page 22: Software Requirement Specification In The Real World - Tobias Andersen - 2009 08 24](https://reader034.vdocument.in/reader034/viewer/2022051819/54c831824a7959e1628b45bb/html5/thumbnails/22.jpg)