DOCSLIB.ORG

NATO Software Engineering Conference. Garmisch, Germany

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
NATO Software Engineering Conference. Garmisch, Germany SOFTWARE ENGINEERING Report on a conference sponsored by the NATO SCIENCE COMMITTEE Garmisch, Germany, 7th to 11th October 1968 Chairman: Professor Dr. F. L. Bauer Co-chairmen: Professor L. Bolliet, Dr. H. J. Helms Editors: Peter Naur and Brian Randell January 1969 2 2 The present report is available from: Scientific Affairs Division NATO Brussels 39 Belgium Note for the current edition: The version of this report that you are reading was prepared by scan- ning the original edition, conversion to text through OCR, and then reformatting. Every effort has been made to do this as accurately as possible. However, it is almost certain that some errors have crept in despite best efforts. One of the problems was that the OCR software used kept trying to convert the original British spellings of words like ‘realise’ to the American spelling ‘realize’ and made other stupid mistakes. Whenever the OCR program was unsure of a reading, it called it to the attention of the operator, but there were a number of occasions in which it was sure, but wrong. Not all of these instances are guaranteed to have been caught. Although the editor tried to conform to the original presentation, certain changes were necessary, such as pagination. In order that the original Table of Contents and Indices would not have to be recalculated, an artifice was used. That is the original page breaks are indicated in the text thusly: 49 indicates that this is the point at which page 49 began in the original edition. If two such indicators appear together, this shows that there was a blank page in the original. The figures have been redrawn to improve legibility. The original size and scale was not changed. In order to accommodate the new pagination, the figures may have been shifted slightly from their position in the original document. Finally, it should be noted that the effort required to produce the current edition was a tiny fraction of the effort required for the original. The current editor therefore wants to express his apprecia- tion to the original editors, Peter Naur and Brian Randell, for producing what was clearly a land- mark effort in the Software Engineering field. Robert M. McClure Arizona 2001 NATO SOFTWARE ENGINEERING CONFERENCE 1968 3 3 HIGHLIGHTS The present report is concerned with a problem crucial to the use of computers, viz. the so-called software, or pro- grams, developed to control their action. The report summarises the discussions at a Working Conference on Software Engineering, sponsored by the NATO Science Committee. The Conference was attended by more than fifty people, from eleven different countries, all concerned professionally with software, either as users, manufacturers, or teachers at universities. The discussions cover all aspects of software including • relation of software to the hardware of computers • design of software • production, or implementation of software • distribution of software • service on software. By including many direct quotations and exchanges of opinion, the report reflects the lively controversies of the original discussion. Although much of the discussions were of a detailed technical nature, the report also contains sections reporting on discussions which will be of interest to a much wider audience. This holds for subjects like • the problems of achieving sufficient reliability in the data systems which are becoming increasingly integrated into the central activities of modern society • the difficulties of meeting schedules and specifications on large software projects • the education of software (or data systems) engineers • the highly controversial question of whether software should be priced separately from hardware. Thus, while the report is of particular concern to the immediate users of computers and to computer manufacturers, many points may serve to enlighten and warn policy makers at all levels. Readers from the wider audience should note, however, that the conference was concentrating on the basic issues and key problems in the critical areas of software engineering. It therefore did not attempt to provide a balanced review of the total state of software, and tends to understress the achievements of the field. NATO SOFTWARE ENGINEERING CONFERENCE 1968 4 4 5 CONTENTS HIGHLIGHTS . 3 CONTENTS . 5 PREFACE . .9 1. BACKGROUND OF CONFERENCE . 13 2. SOFTWARE ENGINEERING AND SOCIETY . 19 3.1. THE NATURE OF SOFTWARE ENGINEERING . 19 3.2. SOFTWARE ENGINEERING MANAGEMENT AND METHODOLOGY . 24 3.3. DESIGN AND PRODUCTION IN SOFTWARE ENGINEERING . 32 4. DESIGN . 35 4.1. INTRODUCTION . 35 4.1.1. Sources of techniques . 35 4.1.2. Need for hardware based on program structure . 35 4.1.3. Relation to mathematics . 37 4.2. DESIGN CRITERIA . 38 4.2.1. Genera design criteria . 38 4.2.2. User requirements . 40 4.2.3. Reliability and design . 44 4.2.4. Logical completeness . 44 4.3. DESIGN STRATEGIES AND TECHNIQUES . 45 4.3.1. Sequencing the design process . 45 4.3.2. Structuring the design . 50 4.3.3. Feedback through monitoring and simulation . 53 4.3.4. High-level languages . 55 4.4. COMMUNICATION AND MANAGEMENT IN DESIGN . 59 5. PRODUCTION . 65 5.1. INTRODUCTION . 65 5.1.1. The problems of scale . 65 5.1.2. The problems of reliability . 70 5.2 PRODUCTION — MANAGEMENT ASPECTS . 72 5.2.1. Production planning . 72 5.2.2. Personnel factors . 83 5.2.3. Production control . 86 5.2.4. Internal communication . 89 6 5.3. PRODUCTION — TECHNICAL ASPECTS . 93 5.3.1. Tools . .93 5.3.2. Concepts . 96 5.3.3. Performance monitoring . 99 6. SERVICE . 103 6.1. INTRODUCTION . 103 6.1.1. The virtue of realistic goals . 103 6.1.2. Initial system release . 103 6.1.3. Frequency of releases . 104 6.1.4. Responsibility for modified systems . 106 6.2. REPLICATION, DISTRIBUTION AND MAINTENANCE . 107 6.2.1. Replication . 107 NATO SOFTWARE ENGINEERING CONFERENCE 1968 5 6.2.2. Distribution . 109 6.2.3. Maintenance . 110 6.3. SYSTEM EVALUATION . 112 6.3.1. Acceptance testing . 113 6.3.2. Performance monitoring . 114 6.4. FEEDBACK TO MANUFACTURERS FROM USERS . 115 6.5. DOCUMENTATION . 116 6.6. REPROGRAMMING . 117 7. SPECIAL TOPICS . 119 7.1. SOFTWARE: THE STATE OF THE ART . 119 7.1.1. Introduction . 119 7.1.2. Problem areas . ..
Load more

