Slides3 - Evaluating Technical Goals Project Costing David...

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

View Full Document Right Arrow Icon
1 Evaluating Technical Goals Project Costing David Tipper Associate Associate Professor Professor Graduate Telecommunications and Networking Program University of Pittsburgh Slides 3 http://www.sis.pitt.edu/~dtipper/2110.html Top Down Network Design • Top Down Network Design – Conceptual Model • Objectives – Business Goals, Technical Goals • Requirements – Business (e.g.,support XYZ application), Technical (availability, delay, bandwidth, security, etc.,) • Constraints – Business (organizational, budget, etc.,) and Technical (vendor, technology, sites to connect, etc.) – Logical Model Technology network graph node location link size etc (where TELCOM 2110 2 • Technology, network graph, node location, link size, etc. (where algorithms are used to minimize cost) – Physical Model • Specific hardware/software implementations • (e.g., wiring diagram, repeater locations, etc.)
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 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 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 TELCOM 2110 3 • Traffic Estimation may be needed – Security – Manageability/Interoperability – Affordability $$ • Need to determine reasonable goal for each category and the importance of each. Technical Requirements • For goal and requirement setting often useful to construct a chart of requirements for each application/ use or network component. • Traffic estimation is need to determine many network performance and capacity requirements and capacity – If incremental network design – determine what the current/existing networks and services are – Benchmark network/application traffic – If greenfield network design - identify applications and services to be provided from surveys and meetings TELCOM 2110 4 – Need to estimate application/traffic characteristics Application or Network Type of Application New App? Freq of use Criticality Data Rate/Goal Delay Goal/Variation Goal Acceptable MTBF/MTTR Sales Tracking Distributed client/server No/hourly Very Bursty/ Max .5Mbps – mean ~100Kbps < 1 sec/NA 6 months/ 2hours
Background image of page 2
3 Application Modeling • Need to quantify application behavior/network traffic • Can roughly classify applications into categories – Terminal/Host – Distributed Client Server – Peer-to-Peer Model – Server/server – Distributed Computing • Classifications used to define – application flows directions and characteristics Unidirectional or bidirectiona TELCOM 2110 5 • Unidirectional or bidirectional • Symmetric or asymmetric • low, medium, or high bit rate – flow boundaries • e.g., LAN-WAN traffic, intra- campus flow etc.
Background image of page 3

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

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 32

Slides3 - Evaluating Technical Goals Project Costing David...

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

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