he company would continue to use Microsoft Windows NT-based work stations or Microsoft Windows 98-based desk top as they are currently configured. Further, the servers for the companyÆs network would continue to be Microsoft Windows NT-based machines.
The director of the companyÆs IT Department agreed to consider the proposed change. This document presents the result of an analysis of the proposal. The structure of the document following this Introduction includes (a) analysis methodology, (b) analyses of the issues, (c) an implementation plan should the decision be to change from a single-operating system configuration to a multi-operating system configuration for the companyÆs network, (d) training costs should the decision be to change the configuration of the network, (e) cost-benefit effects of a change in the network configuration, and (f) conclusions.
The analysis methodology will follow a requirements analysis structure. The requirements analysis activity function may be considered as: (a) the identification of different perspectives on a proposed systemÆs functionality; (b) the negotiation and resolution of conflicts of these perspectives; and (c) the recording of this resolution. Parties who have contributed input for a requirements analysis have their own unique perspective on what the proposed system should be upon completion. Thus, it is important to seek out and examine the perspectives of all stakeholders and to resolve potential conflicts as early as possible in the process. As a part of the requirements analysis process, (a) all assumptions will be questioned, (b) all reasoning will be examined, and (b) each vision of the proposed system will be investigated (Nidumolu and Knotts 106).
The analysis methodology considers four potential configurations for the companyÆs network. The configurations are various combinations of operating systems for the companyÆs servers, work stations, and desk top mach...