WHY SOFTWARE WHY SOFTWARE WHY SOFTWARE WHY SOFTWARE
SUBMITTED TO :
Dr. Arun Timilsina HOD, Department of Electronics and Computer
SUBMITTED BY :
Abhinav Mishra 067/BEX/401
Most software projects can be considered at least partial failures because
only few projects meet all their cost, schedule, quality, or requirements objectives. Failures are rarely caused by mysterious causes, but these
causes are usually discovered post-mortem, or only after it is too late to change direction. This paper illustrates the major challenges faced by the
present-day software industry in regards to their QoS and reliability. Although not a comprehensive compilation of failure causes, this paper outlines several areas that does demand attention.
Roughly speaking, software industry is presently in its 4th decade. From an
outsider's view, it looks like a booming industry with billions of dollars flowing in
every year. Thousands of web-applications along with Internet giants like Google,
Facebook etc. and not to mention the need of every organization to have a software
tailored only for it's purposes does make that outside perception look like a reality.
This has seen millions of youngsters diving in to be part of this illustrious caravan.
But the reality is not that lavish. From the very beginning, this industry has been
facing serious challenges regarding it's output standards , reliability , on-time
delivery and the list goes on. Any one of these challenges if not dealt with properly
may result in the failure of the entire project . Now the major question that arises is
when does a software project actually fails?when does a software project actually fails?when does a software project actually fails?when does a software project actually fails?
The failure mark of disgrace is quite arbitrary and subjective. A project manager
never confesses that his project was a disaster. The intensiveness of the failure also
varies from project to project. Some of the outlines of failures have been listed
• The software did not meet with the consumers need.
• The software release was later than scheduled (deadline violation).
• The software had too many bugs.
STATISTICAL FACTS ABOUT SOFTWARE FAILURE
According to research conducted by the Standish Group in 2005:
• "… only 28 percent of software projects in 2000 succeeded outright …"
• "… Some 23 percent were cancelled, and the remainder were substantially late
• Further, they say the average software project runs 222% late, 189% over
budget and delivers only 61% of the specified functions.
• The following statistics are a result of the year 2000:
CAUSES OF SOFTWARE FAILURES
Now as failure is the norm of industry, let us try addressing some of the causes for
I. Poor User Input : A major number of software projects fail because they did
not meet the end-users need or expectations....