Software Myths

Myth is defined as "widely held but false notation" by the Oxford dictionary. It does mean that some false beliefs are made by some people, and these false beliefs have potentials to harm parties that are involved in it or relating to it like developers team is harmed most of the times. Myths are created when there is no meaningful or logical information is not available or the people do not have correct knowledge about the software or software development.

There are three types of software myths that are given as follows:

1. Management Myths
2. Customer Myths
3. Developer Myths

1. Management Myths:
1. The standards developed by the organizations and the companies can be very helpful. If any development problem occurs they can be solved by the standards that are defined by the company and the organization.
2. Increase in the developer's project team can make the delay and thus increases the communication between the developers. Also, a larger team has too much communication links. Fred Books (1975) also describes that this is a myth which is true sometimes, “Adding people to a late project makes it later”
3. The management can sit idle and relax by outsourcing the project that is assigned is also a myth that is if management outsource the project then still they have any other workloads and duties, so they can’t sit idle or free.
4. Member acquires all the information, is also another myth, actually, the developers don’t have all the information about all the standards because they are often outdated. There is a rare chance of having complete information and following the standards by the developer.
2. Customer Myths:
1. The changes in a software project are easy to make, is also a myth there is a complete and time taking process to make any changes into the actual project. So it is not easy to make changes to the software project.
2. To make software project a general requirement statement is enough, is also a customer myth. The developer needs a detailed description of requirements. The developer makes some validations into the software project with the requirements defined by the customer.
3. Developer Myths:
1. The developer’s job is complete when the code is delivered to the customer, is a developer myth there is always a need of change/modification of code for making any changes into the software project, because there is a high possibility of failing of the software or any other bugs remain in software, so removing of bugs is needed.
2. Project success is only depends upon the quality of delivered project, is also a developer myth, there are many other phases and processes that define the quality of the software project like designing, testing, maintenance etc.
3. You cannot evaluate the quality of software without running the software, is also a myth that is the quality also can be checked and effectively determined by the customer reviews. Formal (Mathematical) analyses also used to verify software security factors and reliability of the software.