...[pic] MUHAMAD SUFRI BIN MUHAMMAD 158034 SOFTWARE VERIFICATION AND VALIDATION DR. SALMI BT. BAHAROM ESSAY ON SOFTWARE FAILURE (FAILURE OF RADIATION-THERAPY MACHINE) SOFTWARE FAILURE IN RADIATION THERAPY MACHINE Computer programmers spend a lot of time debugging software, yet end users like us still encounter bugs or problem while using those software. Computers bugs can result in many errors including unexpected program crashes or even can result in many troubles such as lost cost, reputation of the software product or even life. There are many software failures out there that we can find and learn from their mistakes. This is what happens at National Cancer Institute, Panama City on November 2000 which at least has eight unluckily patients die, while another 20 receive overdose concerned will get risk of health problems or serious complications from radiation. Twelve years ago, Victor Garcia considers himself lucky to be alive which a combination of cancer and miscalculation almost killed him. The software which created by Multidata System International, a U.S firm get trouble due to limitations of the computer program that guided use of a radiation-therapy machine. It is also miscalculates the proper dosage of radiation for patients undergoing radiation therapy. In order to use this software, it is allows a radiation therapist to draw on a computer screen then the placement of metal shields called...
Words: 1174 - Pages: 5
...1 - What are the failure factors for the first NIKE-i2 ERP-SCM implementation? The following factors contributed to the failure if the ERP-SCM implementation for Nike which then resulted in a loss of $48 million for the year: • i2 Inexperience: Nike although were aware that i2 was unable to provide all the required functionalities initially, requested i2, who were already inexperienced with the footwear industry, to adjust and provide high level of complex customization. • Integration: Nike failed to hire a Third Party Integrator which could have assisted them in overlooking the entire implementation. The integrator could have advised on any issues as well as act as a means of communication between Nike and i2. Instead, i2 was not even integrated with the current SAP ERP, and was rather set up to perform in complete isolation • Customization: Nike underestimated the complexity of the implementation by demanding i2 high level of customization by having an extremely high level of detailed forecasting in addition to trying to forecast too far ahead. i2 was unable to keep up with the quick changes in the market and seasonal trends and thus creating several delays and inaccurate forecasts. • Pilot Test: Nike underestimated the potential risk of failure in implementing i2 and did not conduct any pilot testing. Having done so, could have prevented or at least minimized their losses. A pilot test would have enabled them to be better equipped and deal with...
Words: 934 - Pages: 4
...London Ambulance Service Software Failure The London Ambulance Service (LAS) responds between 2000 and 2500 calls per day with a fleet of 750 vehicles, in less than three minutes. Their system was originally manually operated where details of an incident call taken by a control assistant is used to ascertain the location of an incident scene through the use of a map book. This information is then passed to a dispatch team who direct the appropriate ambulance to the incident scene through a radio call. Due to the short comings of this manual system, the LAS thought to computerize its dispatch system in 1987. The first attempt was started in the 1980’s, abandoned in 1990 and failed after spending £7.5 million. The second attempt by LAS was signed in May 1991. On the morning of Monday 26th October 1992 the LAS CAD system went live for the first time. Unfortunately there were 81 known bugs in the system at that time and it had been 10 months since the control room staff were first trained to use the software. The system had 4 primary flaws when it went live; it did not function well. Furthermore, the user interface had black spots which meant that the user could not see all the information on screen and finally, additionally, the system stored incident information even after it was not needed, which caused the system to fill up memory and fail. The first of these problems began to show during the morning rush of calls; there were a number of duplicate calls which led to a...
Words: 1738 - Pages: 7
...Software Project Failure and Solutions According to Krigsman, (2007) business-critical and services project are not completed on time, cost too much, contain a lot of defects and fail to satisfy the business requirements they set out to achieve. Clancy, (1995) states that United States spend more than $250 billion each year on approximately 175,000 IT development project of which most will fail and that software development projects are in chaos. This paper aim to explain the reason why a significant amount of software projects fail and what make software projects succeed by reviewing evidence from a few reports and surveys. Research conducted by Standish Group in 1995, shows that 31.1% of project will fail before they are completed and 52% of project will cost 189% of their original cost. On average only 16.2% of software projects are finish on time and on-budget and 9% of software projects are finish on time within budget for large companies. Similarly failure figures for project failure due to restarts, cost overruns, tie overruns were disheartening and to make things worst nothing change since then (Clancy, 1995). The Standish Group survey of IT executive manager reveals that user involvement, executive management support and clear statement of requirements are the three major reasons why project succeed. Incomplete requirements and lack of user involvement are the main opinion why projects are impaired, eventually cancelled and hence fail. Table 1: Some of...
Words: 1125 - Pages: 5
...FAILURES POSS / 355 Moore Clarence 29 june 2015 BOB O CONNER To begin what is a distributed system? There are several words that can describe parts that make up a distributed system. A program , a process, a message, packet, protocol, network components all take part in helping define what a distributed system makes of. A distributed system is an application that executes a collection of protocols to coordinate cooperate together to perform a single or small set of related tasks. Failure is the defining difference between distributed and local programming. So you have to design distributed system with the expectation of failures. Handling failures is an important theme in distributed systems design. Failures fall into two obvious categories. Hardware and software. Hardware failures was once an issue but since has improved a lot. Dealing with a lot of improvements to such items as wiring and circuits played positive roles to improving hardware the mechanical and network failures are part of todays problems. Software failures is part of a distributed system. When a software failure occurs it often affect downtime to the distributed system. The computer freezing or fail stop and so often even a network failure. Types of failures includes crash failures that is when a server halts, but its working correctly until it halts. Omission failure is another type of failure that a server fails to respond to incoming requests also fails to receive incoming messages or fails to...
Words: 346 - Pages: 2
...POS/355 March 11, 2013 Bhupinder Singh Failures Paper The distributed systems are unique in that it’s executions of the application of the protocols are to coordinate on multiple processes on the network, they have their own local memory and it communicates in entities with each of them using a massage passing mechanism. They also have their own personal users to them that they can use for personal uses. What are shared across the distributed systems are the data, processor, and the memory that can achieve those tasks when processing information. The distributed system has features to help achieve in in solving problems and issues with software and programs, when being useful with the distributed system is not very easy; its capabilities are the components, than just the stand alone systems that are sometimes not as reliable. Because of the complexities of interactions between running the distributed systems, it must have special characteristics like the fault tolerant; this can recover from component failures without performing incorrect actions. Recoverable is where failed components can restart and then rejoin the system after the cause failure has been repaired. The failure on a distributed system can result in anything from easily repairable errors to a catastrophic meltdown. Fault tolerance deals with making the system function in the presence of defaults. Faults can occur in any one of components. In this paper we will look at the different...
Words: 811 - Pages: 4
...Virtualization Executive Summary Jeremy Wright WGU Virtualization Executive Summary Physical servers are prone to failure and require replacement to guarantee availability to the business. Imagine if we took all of those servers and moved them onto a platform that could significantly raise their overall availability, cost less money and made us more technologically agile. There is a way to accomplish all of these goals, and it comes through virtualization of the servers. Availability All of the services that you use every day are run somewhere on a single physical server in our datacenter. Your e-mail is supported by a single physical box that sits neatly in a rack. If that server experiences a power failure or has a part fail, then you will not be able to access your email until a member of my team repairs that server and restores services. When we move to a virtual server platform, we abstract the mail server software away from the physical box and virtualize it into a pool of many redundant host machines. If one of those host machines were to experience a similar issue as mentioned before, the email server would simply migrate to a host that was still functioning as intended. This means that you never miss an email and we can solve the issue behind the scenes without any impact on operations. Costs We are currently replacing an average of 9 physical servers every year. The average server costs around $10k. We are spending $90k a year to replace servers. We can...
Words: 422 - Pages: 2
... | |[Week 4 Individual Assignment-Failures] | | | Types of Failure in Distributed System December 5, 2012 Types of Failure in Distributed System To design a reliable distributed system that can run on unreliable communication networks, it is utmost important to recognize the various types of failures that a system has to deal with during a failure state. Broadly speaking failures of a distributed system fall into two obvious categories: hardware and software failure. A distributed system may suffer any of such types of failures. Yet each of the failure has its own particular nature, reasons and corresponding remedial actions to restore smooth operation (Ray, 2009). Follow are few types of failure that may occur for a distributed system. Transaction failure: Transaction failure is a centralized system failure. The failures generally occur due to two types of errors. These errors are: application software errors and system errors. In case of any logical error in the application software that is used for accessing a database the transaction will not...
Words: 731 - Pages: 3
...Failures of a Distributed System POS/355 July 25, 2013 Failures of a Distributed System In the words of Adam Savage from Mythbusters, “failure is always an option”. This holds true when talking about a distributed system, which is a computer network like a Wide Area Network (WAN) or a Local Area Network (LAN). Distributed systems is defined as a software system in which components located on networked computers communicate and coordinate their actions by passing messages (Coulouris, Dollimore, Kindberg, & Blair, 2012). This allows the computers or even devices like smart phones and tablets, to share resources like printers, hard drives, and even internet access. A centralized system is a computer that is by itself, one that is not connected to a laptop. Think of a centralized computer as one of the spy computers in movies, like Mission Impossible. These systems can and will fail, while sharing some failures; a distributed system has more components that could fail, leading to them having more problems. There a many things that could fail on a distributed system, this paper will cover four of them, starting with hardware failure. Video cards, network access card, hard disk drives, solid-state drives, memory, and power supply units (PSU), these are all pieces of hardware that are in most of the computers sold today, and they can all die at a moment’s notice. Some of these items, if they failed would not affect the network or distributed system at all, like a video card...
Words: 1133 - Pages: 5
...dual degree in Finance and Information Management and Technology. She is aspire to become an effective international business communicator and is currently have more than one year working experience as business technology analyst. Practices that will cause failures in IM management In this specific position, the practice that you cannot correctly translate the business requirement into technical requirement will most likely be the case failure in IM management. Considering the specific profile listed above, it is possible for her to incorrectly translate the requirement since she didn’t have the strong technology background. Business analyst is now crucial for the success of the information management. Since this position provide the “translation service” for the business department and technology department, and imprecise translations will result in failure of the project. A study [2] has showed that poor definition requirements (50%), communications problems (14%) and inadequate risk management (17%) are the major reasons for failure of projects. And these are all related to business analyst. Illustration As shown above, poor definition requirements is the condition that most likely lead to the failure. For example, Business requirements are high level requirements that management and a board of directors would typically...
Words: 2192 - Pages: 9
...They both created commencement speeches for Harvard University that discussed their failures, their drive to help others, and their successes. These two speeches were both inspiring and motivating. When we take a look at Oprah Winfrey, we can see how incredibly successful she has become over the years. She had a 25 year run on her own television show, a magazine, and she currently has her own television network. Along with Winfrey’s success, she has had many failures. She did not allow those failures to define who she is; instead she used them as motivation. “And when you do I want you to know this, remember this: there is no such thing as failure. Failure is just life trying to move us in another direction” (Winfrey, 2013). In her commencement speech to the Harvard graduates, she used this quote to remind the graduates that they will fail but to not lose the motivation to succeed. She wants the graduates to use their success to help others, especially those who are less fortunate. When you think of Bill Gates, you may think there is no way the co-founder of Microsoft has ever failed at anything. Well, you’re wrong! Gates was a student at Harvard University but what you may not know is that he is a college drop-out. While he attended Harvard, he created numerous pieces of computer software but he considers dropping out of Harvard to be one of his biggest failures. As a software developer for Microsoft, he wanted to use his success to help the more under privileged...
Words: 648 - Pages: 3
...IT Project Implementation Failures Tracy Grainger HCS/483 September 19, 2011 Billy Kesserwani IT Project Implementation Failures The IT implementation process begins after an acquisition process. The acquisition process requirements are examined, the request for the proposal is sent, the vendor is chosen and contracts are negotiated and signed. When these parts have been finished the implementation can begin. During the beginning of the implementation the project has to be planned out ahead of time, a team must be selected and the best must be chosen, but problems should always be expected to happen along the line. Some of the IT problems that occur can often be prevented if you are paying close attention. In this particular case study, the implementation process seems to be working well. Dryer and Roberts decided to obtain a CPOE system running for their staff to use. Problems occur when the stakeholders in the faculty believed the system would only be more work for them and would not be very useful to their organization. This is the first sign to indicate a problem is happening. This is the first IT failure within the company. The organization and stakeholders must believe that the system is worth having, be willing to work with it, and believe in the help it will have for the organization. If the stakeholders think the system will fail ultimately then it will fail. They will not work and put forth the effort into the implementation process and training. Dryers and...
Words: 637 - Pages: 3
...Vulnerabilities/Weaknesses When looking at the companies vulnerabilities and weaknesses there are certain aspects to consider. “One aspect of analyzing a customer’s business goals is the process of analyzing vulnerabilities related to disasters and the impact on business operations.” (Oppenheimer, 2011, p. 13) By doing this you will determine what areas of Riordan’s network and services are critical to their business operations and where they are specifically located at, and how better to protect them to ensure operationally ability in case of physical disaster’s such as. Physical Vulnerabilities * Weather * Environmental disaster – Earthquake, flood, tornado * Fire or other preventable disasters * Political instability in foreign countries * Satellite used for communication between China and San Jose, satellite could fail, be destroyed, or lose communication based on orbit and location Once these physical vulnerabilities have been assessed and determined Riordan can then start the process of providing a continuity plan in case of one of these situations arise. By identifying and planning for this emergency’s Riordan will be better prepared to handle these vulnerabilities and protect against them so to minimize their threat to continued communications. Another aspect of assessing Riordan’s vulnerabilities and weaknesses is to conduct a security assessment. “The network is examined from within by professionals, trained in the vulnerabilities exploited...
Words: 422 - Pages: 2
...Network Failure One problem that may arise in a distributed system is a failure within the network. The processors on a distributed system must communicate with each other over a network and failure to do so could cause problems with the function needing to be carried out. In order to fix this problem, you would need to find out which end the problem is originating from. This can be done by checking the data sent by all the processors and seeing if the data is being sent correctly. This will help to determine whether or not the problem is in the sending of the data or the receiving of the data within the network. After isolating the source of the problem, it can be addressed appropriately. Timing Failure A timing failure can occur when processors on the network are not synchronized. When processors are not synchronized, then processes that require two or more processors might become delayed or fail all together. For instance, if a process the uses multiple processors is schedule to occur at noon and one of the processors’ clock is a couple minutes fast, that processor will start the process too early which could result in a failed process. This can be rectified by monitoring the synchronization of the processors and periodically checking to see that the synchronization of all the processors is in place. Omission Failure An omission failure occurs when a message is sent and it either fails to send or is not received by the second party. When an omission failure happens...
Words: 573 - Pages: 3
...According to Webster, a failure is classified as “an omission of occurrence or a state of inability to perform a normal or specified function that ultimately leads to a lack of success.” In the light of operating systems, this topic can be extremely important to a customer and designer of said system. Failures in a system can create catastrophic events that are costly in both monetary and emotional aspects. Faults within a system can be different in nature and can continue to wreak havoc on the system or to do nothing in some cases. Failures in distributed and centralized system can be specific in nature; however a generalized topic can describe the majority of these failures across the system. There are four types of failures in distributed systems that can affect functionality; but two of these four specific failures that can affect centralized systems as well. The general failures include: halting type failures, byzantine style failures, omission failures, and failures related to network issues. While all of these are important some of them affect a system more violently than others. The first types of failures to discuss are halting failures. These types of failures can be frustrating in nature since they affect most of the system and do not allow the operator to really investigate without rebooting the entire system. These failures essentially freeze the system without allowing any action to alleviate the issue. There can be many reasons for a halting failure such as hardware...
Words: 850 - Pages: 4