Recommended publications
  • 1 Oral History Interview with Brian Randell January 7, 2021 Via Zoom
    Oral History Interview with Brian Randell January 7, 2021 Via Zoom Conducted by William Aspray Charles Babbage Institute 1 Abstract Brian Randell tells about his upbringing and his work at English Electric, IBM, and Newcastle University. The primary topic of the interview is his work in the history of computing. He discusses his discovery of the Irish computer pioneer Percy Ludgate, the preparation of his edited volume The Origins of Digital Computers, various lectures he has given on the history of computing, his PhD supervision of Martin Campbell-Kelly, the Computer History Museum, his contribution to the second edition of A Computer Perspective, and his involvement in making public the World War 2 Bletchley Park Colossus code- breaking machines, among other topics. This interview is part of a series of interviews on the early history of the history of computing. Keywords: English Electric, IBM, Newcastle University, Bletchley Park, Martin Campbell-Kelly, Computer History Museum, Jim Horning, Gwen Bell, Gordon Bell, Enigma machine, Curta (calculating device), Charles and Ray Eames, I. Bernard Cohen, Charles Babbage, Percy Ludgate. 2 Aspray: This is an interview on the 7th of January 2021 with Brian Randell. The interviewer is William Aspray. We’re doing this interview via Zoom. Brian, could you briefly talk about when and where you were born, a little bit about your growing up and your interests during that time, all the way through your formal education? Randell: Ok. I was born in 1936 in Cardiff, Wales. Went to school, high school, there. In retrospect, one of the things I missed out then was learning or being taught Welsh.
    [Show full text]
  • Computing Versus Human Thinking
    By Peter Naur, recipient of ACM’s 2005 A.M. Turing Award Computing Versus Human Thinking n this presentation I shall give you an overview of efforts. Indeed, I have found that a large part of what Imy works from the past fifty years concerning the is currently said about human thinking and about sci- issue given in the title. Concerning this title I entific and scholarly activity is false and harmful to invite you to note particularly the middle word, ‘ver- our understanding. I realize that my presentation of sus’. This word points to the tendency of my efforts some of these issues may be offensive to you. This I around this theme, to wit, to clarify the contrast regret, but it cannot be avoided. between the two items, computing and human thinking. This tendency of my work has found its DESCRIPTION AS THE CORE ISSUE OF SCIENCE AND ultimate fulfilment in my latest result, which is a SCHOLARSHIP description of the nervous system showing that this The tone of critique and rejection of established system has no similarity whatever to a computer. ideas has its roots in my earliest activity, from its very It is ironic that my present award lecture is given beginning more than fifty years ago. Already in my under the title of Turing. As a matter of fact, one part work in astronomy, around 1955, a decisive item in of my work concerning computing and human think- my awareness came from Bertrand Russell’s explicit ing has been an explicit critique, or rejection, of the rejection of any notion of cause as a central issue of ideas of one prominent contribution from Alan Tur- scientific work.
    [Show full text]
  • A Politico-Social History of Algolt (With a Chronology in the Form of a Log Book)
    A Politico-Social History of Algolt (With a Chronology in the Form of a Log Book) R. w. BEMER Introduction This is an admittedly fragmentary chronicle of events in the develop­ ment of the algorithmic language ALGOL. Nevertheless, it seems perti­ nent, while we await the advent of a technical and conceptual history, to outline the matrix of forces which shaped that history in a political and social sense. Perhaps the author's role is only that of recorder of visible events, rather than the complex interplay of ideas which have made ALGOL the force it is in the computational world. It is true, as Professor Ershov stated in his review of a draft of the present work, that "the reading of this history, rich in curious details, nevertheless does not enable the beginner to understand why ALGOL, with a history that would seem more disappointing than triumphant, changed the face of current programming". I can only state that the time scale and my own lesser competence do not allow the tracing of conceptual development in requisite detail. Books are sure to follow in this area, particularly one by Knuth. A further defect in the present work is the relatively lesser availability of European input to the log, although I could claim better access than many in the U.S.A. This is regrettable in view of the relatively stronger support given to ALGOL in Europe. Perhaps this calmer acceptance had the effect of reducing the number of significant entries for a log such as this. Following a brief view of the pattern of events come the entries of the chronology, or log, numbered for reference in the text.
    [Show full text]
  • An Early Program Proof by Alan Turing F
    An Early Program Proof by Alan Turing F. L. MORRIS AND C. B. JONES The paper reproduces, with typographical corrections and comments, a 7 949 paper by Alan Turing that foreshadows much subsequent work in program proving. Categories and Subject Descriptors: 0.2.4 [Software Engineeringj- correctness proofs; F.3.1 [Logics and Meanings of Programs]-assertions; K.2 [History of Computing]-software General Terms: Verification Additional Key Words and Phrases: A. M. Turing Introduction The standard references for work on program proofs b) have been omitted in the commentary, and ten attribute the early statement of direction to John other identifiers are written incorrectly. It would ap- McCarthy (e.g., McCarthy 1963); the first workable pear to be worth correcting these errors and com- methods to Peter Naur (1966) and Robert Floyd menting on the proof from the viewpoint of subse- (1967); and the provision of more formal systems to quent work on program proofs. C. A. R. Hoare (1969) and Edsger Dijkstra (1976). The Turing delivered this paper in June 1949, at the early papers of some of the computing pioneers, how- inaugural conference of the EDSAC, the computer at ever, show an awareness of the need for proofs of Cambridge University built under the direction of program correctness and even present workable meth- Maurice V. Wilkes. Turing had been writing programs ods (e.g., Goldstine and von Neumann 1947; Turing for an electronic computer since the end of 1945-at 1949). first for the proposed ACE, the computer project at the The 1949 paper by Alan M.
    [Show full text]
  • Internet Engineering Jan Nikodem, Ph.D. Software Engineering
    Internet Engineering Jan Nikodem, Ph.D. Software Engineering Theengineering paradigm Software Engineering Lecture 3 The term "software crisis" was coined at the first NATO Software Engineering Conference in 1968 by: Friedrich. L. Bauer Nationality;German, mathematician, theoretical physicist, Technical University of Munich Friedrich L. Bauer 1924 3/24 The term "software crisis" was coined at the first NATO Software Engineering Conference in 1968 by: Peter Naur Nationality;Dutch, astronomer, Regnecentralen, Niels Bohr Institute, Technical University of Denmark, University of Copenhagen. Peter Naur 1928 4/24 Whatshouldbe ourresponse to software crisis which provided with too little quality, too late deliver and over budget? Nationality;Dutch, astronomer, Regnecentralen, Niels Bohr Institute, Technical University of Denmark, University of Copenhagen. Peter Naur 1928 5/24 Software should following an engineering paradigm NATO conference in Garmisch-Partenkirchen, 1968 Peter Naur 1928 6/24 The hope is that the progress in hardware will cure all software ills. The Oberon System User Guide and Programmer's Manual. ACM Press Nationality;Swiss, electrical engineer, computer scientist ETH Zürich, IBM Zürich Research Laboratory, Institute for Media Communications Martin Reiser 7/24 However, a critical observer may notethat software manages to outgrow hardware in size and sluggishness. The Oberon System User Guide and Programmer's Manual. ACM Press Nationality;Swiss, electrical engineer, computer scientist ETH Zürich, IBM Zürich Research Laboratory, Institute for Media Communications Martin Reiser 8/24 Wirth's computing adage Software is getting slower more rapidly than hardware becomes faster. Nationality;Swiss, electronic engineer, computer scientist ETH Zürich, University of California, Berkeley, Stanford University University of Zurich. Xerox PARC.
    [Show full text]
  • The Roots of Software Engineering*
    THE ROOTS OF SOFTWARE ENGINEERING* Michael S. Mahoney Princeton University (CWI Quarterly 3,4(1990), 325-334) At the International Conference on the History of Computing held in Los Alamos in 1976, R.W. Hamming placed his proposed agenda in the title of his paper: "We Would Know What They Thought When They Did It."1 He pleaded for a history of computing that pursued the contextual development of ideas, rather than merely listing names, dates, and places of "firsts". Moreover, he exhorted historians to go beyond the documents to "informed speculation" about the results of undocumented practice. What people actually did and what they thought they were doing may well not be accurately reflected in what they wrote and what they said they were thinking. His own experience had taught him that. Historians of science recognize in Hamming's point what they learned from Thomas Kuhn's Structure of Scientific Revolutions some time ago, namely that the practice of science and the literature of science do not necessarily coincide. Paradigms (or, if you prefer with Kuhn, disciplinary matrices) direct not so much what scientists say as what they do. Hence, to determine the paradigms of past science historians must watch scientists at work practicing their science. We have to reconstruct what they thought from the evidence of what they did, and that work of reconstruction in the history of science has often involved a certain amount of speculation informed by historians' own experience of science. That is all the more the case in the history of technology, where up to the present century the inventor and engineer have \*-as Derek Price once put it\*- "thought with their fingertips", leaving the record of their thinking in the artefacts they have designed rather than in texts they have written.
    [Show full text]
  • Structured Programming A.P.I.C
    ¢ . , v'~.1 c: STRUCTURED PROGRAMMING A.P.I.C. Studies in Data Processing General Editor: C. A. R. Hoare 1. Some Commercial Autocodes. A Comparative Study E. L. WiUey, A. d'Agapeyeff, Marion Tribe, B. J. Gibbens and Michelle Clarke. 2. A Primer of ALGOL 60 Programming E. W. Dijkstra 3. Input Language for Automatic Programming A. P. Yershov, G. I. Kozhukhin and U. Voloshin 4. Introduction to System Programming Edited by Peter Wegner 5. ALGOL 60 Implementation. The translation and use of Algol 60 Programs on a Computer B. RandeU and L. J. Russell 6. Dictionary for Computer Languages Hans Breuer 7. The Alpha Automatic Programming System Edited by A. P. Yershov 8. Structured Programming O.-J. Dahl, E. W. Dijkstra and C. A. R. Hoare In preparation Operating Systems Techniques Edited by C. A. R. Hoare and R. H. Perrott A.P.I.C. Studies in Data Processing No. 8 STRUCTURED PROGRAMMING O.-J. DAHL Universitet i Oslo, Matematisk Institut, Blindern, Oslo, Norway E. W. DIJKSTRA Department of Mathematics, Technological University, Eindhoven, The Netherlands C. A. R. HOARE Department of Computer Science, The Queen's University of Belfast, Belfast, Northern Ireland 1972 ACADEMIC PRESS LONDON AND NEW YORK ACADEMIC PRESS INC. (LONDON) LTD. 24]28 Oval Road, London NW1 United States Edition published by ACADEMIC PRESS INC. 111 Fifth Avenue New York, New York 10003 Copyright © 1972 by ACADEMIC PRESS INC. (LONDON) LTD. Second printing 1973 All Rights Reserved No part of this book may be reproduced in any form by photostat, microfilm, or any other means, without written permission from the publishers Library of Congress Catalog Card Number: 72-84452 ISBN: 0--12-200550-3 PRINTED IN GREAT BRITAIN BY WHITSTABLE LITHO~ STRAKER BROTHERS LTD.
    [Show full text]
  • Ebook Download Pluralism in Software Engineering : Turing
    PLURALISM IN SOFTWARE ENGINEERING : TURING AWARD WINNER PETER NAUR EXPLAINS PDF, EPUB, EBOOK Edgar G Daylight | 134 pages | 19 Oct 2011 | Lonely Scholar | 9789491386008 | English | none Pluralism in Software Engineering : Turing Award Winner Peter Naur Explains PDF Book Ludwig Wittgenstein, by contrast, opposed a rational metaphysical view to our now digital world. By penetrating deeply into the research of William James, Naur gradually developed his own theory of how mental life is like at the neural level of the nervous system. Peter Straub Books. In he received his PhD in astronomy and in he joined the staff of Regnecentralen, specializing in high-level programming languages. Proteomics 14 , , Sort order. Refresh and try again. People in the automotive industry who have patience with my philosophical reflections often end up falling into Dreyfus's trap by saying the following:. Packaging should be the same as what is found in a retail store, unless the item is handmade or was packaged by the manufacturer in non-retail packaging, such as an unprinted box or plastic bag. The flight management system for an Airbus A is software. Want to Read saving…. Lists with This Book. Todos tus libros Pluralism in Software Engineering. Our general desire to make AI more aware of the world as a whole instead of a set of rules notwithstanding, let's remember that adding rules to the training set for every new situation is more or less what happened with evolution. Steven Chang marked it as to-read Nov 18, Help Privacy Terms. Friday, July 24, Available from Amazon and many other stores.
    [Show full text]
  • A Purdue University Course in the History of Computing
    Purdue University Purdue e-Pubs Department of Computer Science Technical Reports Department of Computer Science 1991 A Purdue University Course in the History of Computing Saul Rosen Report Number: 91-023 Rosen, Saul, "A Purdue University Course in the History of Computing" (1991). Department of Computer Science Technical Reports. Paper 872. https://docs.lib.purdue.edu/cstech/872 This document has been made available through Purdue e-Pubs, a service of the Purdue University Libraries. Please contact [email protected] for additional information. A PURDUE UNIVERSITY COURSE IN mE HISTORY OF COMPUTING Saul Rosen CSD-TR-91-023 Mrrch 1991 A Purdue University Course in the History of Computing Saul Rosen CSD-TR-91-023 March 1991 Abstract University COUISes in the history of computing are still quite rarc. This paper is a discussion of a one-semester course that I have taught during the past few years in the Department of Computer Sciences at Purdue University. The amount of material that could be included in such a course is overwhelming, and the literature in the subject has increased at a great rate in the past decade. A syllabus and list of major references are presented here as they are presented to the students. The course develops a few major themes, several of which arc discussed briefly in the paper. The coume has been an interesting and stimulating experience for me. and for some of the students who took the course. I do not foresee a rapid expansion in the number of uniVcCiities that will offer courses in the history of computing.
    [Show full text]
  • Boolean Matrix in the Matrix Equation (19)
    General Disclaimer One or more of the Following Statements may affect this Document This document has been reproduced from the best copy furnished by the organizational source. It is being released in the interest of making available as much information as possible. This document may contain data, which exceeds the sheet parameters. It was furnished in this condition by the organizational source and is the best copy available. This document may contain tone-on-tone or color graphs, charts and/or pictures, which have been reproduced in black and white. This document is paginated as submitted by the original source. Portions of this document are not fully legible due to the historical nature of some of the material. However, it is the best reproduction available from the original submission. Produced by the NASA Center for Aerospace Information (CASI) C f I l 1 ^o } Technical Report 69-86 March 1969 Design Automation by the Computer Design Language by Yaohan Cho Professor fr N he computer time used was supported by the National Aeronautics and Space Administration under Grant NsO 398 to the Computer Science Center of the University of Maryland. /i Abstract A Computer Design Language (CDL) has been developed for facilitating design automation of digital computers. When the functional organizatl.on and sequential operation of a digital computer are conceived and specified by the CDL, this d CDL description is called a Macro design. The macro design is highly descriptive in computer elements. it describes precisely and concisely what the computer is expected to do functionally step by step.
    [Show full text]
  • Halting Problems: a Historical Reading of a Paradigmatic Computer Science Problem
    PROGRAMme Autumn workshop 2018, Bertinoro L. De Mol Halting problems: a historical reading of a paradigmatic computer science problem Liesbeth De Mol1 and Edgar G. Daylight2 1 CNRS, UMR 8163 Savoirs, Textes, Langage, Universit´e de Lille, [email protected] 2 Siegen University, [email protected] 1 PROGRAMme Autumn workshop 2018, Bertinoro L. De Mol and E.G. Daylight Introduction (1) \The improbable symbolism of Peano, Russel, and Whitehead, the analysis of proofs by flowcharts spearheaded by Gentzen, the definition of computability by Church and Turing, all inventions motivated by the purest of mathematics, mark the beginning of the computer revolution. Once more, we find a confirmation of the sentence Leonardo jotted despondently on one of those rambling sheets where he confided his innermost thoughts: `Theory is the captain, and application the soldier.' " (Metropolis, Howlett and Rota, 1980) Introduction 2 PROGRAMme Autumn workshop 2018, Bertinoro L. De Mol and E.G. Daylight Introduction (2) Why is this `improbable' symbolism considered relevant in comput- ing? ) Different non-excluding answers... 1. (the socio-historical answers) studying social and institutional developments in computing to understand why logic, or, theory, was/is considered to be the captain (or not) e.g. need for logic framed in CS's struggle for disciplinary identity and independence (cf (Tedre 2015)) 2. (the philosophico-historical answers) studying history of computing on a more technical level to understand why and how logic (or theory) are in- troduced in the computing practices { question: is there something to com- puting which makes logic epistemologically relevant to it? ) significance of combining the different answers (and the respective approaches they result in) ) In this talk: focus on paradigmatic \problem" of (theoretical) computer science { the halting problem Introduction 3 PROGRAMme Autumn workshop 2018, Bertinoro L.
    [Show full text]
  • Niels Ivar Bech
    Niels Ivar Bech Born 1920 Lemvig, Denmark; died 1975; originator of Danish computer development. Niels Ivar Bech was one of Europe's most creative leaders in the field of electronic digital computers.1 He originated Danish computer development under the auspices of the Danish Academy of Technical Sciences and was first managing director of its subsidiary, Regnecentralen, which was Denmark's (and one of Europe's) first independent designer and builder of electronic computers. Bech was born in 1920 in Lemvig, a small town in the northwestern corner of Jutland, Denmark; his schooling ended with his graduation from Gentofte High School (Statsskole) in 1940. Because he had no further formal education, he was not held in as high esteem as he deserved by some less gifted people who had degrees or were university professors. During the war years, Bech was a teacher. When Denmark was occupied by the Nazis, he became a runner for the distribution of illegal underground newspapers, and on occasion served on the crews of the small boats that perilously smuggled Danish Jews across the Kattegat to Sweden. After the war, from 1949 to 1957, he worked as a calculator in the Actuarial Department of the Copenhagen Telephone Company (Kobenhavns Telefon Aktieselskab, KTA). The Danish Academy of Technical Sciences established a committee on electronic computing in 1947, and in 1952 the academy obtained free access to the complete design of the computer BESK (Binar Electronisk Sekevens Kalkylator) being built in Stockholm by the Swedish Mathematical Center (Matematikmaskinnamndens Arbetsgrupp). In 1953 the Danish academy founded a nonprofit computer subsidiary, Regnecentralen.
    [Show full text]