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:
Transition to OO Software Development
Author:
Mohamed Fayad&Mauri Laitinen
ISBN:
0 471 24529 1
Publisher:
Wiley
Pages:
354
Price:
£25-95
Reviewer:
Mark Easterbrook
Subject:
object oriented
Appeared in:
OL37
The book is divided into 4 parts taking the subject from ground zero through to post-mortem. Part I, A Transition Framework, sets the scene for OO and introduces the terminology. It is fairly honest about OO not being a silver bullet to software development, instead giving the benefits of moving switching to a new development tempered with the necessity of a higher skill requirement at all levels.

Part II, Planning and Preproject Activities, contains two chapters mostly covering management and people issues. With all the hype about the technological side I was pleased to see the book focused on the overcoming the real barriers to OO of management planning and general resistance to change.

Part III, Object Oriented Insertion Activities, is a strange term to describe the six activities, one per chapter, essential to implement an OO development environment; Techniques, Tools, Staffing, Training, Legacy systems and Reuse. The text is well illustrated with diagrams, examples and bulleted tips and practical advice. The change in effort and focus as experience is gained is indicated in places to allow estimating for both the initial project and subsequent development.

Part IV, Object-Oriented Project Management, is the final and largest section, which should reflect the importance of this when making such a watershed change to a development process. However, the first chapter in this section covering prototyping really belongs in the previous section and the remainder is pre-occupied with metrics , although tempered by highlighting that it is processes and not people that should be measured. That aside, it still contains a wealth of information on ensuring that all activities are present and how to control them to prevent disregard of procedures or runaway tasks. As with any American sourced book it takes a US-centric view of standards mentioning DoD and SEI standards,however this does not impair the material and the growing importance of ISO9000 is mentioned. Recommended.