There is a chance tomorrow when you set out in your car for work, you may get struck by a bus, or a truck, or another car, or a tree might jump out in front of you. The chance will increase if you forget to put in your contacts, or decide to talk on your phone whilst driving. Take a train and the risk is reduced significantly.
The same applies for computer system stability. Implement any sort of change to a computer system and the chance that the system will become unstable and possibly unavailable increases. Perform some thorough testing and planning and the chance decreases. Risk management at face value sounds relatively straight forward unfortunately, most often it is compromised as a result of the “Bermuda Triangle” of software development: Time, Cost and Quality. The triangle works on the principle that as more emphasis is placed on one element, less is placed on the others.
When a solution is designed, there are typically functional requirements that must be met however non-functional requirements are often over looked or left until far too late in the process. These non functional requirements relate to important issues such as security, performance, capacity & availability.
Read more of this post