It is hard to believe that with new technology in software engineering there are five projects went wrong out of six means only some project become successfull after software development.One third software projects cancelled due to these Seven causes.

Haste:

People try to provide software in hurry.Every thing which works looks right but not Quality.If you work in hurry then you make decision which will effect the Quality.Mostly the testing is the cause of Haste.

Apathy:

Apathy is the worst form of flattery.People don’t want to solve known problems.That is not to say that all solutions are known or fully achievable, but apathy is a basic unwillingness to attempt a solution.

Narrow−Mindedness:

                                                        Narrow−mindedness is the refusal to practice solutions that are otherwise widely known to be effective An example of this is the use of metadata in software systems.Metadata is self−descriptive information in a software system that enables the system to change dynamically.

Sloth:

Sloth is the “healthy sign” of a lazy developer or manager, who makes poor decisions based upon an “easy answer”.

Avarice:

                     Greed can take many forms, but it leads to inappropriate software development decisions.Architectural avarice means the modeling of excessive details, which results in excessive complexity due to insufficient abstraction.Excess complexity leads to many software problems and project challenges. Overly complex systems are expensive to develop, integrate, test, document, maintain, and extend. In some cases, development steps are skipped (such as testing) in order to make up for the lost time and money. This can lead very quickly to project failure.

Ignorance:

                           Ignorance is intellectual sloth. It’s the result of failing to seek understanding. It keeps people stupid  and eventually leads to long−term software problems.

Pride:

Object technology supports many reuse opportunities through the integration of commercial packages, freeware, and wrappered legacy applications.Often, developers unnecessarily invent new designs when knowledge from preexisting systems, products, and standards are readily applied through architecture mining.Reinvention involves many unnecessary risks and costs. New software must be designed,coded, debugged, tested, and documented. New architecture must be prototyped andevolved before it is proven to provide software benefits.

Advertisements