![]() Trade In this Item for up to £15.45
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Software Requirements: Styles and Techniques for an Amazon.co.uk gift card of up to £15.45, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Product details
|
Though everyone in software design knows about requirements, actual examples have usually remained shrouded in secrecy whether out of concerns over intellectual property or client confidentiality. One considerable strength of this title is that the author has seen many good and bad requirements documents and come up with several complete samples for a Danish shipyard and two hospital systems that can be published here.
Reading Software Requirements will likely convince you that you can do better with your requirements documents. Though there is no one "best" way, certain types of requirements work for certain situations better than others. This text can help you choose. Certain to be required reading for serious software analysts, this title can also benefit virtually anyone who works with software design documents. Its clear presentation style, remarkably devoid of jargon, helps make this book a great resource for a wide range of readers, with or without a background in traditional software engineering. --Richard Dragan
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
The book indeed discusses the method invented by the author himself but not only: it contains a quite good inventory of the whole range of modelling and requirement methodologies that have been invented. Each one is positioned with regard to what it can bring and where it helps.
Simply stated: eyes opening!
It's already a few month ago that I purchased the book and tried: as a software and systems architect, the book in general and "tasks & support" method in particular have already been helping me on several occasions.
The author presents various techniques and models, and he stresses that there is no RIGHT model for all situations. He also discusses practical issues/problems, with a balance between pragmatism and perfection. The book discusses the types of projects, contracts and appropriate requirement elicitation/engineering techniques to be considered.
One of the rare books, that discuss seriously Quality Requirements, not from the surface and not just by listing them from standards, but in details with practical examples, especially usability.
I highly recommend this book for anyone who deals with requirements! Practitioners, students and teachers.
|