Software Myths – erroneous beliefs about software and the process that is used to build it
There are three types of myths :
· Management myth
· Customer myth
· Practitioner myth
Management Myths
Myth 1 : 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 is :
Are we rolling, KIDDING ;)
The book of standards may exist, and we read, but is it we understand the meaning of point stated in the book? HAAAAA
When the designer design a software, are they follow exactly what the book said?
Customer Myths
Myth 1 : Project requirements continually change, but change can be easily accommodated because software is flexible.
Reality is :
The beginning of the project, we decided to follow what we going to do, step by step, but, eg : when the management changes, then the new step are been introduced so we have to say “bye” to the old steps and follow the new one.
Practitioner Myths
Myth 1: Job is done once we write and get the program work.
Reality is :
if we decided to do the project in last minute time, there is no 100% successful of the project will end up.
Muhammad Rijaluddin Bin Mohd Rusli (IS085739)
Muhammad Naqib Bin Md Esa (IS085723)
No comments:
Post a Comment