Configuration management of computer programs by the Air Force: principles and documentation
AFIPS '67 (Spring) Proceedings of the April 18-20, 1967, spring joint computer conference
The technical specification: key to management control of computer programming
AFIPS '67 (Spring) Proceedings of the April 18-20, 1967, spring joint computer conference
Air force concepts for the technical control and design verification of computer programs
AFIPS '67 (Spring) Proceedings of the April 18-20, 1967, spring joint computer conference
Configuration management of computer programs by the Air Force: principles and documentation
AFIPS '67 (Spring) Proceedings of the April 18-20, 1967, spring joint computer conference
The technical specification: key to management control of computer programming
AFIPS '67 (Spring) Proceedings of the April 18-20, 1967, spring joint computer conference
Air force concepts for the technical control and design verification of computer programs
AFIPS '67 (Spring) Proceedings of the April 18-20, 1967, spring joint computer conference
Measurement of computer systems: an introduction
AFIPS '72 (Fall, part II) Proceedings of the December 5-7, 1972, fall joint computer conference, part II
| Hi-index | 0.00 |
The classic approach to the development of Air Force operational computer programs has been to award separate contracts for the hardware and for the "software" aspects of an electronic system. The integration of the hardware and the "software" into a homogeneous total system has not always been a planned certainty, primarily due to the lack of definitive management procedures and contractor guidance and control techniques for the area popularly known as "soft-ware." It was with this history in mind that a study was initiated to evolve a technique which would permit the following: a. Development of contractual requirements standards to provide positive control over the contractor's effort in the development of computer programs. b. Development of a series of principles and procedures which would be applied to the configuration management of computer programs. c. Development of a series of design standards and specifications for use during computer program design and development. d. And most important of all, to develop an orderly process of "software" production that would assure full compatibility and timeliness with hardware production.