1 (40 %) A tech company creates software that transforms old-fashioned mainframe screens (known as "green screens") into modern browser-based interfaces that look like regular Windows screens. They made this because new employees find green screens confusing and hard to use. Each screen and program behave differently, which leads to mistakes and lots of notetaking. Pressing the F5 key in one program might mean go back one page, whereas pressing F5 in another program might mean clear the screen. New users are easily confused, make a lot of mistakes, and must write tablets full of notes on how to navigate all the screens. Your company bought this software and put you in charge of installing it. You are currently figuring out what could go wrong and how bad it could be. To help, you are using a method called the Delphi technique, which involve various experts in the field. You have gathered a group of experts, both from within your company and from outside, to share their thoughts on the risks involved. Here's a list of some potential problems they have come up with Vendor viability (will the software company stay in business?) Vendor responsiveness with problems after implementation Software compatibility risk with existing systems. Hardware compatibility risk. Connection to the mainframe risk. Training IT staff members to maintain the product. You send this list back to the Delphi members and ask them to assign a probability of 0.0 to 1.0 and an impact of high-high