Question

5 SENTENCES EACH

What is a software myth?

Describe the Three (3) Types of Software Myths

Which of the Myths do you think would cause a software developer to be frustrated in a company setting? Explain why.

Answer 1

What is a software myth?

Software myths are the misleading attitudes that have caused some serious problems for the managers and the technical staffs. Software myths propagates confusion and misinformation which is not ideal.The development of software requires a lot of dedication and understanding. Many software problems arise due to myths that are formed during the initial stages of software development.

Describe the Three (3) Types of Software Myths

1) Management myths: Managers with the software responsibility are often under pressure to maintain budgets, keep schedules, and improve quality. A example Management myths is as follows:
Myth: We have a book that is full of standards and procedures for building software, won’t that provide my people everything they need to know to develope a software?
Reality: The book of standards may exist, but this is not used. Most software practitioners are not even aware that it exist. Also, It does not reflect the modern software engineering practices.

2) Customer myths: Customer myths often leads to false expectations (by the customer) and ultimately, dissatisfaction with the developer. Following is an example of customer myths:
Myth: A general statement of objectives is sufficient to start writing programs/codes-we can fill in the more details later.
Reality: A formal and detailed description of the functions, behavior, performance, interfaces, design constraints, and validation criteria is essential for developing a software .A poor definition is one of the major cause of failed software efforts.

3) Practitioner’s myths:  Practitioners have following myths(few examples):
Myth: Once we write the program/code and get it to work, our job is done.
Reality:But the Industry data indicate that between 60 % and 80 % of all effort put on a software will be expended after it is delivered to the customer for the first time.
Myth: Until the program is “running” there is no way of assessing its quality.
Reality: "The formal technical review" - One of the most effective software quality assurance mechanisms can be applied from the inception of a project only.

Which of the Myths do you think would cause a software developer to be frustrated in a company setting? Explain why.

I think all the three could cause a software developer to be frustrated in a company setting.

Management myths: As the Manger thinks he has provided and managed all the things that are required for smooth functioning but on the contray that is not sufficient. On top of that there is burden of deadline.

Customer myths: The Customer comes up with his own expectations. But because of some myths and formal conduction the finished product is not upto the expectations. As a result, The developer has to put efforts again.

Practitioner’s myths: As a software developer you put efforts to make a software. So you have your own expectations from your code. But failing to meet the requirement can be frustrating.

Also, a simple solution to all the above myths is proper and formal description of the task at all the levels.