A customer who requests computer software may be a person at the next desk, a technical group, the marketing/sales department or an outside company that has requested software under contract. In many cases, the customer believes myths about software because software managers and practitioners do little to correct misestimations. Myths lead to false exceptions and finally, dissatisfaction with the developer.

Myth
A general statement of objectives is sufficient to being with writing of the programs-Details can be filled later.

Reality
Although a comprehensive and stable statement of requirements is not always possible. Under or ambiguous statement of objectives may lead to disaster. Clear or unambiguous requirements that are stated iteratively are developed only through effective and continuous communication between customer and developer.

Myth
Project requirements continuously change, but changes can be easily accommodated as software is flexible.

Reality
It is true that software requirements change, but the impact of change varies with the time at which it is introduced. When requirement changes are requested early (before design or code has been started), cost impact is relatively small. Every change requires that the complete system be re-verified. If we do not take proper care, this will be an excrement tedious and expensive process.

For more help in Customer Software click the button below to submit your homework assignment