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 w… Mehr…
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. Books > Computer Science eBook, Springer Shop<
Springer.com
new in stock. Versandkosten:zzgl. Versandkosten. Details...
(*) Derzeit vergriffen bedeutet, dass dieser Titel momentan auf keiner der angeschlossenen Plattform verfügbar ist.
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 w… Mehr…
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. COMPUTERS,Software Development & Engineering,General, eBooks.com<
ebooks.com
new in stock. Versandkosten:zzgl. Versandkosten. Details...
(*) Derzeit vergriffen bedeutet, dass dieser Titel momentan auf keiner der angeschlossenen Plattform verfügbar ist.
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 w… Mehr…
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., Springer<
Springer.com
Nr. 978-3-642-59412-0. Versandkosten:Worldwide free shipping, , DE. (EUR 0.00) Details...
(*) Derzeit vergriffen bedeutet, dass dieser Titel momentan auf keiner der angeschlossenen Plattform verfügbar ist.
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 w… Mehr…
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. Books > Computer Science eBook, Springer Shop<
- new in stock. Versandkosten:zzgl. Versandkosten.
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 w… Mehr…
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. COMPUTERS,Software Development & Engineering,General, eBooks.com<
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 w… Mehr…
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., Springer<
Nr. 978-3-642-59412-0. Versandkosten:Worldwide free shipping, , DE. (EUR 0.00)
1Da einige Plattformen keine Versandkonditionen übermitteln und diese vom Lieferland, dem Einkaufspreis, dem Gewicht und der Größe des Artikels, einer möglichen Mitgliedschaft der Plattform, einer direkten Lieferung durch die Plattform oder über einen Drittanbieter (Marketplace), etc. abhängig sein können, ist es möglich, dass die von eurobuch angegebenen Versandkosten nicht mit denen der anbietenden Plattform übereinstimmen.
EAN (ISBN-13): 9783642594120 Erscheinungsjahr: 2012 Herausgeber: Springer Berlin Heidelberg
Buch in der Datenbank seit 2017-05-10T00:15:28+02:00 (Berlin) Detailseite zuletzt geändert am 2023-11-27T07:18:55+01:00 (Berlin) ISBN/EAN: 9783642594120
ISBN - alternative Schreibweisen: 978-3-642-59412-0 Alternative Schreibweisen und verwandte Suchbegriffe: Autor des Buches: ernst manfred, broy, ernst ber Titel des Buches: pioneers, software
Daten vom Verlag:
Autor/in: Manfred Broy Titel: Software Pioneers - Contributions to Software Engineering Verlag: Springer; Springer Berlin 728 Seiten Erscheinungsjahr: 2012-12-06 Berlin; Heidelberg; DE Gedruckt / Hergestellt in Deutschland. Sprache: Englisch 154,00 € (DE)
EA; E107; eBook; Nonbooks, PBS / Informatik, EDV/Informatik; Software Engineering; Verstehen; Software Engineering; data structure; data structures; design; documentation; formal methods; history of computing; modeling; obejct technology; operating system; program analysis; programming; programming languages; software architecture; structured analysis; B; Software Engineering/Programming and Operating Systems; History of Computing; History of Science; Software Engineering; Programming Techniques; Programming Languages, Compilers, Interpreters; Software Engineering; History of Computing; History of Science; Programming Techniques; Compilers and Interpreters; Computer Science; Informatik und Informationstechnologie; Technikgeschichte; Geschichte der Naturwissenschaften; Computerprogrammierung und Softwareentwicklung; Compiler und Übersetzer; SA
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.
Weitere, andere Bücher, die diesem Buch sehr ähnlich sein könnten:
