How do software myths affect a software process?

Answer 1

Software myths are common beliefs that are propogated as truths, may seem to be plausible, but are false. Believing in software myths at best leads to low productivity and poor software quality and at worst leads to failed projects.

Here are just a few myths in the software world:

• The sooner developers start coding the sooner the software will be built
• Development problems can be solved by using state-of-the art tools.
• Late projects can be solved by adding more people
• Change is easily accommodated, since software is malleable.
• A general statement of need is sufficient to start coding
• You can't assess software quality until the program is running.
• Lines of code (LOC) is a useful measure of software productivity

There are many more myths out there, but the common thread is that these myths are believed because people do not get hard evidence on what works in software development and what doesn't. People confuse their personal biases and beliefs with facts.

If you want facts about what works and what doesn't in software development then you want to get books like: The Economics of Software Quality by Capers Jones (link below), which document hard evidence after considering 10,000+ projects.

Other quality authors are Tom Demarco and Edward Yourdon.

Answer 2

Both a product and a vehicle for delivering a product

(1)Product

• Delivers computing potential
• Produces, manages, acquires, modifies, display, or transmits information

(2)Vehicle

• Supports or directly provides system functionality

Controls other programs (e.g., operating systems)

• Effects communications (e.g., networking software)
• Helps build other software (e.g., software tools)

Answer 3

definition of software myth?and explain types?