[Author’s Name]
[Institution’s Name]
Essay on System Development
Client/Server
Client/Server is an arrangement used on local area networks that makes use of “distributed intelligence” to treat both the server and the individual workstations as intelligent, programmable devices, thus exploiting the full computing power of each. This is done by splitting the processing of an application between two distinct components: a “front-end” client and a “back-end” server. The client component, itself a complete, stand-alone personal computer (versus the “dumb” terminal found in older architectures such as the time-sharing used on a mainframe) offers the user its full range of power and features for running applications. The server component, which can be another personal computer, minicomputer, or a mainframe, enhances the client component by providing the traditional strengths offered by minicomputers and mainframes in a time-sharing environment: data management, information sharing between clients, and sophisticated network administration and security features.
The advantage of the client/server architecture over older architectures is that the client and server machines work together to accomplish the processing of the application being used. Not only does this increase the processing power available, but it also uses that power more efficiently (Eric, Gregory, 1999). The client portion of the application is typically optimized for user interaction, whereas the server portion provides the centralized, multi-user functionality.
Network Computing
The broad term "Network Computing" represents a way of designing systems to take advantage of the latest technology and maximize its positive impact on business solutions and their ability to serve their customers. Network computing represents the current wave in the progression of IS architectures from mainframe to mini to PC-LAN and onward. Information systems adhere to the network computing paradigm when functions are appropriately distributed between clients and servers connected by local and wide-area networks. Functionality is centralized to the extent that performance constraints allow and sufficient intelligence is provided locally to support a powerful user interface (Eric, Gregory, 1999). Furthermore, server capabilities are physically distributed as necessary to improve performance and resilience.
