Software Myths
1.Erroneous beliefs about software and the process that is used to build it.
2.Misleading attitudes that have caused serious problems for managers and pactitioners.
Classifications of software myths
Management Myths
Customer Myths
Practitioner Myths
Management 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 exestence?Does it reflect modern SE practices?Is it complete?Is it adaptable?
Customer Myth
Myth - Software requirement 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.
Partitioner Myth
Myth - "Once we write the program and get it work, our job is done."
Reality - Some once said the "the sooner you begin 'writing code', the longer it'll take youto get done".
No comments:
Post a Comment