Network Architecture Department of the IT Systems Functional Area There are thre
ID: 3532121 • Letter: N
Question
Network Architecture Department of the IT Systems Functional Area
There are three standard parts to the proposal for each role.
Instructions
Keep this in mind as you compose your updated plan. The IT Systems Functional Area focuses on the technology infrastructure and systems to support the business model of projected growth. The Network Architecture Department is one of the four main IT departments within the IT Systems Functional Area.
Perform research and place your compositions in the Composition section provided for Network Architecture Department after these instructions.
One component of your composition is to include is ethical considerations. Explain how the Network Architecture Department will adhere to a code of ethics available for stakeholders. The Teamwork Activity Challenge has a suggested resource.
For the second and third component of your composition, review the items below. Choose two to research and elaborate in your composition.
A. Accounting and Financial operations for current and projected revenue and costs.
B. External sales and product information for the company with an inventory control system and automated ordering processes and sales.
C. Human resource management to facilitate projected growth.
D. Production and operations for increased growth and profitability.
E. Web-hosted Internet B2B sales with customer support.
F. Hardware and software for 75 desktop systems supporting sales, marketing, inventory, and production.
G. Network.
H. E-mail.
I. Internal and external connectivity.
J. Internal applications and desktop support.
K. Other: please specify.
Explanation / Answer
It is a network communication design in which the physical components of computers are arranged in a sequence so that they can communicate with each other. Network is a combination of hosts, applications, routers, hardware, software and links of media. Network architecture is a guideline and technology for designing building and managing a network.The purpose of network architecture is to provide assistance and guidance to implement high quality network. The network architecture not only helps you to deploy the network but also assists you in troubleshoot and maintaining architecture. Network architecture also helps you security management and disaster recovery. Network architecture is composed of many layers. In the process of layering the communication tasks are divided into smaller parts, each part is further divided into sub tasks for accomplishing tasks. These subtasks interact with the other communication processes. The process of layering keeps the network design simple. There are many ways to design and set network architecture. There are many choices available to set up a network however every network must have three basic parts like network users, applications and devices. Network itself is operating at physical layer of the OSI model. The devices are operating mostly at data link layer or network layer. The application exists at the session layer of the OSI model. Lastly the user is at the last two layers of the model including presentation and application layer.
Gone are the days when a network encompassed a single building or campus. LANs, as we have come to know them, are a thing of the past. The local area network may be alive and well, but are our networks really as secluded as they used to be? Chances are, even if your company is physically located in one suite or area, you are connected to the Internet. In some cases, you may have employees who require access to resources and applications from outside the confines of your physical infrastructure. These remote employees are a growing segment of the modern-day workforce. The network engineers of today must be prepared to accommodate an environment in which the LAN may not be as local as it once was. Thus, we are all doing our part to make the planet one global network.
There are six basic network architecture components such as servers, proxies, clients, command consoles, server modules and cores. The server is the backbone of any network. The role of servers in network architecture is to communicate with proxies and other peered servers. They are at the top layer of the network and they do not communicate directly with client. Moreover servers receive complete projects and tasks .proxies can be termed as the focal point of the network because it facilitates the communication of the devices. Proxies usually perform buffering and they also communicate with the others of its type to share the loads of the network. The client systems are the workers of the network. They receive tasks, they interact with the users and they perform user applications. Command consoles are the network guidelines which provide assistance to users about how to control the authorize network nodes. The core is the real work done in the system. The cores are verified within the network and with the clients to prevent bad cores. Server modules handle the particular tasks of the server. Server module is generally registered with the server libraries; this would help the server to perform the needed task.
Network Architecture & Design: A Field Guide for IT Consultantswalks you through the design process, from gathering information to implementing the final product. Included is a reference guide for product uses and quirks, a glossary of terms, and a lot of diagrams from actual projects. The most popular products (at publication) are covered in great detail (Microsoft solutions for OS, e-mail and inventory tools, and many others). Some other technologies, such as Novell OS and NetBEUI, are included, but not in such detail. The book follows a logical process:
Gathering the Information
Designing the Network
Assembling the Components
Building the Network
Monitoring the Network
Feel free to navigate through the sections as your projects dictate (not all projects will flow the same way). However, if you are building from the ground up and have not yet started your project, please follow the sections in order; you will get more out of the book, and you may head off some nasty issues. Another point that is hammered in throughout this book is DOCUMENTATION. I can't stress enough the need for good documentation. The next few pages discuss laying the groundwork for good documentation and give some tips on how to organize what you have.
Finally, because the amount of information covered in each chapter is so vast, a summary is included at the end of each chapter. The summary contains all the major pieces of information covered in the chapter. It also can be helpful in reviewing the contents and product descriptions from previous chapters
The old method of network design was to divide a company into manageable pieces. The thought was that users in one part of a company (for example, Accounting or Legal) would have different network needs than the other parts of the company. The pieces would then fit together like a puzzle, creating a complete corporate infrastructure. (The software available at the time helped this mentality along. Most business applications were still very "client-heavy," meaning that a large part of the application resided on the client PC. Therefore, businesses segregated PCs by business function as a way of controlling who had access to what data.) The process would begin with an understanding of each department's needs and priorities. For example, the HR department would need access to the personnel database (or at that time the personnel folders). The Accounting department would need access to the financials. (SeeFigure I.1.) However, in most cases, nobody from one department should have access to the others' databases. Each department would be designed as a separate network, complete with user accounts, rights, and privileges. In some extreme cases, the multiple internal networks had very little contact with each other. This method of design may seem crude by today's standards, but it worked.