Working with the Unix OS

57
Development Tools
- data returned by function
Portability
- to produce code to run on many systems
Documentation
- comments throughout for successor programmer
- list of functions to stop duplication
- instructions on use of applications
- end-user documentation
Project Management
- tracking dependencies between modules of code
- dealing with change request in controlled way
- seeing that milestone dates are met
SCCS
When a program is under the control of SCCS, only one copy of any one version of 1 code can be retrieved for
editing at a given time.
Only the changes are recorded. Each version is identified by its SID (SCCS indent number).
SCCS commands:
admin initialise SCCS files – access
get retrieves versions of SCCS files
delta applies changes to SCCS files
prs prints portions of SCCS files
rmdel remove a delta from SCCS
cdc change comment with delta
what search files for special pattern
sccsdiff show differences between SCCS files
comb combine consecutive deltas into one
val validate an SCCS file
Used to track evolving versions of files:
- store and retrieve files under its control
- allow no more than a single copy of a file to be edited at one time
- provide an audit trail of changes to files
- reconstruct any earlier version of file
History data can be stored with each version,
- Why changes were made,
- Who made them,
- When they were made.
Terminology
A delta is a set of changes made to a file under SCCS custody. To identify and keep track of a delta, it is
assigned as SID (SCCS ID).
Creating SCCS file
A file called "lang" contains the following:
C
PL/1
FORTRAN
COBOL
ALGOL
$ admin -ilang s.lang
$ rm lang
Retrieving file via "get"
$ get s.lang