Software Myths
If we get behind schedule, add more programmers to catch up!
Time is usually spent getting newcomers up to speed instead of doing productive work
Outsource the software to a third party, relax and let the firm build it!
If you cannot manage a project internally, how can you manage it when it is external?
A general statement of objectives is sufficient to begin writing code - fill in details later
An ambiguous "statement of objectives" is a recipe for disaster. Good software is built through effective and continuous communication between customer and developer
Software requirements continually change, but change can be easily accommodated because software is flexible
Early requirement changes have a relative small cost impact. However, as time passes, the cost impact grows rapidly and can cause problems, hence the AGILE MOVEMENT
Once we write the program and get it to work, the job is done! Yay!
The job has only begun.
Industry data indicate that between 60 and 80 percent of all effort expended on software will be expended after it is delivered to the customer for the first time
Software engineering will make us create voluminous and unnecessary documentation and will invariably slow us down
Software engineering is not about creating documents. It is about creating a quality product.
Better quality leads to reduced rework. Reduced rework leads to faster delivery times and less painful maintenance.
Software Development Myths
By David Adamo Jr.
Software Development Myths
- 525