Just A Quick Overview..

9 Mar

Over the past few weeks we’ve all learnt a lot from each others blogs, which will be of huge help during April and May when we’ve cramming as much IS as possible! In previous blogs I have spoken about failures themselves, major global failures, how it’s not just computers that can be affected by failures and healthcare failures. For my last blog I would just like to do a quick overview of how we can reduce these failures from occurring.

  1. A lot of systems fail because people assume (and we all know the saying that goes along with that word!). By assuming, you are putting words into the clients mouth and giving them something that they mightn’t want in the first place. No wonder the system will fail! A probe that was sent to Mars memory became full and so an engineered deleted its memory on how to land, because he assumed it would never have to land again. This caused the probe to lose its ability to move its antenna, meaning they lost all communication with the probe.
  2. Poor user interface is also something that needs to be looked at when developing a system. Overly complex user faces are one of the major problems with the US government. A complex interface can be the difference between sending an invoice in the right currency or the wrong one – something that can seem small but adds up in the long run. Even when the userface is correct, staff still need to be properly trained in on the system.
  3. Systems can also fail because of a poor fit between the company and system. This can be because it was a system brought and not developed with the firm in mind especially. Although this can seem the easier and cheaper option in the short run, in the long run it can cost the firm thousands at least.
  4. Poor development practices is also a major factor. By having poor practices you are setting up a system to fail out right. This can be stopped by simply making out pro types for the client or even just listening properly!

This is only a short reminder of what other members in my group have said, and what I have personally discussed myself. I just felt it was important to have a few points in the end of the project about how to stop systems failing; not just look at the different types of failure that have occurred in various companies, even though we can learn a lot from past failures.


Best of good in the exams, hope I have helped 🙂





3 Responses to “Just A Quick Overview..”

  1. sad111708665 March 9, 2013 at 4:48 pm #

    …useful information about reducing failures! good blog. Best of luck in your exams too ! 🙂

  2. sad109566511 March 9, 2013 at 5:08 pm #

    Really enjoyed all of your blogs!thanks and best of luck to you too in you’re exams 🙂

  3. sad111350396 March 10, 2013 at 12:50 pm #

    Great to know theres ways in which to stop systems from failing and that its not all doom and glum. I personally think that of the 4 you have mentioned that ‘poor fit’ is the the one thta needs to be tackeled properly and effectively in order to reduce failures. The system and the company need to be interlinked to reduce failures. Great blog:)

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: