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.)

The role of testing, Planning the complete testing effort, Personnel issues, The tester at work, Test automation, Code coverage

Offers various resources - including news, articles, forum and job board.

An overview of some simple principles to attain success designing and implementing new projects

Index to articles written by members of Jerry Weinberg's SEM Group.

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

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.

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

John Evans; Crosstalk, June 2000. The importance of software architecture, and related items such as unambiguous requirements and coding standards.

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

Lorin J. May; Crosstalk, July 1998. Based on interviews with software consultants and practitioners who were asked to provide "autopsies" of failed projects with which they have been acquainted.

By a software developer and consultant with over 30 years experience.

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

Characteristics of software developers - personality type, demographics, age, education, attitudes.

Describes the basic rules for all good interfaces - the cardinal dos and don'ts.

The advantages of scripting languages - typeless data, smaller code size, greater reuse, higher productivity. By TCL creator John Ousterhout.

Emphasizes "soft" issues - attitude, approach.

This paper presents seven key steps: improve the testing process, define requirements, prove the concept, champion product testability, design for sustainability, plan for deployment, and face the challenges of success.

People management advice for technical people.

Some aspects of the relationship between quality and aesthetics (beauty) in software, using architecture analogies.

9 Dos and 8 Don'ts for software project success, from NASA's Goddard Space Flight Center. (Sample chapter from Steve McConnell's book Software Project Survival Guide.)

Margaret Kulpa; Crosstalk, September 1998. Common misconceptions concerning software process improvement and the Software CMM.

Explores the importance and purpose of software process and quality.

Recapturing, exploring and celebrating the Art of Computer Programming.

Case study of a well known software error.

CIOs reveal the projects that did not kill them and made them stronger.

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