Annotation of 43BSD/contrib/spms/doc/1.intro.ms, revision 1.1.1.1

1.1       root        1: .PP
                      2: .nr PS 12
                      3: .NH
                      4: Introduction
                      5: .nr PS 10
                      6: .XS
                      7: \*(SN Introduction
                      8: .XE
                      9: .PP
                     10: Software packages on the
                     11: .UX
                     12: operating system are frequently organized in a haphazard manner. The
                     13: conventions for arranging parts of the package within the file system vary
                     14: from package to package, and absolute pathnames are often used to describe
                     15: the location of files. The net result is an amorphous non-portable
                     16: software package requiring a substantial maintenance effort.
                     17: .PP
                     18: It would seem extremely desirable to develop tools and file system
                     19: structures to support more coherent and portable software packages, and
                     20: reduce the maintenance effort associated with them. The Software
                     21: Project Management System (SPMS) is a system for the management of
                     22: medium- to large-scale software systems. SPMS provides, within the
                     23: .UX
                     24: environment\|[5], a number of commands which can greatly simplify many tasks
                     25: associated with program development and maintenance. SPMS does not
                     26: attempt to duplicate existing
                     27: .UX
                     28: program development tools such as
                     29: .I make
                     30: or
                     31: .I SCCS,
                     32: but instead provides a way of coordinating these tools.
                     33: .PP
                     34: If only the simpler commands are used, the SPMS system can be helpful
                     35: for inexperienced
                     36: .UX
                     37: users. If the more advanced SPMS features are used, the experienced
                     38: user can perform complex tasks with less effort and greater
                     39: reliability than by applying the standard
                     40: .UX
                     41: tools directly.
                     42: .PP
                     43: Each software package managed by SPMS is organized as a project\|[7,8]. A
                     44: project is a collection of directories, each of which supports a
                     45: specific activity such as program development, testing, or
                     46: documentation (see fig. 1). There is no restriction on the number
                     47: of directories belonging to a project. The directory layout is arbitrary,
                     48: and can be altered to reflect the changing needs of the package.
                     49: .KF
                     50: .sp 33
                     51: .SM
                     52: .ce
                     53: \fIFigure 1.  \fRProject organization
                     54: 
                     55: .NL
                     56: .KE
                     57: .PP
                     58: SPMS can be fitted to existing software systems. It retains the full
                     59: capabilities of the
                     60: .UX
                     61: environment with unrestricted access to
                     62: .UX
                     63: tools. As a result, software packages developed using SPMS do not depend
                     64: on the system for their survival and can be ported to versions of
                     65: .UX
                     66: that do not support SPMS.
                     67: 
                     68: 

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.