1. UNIT – V NETWORK DESIGN

2. Network layout develops various views of planned network design including detailed
(i)logical diagrams,
(ii)physical blue prints and
(iii) function - specific component plans

3. LOGICAL DIAGRAMS
They show the connectivity and relationships among network devices.
Relationships show how devices may interact with one another , how they work together and and what you might expect from them
These diagrams do not accurately represent the location of different devices, they give only an approximate representations
These diagrams are useful for planning purposes

4. LOGICAL DIAGRAMS

5. NETWORK BLUE PRINTS
These diagrams describe detailed physical aspects of networking design, which specify network devices, cables , servers , plants and physical security. And secure locations, how they are to be interconnected.
These blue prints can consist of single diagram or sets of diagrams, depending on network size.
These consist of mapping strategic locations of network onto network templates

7. MAPPING STRATEGIC LOCATIONS
1.As part of the network blue prints, physical information , like the building plan, location of different rooms .. Etc would have been collected.
2. Using these we map strategic locations for the network
3. Some examples of possible strategic locations on network functions are
Boundary points between secuirty cell ones
Location of major components for moitoring and management
Aggregation of routes, networks and or traffic flows

9. Applying topology Selections
1.The choice of strategic locations should map to selected topologys
2. Topology choices describe the high level structure of network and consists of major locations that support this structure

12. This adds diversity to the network.

13. Addition of technology choices to the network according to architectural process

14. DESIGN TRACEBILITY
1.Each design decision regarding network should be tracebale to one or more architectural decisions and thus to requirements and problem statements
2. Each design decision maps to one or more architectural decisions which inturn maps to requirements , inturn maps to problem statements
3. Traceability indicates how well your network design addresses, reqiorements and problem statements

18. DESIGN METRICS
Each validated requirement should be mapped to one or more metrics, and these metrics are used to determine the success of in meeting each requirement
The metrics associated with design should be coupled to metrics used in requirements
Examples of design metrics include, the ability to achieve a desired diversity level in the network, via routing , topology, equipment redundancy…etc, often associated with metrics for performance requirements such as n/w availability and reliability
Similarly the ability to bound round trip time and or end to end delay is again associated with performance of service delivery requirements