tailieunhanh - Software Engineering A PRACTITIONER’S APPROACH phần 3

một đặc tính của những hậu quả tiềm năng của các lỗi (hàng được dán nhãn 1) hoặc một thất bại để đạt được một kết quả mong muốn (hàng có nhãn 2) được mô tả. Các thể loại tác động được lựa chọn dựa trên các đặc điểm phù hợp nhất với mô tả trong bảng. | CHAPTER 6 RISK ANALYSIS AND MANAGEMENT 151 a characterization of the potential consequences of errors rows labeled 1 or a failure to achieve a desired outcome rows labeled 2 are described. The impact category is chosen based on the characterization that best fits the description in the table. RISK PROJECTION Risk projection also called risk estimation attempts to rate each risk in two ways the likelihood or probability that the risk is real and the consequences of the problems associated with the risk should it occur. The project planner along with other managers and technical staff performs four risk projection activities 1 establish a scale that reflects the perceived likelihood of a risk 2 delineate the consequences of the risk 3 estimate the impact of the risk on the project and the product and 4 note the overall accuracy of the risk projection so that there will be no misunderstandings. Developing a Risk Table A risk table provides a project manager with a simple technique for risk A sample risk table is illustrated in Figure . Risks Category Probability Impact RMMM Size estimate may be significantly low PS 60 2 Larger number of users than planned PS 30 3 Less reuse than planned PS 70 2 End-users resist system BU 40 3 Delivery deadline will be tightened BU 50 2 Funding will be lost CU 40 1 Customer will change requirements PS 80 2 Technology will not meet expectations TE 30 1 Lack of training on tools DE 80 3 Staff inexperienced ST 30 2 Staff turnover will be high ST 60 2 Impact values 1 catastrophic 2 critical 3 marginal 4 negligible FIGURE Sample risk table prior to sorting 2 The risk table should be implemented as a spreadsheet model. This enables easy manipulation and sorting of the entries. 152 PART TWO MANAGING SOFTWARE PROJECTS FIGURE Risk and management concern DVKE Think hard about the software you re about to build and ask yourself What can go wrong Create your own list and ask other members of the software team to .