Myths that are still believed by software practitioners have been fostered by over 50 years of programming culture. During the early days of software, programming was viewed as an out form, old way and attributed die hard.

Myth
Practitioner think, once they write the program and get it to work, there job is completed.

Reality
But in actual the sooner you begin writing code, the longer it will take you to complete. According tot eh industries data 60 and 80 percent of all effort spend on software will be spended after it is delivered to the customer for the first time.

Myth
The quality of the software can be accessed only after the program gets executed.

Reality
One of the most effective software quality assurance mechanisms can be applied fromt eh beginning of the project, known as formal technical review. Software reviews can be tested as a quality filter considered as more effective than testing for finding certain classes of software errors.

Myth
Software engineering requires voluminous and unnecessary documentation and will invariably slow down the work.

Reality
People wrongly think that software engineering require lots of documentations, its about creating documents. But in actual its bout creating quality. Better quality leads to reduced rework. And if the rework is reduced hen it results in faster delivery times.

For more help in Practitioner’s Software click the button below to submit your homework assignment