<p> Network Design Document</p><p>Project Client Organisation: Contact:</p><p>System Name <<To be created by team and client>></p><p>Date of Design <<Date of this version>> Document</p><p>Document Status Draft / Approved <<delete one>></p><p>Document <<FileName.doc>> Reference</p><p>Version Number Version 1<<update as necessary, in whole numbers>></p><p>Prepared by <<Technical Writer>></p><p>Team Members << Names of other team members>></p><p>09041d254826f2fa0bc2d956bb07fa5a.doc 1 of 5 1. Change History</p><p>All changes to the Design Document must be recorded in the Change History.</p><p>Date Description of Reason for Author of Version No. Change Change Change dd/mm/yyyy Initial draft N/A Version 1</p><p>09041d254826f2fa0bc2d956bb07fa5a.doc 2 of 5 2. Table of Contents</p><p>1. CHANGE HISTORY...... 2</p><p>2. TABLE OF CONTENTS...... 3</p><p>3. EXECUTIVE SUMMARY...... 4</p><p>4. PROJECT GOALS...... 4</p><p>5. LOGICAL DESIGN...... 4</p><p>5.1. LOGICAL NETWORK DIAGRAM...... 4 5.2. ADDRESSING AND NAMING STRUCTURE...... 4 5.3. ROUTING AND SWITCHING PROTOCOLS...... 4 5.4. SECURITY...... 4 5.5. VIRTUAL LANS...... 4 5.6. WIRELESS NETWORKS...... 5 5.7. QOS DESIGN...... 5 5.8. NETWORK MANAGEMENT...... 5 6. PHYSICAL DESIGN...... 5</p><p>6.1. NETWORK TOPOLOGY...... 5 6.2. LAN TECHNOLOGIES...... 5 6.3. WAN TECHNOLOGIES...... 5 6.4. PHYSICAL NETWORK DIAGRAM...... 5 6.5. MINIMAL SERVER AND PC REQUIREMENTS...... 5 6.6. WIRELESS TECHNOLOGIES...... 5 7. REFERENCES...... 5</p><p>09041d254826f2fa0bc2d956bb07fa5a.doc 3 of 5 3. Executive Summary <<A high level summary of your proposed network design. It should briefly point out the major strengths of your design and how it meets the customer requirements. The executive summary should be half a page to a page in length.>></p><p>4. Project Goals <<This section has to give a brief description of each goal that the customer has specified for the new (or upgraded) network that you are presenting in the rest of the design document. Within the rest of the document you should refer back to these goals to show how your design meets every single one of them. Again this is a fairly short section and should not be longer than a page.>></p><p>5. Logical Design <<This is the major part of your design document. All aspects of the proposed solution have to be explained in detail and justified.>></p><p>5.1. Logical Network Diagram <<The logical diagram describes the architecture of the network: Subnetting (VLAN) architecture, geographic spread of the network, main interconnecting devices, location of key network services. Overview of addressing and naming should be included in the diagram. See Reading 5 Figure 10.9 as an example of a simple logical network diagram. Other examples will be posted to the forum.>></p><p>5.2. Addressing and Naming Structure <<This section has to include  Subnetting plan (fixed or variable length subnetting)  Statically allocated IP addresses (for routers, servers, ..)  DHCP address ranges for each subnet  Naming scheme (domains, severs, routers, hosts)</p><p>Again each of the choices for subnetting and naming has to be explained and justified.>></p><p>5.3. Routing and Switching Protocols <<In this section you discuss the choice of routing and switching protocols for your network solution. The features of the chosen protocols should be discussed and you have to show why this is an appropriate routing/switching protocol for the proposed network. If your design includes different routing areas or multiple routing protocols a diagram has to be included that shows which of the routers participate in which area/protocol.>></p><p>5.4. Security <<Considering the security of the network infrastructure is a key part of the design process. This section should discuss  location of firewalls  devices in the DMZ  VPN tunnelling end-points  Access Control Lists</p><p>One (or several) diagrams showing the different security zones in your network, the access restrictions and the location of the devices responsible for implementing security. The designed security architecture has to be explained in detail and justified.>></p><p>5.5. Virtual LANs <<If your project requires you to implement VLANs or if you decide that VLANs will be beneficial to your design you have to include this section. Your VLAN design has to include  Number of VLANs  Which user groups belong to which VLAN </p><p>09041d254826f2fa0bc2d956bb07fa5a.doc 4 of 5  Which servers belong to which VLAN  VLAN trunking  Inter-VLAN routing</p><p>You should discuss the benefits of your chosen VLAN allocation, how the resources (servers) are allocated and/or distributed between the VLANs and if communication between the VLANs is necessary.>></p><p>5.6. Wireless Networks <<If your project includes a wireless network, this section should discuss:  Location of wireless APs  Subnets for the WLANs  Channel allocation for each AP if multiple APs are used  WLAN specific security considerations>></p><p>5.7. QoS Design <<If your project includes a quality of service component, this section should discuss:  Necessary Qos Classes for the application used in the organisations  Mapping of application programs to QoS classes  Traffic parameters for each QoS class>></p><p>5.8. Network Management <<If your project includes a network management component, this section should discuss:  Monitoring goals  Architecture of the monitoring applications  Network Performance criteria of interest  Detailed list of measurements and monitoring specifics>></p><p>6. Physical Design 6.1. Network Topology <<The physical topology (star, full mesh, bus, ..) of the network at each site and the topology of the inter-site connections (if your client has multiple sites). >></p><p>6.2. LAN technologies <<You have to discuss and justify your choice of LAN technologies (Ethernet, FDDI, Token Ring, ..). >></p><p>6.3. WAN technologies <<You have to discuss and justify your choice of WAN technologies (dial-up, fibre optic, microwave, …).>></p><p>6.4. Physical Network Diagram <<This section should include a physical network diagram for your LAN/WAN design. >></p><p>6.5. Minimal server and PC requirements <<The minimal requirements for server and user computers based on the applications that will be used in the network and number of users. >></p><p>6.6. Wireless technologies <<If your project includes a wireless network, you have to discuss and justify your choice of wireless technologies (IEEE 802.11a/b/g, Bluetooth, …)>></p><p>7. References <<You must acknowledge all official publications that you use during the life of the project. HOWEVER, templates and other materials provided by lecturers do NOT need to be acknowledged.>></p><p>09041d254826f2fa0bc2d956bb07fa5a.doc 5 of 5</p>