PAGEFLOP
FORWARD
SELECTOR
SELAGAIN
WRONGSEL
YOUR SELECTION IS NOT IN THE 0 - #SELIMIT RANGE Please Try Again
AANVANG
Copyright CourseWare Technologies Inc., 1985-88
Lesson - 8
PROJECT DEVELOPMENT
UNDER UNIX
P0
Project Development|Project Development|8-0.1|15,55
UNIX has been recognized as an operating system
with some of the most effective tools for program
and project development.
UNIX's various program development tools are
unmatched by those of other operating systems.
Discussed in this lesson are:
sdb - the symbolic debugger
sccs - the source code control system
make - the program for maintaining computer
programs
MENU
Project Development|Topics to Learn|8-0.2|12,50
PROJECT DEVELOPMENT MENU
# Topic
--- -------
1 - sdb - The Symbolic Debugger
2 - sccs - The Source Code Control System
-- SCCS Menu
3 - make - The Program Maintenance Utility
-- make Menu
4 - Project Directory Organization
5 - Project Development
0 - Return to the Main Menu
P2
Project Development|Symbolic Debugger|8-1.1|6,50
The sdb utility is UNIX's symbolic debugger
that can be used with C and FORTRAN77 programs.
sdb is available with many larger UNIX
implementations.
P3
Project Development|Symbolic Debugger|8-1.2|14,54
sdb is capable of printing:
* one byte in octal,
* one byte as a character, and
* one word in octal.
sdb also provides:
* breakpoint control,
* a discrete instruction number stepping
capability,
* variable/address examination, and
* an interactive facility for line assignments.
TOPIC2
TOPIC3
P4
Project Development|Project Directory Organization|8-4.1|12,54
Project directory organization varies from
installation to installation.
Important factors to consider for organization
include:
* the purpose of the computer system,
* how many projects are being developed on
the system,
* the security of information, and
* which source code is to be controlled.
P5
Project Development|Project Directory Organization|8-4.2|12,54
If a company keeps an accounting system, a
separate subtree at the root of the system may be
set up for accounting. For example, /acct.
Purchased software is normally installed in
the /usr/local directory.
NOTE: Purchased software should never be
reorganized unless your administrators are intimately
familiar with the delivered software.
P6
Project Development|Project Development|8-5.1|12,54
Assuming that more than one project is being
developed on your UNIX system, Product 730 and Product 750,
for example, you may wish to create directories with
pathnames as follows:
/usr/local/730
/usr/local/750
For source code control purposes, the level below
the product number directories should be the source
code control subdirectories.
P7
Project Development|Project Development|8-5.2|10,54
Normally, there are 4 SCCS subdirectories:
src - the source directory
sccs - the SCCS file directory
stest - the SCCS working directory
valid - the validation directory
The src directory will contain all source code
related to the project that is not under SCCS.
P8
Project Development|Project Development|8-5.3|12,54
sccs - is the mirror image of the src directory.
It will be the storage directory for files
under SCCS.
stest - is the exact mirror image of the sccs
directory. It will serve as a working
directory for SCCS administration.
valid - is similar to the src directory. It will
contain test programs and function for the
executable images contained in the src
directories.
P9
Project Development|Project Development|8-5.4|17,48
A local project development hierarchy may
have a directory hierarchy of the following form:
usr
local
730
users
:
src
purchased software
stest
:
valid
:
750
users
: