In this way it was believed that risks could easily be


As an example of the situation in Problem 17-6, Figure 17-23 shows risk categories at the program, subsystem, and functional levels. Starting at the bottom, data are developed for five engineering indicators and rated according to "high," "medium," or "low" risk. Results of this assessment are then summarized for each subsystem to provide a system overview. This is often considered a template risk analysis method. What are the advantages and disadvantages of this approach? Why is this method not used extensively today?

Figure 17-23

626_548dd08a-48ad-4ec5-92a1-b671aaeab736.png

Problem 17-6

In the 1970s and 1980s, military organizations took the lead in developing ways to assess total program risk. One approach was to develop a rigorous process for identifying specific technical risk at the functional level and translating this detailed information through several steps. In this way, it was believed that risks could easily be monitored and corrected, as shown in Figure 17-22. Why is this method not being supported today?

Figure 17-22

 

2329_f8fef0c4-4051-4dc4-a080-c6a7ef69dd70.png

Request for Solution File

Ask an Expert for Answer!!
Basic Computer Science: In this way it was believed that risks could easily be
Reference No:- TGS01648804

Expected delivery within 24 Hours