software design

Many books I read talk about requirement analysis living the previuos steps (exlicitation and documentation) to the reader.
This books presents, in a very pleasant way, the different forms we have to describe requirements in a SOW or a SRS.
It compares differents style and gives very good advices.
A must to have.

If you've ever worked/will work with getting requirements in a software project, you can't go wrong with this book. Taking you first through the basics, Lauesen then goes on to discuss the different techniques of specifying requirements under different conditions. Man, this is gonna save your bacon one of these days... :)

Very original book; a rich source of knowledge and reflection. The approach is quite distinctive; it combines industrial and academic experience. We feel from the examples presented in the book and their conceptualisation that the author went through a long and painful (but fruitful) learning process of requirements engineering.

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.