Annotated Bibliography and References - The Technical and Social History of Software Engineering - page 433

classic of software engineering and is filled with sharp insights and pithy observa-
tions, such as adding people to a late project makes it later.
Campbell-Kelly, Martin. A History of the Software Industry: From Airline
Reservations to Sonic the Hedgehog . MIT Press, Cambridge, MA, 2004.
This interesting book came out in 2004 and does a good job of discussing the
companies and trends from the 1950s forward to 2004. The topic also shows sales
volumes and revenues for selected kinds of software spanning several decades. It
was a useful reference source for this topic to ensure that the focuses of each dec-
ade were congruent between the two.
DeMarco, Tom, and Lister, Tim. Peopleware . Dorset House Press, 1999.
Tom DeMarco is a famous consultant, public speaker, and author on a variety
of important software topics. Tim Lister is a colleague of Tom's and a partner in
the Atlantic Systems Guild. The topic selected for this annotated bibliography was
chosen because it, along with Jerry Weinberg's Psychology of Computer Program-
ming , deals with the fundamental issue that software applications are designed and
developed by human beings.
Weinberg's book dealt with programmers as individuals. DeMarco and Lister's
book expands the view to groups and also to the physical environments provided
for the groups. For example, Peopleware was the first book to address the issues
of office space and privacy. This topic, along with many others by Tom DeMarco,
has been influential across several decades.
Gack, Gary. Managing the Black Hole—The Executive's Guide to Project
Risk . The Business Expert Publisher, Thomson, GA, 2010.
The current book states several times in several chapters that large software
projects are subject to unexpected delays, cost overruns, and outright failure. This
interesting book by Gary Gack is congruent with the statements in this topic, and it
provides additional evidence. It also provides some suggested solutions for avoid-
ing these endemic problems, including use of formal inspections and better quality
control.
Gilb, Tom, and Graham, Dorothy. Software Inspections . Addison-Wesley,
Reading, MA, 1993.
Formal inspections of requirements, design, code, and other deliverables were
invented at the IBM Kingston development labs in the 1970s. Two well-known pi-
oneers of inspections were Michael Fagan and Ronald Radice.