Slides2 - Technical Goals and Requirements David Tipper...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Technical Goals and Requirements David Tipper Associate Professor Graduate Telecommunications and Networking Program University of Pittsburgh Slides 2 http://www.sis.pitt.edu/~dtipper/2110.html Last Week • Network Design is not a precise science. – Many different types of problems • Size: LAN vs. MAN vs WAN Technology: wired vs wireless • Technology: wired vs. wireless • Lifecycle Stage: greenfield, incremental, etc. – There can be many good answers - no best solution – Design involves trade-offs among cost vs. performance • Top Down Design approach useful as a framework – Conceptual Mode TELCOM 2110 2 Conceptual Model – Logical Model – Physical Model – Implementation, Testing, Tuning, and Documentation
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Analyze requirements Top-Down Network Design Steps Develop logical design Develop Monitor and optimize network performance Implemen physical design Test, optimize, and document design t and test network Source: P. Oppenheimer Conceptual Model Network Design • Conceptual Model Design • At end of conceptual model design should have gathered/identified gathered/identified • Objectives – Business Goals (e.g., make sales force more responsive to customers on sales calls) – Technical Goals (e.g., provide wireless access to corporate data to sales force) • Requirements TELCOM 2110 4 – Business (e.g.,support XYZ application) – Technical (availability, delay, bandwidth, etc.,) • Constraints – Business (organizational, budget, etc.,) – Technical (vendor, technology, sites to connect, security,etc.)
Background image of page 2
3 Technical Requirements & Constraints • From surveys/questionnaires, meetings etc. application data determine technical requirements and constraints • Technical goal is to build a network that meets user’s requirements + some they may not know they need. • Technical Goals – Scalability – Availability/reliability – Network Performance • Utilization, Throughput, Delay, Delay Jitter, packet loss rate, call/connection blocking rate • Traffic Estimation needed Security TELCOM 2110 5 – Security – Manageability/Interoperability – Affordability $$ • Need to determine reasonable goal for each category and the relative importance of each. Scalability • Scalability – how much growth a network design can support? • can the design adapt to changing network load and QoS requirements? – Need to examine the network needs out a few years • Key points to understand – How many more sites will be added? – How extensive will networks be at each site? TELCOM 2110 6 – How many more users will be added? – How many more servers, etc will be added? – How many and what applications will be added? – Technology migration path?
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Scalability • Scalability – For logical network design – how much additional traffic can be added – without substantial additional traffic can be added without substantial additional investment – For physical design - thought of as expandability and upgrade capability – For example, • Given specific Router Can interface bit rate be upgraded TELCOM 2110
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 43

Slides2 - Technical Goals and Requirements David Tipper...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online