Process Patterns: Building Large-Scale Systems Using Object Technology

This book's collection of process patterns is the foundation for best practices in applications delivery, and align to a variety of methodologies, including the Rational Unified Process. These patterns can also be used as the basis for key process areas for achieving increasing levels of capability maturity or process improvement capability for organizations that use SEI's CMM or ISO/IEC15504 (SPICE).Chapter 1 assumes no prior knowledge of patterns or object-oriented software processes, and gives a descriptive overview of both. It also discusses various approaches to software development, which provides a context for how patterns can fit within various approaches, such as serial, iterative, incremental or parallel projects. It also introduces a process framework called Object-Oriented Software Process (OOPS)and compares this process to other common OO approaches to development. Although this book is structured for OOSP, the patterns will fit within any framework or methodology. This makes the book valuable to any shop regardless of whether OO or traditional procedural languages and approaches are used. A highlight of this chapter is the discussion of process maturity that uses SEI's CMM as a baseline. The information can be realigned to SPICE or Bootstrap as well because there is no firm bias towards the CMM - I suspect the CMM is used because it's well known to U.S. readers.The book is divided into parts after chapter 1, with each part aligned to a life cycle stage and comprised of a collection of chapters that describe patterns that are applicable to the stage. Each chapter is a pattern and is structured as Initial Context, Solution, Solution Project Tasks, Resulting Context, Process Checklist and What you have learned. Part I is the INITIATE stage. Patterns include: Initiate Phase (how to start the phase itself), Define and Validate Initial Requirements, Define Initial Documents, Justify and Define Infrastructure. Part II is CONSTRUCT, with patterns for Construct Phase Initiation, Model, Program (development), Generalize and Test in the Small.What I like is the format of the patterns make them easy to read and consistent. It is easy to tailor them for organizational use, as well as to add more patterns. It also adds a defined structure to the development process itself, providing a solid basis for documenting key process areas and defining development workflow. The second book in this series, More Process Patterns, completes the pattern library by addressing test, release and operational aspects of applications and systems. I read that book last February and feel that both books should be a part of any mature development organization, or organizations that are seeking to improve their processes and capabilities maturity.

In the two years since I first read this book I have found myself going back to it like an old friend. It is a constant source of information that focuses on application development processes that are set forth in the form of patterns.The explanatory text covering processes, phases and stages in the OOSP (object-oriented software process) has crystalized the development process like no other book in my library. The accompanying patterns have been a source of best practices that I keep referring to in one consulting engagement after another.This, and the companion (More Process Patterns) are an A to Z resource for development, application delivery and service delivery. I have used it in the past as a resource for developing and implementing software engineering processes. My present situation (in early 2001) finds me using this book as a source of ideas on how to integrate application delivery and service delivery for a model on information technology management that I co-developed. The approach provided in the book, the framework of OOSP, and the patterns themselves have heavily influenced the development and refinement of the model. They have also further clarified my ideas on development life cycles that have led me into the Rational Unified Process camp.From the foregoing it is clear that this book remains a valid reference on system development, as well as the foundation of service delivery (which is addressed in more detail in More Process Patterns). It is also must reading for project managers and software engineering process practitioners. What is not so obvious, but in my opinion eaqually valid, is that this book also provides a foundation for a solid software quality assurance program. It does so by providing patterns that have clearly defined quality objectives for every phase and stage in the development life cycle. This is an unexpected bonus that I did not catch the first time through the book. I strongly recommend that anyone involved in development (maintenance or project level efforts), and SQA read this book. If your focus is application and service delivery, get this book as a foundation for More Process Patterns, which is more applicable to those areas. Regardless of what your job is in the IT or consulting world you will find information and ideas that in this book that will influence your thinking and approach.

I was really impressed with this book, and it's follow-up, More Process Patterns. It's about time someone described a software process that can be used by actual development teams, likely because it is written based on the author's real-world experiences. He tackles all the issues of software development, not just the cool ones such as modelling and programming that everyone else appears to focus on. The fact that he has shown how "boring" topics such as quality assurance, risk management, reuse, and people management fit into the picture throughout the entire software process makes the book worthwhile for any project manager. The programmers that I've shared the book with have gotten a lot out of it, in fact one was even amazed at how complex software development actually is. A true eye opener. There is something in this book for everyone.I think readers will benefit most from the general philosophies that pervade the book, such as testing early and often, letting requirements drive modeling which drives programming (i.e. think first, then act), taking maintenance and support into consideration, and actually doing the work necessary to obtain high levels of reuse. I highly suggest this book to anyone involved in the development of software. Although the book is large, 550 pages, it is an easy read. Another good thing about it is that it's size and content make it a good book to beat your pointy-haired managers over the head with when they do something stupid like set an unrealistic schedule for your team.

Scott's books (you should get More Process Patterns also) describe the processes necessary to provide lifecycle coverage to a software project. Scott's approach of reviewing the high level for strategic importance and then dive bombing in on the specific issue gives you the information you need to address your software projects. Scott's war stories give you the impression that he has worked on YOUR project. His insight is wonderful.

First, the book is actually a hard-cover that is 550 pages in length, and is one of two books that I've written about the OO software process (the second is entitled More Process Patterns and will be available in January 1999). I wrote the book to share my experiences regarding large-scale, mission-critical software using object technology. Our industry runs upward to an 85% failure rate, so it seems to me that we should invest some time understanding how to successfully develop, maintain, and support software. The concepts, techniques, and ideas presented in this book are based on real-world experience, and are backed-up by a wealth of material already existing in the industry.Process Patterns is concerned with with first half of the OO software process, the Initiate phase where you get your development efforts organized, and the Construct phase where you build your software. The second half of the OO software process is described in detail in More Process Patterns, concentrating on the Deliver phase and the Maintain and Support phase.I believe that you will find the material presented in Process Patterns, and its sister book More Process Patterns, to be of exceptional value to your organization's efforts to improve its software productivity and success rate. I know of several organizations that are already using this book as a supplement to the Rational Unified Process (RUP), which for the most part is geared towards the development of a single project as opposed to this book which is geared to organizations working on several projects and who are concerned about the maintenance and support of them once they are in production.