Software Pioneers

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.

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.

Captures where we are today through a tour of yesterday's achievements to help us better understand the evolution of computing technology. This book recounts the experiences of those who formed and functioned in the "Pioneering Era" of Software. In the Beginning: Recollections of Software Pioneers records the stories of computing's past enabling today's professionals to improve on the realities of yesterday. The stories in this book clearly show modern concepts, such as data abstraction, modularity, and structured approaches, date much earlier in the field than their appearance in academic literature. These stories help capture the true evolution. The book illustrates human experiences and industry turning points through personal recollections by the pioneers...people like Barry Boehm, Peter Denning, Watts Humphrey, Frank Land, and a dozen others.

Regarding the controversial and thought-provoking assessments in this handbook, many software professionals might disagree with the authors, but all will embrace the debate. Glass identifies many of the key problems hampering success in this field. Each fact is supported by insightful discussion and detailed references.

The huge success of personal computing technologies has brought astonishing benefits to individuals, families, communities, businesses, and government, transforming human life, largely for the better. These democratizing transformations happened because a small group of researchers saw the opportunities to convert sophisticated computational tools into appealing personal devices offering valued services by way of easy-to-use interfaces. Along the way, there were challenges to their agenda of human-centered design by: (1) traditional computer scientists who were focused on computation rather than people-oriented services and (2) those who sought to build anthropomorphic agents or robots based on excessively autonomous scenarios. The easy-to-learn and easy-to-use interfaces based on direct manipulation became the dominant form of interaction for more than six billion people. This book gives my personal history of the intellectual arguments and the key personalities I encountered. I believe that the lessons of how the discipline of Human-Computer Interaction (HCI) and the profession of User Experience Design (UXD) were launched can guide others in forming new disciplines and professions. The stories and photos of the 60 HCI pioneers, engaged in discussions and presentations, capture the human drama of collaboration and competition that invigorated the encounters among these bold, creative, generous, and impassioned individuals.

A guided tour by software pioneer Robert L. Glass through early computing and software engineering, 1940s-1990s. First-hand accounts of the people and innovations that made our age possible. Three female pioneers added for this new edition.

First Published in 1996. Routledge is an imprint of Taylor & Francis, an informa company.