Development Myths

A general "statement of objectives" is all I need from the customer. I will fill in the details later.

As a customer I can keep changing my mind and redefining the intent of a program. After all, software is flexible, isn't it?

I have got to begin coding because we are already late!

The only deliverable for a successful project is a source code listing.

It is impossible to assess the quality of a program until after it is written and working.

Once the program is written, we are done.

Any competent engineer can write programs.

Let us run a few test cases and then we'll be finished!

I know what the program does, I don't have time to document it.

I am working on programs that were originally written 30 years ago. How can I use modern software engineering techniques?