Practitioners Books

This book contains 170 information-packed pages that describe a comprehensive and effective approach to managing software development risks.

The approach is based on a just-in-time (JIT) strategy. Key elements of this strategy include (1) strategic planning and operational planning, the former is focused on product-line based software and makes a distinction between the software under development being the product itself or a part of the product, and the latter is focused on project planning and controls; (2) early risk identification, and (3) parallel development. When this book was first published parallel development was a complex goal; however, with component-based development strategies the approach is ideal. Perhaps the author was ahead of his time.

Some of the best chapters in this book are: Chapter 4 - provides excellent insights and advice on managing the strategic and operational elements of the JIT strategy, Chapter 5 - comprehensive list of software risk elements and Chapter 7 - another comprehensive list that covers risk metrics.

Chapter 8 describes the JIT method as it applies to each phase in the software development life cycle. This chapter contains valuable tables that can be used as checklists in your own project, and is full of useful information that can be applied to project risk management regardless of whether or not you implement the JIT approach described in this book. Chapter 9 shows how to apply the JIT approach to a project. This chapter is short is really a brief summary of the software engineering risk model (SERIM) from which the JIT approach was derived. Chapter 10 is a collection of JIT examples that can easily be recast into patterns. I especially like the way these examples clarify the information in preceding nine chapters. I recommend that you refer to this chapter as you read through the book because there will almost certainly be an example that will illustrate any fuzzy areas.

This is one of my favorite books on risk management in general and software risk management in particular. The information and approach are not limited to software engineering, although the book was obviously written for that technical domain. I have borrowed techniques from this book and have successfully applied them in other kinds of projects, as I am sure you will. I give it 5 stars and a strong recommendation.

Software Standards is a developing field for most companies. It is a jungle out there, and the number of books about the subject is huge and growing. This book attempts (and succeeds in my humble opinion) to show a clear path for those who seek to manage the chaos of software engineering. However, I also recommend getting the IEEE book as reference, ISBN 1-55937-898-0, although this book includes most of what you'll need.

With exceptions that I've noted below this is an in-depth examination of standards, initiatives and methods for software process improvement (SPI) and software process assessment (SPA).

The book is divided into twelve chapters, each of which contains two or more papers written by top experts in the field, including Mark Paulk (of CMM fame), Watts S. Humphrey (creator of PSP and TSP, and prolific author of software engineering process papers), Robert B. Grady (author of three standard references on metrics), and others who key players, but are not as widely known outside of the SPI and SPA community.

Chapter 1 covers software process assessment with an article by Paulk that surveys the more common models for SPI and SPA, and a reprint of Sarah Sheard's excellent article from CrossTalk Magazine titled "The Frameworks Quagmire". Chapter 2 contains three articles on the SW-CMM, which seems to be the centerpiece of this book. Chapter 3, "Other Approaches to Software Process Assessment" contains four articles that add balance by covering non-CMM approaches that are in common use, especially in Europe (Bootstrap). I especially liked the article by David N. Card titled "Sorting out Six Sigma and the CMM", which combines two hot topics. One of the exceptions that I cited at the beginning of this review is the article on Trillium, which in my opinion has been superseded by TL 9000 in the telecommunications industry.

The three articles in Chapter 4 (Software Process Improvement: How To Do It) address common concerns and barriers to any SPI initiative, and each add well thought out ideas, especially Sandra McGill's "Overcoming Resistance to Standard Processes, or, Herding Cats", and William Florac's "Statistically Managing the Software Process".

Watts Humphrey's Personal and Team Software Processes, and CMMI are the key topics in Chapter 5, which covers developments inspired by the SW-CMM. All of Chapter 6's Software Product Evaluation articles were my favorites from among the collection in this book, and I particularly liked Jørgen Bøegh's "Quality Evaluation of Software Products" and Geoff Dromey's "A Model for Software Product Quality" because they go to the heart of key issues in both product line engineering challenges and user acceptance testing.

Chapter 7, ISO 9000 Series and TickIT, is the second exception that I previously noted. Much has changed in ISO 9000 with the 2000 standard, which renders this entire chapter moot in my opinion. I also thought the five articles in Chapter 8, The SPICE Project, would have been a better fit in Chapter 3. The same goes for Chapter 9, Experiences of Software Process Assessment, which is nearly an extension of Chapter 8, and is closely related to Chapter 3.

Two other favorite chapters are 10 (Software Process Improvement for Small Organizations) and 11 (Benefits of Software Process Improvement). Chapter 10's three articles dispell any notion that SPI is only feasible for large organizations, and the three articles in Chapter 11 focus on the benefits of SPI, especially Herb Krasner's article titled "Accumulating the Body of Evidence for the Payoff of Software Process Improvement". I also liked the final chapter, which covers software processes in general, including an excellent article on modeling. I felt that this chapter should have been at the beginning of the book instead of the end.

Overall, this is a book for those of us who are nearly religious about SPI; but is not a good introductory text. It's main value will be to IT consultants who specialize in either SPI or SPA (or both), and who need to be familiar with the mainstream standards and approaches.

This is a very good book, covering a breadthof topics for software qa people of all levelsand all ranges of experience. Ernest has taken the time to catalog many successful methods, tips, techniques, and arguments.

