A lucid statement of the philosophy of modular programming can be found in a 1970 textbook on the design of system programs by Gouthier and Pont [1, l Cfl0. 23], which we quote below: A well-defined segmentation of the project effort ensures system modularity. Each task fonos a separate, distinct program module. At implementation time each module and its inputs and outputs are well-defined, there is no confusion in the intended interface with other system modules. At checkout time the in tegrity of the module is tested independently; there are few sche duling problems in synchronizing the completion of several tasks before checkout can begin. Finally, the system is maintained in modular fashion; system errors and deficiencies can be traced to specific system modules, thus limiting the scope of detailed error searching. Usually nothing is said about the criteria to be used in dividing the system into modules. This paper will discuss that issue and, by means of examples, suggest some criteria which can be used in decomposing a system into modules. A Brief Status Report The major advancement in the area of modular programming has been the development of coding techniques and assemblers which (1) allow one modu1e to be written with little knowledge of the code in another module, and (2) alJow modules to be reas sembled and replaced without reassembly of the whole system.
Le informazioni nella sezione "Riassunto" possono far riferimento a edizioni diverse di questo titolo.
From the reviews:
"Software Pioneers documents the proceedings of a celebration of software engineering held in Bonn, Germany, in June 2001. ... As a celebration of software engineering the book works well. It is fairly priced, and the contributions are mostly original, readable and insightful. It is beautifully produced on blued paper, lending a uniformity to the varied typefaces of the facsimile reproductions of historical documents." (Martin Campbell-Kelly, Times Higher Education Supplement, February, 2003)
"This book, coming with four DVDs, presents epochal works of 16 of the most influential software pioneers. ... The volume editors coherently integrated the historical contributions with current aspects and future perspectives. ... Together, the book and the four DVDs constitute a unique and major contribution to the history of software engineering." (www.amazon.de, December, 2002)
“This book is based on a conference that took place in 2001 ... . The speakers at the event ... included many of the most legendary names in the history of software development who were asked to reflect on their own pioneering contributions to software engineering in the 20th century. ... each of them address the conference with the added benefit of being able to re-read their lectures. This is a ‘must have’ resource for anyone ... interested in the history of computing.” (Sue Gee, I Programmer, February, 2009)Software Engineering — From Auxiliary to Key Technology.- The Relevance of the Software Pioneers for sd&m.- From the Stack Principle to ALGOL.- Sequentielle Formelübersetzung.- Verfahren zur automatischen Verarbeitung von kodierten Daten und Rechenmaschinen zur Ausübung des Verfahrens.- The Roots of Object Orientation: The Simula Language.- Class and Subclass Declarations.- Pascal and Its Successors.- The Programming Language Pascal.- Program Development by Stepwise Refinement.- The IBM Operating System/360.- The Functional Structure of OS/360.- Graphical User Interfaces.- B-Trees and Databases, Past and Future.- Organization and Maintenance of Large Ordered Indexes.- A Relational Model of Data for Large Shared Data Banks.- Entity-Relationship Modeling: Historical Events Future Trends and Lessons Learned.- The Entity Relationship Model — Toward a Unified View of Data.- EWD 1308: What Led to “Notes on Structured Programming”.- Solution of a Problem in Concurrent Programming Control.- Go To Statement Considered Harmful.- Assertions: A Personal Perspective.- An Axiomatic Basis for Computer Programming.- Proof of Correctness of Data Representations.- The Secret History of information Hiding.- On the Criteria to Be Used in Decomposing Systems into Modules.- On a “Buzzword”: Hierarchical Structure.- Abstract Data Types, Then and Now.- Abstract Data Types and the Development of Data Structures.- JSP in Perspective.- Constructive Methods of Program Design.- Structured Analysis: Beginnings of a New Discipline.- Structure Analysis and System Specification.- A History of Software Inspections.- Design and Code Inspections to Reduce Errors in Program Development.- Advances in Software Inspections.- Early Experiences in Software Economics.- Software Engineering Economics.- Design Patterns — Ten Years Later.- Design Patterns: Abstraction and Reuse of Object-Oriented Design.
Le informazioni nella sezione "Su questo libro" possono far riferimento a edizioni diverse di questo titolo.
Da: Versandbuchhandlung Kisch & Co., Fürstenberg OT Blumenow, Germania
Taschenbuch. Condizione: Wie neu. Gebraucht - Wie neu Ungelesen, vollständig, sehr guter Zustand, leichte Lagerspuren, als Mängelexemplar gekennzeichnet -A lucid statement of the philosophy of modular programming can be found in a 1970 textbook on the design of system programs by Gouthier and Pont [1, l Cfl0. 23], which we quote below: A well-defined segmentation of the project effort ensures system modularity. Each task fonos a separate, distinct program module. At implementation time each module and its inputs and outputs are well-defined, there is no confusion in the intended interface with other system modules. At checkout time the in tegrity of the module is tested independently; there are few sche duling problems in synchronizing the completion of several tasks before checkout can begin. Finally, the system is maintained in modular fashion; system errors and deficiencies can be traced to specific system modules, thus limiting the scope of detailed error searching. Usually nothing is said about the criteria to be used in dividing the system into modules. This paper will discuss that issue and, by means of examples, suggest some criteria which can be used in decomposing a system into modules. A Brief Status Report The major advancement in the area of modular programming has been the development of coding techniques and assemblers which (1) allow one modu1e to be written with little knowledge of the code in another module, and (2) alJow modules to be reas sembled and replaced without reassembly of the whole system. 732 pp. Englisch. Codice articolo INF1100466435
Quantità: 1 disponibili
Da: Che & Chandler Versandbuchhandlung, Fürstenberg OT Blumenow, Germania
Taschenbuch. Condizione: Wie neu. Gebraucht - Wie neu Ungelesen, vollständig, sehr guter Zustand, leichte Lagerspuren, als Mängelexemplar gekennzeichnet -A lucid statement of the philosophy of modular programming can be found in a 1970 textbook on the design of system programs by Gouthier and Pont [1, l Cfl0. 23], which we quote below: A well-defined segmentation of the project effort ensures system modularity. Each task fonos a separate, distinct program module. At implementation time each module and its inputs and outputs are well-defined, there is no confusion in the intended interface with other system modules. At checkout time the in tegrity of the module is tested independently; there are few sche duling problems in synchronizing the completion of several tasks before checkout can begin. Finally, the system is maintained in modular fashion; system errors and deficiencies can be traced to specific system modules, thus limiting the scope of detailed error searching. Usually nothing is said about the criteria to be used in dividing the system into modules. This paper will discuss that issue and, by means of examples, suggest some criteria which can be used in decomposing a system into modules. A Brief Status Report The major advancement in the area of modular programming has been the development of coding techniques and assemblers which (1) allow one modu1e to be written with little knowledge of the code in another module, and (2) alJow modules to be reas sembled and replaced without reassembly of the whole system. 732 pp. Englisch. Codice articolo INF1100466435
Quantità: 1 disponibili
Da: Brook Bookstore On Demand, Napoli, NA, Italia
Condizione: new. Questo è un articolo print on demand. Codice articolo L4GQZKFEJM
Quantità: Più di 20 disponibili
Da: BuchWeltWeit Ludwig Meier e.K., Bergisch Gladbach, Germania
Taschenbuch. Condizione: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware -A lucid statement of the philosophy of modular programming can be found in a 1970 textbook on the design of system programs by Gouthier and Pont [1, l Cfl0. 23], which we quote below: A well-defined segmentation of the project effort ensures system modularity. Each task fonos a separate, distinct program module. At implementation time each module and its inputs and outputs are well-defined, there is no confusion in the intended interface with other system modules. At checkout time the in tegrity of the module is tested independently; there are few sche duling problems in synchronizing the completion of several tasks before checkout can begin. Finally, the system is maintained in modular fashion; system errors and deficiencies can be traced to specific system modules, thus limiting the scope of detailed error searching. Usually nothing is said about the criteria to be used in dividing the system into modules. This paper will discuss that issue and, by means of examples, suggest some criteria which can be used in decomposing a system into modules. A Brief Status Report The major advancement in the area of modular programming has been the development of coding techniques and assemblers which (1) allow one modu1e to be written with little knowledge of the code in another module, and (2) alJow modules to be reas sembled and replaced without reassembly of the whole system. 728 pp. Englisch. Codice articolo 9783642639708
Quantità: 2 disponibili
Da: moluna, Greven, Germania
Condizione: New. Dieser Artikel ist ein Print on Demand Artikel und wird nach Ihrer Bestellung fuer Sie gedruckt. Unique collection of historically significant papers in software engineeringDescription of the software pioneers and of their workContributions from a prospective of todayA lucid statement of the philosophy of modular programming can be found in. Codice articolo 5066230
Quantità: Più di 20 disponibili
Da: Ria Christie Collections, Uxbridge, Regno Unito
Condizione: New. In English. Codice articolo ria9783642639708_new
Quantità: Più di 20 disponibili
Da: GreatBookPrices, Columbia, MD, U.S.A.
Condizione: New. Codice articolo 21683485-n
Quantità: 15 disponibili
Da: GreatBookPrices, Columbia, MD, U.S.A.
Condizione: As New. Unread book in perfect condition. Codice articolo 21683485
Quantità: 15 disponibili
Da: preigu, Osnabrück, Germania
Taschenbuch. Condizione: Neu. Software Pioneers | Contributions to Software Engineering | Manfred Broy (u. a.) | Taschenbuch | iv | Englisch | 2014 | Springer | EAN 9783642639708 | Verantwortliche Person für die EU: Springer Verlag GmbH, Tiergartenstr. 17, 69121 Heidelberg, juergen[dot]hartmann[at]springer[dot]com | Anbieter: preigu. Codice articolo 111013988
Quantità: 5 disponibili
Da: AHA-BUCH GmbH, Einbeck, Germania
Taschenbuch. Condizione: Neu. Druck auf Anfrage Neuware - Printed after ordering - A lucid statement of the philosophy of modular programming can be found in a 1970 textbook on the design of system programs by Gouthier and Pont [1, l Cfl0. 23], which we quote below: A well-defined segmentation of the project effort ensures system modularity. Each task fonos a separate, distinct program module. At implementation time each module and its inputs and outputs are well-defined, there is no confusion in the intended interface with other system modules. At checkout time the in tegrity of the module is tested independently; there are few sche duling problems in synchronizing the completion of several tasks before checkout can begin. Finally, the system is maintained in modular fashion; system errors and deficiencies can be traced to specific system modules, thus limiting the scope of detailed error searching. Usually nothing is said about the criteria to be used in dividing the system into modules. This paper will discuss that issue and, by means of examples, suggest some criteria which can be used in decomposing a system into modules. A Brief Status Report The major advancement in the area of modular programming has been the development of coding techniques and assemblers which (1) allow one modu1e to be written with little knowledge of the code in another module, and (2) alJow modules to be reas sembled and replaced without reassembly of the whole system. Codice articolo 9783642639708
Quantità: 2 disponibili