Stereotypes portray software engineers as a reckless lot, and stereotypes paint software configuration management (SCM) devotees as inflexible. Based on these impressions, it is no wonder that projects can be riddled with tension! The truth probably lies somewhere in between these stereotypes, and this book shows how proven SCM practices can foster a healthy team-oriented culture that produces better software. The authors show that workflow, when properly managed, can avert delays, morale problems, and cost overruns. A patterns approach (proven solutions to recurring problems) is outlined so that SCM can be easily applied and successfully leveraged in small to medium sized organizations. The patterns are presented with an emphasis on practicality. The results speak for themselves: improved processes and a motivated workforce that synergize to produce better quality software.
Table of Contents
List of Figures.
I. BACKGROUND. 1. Putting a System Together.
Balancing Stability and Progress.
The Role of SCM in Agile Software Development.
SCM in Context.
SCM as a Team Support Discipline.
What Software Configuration Management Is.
The Role of Tools.
The Larger Whole.
This Book's Approach.
Further Reading.2. The Software Environment.
What Software Is About.
The Development Workspace.
The Big Picture.
Further Reading.3. Patterns.
About Patterns and Pattern Languages.
Patterns in Software.
Configuration Management Patterns.
Structure of Patterns in This Book.
The Pattern Language.
Overview of the Language.
II THE PATTERNS. 4. Mainline.
Simplify Your Branching Model.
Further Reading.5. Active Development Line.
Define Your Goals.
Further Reading.6. Private Workspace.
Isolate Your Work to Control Change.
Further Reading.7. Repository.
One Stop Shopping.
Further Reading.8. Private System Build.
Think Globally by Building Locally.
Further Reading.9. Integration Build.
Do a Centralized Build.
Further Reading.10. Third Party Codeline.
Use the Tools You Already Have.
Further Reading.11. Task Level Commit.
Do One Commit per Small-Grained Task.
Unresolved Issues.12. Codeline Policy.
Define the Rules of the Road.
Further Reading.13. Smoke Test.
Verify Basic Functionality.
Further Reading.14. Unit Test.
Test the Contract.
Further Reading.15. Regression Test.
Test for Changes.
Further Reading.16. Private Versions.
A Private History.17. Release Line.
Branch before Releasing.
Further Reading.18. Release-Prep Code Line.
Branch Instead of Freeze.
Unresolved Issues.19. Task Branch.
Handling Long-Lived Tasks.
Use Branches for Isolation.20. Referenced Patterns.
Named Stable Bases.
Daily Build and Smoke Test.Appendix A: SCM Resources Online.
The Configuration Management Yellow Pages.
CM Crossroads-Online Community and Resource Center for CM Professionals.
CM Today-Daily Configuration Management News.
UCM Central-Unified Configuration Management.
ACME--Assembling Configuration Management Environments (for Software).
The Software Engineering Institute's SCM Publications.
Steve Easterbrook's Configuration Management Resource Guide.
The Software Configuration Management FAQ.
The Association for Configuration and Data Management.
Software Engineering Resource List for Software Configuration Management.
R.S. Pressman and Associates Software Engineering Resources for SCM.
SEweb Software Configuration Management Resources at Flinders University.
Pascal Molli's “CM Bubbles” SCM Resources Page.
The Usenet Newsgroup comp.software.config-mgmt.Appendix B. Tool Support for SCM Patterns.
VSS-Visual Source Safe.
CVS-The Concurrent Versions System.
ClearCase-base functionality (non-UCM).
ClearCase-Unified Change Management (UCM).
PVCS Version Manager.
MKS Integrity (Enterprise edition).Further Reading. Photo Credits. About the Photos. Bibliography. Index. 0201741172T10072002
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: Develop the next version of a product while fixing problems with the current one. Develop code in parallel with other developers and join up with the current state of codeline. Identify what versions of code went into a particular component. Analyze where a change happened in the history of a component's development. Use current tools more effectively, and decide when to use a manual process. Incrementally introduce good practices into individual workspaces and throughout the organization. Identify crucial aspects of the software process so that team projects can run smoothly. Build and foster a development environment focused on producing optimal teamwork and quality products.
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.
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.