Our group has finished the discussions on all myths since we have go through many articles on all 3 myths and we found Practitioner Myth is most serious misleading among all.
What is Software Engineering Myths ?
Software Engineering myths are misleading attitudes that have caused serious problems for managers and practitioners and this erroneous beliefs about software and the process that is used to build it.
#1 What is Management Myth ?
One thing you can say about philosophers, however, is that they have nothing to work with but ideas, so they become very good at detecting flaws in arguments. Credit to Bruce Eckel.
What is the myth ?
Myth : We already have a book that’s full of standards and procedures for building software. Won’t that provide my people with everything they need to know?
Reality : The book of standards may exist, but is it used? Are practitioners’ aware of its existence? Does it reflect modern SE practices? Is it complete? Is it adaptable?
What we found throughout discussion is ?
Management is something can be done even lack of educations. Because management is a attitude or an idea in our views. An experienced management people is the one who process his own life experience and it is not taught in any lessons. He might can find out what we have missed in school time and give us a clearer path to do things / job better. This is management all about.
#2 What is Customer Myth ? And what is the myth ?
Myth : Software requirements continually change, but change can be easily accommodated because software is flexible.
Reality : The impact of change varies with the time at which it is introduced. The cost of impact of changes in early stage of software project is relative small. However, changes introduced at a later development stage may requires a lot of resources and major design modification.
What we found throughout discussion is ?
In bussiness world , we knew that "The Customer is Always Right". Isn't that what we have been told? If we are in business, we know how preposterous that statement is. The truth is customer isn't always right, the customer is often wrong. Worse yet, we know it, he knows it, and he knows we know it. Even though , we still have to done our job by using our method but make it seems to be customer's way of doing things. Arguement won't lead us to successful software develop but compromise did lead us to a successful end product by finding out best method.
#3 What is Practitioner's Myth ?
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.
So what is the myth about?
Myth : Once we write the program and get it to work, our job is done.
Reality: Someone once said that the sooner you begin writing code, the longer it’ll take you to get done. ( Industry data indicate that between 60 and 80 percent of all effort expended on software will be expended after it is delivered to the customer for the first time. )
What we found throughout discussion is ?
In fact , through all the research we did. Practitioner is the one who practices something, especially an occupation, profession, or technique based on dictionary.com. But in computing practitioner is person who type codes or we called programmers. For most programmer , they will test the software usability through some testing and edit. When they found no errors the software considered done. But the fact is it doesn't done yet sometimes. Errors might not be there as programmer can't act like a normal user who going to use the software everyday. Software may meet failure when it meets certain unsolved and inconsistent functions inserted. Maintenances are always important for programmer to keep a software running smooth with minimum errors.
