Why Software Fails?

Why Software Fails?

Software Failures Cost up to $60 Billion to US economy a success is only 16.2%. These are the software projects that are completed on time and on budget. This success rate is even lower in bigger organizations; an alarming 9% that manage to meet their time and cost requirements, most of which still fail to meet their specifications. Alarmingly, A Standish Group research report shows that a staggering 31.1% of projects are cancelled before they ever get completed. Further results indicate 52.7% of projects will cost 189% of their original estimates[1]" annually.
                                      

Moreover, the average number of projects becoming a success is only 16.2%. These are the software projects that are completed on time and on budget. This success rate is even lower in bigger organizations; an alarming 9% that manage to meet their time and cost requirements, most of which still fail to meet their specifications.

A project is said to have failed when it is unable to complete in the allotted budget and resources, or when it delivers later than it was decided, or when it is unable to meet the requirements set out in the project definition phases. History shows that the proportion of projects meeting all three of these requirements is very small.
        
IT projects, especially those involved in the creation and management of software are very different from other kinds of projects such as a construction project. First of all; Failure or flaw in an IT project might not be as apparent as projects that can be seen and touched and more alarmingly, identifying the root cause is not as simple a job in IT projects as it might be in other sorts of projects.
There is an old saying that Goes like, "There are a million ways to do something wrong but only one way to do it right". When it comes to IT projects, nothing can be further from reality. It is always the same bunch of reasons that cause failure. This article and those that follow will highlight a few of them hoping that it helps us be prepared to dodge these reasons in the future!

Failed projects could be of the following 4 Kinds:
1) Failure caused by bad management
2) Failure caused by poor team effort
3) Failure caused by poor end product
4) Failure caused by errors that could have been caught

Author: Clara James
Source: Link

Comments

Post a Comment

Popular posts from this blog

What is LCSAJ Testing?

Image
LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred. Test cases shall be designed to exercise LCSAJs. For each test case, the following shall be specified: - the input(s) to the component; - identification of the LCSAJ(s) to be executed by the test case; - the expected outcome of the test case.
Read more

What is State Transition Testing?

Image
State transition testing uses a model of the states the component may occupy, the transitions between those states, the events which cause those transitions, and the actions which may result from those transitions. The model shall comprise states, transitions, events, actions and their relationships.   The states of the model shall be disjoint, identifiable and finite in number.   Events cause transitions between states, and transitions can return to the same state where they began.   Events will be caused by inputs to the component, and actions in the state transition model may cause outputs from the component. The model will typically be represented as a state transition diagram, state transition model, or a state table. Test cases shall be designed to exercise transitions between states.   A test case may exercise any number of transitions.   For each test case, the following shall be specified: -   the starting state of the component          -   the input(s) to the compo
Read more

ISEB-ISTQB Sample Exam Paper 12

Image
1. Which of the following statements contains the correct use of the terminology? a) a fault by a person may introduce an error into the software that may cause a failure in operation b) a failure by a person may introduce a fault into the software that may cause an error in operation c) an error made by a person may introduce a fault into the software that may cause a failure in operation d) an error made by a person may introduce a failure into the software that may cause a fault in operation e) a failure by a person may cause an error in the software that may cause a fault in operation 2.   A reliable system will be one that: a) is unlikely to be completed on schedule b) is unlikely to cause a failure c) is likely to be fault-free d) is likely to be liked by the users e) includes a minimum number of components 3.   Which of the following statements about ‘Integration Testing in the Small’ is false? a) It can combine all the components together in one go
Read more