Please answer the following questions below with True or False:

T F Many newly hired and recently promoted IT staff members sometimes are assigned to maintenance projects because their managers believe that maintenance work offers the best training experience. T F IT staff members usually initiate requests for perfective and preventive maintenance. T F If a maintenance request involves a severe problem, a system administrator either accepts or rejects the request or postpones action pending further study. T F When corrective action cannot occur immediately, users appreciate feedback from the system administrator and should be kept informed of any decisions or actions that affect their maintenance requests. T F In many companies, the systems review committee separates maintenance requests from new systems development requests when evaluating requests and setting priorities. T F As enterprise-wide information systems grow more complex, configuration management becomes unimportant. T F A system implemented in multiple environments always has the same version for each platform, and thus requires the same maintenance updates. T F Few maintenance projects require documentation changes. T F A change from version 1.4 to 1.5 indicates a significant upgrade, while whole number changes, such as from version 1.0 to 2.0 indicate relatively minor enhancements. T F Using a release methodology increases the documentation burden. T F With a release methodology, even when changes would improve system efficiency or user productivity, the potential savings must wait until the next release date, which might increase operational costs. T F The IT staff are responsible for configuring systems that have several modules at various release stages