In the system design phase the system architecture is established. The system that was implemented at Gusher, Inc., was hurriedly done with little attention during the design phase. During the design phase Gusher Inc. could have done so many things differently to increase the chances of system success. Amongst the things they could have done differently include; establishment of an architecture document. The architecture document helps map the system requirements into an appropriate architecture (Louwers 642). By analyzing the architecture Jeffries could have identified the compatibility issues of the available mainframe and the system they were to purchase. Besides, they could have established the system requirements in the process. Proper communication; in the design phase, the organization only involved Hamilton in collecting the system requirements. A better way could have been to involve all the stakeholders. This could have resulted in less resistance as witnessed from the Hamilton’s staff.
Most problems were encountered because of poor system requirements definition. Only Hamilton was involved in the system requirements definition. This later resulted in staff resistance to the system as they did not see the need for the system. Also problems were encountered due to the selection of just one supplier; Jeffries had no time of sending for proposals to more vendors. Furthermore, the hardware on which the software purchased was to run was snot as powerful as was required.
A detailed feasibility study could have established the compatibility issues of the proposed system and the existing hardware. Similarly, such a feasibility study could have involved more people; this could have in effect resulted in less resistance from the staff upon rollout of the system.
Works Cited
Louwers, Timothy J. Auditing and Assurance Services. New York: McGraw-Hill, 2005. Print.
