Client or Server versus Web-based Approaches - Essay Example

Client/Server vs. Web-based Approaches Introduction: Organizations have had to struggle with the decision of choosing the type of implementation for their enterprise systems for quite some time now. This is generally because conflicting ideas and requirements emerge from the different disciplines that are required to tackle this i.e. IT and engineering. The organizations have had to make tradeoffs in terms of cost, functionality, simplicity in deployment, usability and long-term support (Goodyear, 2000). This paper looks into factors that are considered in deciding the implementation method for an enterprise system. Several issues should be examined when deciding on the software to purchase or develop for an organization. They include the extent to which the software provides functionality, the documentation and usability of the graphical user interface, the reputation of the software vendor and training and support availability. However, another important aspect is the deployment method of the software i.e. is the software going to be web based or is it going to be deployed as client/server software (Goodyear, 2000). Web deployed enterprise application software may be the best for some software applications. However, the client/server approach may incur less overhead and better performances, in some cases, compared to web based approach. Web Based Approach: Advantages: Accessibility of the application – This is because one can access the application remotely with the use of a browser and internet (Goodyear, 2000). Depending on the internet connection communication can be efficient and quite fast. Access can be done by the use of a password or a direct connection. This form of access allows employees who are not within the company premises to conduct business and carry out transactions from their location. Such access is beneficial to companies that have a sales department. The sales people are usually away from the business premises selling and looking for new customers. With such a system, the sales people are able to communicate with the company; thus, serving the customers better and faster. Less overhead costs – this approach does not require any software installation or implementation. Thus, cutting the costs associated with such processes (Goodyear, 2000). Small companies that want to make use of the reliability and performance but have no additional funds to implement them can make use of this approach. This approach requires no additional hardware or software; thus, eradicating any implementation risks. One does not need to worry about any costs associated with maintenance or software upgrades. It is also s simple software; therefore, requiring less overhead in the training of staff compared to the ERP client/server software. Disadvantages: Usability – Despite the fact that web-based systems have significantly improved over time, a lag still exists in terms of usability. Web based ERP applications have not been able to support the amount of usability of the interface that the users expect (Goodyear, 2000). Therefore, when implementing such an ERP system overhead costs can be incurred in training of users. This can also lead to disruption of company operations, since the users require more time to be fully trained. There is also the aspect of web browser being different in their presentation. Some browsers may create difficulties in the usage of such a system. Thus, the organization should decide on the browser that best displays the application and recommend it to the users. Security – this approach entails that the application can be accessed anywhere and on any computer as long as the internet and a web browser are present (Goodyear, 2000). This means that anyone can access the application’s login page. In an instance where the authorized users are careless with their passwords, a passerby may acquire the password, and access the application and alter or modify organizational data. However, if awareness is created among the users of the need of security, this risk can be eliminated or reduced. Client/Server Approach: Advantages: Usability – Software designed to be implemented using this approach is developed using rich languages that provide capabilities to facilitate a rich interface (Goodyear, 2000). Once developed, the application remains the same on each computer, unlike web based ERP software that depends on the browser. Performance – This approach is usually contained within a private network. The organization makes use of several servers to handle any incoming requests from the client computers. Therefore, the traffic in such a network is less compared to traffic in the internet. Hence, performance of applications deployed using this approach is significantly high. Security – This approach entails installation of the software in computers that are connected in a network. Passwords may be used for authentication and authorization. Therefore, for one to access the application, physical access to a networked computer is necessary. If an organization can limit access to their computers to authorized persons only, the chances of the system being hacked is very low since it is a private network Disadvantages: Increased overhead costs – it is very expensive to develop or buy ERP software (Goodyear, 2000). This software requires installation on computers that will be used in the company operations. Installation and implementation may entail the addition of new hardware and software. This adds on the expenses incurred in deploying the application. Thus, many small companies may not afford such ERP. User training – This application software contains many different modules to cater for all organizational operations. In essence, the application might appear to the users as a very difficult system to learn. Training requires going through all the modules that relate to the organization in intricate detail. This in the long run may add on to the overall costs especially if the trainers are paid by the hour. Accessibility of the application – This approach requires that the software be implemented on various computers in the organization network. This means that any computer whether on the network or not without the software installation cannot be used to access the application. This eliminates any support for remote access of the system (Goodyear, 2000). Such a system can, therefore, be termed as rigid since services provided on the ground will be slow and inefficient. Sales people would be required to either call in or avail themselves physically in order to get the required information or submit a request. Conclusion: The debate for whether web based software is better than client/server based software has been around for quite a while now. However, the real question should be considered specifically. Each organization requiring the services and performance of an enterprise software application should look into their organization to identify the best approach. Some aspects of the organization such as size, performance need, usability etc. should be carefully considered before deciding on the deployment method. Among the two methods, the web based approach is best favored because it requires minimal requirements in terms of installation. In case this approach does not adequately promote performance and reliability; the client/server approach may be a feasible approach. Reference: Goodyear, M. (2000). Enterprise System Architectures: Building Client/server and Web-based Systems. Boca Raton, FL: CRC. Read More