Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Software Configuration Management Patterns: Effective Teamwork, Practical Integration Paperback – November 14, 2003
See the Best Books of the Month
Want to know our Editors' picks for the best books of the month? Browse Best Books of the Month, featuring our favorite new books in more than a dozen categories.
Frequently Bought Together
Customers Who Bought This Item Also Bought
From the Back Cover
Effective software configuration management (SCM) strategies promote a healthy, team-oriented culture that produces better software. Software Configuration Management Patterns alleviates software engineers' most common concerns about software configuration management—perceived rigidity and an overemphasis on process.
Through the use of patterns, the authors show that a properly managed workflow can avert delays, morale problems, and cost overruns. The patterns approach illustrates how SCM can be easily and successfully applied in small- to mid-size organizations. By learning how these patterns relate to each other, readers can avoid common mistakes that too often result in frustrated developers and reduced productivity.
Key coverage includes instruction on how to:
Software Configuration Management Patterns also includes a detailed list of SCM tools and thorough explanations of how they can be used to implement the patterns discussed in the book. These proven techniques will assist readers to improve their processes and motivate their workforce to collaborate in the production of higher quality software.
About the Author
Stephen P. Berczuk has been developing object-oriented software applications since 1989, often as part of geographically distributed teams. He has been an active member of the Software Patterns community since the first PLoP conference in 1994, and did early work on the relationship between organization, software architecture, and design patterns. He has an M.S. in Operations Research from Stanford University and an S.B. in Electrical Engineering from MIT.
Brad Appleton has been a software developer since 1987 and has extensive experience using, developing, and supporting SCM environments for teams of all shapes and sizes. A former Patterns++ section editor for the C++ Report, Brad is also well versed in object-oriented design and agile software development, and cofounded the Chicago Patterns and Chicago Agile Development Groups. He holds an M.S. in Software Engineering and a B.S. in Computer Science and Mathematics.
More About the Author
Top Customer Reviews
The book starts with a couple of introductory chapters and then devotes a chapter to each of 16 patterns. I really like that the book devotes a full chapter to each pattern (and therefore covers substantial patterns) rather than covering each in two pages as is often the case in patterns books.
As a coach and trainer of agile software development teams, I am often asked by these teams how they handle the software configuration management with such fast-moving processes. These excellent and highly readable book has collected a wonderful set of practices and will become a part of the standard canon I recommend to clients.
The book begins with an overview of SCM concepts and a discussion of the role of SCM in agile software development. This discussion dispels the myth that software configuration management must be process heavy to be effective.
Much of the book consists of a description of patterns (i.e., problems that occur over and over again) related to software configuration management. Each pattern is described in a brief chapter that begins with a question about a common SCM problem. For example, the chapter on the task level commit pattern begins with the question, "How much work should you do between submissions to the version control system?"
Each chapter that presents an SCM pattern describes the circumstances in which the pattern is relevant. The authors explain the pattern with the help of easy-to-understand diagrams and brief narratives of situations from real software projects in which the pattern is relevant. Most chapters also include relevant references to books and papers that elaborate on material covered in the chapter.
Perhaps the most valuable aspect of this book is that an SCM engineer can reference it when speaking to project management and members of the development team about common SCM pitfalls and practical techniques that can be used to correct or avoid these pitfalls.
To support other readers' comments (and update my review): Using a pattern language to describe SCM process has been helping people on my teams to take a more proactive role in SCM activities- identifying well thought-out branching scenarios, and how to manage their work areas (and work) to complete parallel development tasks. Impressive how describing parts of the process using several simple behavior patterns simplifies things...
The patterns given in this book comprise a complete picture of software configuration management, and will allow you to fully understand the scope and complexity of implementing, managing and continuously improving an SCM process. From the following list you'll see that these patterns are end-to-end:
- Mainline and active development line, both of which are designed to manage baselines, as well as to promote stability in the code base.
- Private Workspace, repository, private versioning, and private system build patterns are the essence of SCM as well as reflecting best practices in team-oriented integration and testing while preserving the integrity of the code base.
- Third party codeline is an interesting pattern that I've not encountered, but one that is highly useful when you are working with subcontractors, or have outsourced some development. The patterns for task level commit and task branches are also useful approaches to team-oriented development, whether internal or distributed among subcontractors.
- Codeline policy, smoke and unit test patterns govern the SCM process and prepare for the transition from development to QA. These are core patterns that are directly tied to the development process.
- Release line, release prep codeline, and regression test patterns cover the promotion to QA and release management portions of the development process.Read more ›
Most Recent Customer Reviews
Didn't meet my expectations. I purchased this book to learn the formalities of configuration management, since all I know about it is hands-on experience. Read morePublished on November 9, 2013 by fmcf
This book outlines detailed SCM patterns that can be applied to any SCM provider. I use Microsoft Visual SourceSafe and Team Foundation Server at work and Git for open source... Read morePublished on August 19, 2013 by Eki
This book provides a good starting point for basic configuration management techniques. As it defines a pattern language, it is easy to read and easy to come back to for specific... Read morePublished on January 24, 2011 by Ramon Jimenez
Based on the reviews, I had high hopes for this book especially because I knew nothing of Software Communication Management. Read morePublished on October 7, 2010 by A. Delorme
When I first started reading this book, I was like, "This is common sense," but that's only because our lab already does many of the things outlined in this book. Read morePublished on February 10, 2009 by Slick Rhoads
The book content itself looks great - I've only just received it and started reading. However the print quality looks like it came out of a photo-copier. Read morePublished on December 18, 2008 by I. Maclean
This is an outstanding book for software development teams that see software configuration management as a means to an end, not the end itself. Read morePublished on September 28, 2007 by Paul M. Duvall
I am surprised to apparently be the only person to find this book disappointing. Let me go into the details.
Physical book. Read more
Objective, clear and simple. War stories told by a intellectually savvy trooper are not complex. They tell us about complex scenarios in a simple way. Field experience. Read morePublished on March 21, 2007 by Ernani Santos