Having each person’s identity attached to his or her changes is useful. If
a junior SA makes a mistake, the more senior person who discovers it can
take the person aside and use the opportunity to do some mentoring on that
area of the system.
Source code control systems that are used by software developers are the
sorts of tools that you should look at for this functionality. Under UNIX, such
tools are SubVersion, Revision Control System and Source Code Control
System (Bolinger 1995), and Concurrent Versions System (Berliner 1990),
which store the differences from version to version, along with identity and
a comment, and also provide locking. SourceSafe is an example of such a
system under Windows. Many commercial systems also are available and
may already be in use by developers at a given site.