Network Proposal Memo

A. Why We Need a Client/Server Architecture

Before we purchased Brake, we had approximately 4,000 items in inventory and a customer database of approximately 800 clients. We had discussed , in numerous meetings, the advisability of committing to a full Intranet configuration, but the costs were deemed prohibitive. A large part of that problem has been eliminated with the purchase of Brake, since that company has a solid Intranet and Extranet program in place. What it does not have is customers, since the company was founded on the Amazon model, and

relied on the concept "If we build it they will come." They didn't.

And so we have a company with customers and no real communication infrastructure, and a company with an infrastructure and no customers. We have taken the liberty of doing a computer inven

. . .
data in the windows. This graphic (next page) shows the relationship of the elements discussed so far. Typical Client/Server Configuration
B. How Much does the Network Cost? As shown in the chart in the first part of this memo, there are a number of computers already in existence. Our plan calls for three servers (detailed later) and 55 client computers. Even though the chart shows that there are 45 PCs in the combined companies, we will eliminate the 21 486s and purchase an additional 34 PCS. Estimated cost for the 34 PCs is $30,000. The key hardware to buy or lease is the server. One of the servers we will use is a simple file server, in which the client passes requests for files or file records over a network to the file server. This form of data service requires large bandwidth and can slow a network with many users down considerably. Traditional LAN computing allows users to share resources, such as data files and peripheral devices, by moving them from standalone PCUs onto a Networked File Server (NFS). We will use the second server as a database and transaction server, in which all of the clients pass SQL (Structured Query Language) requests to the server and the results of the query are returned over
. . .

Some common words found in the essay are:
MIS Brake, Telecom Strategy, Mobasher Moore, Conclusions Traditional, Query Language, Unit MAU, Brake Environments, PCS Estimated, Linux/UNIX Servers, Client/Server Architecture, file server, user interface, na na, client/server computing, client process, tiger hqs, servers running, layer implements, plan calls, mobasher moore 1998, boley gini, servers running platforms, gini hastings mobasher, boley gini hastings, hall helmerich ca¦adas,
Approximate Word count = 1766
Approximate Pages = 7 (250 words per page)

More Essays on Network Proposal Memo