Software Studies

This collection of short expository, critical and speculative texts offers a field guide to the cultural, political, social and aesthetic impact of software. Experts from a range of disciplines each take a key topic in software and the understanding of software, such as algorithms and logical structures.

An argument that we must read code for more than what it does—we must consider what it means. Computer source code has become part of popular discourse. Code is read not only by programmers but by lawyers, artists, pundits, reporters, political activists, and literary scholars; it is used in political debate, works of art, popular entertainment, and historical accounts. In this book, Mark Marino argues that code means more than merely what it does; we must also consider what it means. We need to learn to read code critically. Marino presents a series of case studies—ranging from the Climategate scandal to a hactivist art project on the US-Mexico border—as lessons in critical code reading. Marino shows how, in the process of its circulation, the meaning of code changes beyond its functional role to include connotations and implications, opening it up to interpretation and inference—and misinterpretation and reappropriation. The Climategate controversy, for example, stemmed from a misreading of a bit of placeholder code as a “smoking gun” that supposedly proved fabrication of climate data. A poetry generator created by Nick Montfort was remixed and reimagined by other poets, and subject to literary interpretation. Each case study begins by presenting a small and self-contained passage of code—by coders as disparate as programming pioneer Grace Hopper and philosopher Friedrich Kittler—and an accessible explanation of its context and functioning. Marino then explores its extra-functional significance, demonstrating a variety of interpretive approaches.

An alternative history of software that places the liberal arts at the very center of software's evolution. In The Software Arts, Warren Sack offers an alternative history of computing that places the arts at the very center of software's evolution. Tracing the origins of software to eighteenth-century French encyclopedists' step-by-step descriptions of how things were made in the workshops of artists and artisans, Sack shows that programming languages are the offspring of an effort to describe the mechanical arts in the language of the liberal arts. Sack offers a reading of the texts of computing—code, algorithms, and technical papers—that emphasizes continuity between prose and programs. He translates concepts and categories from the liberal and mechanical arts—including logic, rhetoric, grammar, learning, algorithm, language, and simulation—into terms of computer science and then considers their further translation into popular culture, where they circulate as forms of digital life. He considers, among other topics, the “arithmetization” of knowledge that presaged digitization; today's multitude of logics; the history of demonstration, from deduction to newer forms of persuasion; and the post-Chomsky absence of meaning in grammar. With The Software Arts, Sack invites artists and humanists to see how their ideas are at the root of software and invites computer scientists to envision themselves as artists and humanists.

Nowadays, societies crucially depend on high-quality software for a large part of their functionalities and activities. Therefore, software professionals, researchers, managers, and practitioners alike have to competently decide what software technologies and products to choose for which purpose. For various reasons, systematic empirical studies employing strictly scientific methods are hardly practiced in software engineering. Thus there is an unquestioned need for developing improved and better-qualified empirical methods, for their application in practice and for dissemination of the results. This book describes different kinds of empirical studies and methods for performing such studies, e.g., for planning, performing, analyzing, and reporting such studies. Actual studies are presented in detail in various chapters dealing with inspections, testing, object-oriented techniques, and component-based software engineering.

This book contains a refereed collection of thoroughly revised full papers based on the contributions accepted for presentation at the International Workshop on Studies of Software Design, held in conjunction with the 1993 International Conference on Software Engineering, ICSE'93, in Baltimore, Maryland, in May 1993. The emphasis of the 13 papers included is on methods for studying, analyzing, and comparing designs and design methods; the topical focus is primarily on the software architecture level of design and on techniques suitable for dealing with large software systems. The book is organized in sections on architectures, tools, and design methods and opens with a detailed introduction by the volume editor.

In this work, over 40 pioneering implementers share their experiences and best practices in 28 case studies. Drawing on their insights, you can avoid the pitfalls associated with test automation, and achieve powerful results on every metric you care about: quality, cost, time to market, usability, and value.

Software engineering is of major importance to all enterprises; however, the key areas of software quality and software process improvement standards and models are currently geared toward large organizations, where most software organizations are small and medium enterprises. Software Process Improvement for Small and Medium Enterprises: Techniques and Case Studies offers practical and useful guidelines, models, and techniques for improving software processes and products for small and medium enterprises, utilizing the authoritative, demonstrative tools of case studies and lessons learned to provide academics, scholars, and practitioners with an invaluable research source.

The authors examine software from a spatial perspective, analyzing the dyadic relationship of software & space. The production of space, they argue, is increasingly dependent on code, & code is written to produce space.