We accept

Reviewing THE PROBLEMS Of Software Systems Information Technology Essay

In this newspaper I am especially focus on the problem of failure with regards to that group of software systems known as information systems. I QUICKLY will discuss two well-known conditions that of the London ambulance service computer-aided dispatch system (L ) project as well as the London stock market (TAURUS) project, and express strong inability factors of information systems failure. My purpose is also to make use of the generic material on IS failing and the specific details of this particular case study to critique the problems of safety,

Literature review

Like most computing professionals in the UK we were alert to the failure, making use of this term broadly, of the computer aided dispatch (CAD) system deployed by the London Ambulance Service (LAS) in, or shortly after,

For orientation a short sketch of the statement follows. There were lots of other analyses of the LAS CAD system inability of which Mellor (1994) is just about the most useful.

The London Ambulance System Disaster, 1992


The basic operation of the designed LASCAD system was as follows: United kingdom Telecom (BT) providers would course all 999 calls related to medical emergencies as a matter of usual to LAS headquarters (HQ) in Waterloo. 18 HQ 'receivers' were then expected to record on the machine the name, phone number and address of the caller, and the name, destination address and simple details of the patient. These details would then be sent over a local area network to a locator.

"The machine was lightly filled at start-up on 26 Oct 1992. Any problems, brought on especially by the communications systems (such as ambulance crews pressing the wrong control keys, or ambulances being radioed in dark-colored locations), could be effectively been able by personnel. However, as the amount of ambulance happenings increased, the amount of inappropriate vehicle information saved by the machine increased. This acquired a knock-on impact in that the system made wrong allocations based on the information it got. For example, multiple vehicles were sent to the same incident, or the closest vehicle was not chosen for dispatch. As a consequence, the system possessed fewer ambulance resources to allocate. The machine also placed cell phone calls that hadn't gone through the correct protocol over a waiting list and generated exception text messages for those incidents that it possessed received incorrect status information. Indeed, the amount of exception messages seems to have increased to this extent the personnel were not in a position to clear the queue. It became progressively more difficult for personnel to wait to messages that acquired scrolled off of the screen. The increasing size of the queue slowed the machine. "

Factors Contributed to Such a Disaster

Managerial failure

Technical failure

Human failure

Managerial failure

LAS management overlooked or selected not accept advice provided to it from many resources beyond the service on the time desk or the high risk of the extensive systems requirement

The project didn't show, or consult with, the LAS Plank independence recommendations on the business lead CAD service provider, that raised questions on their capability to take care of such a significant project

The LAS boards were given a deceptive impression, by the job team of the prior experience of the lead contractor in crisis service system

In awarding the agreement for CAD to a small software house, with no previous connection with similar systems, LAS management were taking higher risk

Project management throughout the development and implantation process was insufficient and sometimes ambiguous. A major system integration job such as CAD requires full time. Professional, experienced task management, this was lacking

There was incomplete "ownership" of the machine by the majority of it users. The many problems recognized with lots of the system components in the preceding months acquired installed an atmosphere of system destruct in which personnel expected system to fail rather than prepared it to succeed

LAS table and RHA management, whilst noticing that there have been continuing problems with the execution of CAD, consistently accepted assurances from professional directors that problems were being rectified which successful execution would be performed never was a complete impartial review commissioned of the true talk about of the project

Technical failure

LAS neglect to follow the PRINCE job Management Method in the setup and operation of the it (IT) professional committee, project panel, project management team and task confidence team: London Ambulance Service

The CAD system relied on near perfect home elevators vehicle location and position being open to it at all times. The job team failed to appreciate totally the impact that a higher-level of imperfection would have on the system

The system had not been fully analyzed to a satisfactory level of quality and resilience before full execution on 26 October 1992

On 26 and 27 Oct 1992 the computer system itself didn't fail in a technical sense. Response times does on events become undesirable, but overall the machine did what it turned out made to do. However, a lot of the design got fatal flaws that could, and does, cumulatively lead to all of the symptoms of systems failure

On 4 November 1992 the system did fail. This was caused by a minor programming mistake that caused the machine to "crash" The automatic change to the back up system was not adequately analyzed, those the complete system was helped bring down

Human failure

Training provided to CAD staff and ambulance crews was imperfect and inconsistent

LAS management consultancy attributed CAD problems to willful misuse of the machine by some ambulance crews. There is no direct proof this, but the circumstantial facts that does are present indirect to the Inquiry Team that it could have been only one of the many contributory factors that led to the CAD failure

In the period before an including 26 and27 Oct 1992 there were insufficient control assistants taking crisis call. This contributed to an unacceptable level of getting in touch with times. This has since been rectified


Failure was anticipated to a sophisticated mixture of factors

Participation by themselves is not sufficient but helps!

