TASK 4

Myth is defined as "widely held but false notation" by the oxford dictionary, so as in other fields software arena also has some myths to demystify.Software myths prevail but though they do are not clearly visible they have the potential to harm all the parties involved in the software development process mainly the developer team.

Three types of software myths:-

1. Management Myth
2. Customer Myth
3. Practitioner Myth

  1.Management Myths: Managers with software responsibility, like managers in most       disciplines, are often under pressure to maintain budgets, keep schedules from slipping, and improve    quality. Like a drowning person who grasps at a straw, a software manager often grasps at belief in a software myth, if those beliefs will lessen the pressure.

           

            Some common managerial myths:-

·         We have standards and procedures for building software, so developers have

·         everything they need to know.

·         We have state-of-the-art software development tools; after all, we buy the latest computers.

·          If we're behind schedule, we can add more programmers to catch up.

·         A good manger can manage any project.

   2.Customer Myths: A customer who requests computer software may be a person at the next desk, a technical group down the hall, 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 misinformation. Myths lead to false expectations by the customer and, ultimately, dissatisfaction with the developer. Commonly held myths by the clients are:

·         A general statement of objectives is sufficient to begin writing programs -

·         we can fill in the details later.

·          Requirement changes are easy to accommodate because software is flexible.

·         I know what my problem is; therefore I know how to solve it.

3.  Practitioner Myths: 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 art form. Old ways and attitudes die hard. A malpractice seen is developers are that they think they know everything and neglect the peculiarity of each problem.

·         If I miss something now, I can fix it later.

·          Once the program is written and running, my job is done.

·         Until a program is running, there's no way of assessing its quality.

·          The only deliverable for a software project is a working program.

·         Every developer should try to get all requirement is relevant detail to

effectively design and code the system.

Some misplaced assumptions that intensify the myths are :-

1.All requirements can be pre-specified
2. Users are experts at specification of their needs
3. Users and developers are both good at visualization
4. The project team is capable of unambiguous communication

On the whole, realities are always different from the myths. So the myths must be demystified and work should be based on systematic, scientific and logical bases than the irrational myths. The systemic view must be considered to determine the success of any software project its not only the matter of hard skills but soft skills of the developer team also matter to come up with a efficient system.