User:Riskriskrisk

As a retired Boeing software engineer, I came to learn that the 3 most important things to consider when designing a complex, software-intensive system that delight's stakeholders, and planning a project to construct it are risk, risk, and, you guessed it, risk.  Beneath the trades of cost, quality and schedule lurk known and unknown unknowns. Good engineers are constantly swiveling their head to find these risks which unfound, result in unhappy customers with unachieved missions. I thought I had left this all behind after retiring in New Orleans when along came Hurricane Katrina, a fast moving natural phenomena that triggered a series of man-made catastrophies which are still bedeviling me after two years. All the calamaties could have been avoided if key engineers, managers and administrators had individually and collectively consider risk.

You will find this risk theme sprinkled throughout my posts. I invite you to become more familiar with modern risk management concepts particularly those esposed in Barry Beohm's model-driven software development and the Rational Unified Process