Assignment: Bead Bar Network Paper
Join now to read essay Assignment: Bead Bar Network Paper
Assignment: Bead Bar Network Paper
Ken Wexler
Axia College
Assignment: Bead Bar Network Paper
In this paper I will outline the development of a high-level computer network design for Bead Bar. The text will explain the recommendations of a network topology I think should be used, the network architecture, and the advantages and drawbacks that the recommended network would provide to the organization.
Bead Bar is company that has three divisions: Studios, Franchises, and Bead Bar on Board. The studio division oversees the companys six bead bar studios. Along with the original, there are now two studios in New York City, one on Long Island; one in Washington, D.C. and; one in Boston, Massachusetts. The franchise division sells a complete beading supply package to businesses that want to open their own bead studio. The division is responsible for fulfilling franchisees supply requirements. The company still uses paper-based forms. The Bead Bar is now large enough that the paper-based system is inefficient and has caused some problems, including lost orders, incorrect invoicing, and fulfillment delays. Therefore, a new computer network and website will allow Bead Bar to go global.
The recommendations I would choose for a network topology would be the bus topology for a start. The bus network topology is inexpensive and simple to configure. Simply add whichever hardware by plugging the hardware into the network. Bus Networking does have its disadvantages, which is why an upgrade would be needed later.
The network architecture I would recommend for Bead Bar would be the client/server type because the file servers become the heart of the system, providing access to resources and providing security. Individual workstations (clients) have access to the resources available on the file servers (FCIT).
Since Bead Bar is just beginning to go global, and before they know if their business will take off on the Web they should keep costs at a minimum. That is why I believe the Bead Bar should use a bus topology. The bus topology is probably the most simple of the network topologies. In a bus topology, all the devices on a network are connected to a common central cable called a bus, which is the backbone of the network. A backbone is the main portion of a computer network that is capable of carrying the majority of traffic on the network. The backbone is commonly used to connect large networks or companies together.
The major advantages of the bus topology are that it is relatively inexpensive and; it is easy to add new devices to the network by simply connecting them to the bus. Due to its low cost and simple configuration, the bus topology would be the appropriate choice for the Bead Bar.
The disadvantages of the bus topology are that if the main cable fails; the entire network will shut down and; it may be difficult to determine why the cable failed. Other disadvantages are that terminators are required at both ends of the backbone cable and; it is not meant to be used as a stand-alone solution in a large building (FCIT). Although a networks topology specifies how a network operates at a physical level, its architecture defines how it operates at a conceptual level.
Going into further detail as to why I recommend a client/server type of architecture for the Bead Bar. The client/server will help to control and operate what features Bead Bar wants to import, and will allow organized information from clients to be sent. In networks with client/server architecture, certain computers act as providers of services, or servers, and others act as requesters of services, or clients. A server is a powerful computer with a fast processor and large memory that is capable of handling simultaneous requests from clients. Some servers may be set up to provide shared data for clients, some handle only printing, and others might provide a variety of services.
There are many advantages to the client/server system. For example: client/server is centralized (FCIT). So, this type lets the user consolidate data in one place, because data is always accessed by requesting it from the server,