Management Procedures in Computer Programming for Apollo Interim Report

Management Procedures in Computer Programming for Apollo Interim Report

TH-64-222-1 MANAGEMENT PROCEDURES IN COMPUTER PROGRAMMING INTERIM REPORT November 30, 1364 W, M, Keese - Bellcomm, Incc B, If, W, J, LicbowltzMar*tin - Bellcomm, - Bellcomm, Inc, Inc, I, D, Nehama - Bellcomm, Inc, A. I{. Scheinman - Rellcomm, Inc, C, S, Sherrerd - Bellcomm, Inc, W, C, Dennis - Computer Sciences Corporation s, E, Fliege - Computer Sciences Corporation D. A, Jackson - Computer Sciences Corporation B, J, Thielen - Computer Sciences Corporation Work Performed for Manned Space Plight, National Aeronautics and Space Administration, as part of Task 22 under Contract NASW-417, BELLCOMM, INC. TABLE OF CONTENTS Abstract Table of Contents 1. Introduction- 2. Problems in Developing Computer Programs 2.1 Lack of Definitive Requirements 2.2 Complex Interface of Elements 2 . 3 Inadequate Quaiity 2.4 Inadequate Understanding of Th.e Pro- gramming Process 2.5 Inadequate Understanding of The Cost Elements 3. Management Tools for Computer Programming 3.1 Description of The Computer programming Process 3.1.1 Understanding The. Process , 3,1,2 The Elements of a Programming Svstern ~ . I 3.1.3 Types of Computer Programming Projects 3.1.4 The Phase6 of Problem Solution 1, Definition of System Requirements 2. Definition of Performance Specifications 3. Development of Program Design 4, Program Implementation 5, System Integration 6. Program Maintenance 3.2 Policies, Procedures, and Standards 3 a 2 1 Planning 1, Role of the Information Proces- sing Specialist in Planning 2. The Software System Baseline 3* Planning, Scheduling, and Cost Estimating 3,2,2 Development of* Program Production Procedures and Standards 1, Programming Procedures and Standards A, Program Design Bo Flow Diagramming C, Program Coding Do Program Desk Checking E, Program Assembly and Modifioation BELLCOMM, INC. F Program Testing Go Documenting 2, Configuration Management A, configuration Identification Ua Configuration Control C, Configuration Accounting Documentation Requirements 1, Documentation Related to Program Requirements A, Dcflnition of Software Requirements B, Software Performance Specifications C, Development of Program Deslpp (1) Computer Program System Design Specifications (2) Basic Programming Language Manual (3) Machine-Program Interfaces Specifications (4 1 Man-Machine Interfaces Specification 2, Documcrltation Related to Program Implementation A, Individual Program Coding Descriptions B, Self-Suf'ficicncy of the Program Listina~ ~~" Co Subprogrim Interrelationships Descriptions D,2 Progress Reports Software Testing 3.3 Writing of Contracts 3.301 Contract Clauses 1, Customer Furnished Items 2, Baseline Documentation 3, Implementation Procedures and Standards 4, Planning, Scheduling and Progress Reporting 5* Deliverable Items 6, Contract Reviews 70 Acceptance Tests 80 Milestone Dates 90 costs 1Oa Change Control ., . .. BELLCOMM. INC. 3,3,2 Phases of the Programming Process and the Contract 1, Definition of System Requirements 2, Definition of Performance Speci- fications 3" Development of Program Design 4, Program Implementation 5o Systems Integration 6, Program Maintenance 304 Monitoring and Control by Management 304,1 Introduction 3,4,2 Management-Support Functions and Organizations 1, Quality Assurance Group A, The Need for Quality Assurance in Software Development Bo Responsibilities of the Group (1) Monitoring (2) Testing C, Staffing D, Independence of the Group 2, Center Programming Group 3* NASA Headquarters Programming Group A, Administrative and Monitoring Functions Bo Computer Program Status and Requirements Reviews 3.h03 Example of an Integrated Management Structure 4, Conclusions 5. Future Effort Bibliography Glossary Appendix Table 1, sheets 1 through 6 Figure 1, sheets 1 through 4 Figure 2 Figure 3 Distribution List BELLCOMM, INC. ""-> ""-> ABSTRACT This report concludes that computer programming is a describ- able, orderly process having a determinable, predictable end product, It is susceptible to close management control at the NASA center level for the purpose of delivering usable programs on schedule within estimated costs, A set of management functions and procedures is proposed, which are submitted at this time as tentative recommendations, and which will ensure control over procurement and production of computer programs for Apollo, It is recommended that: 1, A mechanism be established for the identification of computer progratnming end items, and the reporting of milestone information be made to specified levels of management 2, The contract be used as the principal instrument of NASA control of procurement and production of computer programs; standard contractual clauses be developed to assure adherence to delivery costs, documentation and production requirements, '30 The function of quality control of computer programs be implemented at the NASA center level, Groups of information processing specialists be formed at the centers and headquarters to provide a source,of programming expertise to managemento 4, Managers at all levels of Project Apollo be made aware of the computer programming process so as to better understand the requirements and costs involved, 5,, Pertinent statistics related to the production of computer programs be collected and processed to provide criteria fop measuring contractor performance and estimating expected costs,, These proposals will be examined and developed in depth, and final recommendations made in forthcoming reports, BELLCOMM, INC. MANAGEMENT PROCEDURES IN COMPUTER PROGRAMMING FOR APOLLO INTERIM REPORT 1a 0 INTRODUCTION This is the first report on Task 22 undertaken by Bellcomm at . the request of the Director of the Apollo Program for the purpose of studying,, developing and recommending management procedures in computer programming for Apollo, The conditions which gave rise to this task can be summarized as follows : The utilization of computers in the Apollo Program -- consider- ing all the technical uses, iaeo, real-time and off-line, t.0 which they will be put -- represents a twenty- to fifty-fold increase compared to the previous manned space flight programs that will have been undertaken by NASA,, Experience from similar situations indicates, without exception, that the effects on costs, manpower and management resources associated with the pro- duction of the necessary computer programs will be greater by a factor of two to five compared to the corresponding effects associated with computer hardware One of the more serious problems created by the drastic in- creases in computer usage in the Apollo Program is the problem of technic,al management of computer programming, That NASA is not alone In facing this problem is attested by the vast amount / of literature on the subject from sources in government and industry+* The underlying cause seems to be that, while the management capability available in these agencies and industrial organizations is derived from long experience with hardware systems, the experience with computer “software” has been rela- tively small, * A bibliography of articles and books discussing problems associated with computer programming and programmers is given at the end of this report, I-. .”””-.- BELLCOMM, INC. Several factors contribute in compoundlng the problems asso- ciated with computer programming in Apollo, One factor is the size .of the effort involved. It has been estimated that a total of more than five million machine language instructions will hqve to be produced, Another factor is that responsibility for computer programs in Apollo is apread over four NASA Space Flight Centers: GSFC, KSC, MSC and MSFC, Eighteen operationaJ* programming systems associated with these Centers have been identified (see Table l), These programs do not constitute complete systems by themselves, but are intended to perform certain functions in conjunction with other systems for the accomplishment of a mission. The specification of requirements for these programs, perhaps the most. important initial step in tlfe process, is the responsibility o.f the "ultimate user" -- in general, not an information processing specialist -- in the Center. It is the thesis of this report that the problems of technical management of computer programming can be solved, and that work- ing, well-documented programs can be delivered on time within estimated costs; that management tools useful at the project level in the Centers can be developed and imp1emented.to insure control over production of computer programs; and that .'informa- tion reporting schemes can be established so that ma,nagement at a11 levels in NASA can be made aware of, and reac't to problems related to computer programming, The report includes a broad discussion of the major ordered activities and elements of the computer programming process involved in a large-scale programming effort, such as will be required in Apollo,' From this broad treatment, a number of tentative conclusions are drawn concerning the type of manage- ment procedures needed, and means of implementing them in the NASA environment. The concept of quality control in program- ming is also introduced, Some important management functions are described in terms of a hypothetical organization structure for purposes of illustration on,ly, and are not intended to be final recommendations at this time, The tentative conclusions presented in this report will be examined in detail in the continuing effort on this task, and recommendations will be made in a series of forthcoming reports, * For definitions of some of the special terms used in this report, see

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    68 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us