All Changes to the Design Document Must Be Recorded in the Change History

Total Page:16

File Type:pdf, Size:1020Kb

All Changes to the Design Document Must Be Recorded in the Change History

Network Design Document

Project Client Organisation: Contact:

System Name <>

Date of Design <> Document

Document Status Draft / Approved <>

Document <> Reference

Version Number Version 1<>

Prepared by <>

Team Members << Names of other team members>>

09041d254826f2fa0bc2d956bb07fa5a.doc 1 of 5 1. Change History

All changes to the Design Document must be recorded in the Change History.

Date Description of Reason for Author of Version No. Change Change Change dd/mm/yyyy Initial draft N/A Version 1

09041d254826f2fa0bc2d956bb07fa5a.doc 2 of 5 2. Table of Contents

1. CHANGE HISTORY...... 2

2. TABLE OF CONTENTS...... 3

3. EXECUTIVE SUMMARY...... 4

4. PROJECT GOALS...... 4

5. LOGICAL DESIGN...... 4

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

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

09041d254826f2fa0bc2d956bb07fa5a.doc 3 of 5 3. Executive Summary <>

4. Project Goals <>

5. Logical Design <>

5.1. Logical Network Diagram <>

5.2. Addressing and Naming Structure <

Again each of the choices for subnetting and naming has to be explained and justified.>>

5.3. Routing and Switching Protocols <>

5.4. Security <

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.>>

5.5. Virtual LANs <

09041d254826f2fa0bc2d956bb07fa5a.doc 4 of 5  Which servers belong to which VLAN  VLAN trunking  Inter-VLAN routing

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.>>

5.6. Wireless Networks <>

5.7. QoS Design <>

5.8. Network Management <>

6. Physical Design 6.1. Network Topology <>

6.2. LAN technologies <>

6.3. WAN technologies <>

6.4. Physical Network Diagram <>

6.5. Minimal server and PC requirements <>

6.6. Wireless technologies <>

7. References <>

09041d254826f2fa0bc2d956bb07fa5a.doc 5 of 5

Recommended publications