notes06 - Steps in Simulation Study TELCOM 2120 Network...

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

View Full Document Right Arrow Icon
1 Steps in Simulation Study TELCOM 2120 Network Performance Joseph Kabara Telecommunications Program University of Pittsburgh Spring 2008, notes6 TELCOM 2120: Network Performance 2 Designing Simulation Studies Types of simulation software – general purpose – event scheduled simulation language – process oriented simulation language – application oriented simulator. The basic steps in a simulation study the same regardless what type of software used Begin with basic problem formulation – independent of software! Spring 2008, notes6 TELCOM 2120: Network Performance 3 A Simulation Study Yes End Start Results statistically useful? No No Results sufficiently detailed? Choosing input and running simulations System results accurate? Defining input and output Specifying the system model No Choosing aspects to be modeled Understanding your goals for the simulation Understanding the system
Image of page 1

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

View Full Document Right Arrow Icon
2 Spring 2008, notes6 TELCOM 2120: Network Performance 4 Essential Simulation Steps Problem Formulation Data Acquisition/Model Specification Model Building Model Translation • Verification • Validation Design of Experiments Output Analysis • Documentation Spring 2008, notes6 TELCOM 2120: Network Performance 5 Problem Formulation Define clear problem statements, objectives, scopes Bad: to study the performance of system X. Better: to study the performance metric M of system X under factors A, B, C, D. Bad: to study if system X is better than system Y. Better: Compare systems X and Y with respect to performance metric M1, M2. Measurable and specific goals. Must consider cost, time frame, required resources. Spring 2008, notes6 TELCOM 2120: Network Performance 6 Data Acquisition/Model Specification Collect input data Distributions of interarrival time Input traffic model Packet size distribution Specify level of details Too much detail more development time, more bugs, more execution time. Too simplified less accurate. Must capture essential features. Ex: Queueing node with background traffic. Generate 100 background traffic flows. Or Generate a single aggregate flow to represent 100 flows.
Image of page 2