Current loctn: reading list > software reqs

Wiegers, Karl E.  Software Requirements.  1999. Microsoft Press. 350pp. 

This is the most approachable reference I've found on the subject of software requirements.  Nonetheless, Wiegers has managed to provide good explanations of important technical issues.  I find his explanation of the distinctions (and the importance of these distinctions) between business, user, software, functional and non-functional requirements to be the most understandable among all references I've looked at.  

Before I encountered this book, the others I'd seen all seemed too much intent on highly technical explanations, on approaches used in specific areas of application, etc. This is my preferred general reference on the subject. 

The book includes useful practical advice on: 

• techniques for uncovering and documenting requirements
• the customer's perspective on requirements
• good practices and principles in requirements management
• improvement of requirements processes
• how software requirements address risk management
• major diagrammatic techniques for requirements documentation
• prioritization of requirements
• the use of prototyping to reduce development risks
• requirements verification
• management of change requests
• summaries of several tools used for requirements management/tracking.  

A very good bibliography of materials is also provided. 

As I understand, a second of edition of the book is now available. 

Last modified: 13:22:56 23-Jan-2009