Proceedings of the April 18-20, 1967, Spring Joint Computer Conference on - AFIPS '67 (Spring) 1967
DOI: 10.1145/1465482.1465489
|View full text |Cite
|
Sign up to set email alerts
|

Configuration management of computer programs by the Air Force

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

1967
1967
2011
2011

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 3 publications
0
3
0
Order By: Relevance
“…In the first cycle, data for 27 programming efforts (data points) completed at SDC were analyzed and the results were reported in the fall of 1964 (19). The work in the second cycle, an analysis of a total of 7^ data points also representing SDC programming work, was reported in detail in the fall of 1965 (62), and summarized and extended in the spring of 1966 (53). The third cycle, which included analysis of 169 data points,3 69 of which were programmed at SDC and 100 at Air Force and industrial programming organizations, provides most of the quantitative guidelines found in the section on Computer Program Design, Code, and Test.…”
Section: Introductionmentioning
confidence: 99%
“…In the first cycle, data for 27 programming efforts (data points) completed at SDC were analyzed and the results were reported in the fall of 1964 (19). The work in the second cycle, an analysis of a total of 7^ data points also representing SDC programming work, was reported in detail in the fall of 1965 (62), and summarized and extended in the spring of 1966 (53). The third cycle, which included analysis of 169 data points,3 69 of which were programmed at SDC and 100 at Air Force and industrial programming organizations, provides most of the quantitative guidelines found in the section on Computer Program Design, Code, and Test.…”
Section: Introductionmentioning
confidence: 99%
“…These Air Force 375 Management Concepts as applied to 7.13 ANALYZING SYSTEM DEVELOPMENT software are based on the decision that a computer program can be defined as a Computer Program Contract End Item (CPCEI). Described in some detail in References 14,15,16,and 20, the procedures detailed in this system include the definition of specifications and review procedures which assist considerably in assuring that the operational requirements are defined. before the system implementation begins.…”
Section: People Don't Understand the Complete Operational Problemmentioning
confidence: 99%
“…The translator also contains specialized information for dealing with quantifiers and and/or clauses. For example, the following expressions will be translated correctly into the equivalent LISP forms: NO MEMBER OF X IS ATOMIC AND NOT NULL 148 THE FIRST ELEMENT OF X IS GREATER THAN THE SECOND AND NOT LESS THAN THE THIRD THE FIRST ELEMENT OF SOME MEMBER OF X IS A NUMBER THAT IS GREATER THAN THE SECOND ELEMENT FORTRAN 10,22,25,29,30,31,36,44,52,77,80,101,116 12,15,20,39,44,51,52,58,64,99 Ossification 61 Oxford 29…”
Section: Toward a Programming Laboratory By Warren Teitelmanmentioning
confidence: 99%