Myth is an erroneous beliefs about software and the process that is used to build it which can be trace to the earliest days of computing. In software engineering, there are three types of myth that have to be highlight. These are includes management myth, customer myth and practitioner’s myth.
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 that belief will lessen the pressure (even temporarily).
MYTH 1 :
If I decide to outscore the software project to a third party, I can just relax and let that firm built it
REALITY 1 :
If an organization does not understand how to manage and control software projects internally, it will invariably struggle when it outsourses software projects.
MYTH 2 :
If I decide to outscore the software project to a third party, I can just relax and let that firm built it
REALITY 2 :
If an organization does not understand how to manage and control software projects internally, it will invariably struggle when it outsourses software projects.
Myths that lead to false expectations by the customer and result in dissatisfaction with the developer. Problem with :
MYTH 1 :
Poor up-front definition is the mayor cause of failed SW efforts. Detailed description of function, performance, interfaces, design constraints and validation criteria essential.
REALITY 1 :
A formal and detailed description scan be communication determined only after thorough between customer and developer.
MYTH 2 :
Project requirements continually change„ but change can be easily accommodated because software is flexible
REALITY 2 :
It is true that software requirements changes, but the impact of changes varies with the time at which it is introduced.
Myth 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.
MYTH 1 :
Job is done once we write and get the program work.
REALITY 1 :
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.
MYTH 2 :
I should not accessing the quality, until i got the program running.
REALITY 2 :
One of the most effective software quality assurance mechanisms can be applied from the inception of a project – the formal technical review. Software reviews are a “quality filter” that have been found to be more effective than testing for finding certain classes of software errors.
References :
http://pswlab.kaist.ac.kr/courses/cs550-07/ch1.pdf
http://www.slidefinder.net/c/cpsc_333_seng_311_foundations/5493755
http://google.com
http://www.wikipedia.org
No comments:
Post a Comment