CSC/ECE 517 Fall 2009/wiki1a 4 co: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Best | == Best Practices For Source-Control Management With Version-Control Systems == | ||
“Tip 23: Always Use Source Code | “Tip 23: '''Always Use Source Code Control'''” | ||
– Hunt and Thomas, The Pragmatic Programmer [HT 00] | – Hunt and Thomas, The Pragmatic Programmer [HT 00] | ||
Revision as of 14:10, 7 September 2009
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.