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

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 1918 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:
Making the Software Business Case
Author:
Donald Reifer
ISBN:
0 201 72887 7
Publisher:
Addison-Wesley
Pages:
292pp
Price:
£22-99
Reviewer:
Huw Lloyd
Subject:
business
Appeared in:
14-2
This book's principal concern is the measurement and presentation of software and programming as capital.

The text is well structured and self-encapsulating. I found the bibliography to be especially useful (each reference is accompanied with a description of the text's relevance).

The first half of the book titled 'Fundamental concepts' sets the scene and presents an incremental analysis of the domain. It makes frequent use of bullet-points, diagrams and tables to help depict the narrative.

Example cases constitute the second half of the book. They are written in the second person, with the reader taking on the role of the instigator for organisational change (enterprise software project manager) and the author often taking the role of consultant. Hence the narrative is an experiential account as opposed to a domain analysis.

Despite the clear writing and broad coverage, I felt it lacked impact. Many issues are often bundled together as key considerations without much reflection of their origin. I would have appreciated a further chapter articulating the author's personal analysis of his experiences.

I found myself disagreeing with some technicalities, which is understandable given the social and technical complexity of the activity (although the author allows for the interchange of models) for example:

i) Boehm's COCOMO II model takes a dominant role.

ii) The examples are large-scale (enterprise level) efforts. Whether the application of business cases scales down to sub-projects is not clear.

It is a thought provoking text that helps clarify a complicated activity. I recommend it for software associates seeking knowledge of business cases, or indeed of the application of software in business itself.