“…Common techniques introduced in undergraduate software engineering courses include risk exposure, which quantitatively analyzes the probability of an unsatisfactory outcome and the loss to the stakeholders affected if the outcome is unsatisfactory 9 . Another method taught in the classroom, as well as used in industry, is the listing of project top-n risk items (e.g., n=10) 9,10,11,12 . Examples of top ranked risk items are personnel shortfalls, requirements volatility, architecture complexity, and quality tradeoffs.…”