Task 4

HyE EveryOne...!!!!!

SOFTWARE ENGINEERING MYTH

Discuss one software engineering myth from each category of management myths, customer myths and practitioner myths.

• Software myths – erroneous beliefs

  about software and the process

  that is used to build it.

• Misleading attitudes that have

 caused serious problems for

 managers and practitioners.

• Classifications of software

  myths:

–Management myths

–Customer myths

–Practitioner myths

Types of Management Myths:

Management Myths: Managers with Software responsibility, like managers in most discipline, are often under pressure to maintain budgets, keep schedules and maintain quality.

Like a drowning person who grasps straw, software manager often grasp at a belief in a software myth even though it gives temporary relief.

Management Myths:

Myth: We already have a book that has procedures and standards for building software. Won’t they provide my people with everything they want to know?

Reality: The book of standards very well exists, but is it used?

  Are the software engineers aware of its existence?

  Does it reflect the Modern Engineering Practices? Is it Complete?

  In many cases Answers to above all the question is – No.

Myth:

CEO calls the Developer Raju and has the following conversation…..

CEO: Hi!! Raju, you are working very slow, I have given the assignment 1

          month before. But you have not completed till today. Why? You should

          give proper explanation to me immediately.

Raju: Sir, I am running short of materials that’s why I couldn’t able to

          complete in time sir.

CEO: We already have a book, which has procedures and standards for

          building software. It will provide every detail you require.

Raju: I do not know Sir. I will refer it and complete within an hour sir.

          (After 1 hour Raju Meeting CEO)

Raju: The book not covers the modern practices Sir.

Now Show the Chart that contains the following information:

The book of standards very well exists, but is it used?

Are the software engineers aware of its existence?

Does it reflect the Modern Engineering Practices? Is it Complete?

In many cases Answers to above all the question is – No.

Customer Myths

Now that the learners have a clear idea about Management Myth, it would be time to have a look at the next Myth i.e. is Customer Myths.

Myth: A general statement of objective is “It is sufficient to begin writing programs – we can fill in the details later”.

Reality: The above definition is the major cause of failed S/W efforts. Formal and details of information domain, function, behavior, performance, interfaces, design constraints and validation criteria is essential. These characteristics can be determined only after the through communication between customer and developer.

Myth:

CEO is having the conversation with Team Manager…..

CEO: Hi, We have got a new assignment from Mannaran Company. When

          can you take up this new assignment?

Team Manager: We have to do feasibility study and Requirement Analysis

                         after that only we may able to take sir.

CEO: How long you need to finalize these things.

Team Manager: I need a month time sir.

                          (After a month CEO Calling Team Manager and discussing)

CEO: Can we start the assignment from today.

Team Manager: No Sir. I need some more time. I have to collect some

                        more information from the customers.

CEO: “It is sufficient to begin writing programs – we can fill in the details

          later”

Team Manager: No Sir. That’s not possible. Before writing the program we

                         need a complete detail.

Now Show the Chart that contains the following information:

Formal and detail of information domain, function, behavior, performance, interfaces, design constraints and validation criteria is essential. These characteristics can be determined only after the through communication between customer and developer.

Practitioners Myth

By now the learners would have developed a clear idea about Management and Customer Myths. At this point, it would be appropriate to take up Practitioners Myth.

Myth: Until I get the program “running”. I have no way of assessing its quality.

Reality: One of the most effective software quality assurance mechanisms

   can be applied from the infection of the project – Formal Technical Review

   Software reviews are a “Quality Filter” that have been found to be more

   effective than testing to find the software defects.

CEO is having the conversation with Team Manager…….

CEO: What about you’re Project Progress? When can I expect the

           completion?

Team Manager: We have almost completed all the parts. We may able to release within a couple        

                           of days.

CEO: Have you finished the Quality assessment part?

Team Manager: Until the program is running I can’t asses the Quality.

Now Show the Chart that contains the following information:

One of the most effective software quality assurance mechanisms can be applied from the infection of the project – Formal Technical Review

References and credit: Contents in the slides are adopted from the book and the slides that accompanied the  book by R.S. Pressman, Software Engineering: A Practitioner’s Approach, 7th. Edition, McGraw Hill, 2009

NURUL AIN MD HASHIM (IS086681) & THEEPA LAKNAKUMARAN (SW086630)