London Ambulance Service Failures
LAS Project Failures
SOFTWARE PROBLEM
One of the reasons for project failure was total dependence on the software used, once the software has not been tested enough that it could create a contingency plan in case of system failure. Neither the Computer Aided Despatch (CAD) system itself, nor its users, were ready for full implementation on 26 October 1992. The CAD software was not complete. There were outstanding problems with data transmission to and from the mobile data terminals. The CAD system implemented in 1992 was over ambitious and was developed and implemented against an impossible timetable.
Software testing is not something new, but still, even today, companies prefer to develop systems without a methodology based on quality, see the inconsistency, when buying a car, it went through several tests, when a toy is manufactured this also involves testing to know that the paint is not harmful to children, the eyes will not leave the child's mouth and so on, and they all want quality products, then why is not applied to Software?
Quality is something in industries covered long ago, several methodologies have emerged, all with the goal of improving quality while reducing costs, since the cost of the defect can be disastrous, not only for finance but also for the name of firm
According Bastos et. al. There are three dimensions of quality that need to be considered:
Reliability: The system is resilient to failures during execution, ie, no loops, no stops running due to lack of resources, etc.
Functionality: the system behaves as expected and set to your requirements.
Performance: the system has a time adequate and acceptable response, even when subjected to a processing volume close to real situations or peak?
And to answer the three dimensions, the developer and analyst, has a new job, with a focus on developing quality, besides the size, the analysis team and development can make use of the well-known PECA cycle: Plan, Execute, Check, Act .
If all this
SOFTWARE PROBLEM
One of the reasons for project failure was total dependence on the software used, once the software has not been tested enough that it could create a contingency plan in case of system failure. Neither the Computer Aided Despatch (CAD) system itself, nor its users, were ready for full implementation on 26 October 1992. The CAD software was not complete. There were outstanding problems with data transmission to and from the mobile data terminals. The CAD system implemented in 1992 was over ambitious and was developed and implemented against an impossible timetable.
Software testing is not something new, but still, even today, companies prefer to develop systems without a methodology based on quality, see the inconsistency, when buying a car, it went through several tests, when a toy is manufactured this also involves testing to know that the paint is not harmful to children, the eyes will not leave the child's mouth and so on, and they all want quality products, then why is not applied to Software?
Quality is something in industries covered long ago, several methodologies have emerged, all with the goal of improving quality while reducing costs, since the cost of the defect can be disastrous, not only for finance but also for the name of firm
According Bastos et. al. There are three dimensions of quality that need to be considered:
Reliability: The system is resilient to failures during execution, ie, no loops, no stops running due to lack of resources, etc.
Functionality: the system behaves as expected and set to your requirements.
Performance: the system has a time adequate and acceptable response, even when subjected to a processing volume close to real situations or peak?
And to answer the three dimensions, the developer and analyst, has a new job, with a focus on developing quality, besides the size, the analysis team and development can make use of the well-known PECA cycle: Plan, Execute, Check, Act .
If all this