Expectation of failing performs a part

does not meet the needs of the stakeholders

Systems should strive to meet the shared goals & needs of different stakeholders



The London stock exchange is one of the largest stock exchanges on the globe with numerous overseas listings as well as British organizations

In 1989 the London STOCK MARKET (LSE) put forward a proposal for a computerized system to ensure that talk about certificates and cash changed hands between the interested parties following the trading transaction; implicit in this is the dematerialization of stock certificates. It was a big task with a huge selection of personnel contracted in and lots of external stresses from various different stakeholders.

The first goals of the system were 4 folded.





What TAURUS Team does wrong?

Lack of professional and stakeholders support

Based on the problems encountered it seem to be that the project manager had not been that experience

Have a sizable expanding scope

Went in advance with the implementation of something with insufficient individual and stakeholder's determination.

Lack of skilled resources and clear complete technical specs.

Reason for TAURUS Collapse

Poor monitoring and controlling

Monitoring a project work includes collecting, measuring, and disseminating performance information. If TAURUS management experienced good monitoring and control techniques they would have known when they project was not achieving project objectives

Poor management of the nine job management knowledge areas

Knowledge Areas

TAURUS project professionals handled the nine project management knowledge areas poorly

Scope: If they had monitored the opportunity of the project effective the huge range creep would not have been came across.

Cost: If this was handled effectively the project would not have gone over budget 100%

Time: If this area had been manage effective the job would not have had a schedule overrun by 100%

Quality: If the quality area of the system was manage properly the standards was have been clear and complete

Risk: If the chance had been handled effectively they could have had the opportunity to abundant the project earlier.

Communication: If communication was monitored all changes and hold off would be communicated in a timely.

Human resources: skilled resources would be received and implemented.

Integrated Change Control

If TAURUS possessed a built-in change control they could have been able to impact the factors that create changes to ensure that changes are advantageous and control the range of the project.

Changes would be communicated to top management and steering committee regularly and they can deal with these changes as they occur because change control is a critical success factors.

Project Management Issues

Poor Management of triple constraints


TAURUS managers didn't control and monitor the opportunity of the project


Management didn't specify maintain and utilize clear timetables with small milestones


Management didn't maintain and trail change to the project budget

Additionally, the budget and time constraints of the projects were seen to be a differentiator with their success. Goulielmos (2003) areas that of the four concepts of inability in Information Systems is process failing where the task over runs its budget or time constrictions. TAURUS have both incurring increasing marketing attention and scrutiny, which resulted in a rise in strain on the job team (Brain, 2001).


Throughout the job there have been several indicators that were skipped.

The project conclusion date was postponed 100%

Constantly changing requirements

Project not being accepted by major stakeholders

Incomplete specifications

100% over cost.

Fragmentation of the job (components to interact)

Appraisal of leading system development methodologies

Waterfall Model

This is the most frequent and common of life circuit models, also referred to as a linear-sequential life circuit model. It's very easy to understand and use. In a waterfall model, each stage must be completed in its entirety prior to the next phase will start. At the end of each period, a review takes place to see whether the task is on the correct path and whether or not to keep or dispose of the project. Unlike what I mentioned in the overall model, stages do not overlap in a waterfall model.

Waterfall Life Routine Model


Simple and easy to use.

One of the primary features of the waterfall model is its ease. It is conceptually uncomplicated and divides the top task of creating a software system into some cleanly divided phases, each phase interacting with another logical concern. Additionally it is easy to manage in a contractual setup-as each phase is completed and its own work product produced, some sum of money is given by the customer to the expanding organization.

The project management stakeholders are required to correctly identify the business requirements paperwork (BRD) and the task management requirements. With the sometime the designers are forced to understand these thoroughly before they start writing the program requirements specs (SRS), advanced design and code.

It essentially requires records at every level. This gives better knowledge of the requirements, the reasoning of the codes and tests that were conducted on the software.


The project opportunity statement needs to be complete in infinite depth right away because changes are not possible when working with waterfall methodology. It is because the only way to amend something has been already developed is to return and start again. This may cause huge problems on jobs where the task sponsors are indecisive and quickly causes range creep.

Project communications with your client are extremely limited being either at the beginning or by the end of the development. Among, there is no manner in which one can get opinions or potentially clarify any misunderstanding over what the necessity actually means. The knock on impact is that it's up to the project team to make the key decisions on what requirements can be developed within the timeframes required, and what's developed later in a later deployment release by project planning in groups. This not only increases the overall time required to develop the program but does mean that regardless of the team's best initiatives, the customer may be extremely miserable with the end product delivered.

Key team members stay idle for long durations. The thing is that Waterfall does not are powered by a matrix basis making project tool management an exceptionally rigid activity. Essentially those allocated to the project stay on it until that phase is over. This as we can see right now, has a direct knock on influence on the project budget.

