Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Overview of this book

Why is Software Configuration Management important?Software Configuration Management (SCM) is the discipline of managing the building and modification of software through techniques including source-code control, revision control, object-build tracking, and release construction. SCM involves identifying the configuration of the software at given points in time, systematically controlling changes to the configuration, and maintaining the integrity and traceability of the configuration throughout the software development lifecycle.Software Configuration Management is one of the first skills a serious developer should master, after becoming proficient with his or her development tools of choice. Unfortunately, this does not always happen because the subject of SCM is not commonly taught in either academic or company training.When developing software, you need to have a manageable team development effort, track and maintain the history of your projects, sustain parallel development on multiple product versions, fix bugs, and release service packs while further developing the application. This is where the concepts of Software Configuration Management come into play; SCM is about getting the job done safer, faster, and better.Visual SourceSafe has a long history behind it. The previous versions were either loved for their ease of use and integration with other Microsoft products, or hated because the headaches caused by using them improperly. This book will help you to avoid such problems.
Table of Contents (15 chapters)
Visual SourceSafe 2005 Software Configuration Management in Practice
About the Author
About the Reviewers

Team Cooperation

When developing the solution in a team environment, team cooperation is an essential requirement. This is where, although it can be changed later, a cooperation model must be chosen.

If you remember from Chapter 1, there are two main approaches in SCM when it comes to cooperation models:

  • Check out-Modify-Check in

  • Modify-Merge-Commit

Visual SourceSafe is built around the Check out-Modify-Check in model. This model has two sub-models of operation:

  • Exclusive Check-Out Model

  • Multiple Check-Out Model

Choosing a Check-Out Model

The Exclusive Check-Out Model uses a pessimistic concurrency scheme characterized by a Lock-Modify-Unlock mode of operation because it allows only one user at a time to modify a resource.

The Multiple Check-Out Model uses an optimistic concurrency scheme characterized by a Copy-Modify-Merge mode of operation because it allows multiple users at a time to modify a resource, after which a merge operation is performed. During the merge operation conflicts may appear...