CSC/ECE 517 Fall 2009/wiki1a 4 co

Best Practices For Source-Control Management With Version-Control Systems

  “Tip 23: Always Use Source Code Control” 
         – Hunt and Thomas, The Pragmatic Programmer [HT 00]

In software development, change is almost always inevitable [P 05] . Using a source configuration management (SCM) system (also known as a Source Code Control System (SCCS) or version-control system) can help individuals and teams manage the changes that occur during the software development process [D 90]. This article will provide the reader with basic information, and direct the reader to additional reading for more in-depth consideration.

Why Source Code Control is Necessary

According to Pressman, “Change is inevitable when computer software is built. [P 05]” He suggests four primary reasons for change:

• New business or market conditions
• New customer needs
• Reorganization, business growth, or downsizing
• Budgetary or scheduling constraints

Each of these reasons can cause changes in project requirements, in project priorities, or in the resources available to create or enhance a project. Managing the change with an SCM enables engineers to focus on technical work, and enables project managers to control changes which can affect project outcomes.

Links and Resources

These links and resources can help the reader further understand the need for source code control:

• http://oreilly.com/catalog/practicalperforce/chapter/ch07.pdf, pp. 176-178.
• Dart, S. “Spectrum of Functionality in Configuration Management Systems", Software Engineering Institute, 1990. Review pp. 1-4.
• http://svnbook.red-bean.com/en/1.4/svn-book.html, review the Forward section.
• A Visual Guide to Version Control. Review the section titled “So Why Do We Need A Version Control System (VCS)?”
• Pressman, Roger S., Software Engineering: A Practitioner’s Approach, pp. 739-742, McGraw-Hill, New York, NY, 2005

Understanding Basic Concepts

Blah

Links and Resources

Blah

Advice on Using an SCM or SCCS

Blah

Links and Resources

Blah

References

• http://oreilly.com/catalog/practicalperforce/chapter/ch07.pdf
• http://msmvps.com/blogs/peterritchie/archive/2008/10/18/developing-with-source-code-control-best-practices-part-1.aspx
• http://msmvps.com/blogs/peterritchie/archive/2009/03/11/developing-with-source-code-control-best-practices-part-2.aspx
• http://www.perforce.com/perforce/papers/bestpractices.html
• http://www.ericsink.com/scm/source_control.html
• http://svnbook.red-bean.com/en/1.4/svn-book.html
• http://msdn.microsoft.com/en-us/library/ee371247%28Expression.30%29.aspx
• http://books.google.com/books?id=-2wqcKAq4tIC&pg=PA45&lpg=PA45&dq=source+code+control+best+practices&source=bl&ots=-xsMTMYYb5&sig=taEE2yPdLfWS9eEOjiwjbQxZn7Q&hl=en&ei=uNGaSrzhEo2e8QbL0PXFAQ&sa=X&oi=book_result&ct=result&resnum=1#v=onepage&q=source%20code%20control%20best%20practices&f=false
• http://en.wikipedia.org/wiki/Source_Code_Management
• http://betterexplained.com/articles/a-visual-guide-to-version-control/

Additional References

• [P 05] Pressman, Roger S., Software Engineering: A Practitioner’s Approach, pp. 739-768, McGraw-Hill, New York, NY, 2005
• [HT 00] Hunt A. and Thomas D., The Pragmatic Programmer: From Journeyman to Master, pp. 86-89, Addison-Wesley, Boston, MA, 2000
• [D 90] Dart, S. “Spectrum of Functionality in Configuration Management Systems, Software Engineering Institute, 1990, available at http://www.sei.cmu.edu/reports/90tr011.pdf.