ACCU Home page ACCU Conference Page
Search   Contact us ACCU at Flickr ACCU at GitHib ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

ACCU Menu

Advertisement

Advertisement

Membership

Join ACCU

Login

» Create an account

» Password Reminder

ACCU Buttons

Add them to your site:

ACCU: professionalism in programming (116x31 px)
ACCU: professionalism in programming (225x60 px)

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1949 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
Practical Software Requirements
Author:
Benjamin Kovitz
ISBN:
1 884777 59 7
Publisher:
Manning
Pages:
pp425
Price:
$47-95
Reviewer:
Francis Glassborow
Subject:
documentation; management
Appeared in:
11-2
It is very easy to tell a young programmer that he should have documented requirements. S/he is likely to agree but the follow up is for them to ask you exactly what that means and how it should be done.

Those of you who are experienced contractors know all too well how poorly this part of software development is done by most companies that do it at all. Among all the other requirements for requirements documents is that they should be readable and informative.

This book sets out to provide guidance on how to prepare software requirements documents. If we can persuade more to follow the guidelines of this book (or some other effective guidelines) I would expect a considerable improvement not only in these documents but the whole process of which these are just a small, though important, part.

If you need to prepare requirements documents or provide guidance to a neophyte this book will be well worth its price. If you write software without these documents, read the book and decide whether you shouldn't change your working practices.