Get Free Shipping on orders over $79
Software Pioneers : Contributions to Software Engineering - Manfred.. Broy

Software Pioneers

Contributions to Software Engineering

By: Manfred.. Broy, Ernst Denert

eText | 6 December 2012 | Edition Number 1

At a Glance

eText


$239.00

or 4 interest-free payments of $59.75 with

 or 

Instant online reading in your Booktopia eTextbook Library *

Why choose an eTextbook?

Instant Access *

Purchase and read your book immediately

Read Aloud

Listen and follow along as Bookshelf reads to you

Study Tools

Built-in study tools like highlights and more

* eTextbooks are not downloadable to your eReader or an app and can be accessed via web browsers only. You must be connected to the internet and have no technical issues with your device or browser that could prevent the eTextbook from operating.
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.
on
Desktop
Tablet
Mobile

More in Software Engineering

The End of Leadership - Barbara Kellerman

eBOOK

The Ghidra Book, 2nd Edition : The Definitive Guide - Chris Eagle

eBOOK

The Developer's Guide to AI - Jacob Orshalick

eBOOK

RRP $81.32

$65.99

19%
OFF
Nuts 1 Programming - Mihigo ER Anaja

eBOOK