Case study of a well known software error.

Software safety. Parallels between the early development of high-pressure steam engines and software engineering that we can apply to the use of computers in complex systems.

For business software, faster-cheaper can be better too.

One of the classic articles leading to modern software engineering, by D.L. Parnas.

Technical and managerial best/worst practices. Based on study of US Department of Defense software projects.

Explores the importance and purpose of software process and quality.

Advanced use of assertions for clearer specifications and greater software reliability. By OO guru Bertrand Meyer, creator of Eiffel.

Description of 36 ineffective development practices: people-related, process-related, product-related, technology-related. (Sample chapter from Steve McConnell's book Rapid Development.)

User-Centered Design. Simple approaches for delivering smaller, simpler systems that better serve the needs of users.

Adaptive Programming - specifying the connections between objects as loosely as possible. Makes programs more flexible, more resilient to change, and more adaptable to varying configurations of classes within a given domain