SYSC 4106 Lecture Notes - Lecture 5: Event Management, Debt Management Plan, Relate

• School: Carleton University
• Department: Systems and Computer Engineering
• Course: SYSC 4106
• Professor: Samuel Ajila

Document Summary

Sysc (cid:1008)(cid:1005)(cid:1004)(cid:1010) lecture (cid:1009): risk a(cid:374)alysis : some definitions of risk. It involves a possible cause and its effect(s). Might affect the successful completion of a software project: ex. developer leaves vs task delayed, risk category framework: a sociotechnical model, a sociotechnical model (bottom to top): hardware, o/s, data, app, design, Organization, people: (cid:862) o(cid:272)io(cid:863) is orga(cid:374)izatio(cid:374) a(cid:374)d people, (cid:862)te(cid:272)h(cid:374)i(cid:272)al(cid:863) is e(cid:448)er(cid:455)thi(cid:374)g (cid:271)elo(cid:449) Ignore when impact, probability of occurrence, and management concern is low: have to do something in white area outside disregard area. In gray area, abandon the project: risk assessment, for assessment to be useful, a risk referent level must be defined. In reality, the referent level can rarely be represented as a smooth line on a graph. In most cases it is a region in which there are areas of uncertainty; that is, attempting to predict a management decision based on the combination of referent values is often impossible.