Determining New Requirements
Now that we have looked at the current network infrastructure, we will
start to look towards the future of the firm to help determine how the
network can be improved. Again, the Teare book presents a series
of steps that will first be presented summarily and then described in
Now we will go into much more detail about each of these steps.
Step 1 - Identify Business Constraints. The following outlines three major aspects of performing this identification.
Step 2 - Identify Security Requirements. The following outlines five major aspects of performing this identification.
One of the standard ways to help identify security requirements is to develop an Authorization Matrix. Such a matrix is going to list the services that users may need authorizations across the top. It is going to list the users and user groups and the sorts of authorizations they will need for these services down the side. Then the elements of the matrix are filled in with appropriate abbreviations to denoted things like read access, write access, administrative rights, report access and on and on. The following is a small example matrix for a small e-commerce firm.
R - read access
W - write access
E - execute access
U - use access
X - no access
|Step 3 - Identify
Manageability Requirements. The following outlines five major aspects
of performing this identification.
Step 4 - Determine Application Requirements. The following outlines five major aspects of performing this identification.
Step 5 - Characterize New Network Traffic. The following outlines three major aspects of performing this characterization. Two of these aspects have a sizable number of sub-aspects that will be outlined also. Since this entire step will often get more technical and involved than the other steps, we will dedicate an entire subsequent web page to this step.
Step 6 - Identify Performance Requirements. The following outlines seven major aspects of identifying performance requirements.
Step 7 - Create Customer Needs Specification Document (Optional). To create a customer needs document you need to record the customer's requirements and constraints, and the characteristics of the existing network. The goal of this document is to record the
The information from this page's process and the steps completed in the previous two webs are agglutinated and organized in one place.
This document can also serve as the basis of the agreement between you and your customer on the network design requirements. It is also an excellent start for the document you will produce when you complete the implementation of your design.