Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
71 views29 pages

Chapter 1 Analyzing Business Goals and Constraints

The document outlines the assessments, course outline, and top-down approach to network design. It discusses analyzing business goals and constraints, technical goals, and characterizing existing networks and traffic before designing logical and physical network models.

Uploaded by

foxd9522
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views29 pages

Chapter 1 Analyzing Business Goals and Constraints

The document outlines the assessments, course outline, and top-down approach to network design. It discusses analyzing business goals and constraints, technical goals, and characterizing existing networks and traffic before designing logical and physical network models.

Uploaded by

foxd9522
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 29

Computer Networks Design and

Implementation
ITE 402

Dr. Mohamed ELHADAD

1
Assessments

Assessment tools
2 assignments (2 x 5%) 10%
Labs (3 x 5%) 15%
Quizzes (2 x 5%) 10%
Project 10%
Midterm Exam 20%
Final Exam 35 %

2
Course outline

Part 1 Chapter 1 Analyzing Business Goals and Constraints

Chapter 2 Analyzing Technical Goals and Constraints


Identifying Your Customer’s Needs
and Goals` Chapter 3 Characterizing the Existing Internetwork

Chapter 4
Characterizing Network Traffic

Part 2 Chapter 5 Designing Models for Addressing and Naming


Chapter 6 Selecting Bridging, Switching, and Routing Protocols
Logical Network Design
Chapter 7 Developing Network Security Strategies
Chapter 8 ` Developing Network Management Strategies
Chapter 9
Part 3 Selecting Technologies and Devices for Campus Networks

Physical Network Design Chapter 10 Selecting Technologies and Devices for Enterprise Networks

Part 4 Chapter 11 Testing, Optimizing, and Documenting Your Network Design

Testing, Optimizing, and Documenting


Your Network Design

3
Top-Down Network Design

Chapter One

Analyzing Business Goals and


Constraints

4
Top-Down Network Design

 Network design should be a complete


process that matches business needs to
available technology to deliver a system
that will maximize an organization’s
success
 In the LAN area it is more than just buying a few
devices
 In the WAN area it is more than just calling the
phone company

5
Start at the Top
 Don’t just start connecting the dots
 Analyze business and technical goals first
 Explore divisional and group structures to find
out who the network serves and where they
reside
 Determine what applications will run on the
network and how those applications behave
on a network
 Focus on the higher Layers of the network
stack
6
Layers of the OSI Model
Layer 7 Application

Layer 6 Presentation

Layer 5 Session

Layer 4 Transport

Layer 3 Network

Layer 2 Data Link


Layer 1 Physical

7
Structured Design
 A focus is placed on understanding data flow, data types, and
processes that access or change the data.
 A focus is placed on understanding the location and needs of user
communities that access or change data and processes.
 Several techniques and models can be used to characterize the
existing system, new user requirements, and a structure for the
future system.
 A logical model is developed before the physical model.
 The logical model represents the basic building blocks, divided by

function, and the structure of the system.


 The physical model represents devices and specific technologies

and implementations.

8
Systems Development Life Cycles

 SDLC: Does it mean Synchronous Data Link


Control or Systems Development Life Cycle?
 The latter for the purposes of this class!
 Typical systems are developed and continue
to exist over a period of time, often called a
systems development life cycle (SDLC)

9
Top-Down Network Design Steps
Analyze
requirements

Monitor and Develop


optimize logical
network design
performance

Implement Develop
and test physical
network design
Test, optimize,
and document
design

10
Network Design Steps

 Phase 1 – Analyze Requirements


 Analyze business goals and constraints
 Analyze technical goals and tradeoffs
 Characterize the existing network
 Characterize network traffic

11
Network Design Steps

 Phase 2 – Logical Network Design


 Design a network topology
 Design models for addressing and naming
 Select switching and routing protocols
 Develop network security strategies
 Develop network management strategies

12
Network Design Steps

 Phase 3 – Physical Network Design


 Select technologies and devices for campus
networks
 Select technologies and devices for enterprise
networks

13
Network Design Steps

 Phase 4 – Testing, Optimizing, and


Documenting the Network Design
 Test the network design
 Optimize the network design
 Document the network design

14
The PDIOO Network Life Cycle
Plan

Design

Retire
Optimize

Implement

Operate

15
Business Goals

 Increase revenue
 Reduce operating costs
 Improve communications
 Shorten product development cycle
 Expand into worldwide markets
 Build partnerships with other companies
 Offer better customer support or new
customer services

16
Recent Business Priorities
 Mobility
 Security
 Resiliency (fault tolerance)
 Business continuity after a disaster
 Network projects must be prioritized based
on fiscal goals
 Networks must offer the low delay required
for real-time applications such as VoIP

17
Business Constraints

 Budget
 Staffing
 Schedule
 Politics and policies

18
Collect Information Before the
First Meeting
 Before meeting with the client, whether
internal or external, collect some basic
business-related information
 Such as
 Products produced/Services supplied
 Financial viability
 Customers, suppliers, competitors

19
Meet With the Customer

 Try to get
 A concise statement of the goals of the
project
 What problem are they trying to solve?

 How will new technology help them be


more successful in their business?
 What must happen for the project to
succeed?

20
Meet With the Customer

 What will happen if the project is a failure?


 Is this a critical business function?
 Is this project visible to upper management?
 Who’s on your side?

21
Meet With the Customer
 Discover any biases
 For example
 Will they only use certain company’s
products?
 Do they avoid certain technologies?
 Talk to the technical and
management staff

22
Meet With the Customer
 Get a copy of the organization chart
 Obtaining an organization chart provides a visual
representation of the company's structure, highlighting
key departments, positions, and reporting relationships It
will suggest users to account for
 It will suggest geographical locations to account for

23
Meet With the Customer
 Get a copy of the security policy
 How does the policy affect the new design?
 How does the new design affect the policy?
 Is the policy so strict that you (the network designer)
won’t be able to do your job?
 Start cataloging network assets that security
should protect
 Hardware, software, applications, and data
 intellectual property, trade secrets, and a company's
reputation

24
The Scope of the Design Project
 Small in scope?
 Allow sales people to access network via a VPN
 Large in scope?
 An entire redesign of an enterprise network
 Use the OSI model to clarify the scope
 New financial reporting application versus new
routing protocol versus new data link (wireless, for
example)
 Does the scope fit the budget, capabilities of
staff and consultants, schedule?
25
Gather More Detailed Information

 Applications
 Now and after the project is completed
 Include both productivity applications and
system management applications(monitoring
tools and antivirus software)
 User communities
 Data stores
 Protocols
 Current logical and physical architecture
 Current performance
26
Network Applications
Name of Type of New Criticality Comments
Application Application Application?

27
Summary

 Systematic approach
 Focus first on business requirements and
constraints, and applications
 Gain an understanding of the customer’s
corporate structure
 Gain an understanding of the customer’s
business style

28
Review Questions
 What are the main phases of network design per
the top-down network design approach?
 What are the main phases of network design per
the PDIOO approach?
 Why is it important to understand your customer’s
business style?
 What are some typical business goals for
organizations today?
 What are the layers OSI Model?
 What is meant by VPN, give brief definition and the
reason of using it?

29

You might also like