软件配置管理

1.Source code control—Managing the source code of the project. This
includes access to the code and tracking changes to the code. Exactly what
constitutes source code depends on the organization and project. It can
range from being only the source code for the system to including every piece
of electronically stored information for the project, such as documents and
project plans.
2. Defect tracking—Registering defects and tracking how they are handled.
Defects (bugs) are typically registered by testers, support personnel, or users.
Defect tracking systems allow defects to be classified and assigned to a
person in the organization.
3.Change management—Registering changes to requirements. This includes
changes to existing functionality as well as requests for new functionality.
Change management systems should allow changes to be classified, ranked,
and tracked.

 

---

 

源代码管理有两种方式:

• Reserved—When an SCM uses reserved access to artifacts, then you must
  obtain a lock on the artifact before you can change it. Once you have finished
  changing the artifact, you send your changes to the SCM and the lock is
  released. This eliminates the risk of simultaneous changes.
•  Unreserved—When an SCM uses unreserved access to artifacts, there are
  no locks and files can be changed simultaneous. These systems detect, but
  do not prevent, problems encountered with simultaneous changes.

 

 

---

 

cvs 介绍

CVS uses an unreserved (commit/update) protocol for managing access to
artifacts. If more than one developer has changed an artifact, the changes will be
merged if possible. If the changes are conflicting, then the conflicting lines will be
marked in the source file, and one of the developers can manually fix the conflict.
This merging cannot be done with binary artifacts. If there are conflicts with a
binary artifact, then the conflict must be resolved manually.