Amazon.co.uk Review
Suitable for most any IT professional who wants to build better software,
Software Requirements: Styles and Techniques offers a surprisingly readable textbook-style treatment of software engineering's numerous attempts to get it right with defining requirements. Surveying almost every conceivable style of defining requirements, yet remaining thoroughly practical, this book can let your organisation do more with its requirements documents, which is a good step to creating software that succeeds better with your users.
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
Product Description
Most IT systems fail to meet expectations. They don't meet business goals and don't support users efficiently. Why? Because the requirements didn't address the right issues. Writing a good requirements specification doesn't take more time. This book shows how it is done - many times faster and many times smarter. This book covers many aspects of requirements. Styles: Traditional and more cost/effective ways of expressing requirements. Techniques: Ways of gathering, verifying, and maintaining requirements; ways of getting commitment from the stakeholders and support - yet limit - innovation; ways of ensuring that you meet your business goals. It discusses the styles and techniques useful for different project types, for instance software developed specifically for the customer, software bought off-the shelf and adapted for the customer (COTS), and software developed for a broad market. The book illustrates everything through real-life examples. It also deals with difficult requirements, for instance how to specify ease-of-use, how to specify very complex computations, and how to deal with 200 reports that the old system has, and the new system may or may not need. The book shows two complete, real-life specifications and large parts of several others. It also has exercises and figures for presentation.
See all Product Description
by Ian Alexander
by Suzanne Robertson
With an Amazon.co.uk Gift Certificate, you can get them what they want (even if you don't know what that is). 
Amazon Home