It is a very inflexible method which does not entertain any change in requirements and making any subsequent efficiency changes required extremely difficult and expensive to apply. As such the fast speed of changing requirements motivated makes this strategy difficult to use and calls for more quick methods of software development such as agile technique.

Prototyping Model

This is a cyclic version of the linear model. On this model, after the requirement analysis is performed and the look for a prototype is manufactured, the development process gets started. After the prototype is created, it is directed at the client for evaluation. The client tests the offer and provides his/her feed back again to the designer who refines the merchandise based on the customer's exact expectation. After having a finite variety of iterations, the final software package is given to the customer.

In this methodology, the program is evolved therefore of periodic shuttling of information between the customer and programmer. This is actually the most popular development model in the modern IT industry. Most of the successful software products have been developed by using this model - as it's very difficult to grasp all the requirements of a customer in one shot.


For example, design documents, a test plan, and a test case specification aren't needed through the development of the prototype. Another important cost-cutting measure is to lessen testing. Because evaluating consumes a significant part of development expenditure during regular software development, this has a significant impact in lowering costs. Through the use of these types of cost reducing methods, it is possible to keep the price tag on the prototype to less than a few percent of the full total development cost.

Overall, prototyping is perfect for jobs where requirements are hard to find out and the self-assurance in the mentioned requirements is low. In such projects where requirements aren't properly understood initially, using the prototyping process model can be the most effective method for developing the software. It is also an excellent technique for minimizing some types of dangers associated with a task.

Agile Methodology

Agile methodology can be an approach to job management, typically used in software development. It helps teams respond to the unpredictability of building software through incremental, iterative work cadences,

10 Key Guidelines of Agile Software Development,

Active user involvement is imperative

2. The team must be empowered to make decisions

3. Requirements progress but the timescale is fixed

4. Record requirements at a higher level; light and portable & visual

5. Develop small, incremental produces and iterate

6. Focus on repeated delivery of products

7. Complete each feature before shifting to the next

8. Apply the 80/20 rule

9. Examining is integrated throughout the project lifecycle - test early and often

10. A collaborative & cooperative strategy between all stakeholders is essential

IT/IS Tasks Fail. AND EXACTLY HOW Agile Guidelines Help

Common reason behind failure

How agile helps

Project Initiation & Planning Issues

Poor description of project scope and objectives

Agile projects also benefit from clear meaning of scope and targets, even though details are permitted to emerge throughout the development.

Insufficient time or money directed at project

If only agile could solve this!

Long or unrealistic timescales; forcing project end dates despite best estimates

Agile tasks encourage brief and regular iterations, producing the software and delivering working product in small bite size bits.

Technical & Requirements Issues

Poor or no requirements classification; imperfect or changing requirements

Agile jobs expect requirements to be incomplete and changing. That is the characteristics of software. Rather than resisting this, agile jobs provide for it by allowing requirements are permitted to emerge and develop. Requirements being produced over a feature-by-feature basis, just with time to be developed, aid in definition since it breaks this rigorous process into small parts instead of being truly a mammoth effort in advance.

Unfamiliar or changing technologies; insufficient required specialized skills

Agile methods don't help immediately with this problem, although can help to surface such issues early, and make them visible.

Stakeholder Management & Team Issues

Inadequate awareness of project status

Agile projects provide clear visibility of measurable improvement on a daily basis.

Project associates lack experience and don't have the mandatory skills

Agile principles can help to surface such issues early on, as they could well be noticeable in early on iterations of the software. Regular delivery of iterations and constant testing can help mitigate this risk when it could otherwise go unnoticed until much later in the project.

Poor cooperation, communication and teamwork

Close cooperation and collaboration between all stakeholders is essential.

Project Management Issues

Weak ongoing management; inadequately trained or inexperienced job managers

Agile methods and ideas are just management tools. A fool with a tool is still a fool!

Ineffective time and cost management

Daily presence of measurable improvement.


The most Triggers for Software Projects to are unsuccessful Changes in Requirements

Classical Software Development life cycles assume that the requirements are fixed at the start of the job, Customer only views the product at the end of the program development, Customer is not aware of the current status of the program Development. This happens due to changes in the Business environment, as the customer runs on the software component, he/she will dsicover new features that are necessary

All modern software development methodologies (such as Agile) encourage shorter iterations, usually iterations are measured in weeks, and the designers demo the new features through the meetings with the client by the end of every iteration. The customer can provide valuable opinions that will ensure that the software developed will meet the customer's genuine requirements.

More than 7 000 students trust us to do their work
90% of customers place more than 5 orders with us
Special price $5 /page
Check the price
for your assignment