This book is a collection of 14 essays on software quality and testing that has been compiled and edited by Dr. Hoang Pham. The material is more suited for academic, R&D and advanced software quality assurance professionals, and is highly technical in nature. Dr. Pham is one of the top names in software reliability and quality. His credentials as author, contributor or editor of over 50 articles and 18 books, and his forward-thinking research ensures that the essays in this book represents solid material. Although this compilation of essays was published in 1995 they are still applicable and are an excellent source of material for researchers and advanced practitioners.

The essays are divided among two main topics: (1) software reliability and (2) theoretical testing and assurance techniques.

Essay titles that focus on reliability are: Realistic Assumptions for Software Reliability Models, Predicting Software Development Errors Using Software Complexity Metrics, The Infeasibility of Quantifying the Reliability of Life-Critical Real-Time Software, Reliability Analysis of Large Software Systems: Defect Data Modeling, A Micro Software Reliability Model for Prediction and Test Apportionment, and Optimization Models for Selection of Programs Considering Cost & Reliability.

The essays that focus on testing and assurance techniques are: Software Reliability Measurement in Imperfect Debugging Environment and its Application, Are We Testing for True Reliability?, Safety Arguments, Software and System Reliability, Application of Software Reliability Modeling to Product Quality and Test Process, Some New Models of Software Testing with Performance Comparisons, Software Fault Content and Reliability Estimations for Telecommunication Systems, Adapting, Correcting, and Perfecting Software Estimates: A Maintenance Metaphor, and Enhanced Availability of Transaction Oriented Systems using Failure Tests.

Each essay is an in-depth monograph on its topic. The essays that I personally thought were highlights of this book were Predicting Software Development Errors Using Software Complexity Metrics, Adapting, Correcting, and Perfecting Software Estimates: A Maintenance Metaphor, and Enhanced Availability of Transaction Oriented Systems using Failure Tests. From each of these I learned some interesting techniques that were directly applicable to applications and service delivery from QA and support points of view that could be incorporated into real-life processes.

Do not let the age of this book deter you - it's as applicable to reliability and quality challenges we face in 2001 as it was when written in 1995. If you are among the target audience I cited above this will prove to be a valuable resource, and a gold mine of advanced ideas on reliability and quality.

As a Space Law practitioner, researcher, and author I have found this book'to be one of the most useful, complete and original among all the existing books in this field..

Following the very successful first edition is an updated second edition of Special Needs and Early Years: A Practitioner's Guide - a reference which offers the latest early years initiatives and legislation along with leading examples of good practice and handling parents of children with special needs. This isn't a parent's pick so much as a set of guidelines and recommendations for professionals working with such children and their families - and students at the college level.

Although now ten years old, Judy's book remains an extremely readable and comprehensive introduction to thinking about advertising. It is full of wise advice - from someone who has good experience in the business - and good examples, which should resonate with all but the youngest reader. My copy is well worn and thoroughly dog-eared as I have lent it to so many people. I recently ordered 3 more copies for exactly that reason.

Anderson, et al, create an accessible, realistic view of what it is to be a practitioner-researcher in schools today. This text is easy to use and provides useful examples and scenarios.

It's difficult to find a new book on outsourcing that maintains a neutral perspective and does not promote an agenda for or against. This is such a book. The author leads you through the key issues, devotes an entire chapter to the pros and cons of outsourcing with sufficient information with which to make an objective decision, then steps you through the process.

The process set forth in this book is straightforward. There are no innovative wrinkles, not should there be in my opinion. The tasks, completely covered in individual chapters, are:

- Establish objectives and parameters for outsourced services. Clarify the business drivers, define service objectives, analyze the business case, and examine factors such as staff transfers, etc. The business case analysis material in this book is particularly strong in that it looks at a multitude of factors. I also like the elicitation of stakeholder views and requirements in the initial stage of the process.

- Choose a provider. This is covers the RFI/RFP process, negotiations, selection and award. All aspects of due diligence are covered in the chapter devoted to this stage.

- Manage performance. There is a solid focus on service management and contract administration in this section, and is sprinkled with good advice throughout.

- Measure performance. This is one of the strongest sections. The coverage is complete and customer-focused. It is also objective and partners with the provider - one of many indications of the balanced and objective approach the author takes.

- Risks and controls. This section addresses the transition to the provider, associated risks, and how to effectively use the contract as a control mechanism. Key risks and how to deal with them during the life of the contract are outlined. This information shows the depth of experience the author has, and the advice is genuinely useful.

- When outsourcing fails to deliver. This section is tied to the previous one. It provides common symptoms, how to proactively resolve them, escalation when necessary, including arbitration, alternative dispute resolution, and litigation if necessary (and permitted by the contract). Knowing this information in advance can help to craft contract terms and conditions that anticipate them, and protect both parties and their respective interests.

The book wraps up with a section on alternative supply models, such as application service providers, managed providers of storage, security and other models. This information shows not only future trends, but may spark ideas about how to source your services in ways other than traditional outsourcing.

Information provided in this book will work with both on- and off-shore providers; however, be aware that there are additional issues with off-shore providers, including off-site staff, time zone differences, and perceived control.

A book that I recommend reading in conjunction with this one - before reading it in fact - is "Outsourcing: How to Make Vendors Work for Your Shareholders" (ISBN 1892606046). It is more of a sanity check document that will cause you to think about objectives and alternatives to outsourcing before you embark on a course of action that leads to outsourcing.