Scribd
Upload
236 views

Lab 1b Introduction To Modeling and Simulation

This document provides an introduction to modeling and simulation. It discusses the goals of using simulation to model systems too expensive or impractical to study directly. Simulation involves creating and running models of systems over time. The document outlines key concepts in modeling like the types of models, what constitutes a model, simulation, and applications of simulation. It also discusses best practices for simulation projects like defining clear goals, collecting input data early, verifying models match intentions, and validating models represent the actual system.

Uploaded by

Mir Sohail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
236 views

Lab 1b Introduction To Modeling and Simulation

This document provides an introduction to modeling and simulation. It discusses the goals of using simulation to model systems too expensive or impractical to study directly. Simulation involves creating and running models of systems over time. The document outlines key concepts in modeling like the types of models, what constitutes a model, simulation, and applications of simulation. It also discusses best practices for simulation projects like defining clear goals, collecting input data early, verifying models match intentions, and validating models represent the actual system.

Uploaded by

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

Introduction To

Modeling and
Simulation

Introduction

Goals Of This Course


Introduce Modeling
Introduce Simulation
Develop an Appreciation for the Need for
Simulation
Develop Facility in Simulation Model
Building
Learn by Doing--Lots of Case Studies

Introduction

What Is A Model ?
A Representation of an
object, a system, or an idea
in some form other than that
of the entity itself.
(Shannon)
Introduction

Types of Models:
Physical
(Scale models, prototype plants,
)
Mathematical
(Analytical queueing models,
linear programs, simulation)

Introduction

What is Simulation?
A Simulation of a system is the operation of
a model, which is a representation of that
system.
The model is amenable to manipulation
which would be impossible, too expensive,
or too impractical to perform on the system
which it portrays.
The operation of the model can be studied,
and, from this, properties concerning the
behavior of the actual system can be
inferred.
Introduction

Applications:
Designing and analyzing manufacturing
systems
Evaluating H/W and S/W requirements for
a computer system
Evaluating a new military weapons
system or tactics
Determining ordering policies for an
inventory system
Designing communications systems and
message protocols for them
Introduction

Applications:(continued)
Designing and operating transportation
facilities such as freeways, airports,
subways, or ports
Evaluating designs for service
organizations such as hospitals, post
offices, or fast-food restaurants
Analyzing financial or economic systems

Introduction

Steps In Simulation and


Model Building
1. Define an achievable goal
2. Put together a complete mix of skills on
the team
3. Involve the end-user
4. Choose the appropriate simulation tools
5. Model the appropriate level(s) of detail
6. Start early to collect the necessary
input data

Introduction

Steps In Simulation and


Model Building(contd)
7. Provide adequate and on-going
documentation
8. Develop a plan for adequate model
verification
(Did we get the right answers ?)
9. Develop a plan for model validation
(Did we ask the right questions ?)
10. Develop a plan for statistical output
analysis
Introduction

Define An Achievable Goal


To model the is NOT a goal!
To model thein order to
select/determine feasibility/is a
goal.
Goal selection is not cast in concrete
Goals change with increasing insight
Introduction

10

Put together a complete


mix of skills on the team
We Need:
-Knowledge of the system under
investigation
-System analyst skills (model formulation)
-Model building skills (model Programming)
-Data collection skills
-Statistical skills (input data representation)
Introduction

11

Put together a complete


mix of skills on the
We Need:
team
(continued)
-More statistical skills (output data
analysis)
-Even more statistical skills (design of
experiments)
-Management skills (to get everyone
pulling in the same direction)

Introduction

12

INVOLVE THE END USER


-Modeling is a selling job!
-Does anyone believe the results?
-Will anyone put the results into action?
-The End-user (your customer) can (and
must) do all of the above BUT, first he
must be convinced!
-He must believe it is HIS Model!
Introduction

13

Choose The Appropriate


Simulation Tools
Assuming Simulation is the appropriate
means, three alternatives exist:
1.
Build Model in a General Purpose
Language
2.
Build Model in a General
Simulation
Language
3.
Use a Special Purpose
Simulation
Package
Introduction

14

MODELLING W/ GENERAL
PURPOSE LANGUAGES
Advantages:

Little or no additional software cost


Universally available (portable)
No additional training (Everybody knows(language
X) ! )

Disadvantages:

Every model starts from scratch


Very little reusable code
Long development cycle for each model
Difficult verification phase

Introduction

15

GEN. PURPOSE LANGUAGES


USED FOR SIMULATION
FORTRAN

Probably more models than any other language.

PASCAL

Not as universal as FORTRAN

MODULA

Many improvements over PASCAL

ADA

Department of Defense attempt at


standardization

C, C++

Object-oriented programming language

Introduction

16

MODELING W/ GENERAL
SIMULATION LANGUAGES
Advantages:

Standardized features often needed in


modeling
Shorter development cycle for each model
Much assistance in model verification
Very readable code

Disadvantages:
Higher software cost (up-front)
Additional training required
Limited portability

Introduction

17

GENERAL PURPOSE
SIMULATION LANGUAGES
GPSS

Block-structured Language
Interpretive Execution
FORTRAN-based (Help blocks)
World-view: Transactions/Facilities

SIMSCRIPT II.5

English-like Problem Description Language


Compiled Programs
Complete language (no other underlying
language)
World-view: Processes/ Resources/ Continuous

Introduction

18

GEN. PURPOSE
SIMULATION LANGUAGES
MODSIM III
(continued)
Modern Object-Oriented Language
Modularity Compiled Programs
Based on Modula2 (but compiles into C)
World-view: Processes

SIMULA
ALGOL-based Problem Description Language
Compiled Programs
World-view: Processes

Introduction

19

GEN. PURPOSE
SIMULATION LANGUAGES
SLAM
(continued)
Block-structured Language
Interpretive Execution
FORTRAN-based (and extended)
World-view: Network / event / continuous

CSIM
process-oriented language
C-based (C++ based)
World-view: Processes

Introduction

20

MODELING W/ SPECIALPURPOSE SIMUL.


Advantages
PACKAGES
Very quick development of complex models
Short learning cycle
No programming--minimal errors in usage

Disadvantages
High cost of software
Limited scope of applicability
Limited flexibility (may not fit your specific
application)

Introduction

21

SPECIAL PURPOSE PACKAGES


USED FOR SIMUL.
NETWORK II.5

Simulator for computer systems

OPNET

Simulator for communication networks,


including wireless networks

COMNET III

Simulator for communications networks

SIMFACTORY

Simulator for manufacturing operations

Introduction

22

THE REAL COST OF


SIMULATION
Many people think of the cost of a
simulation only in terms of the software
package price.
There are actually at least three
components to the cost of simulation:
1.
Purchase price of the software
2.
Programmer / Analyst time
3.
Timeliness of Results

Introduction

23

TERMINOLOGY
System
A group of objects that are joined together in
some regular interaction or interdependence
toward the accomplishment of some
purpose.
Entity
An object of interest in the system.
E.g., customers at a bank

Introduction

24

TERMINOLOGY (continued)
Attribute
a property of an entity
E.g., checking account balance

Activity
Represents a time period of specified length.
Collection of operations that transform the
state of an entity
E.g., making bank deposits

Introduction

25

TERMINOLOGY (continued)
Event:
change in the system state.
E.g., arrival; beginning of a new execution;
departure

State Variables
Define the state of the system
Can restart simulation from state variables
E.g., length of the job queue.

Introduction

26

TERMINOLOGY (continued)
Process
Sequence of events ordered on time

Note:
the three concepts(event, process,and
activity) give rise to three alternative ways of
building discrete simulation models

Introduction

27

A GRAPHIC COMPARISON OF
DISCRETE SIMUL.
METHODOLOGIES

A1

P1

A2

E1

E2 /E3

E4

A1

P2
E1

A2
E2

E3

E4

Simulation Time
Introduction

28

SIMULATION WORLDVIEWS
Pure Continuous Simulation
Pure Discrete Simulation
Event-oriented
Activity-oriented
Process-oriented

Combined Discrete / Continuous


Simulation
Introduction

29

Examples Of Both Type


Models
Continuous Time and Discrete Time
Models:
CPU scheduling model vs. number of
students attending the class.

Introduction

30

Examples (continued)
Continuous State and Discrete State
Models:
Example: Time spent by students in a
weekly class vs. Number of jobs in Q.

Introduction

31

Other Type Models


Deterministic and Probabilistic Models:
Output

Output

Input

Input

Static and Dynamic Models:


CPU scheduling model vs. E = mc2
Introduction

32

MODEL THE APPROPRIATE


LEVEL(S) OF DETAIL
Define the boundaries of the system to
be modeled.
Some characteristics of the
environment (outside the boundaries)
may need to be included in the model.
Not all subsystems will require the same
level of detail.
Control the tendency to model in great
detail those elements of the system
which are well understood, while
skimming over other, less well understood sections.
Introduction

33

START EARLY TO COLLECT THE


NECESSARY INPUT DATA
Data comes in two quantities:
TOO MUCH!!
TOO LITTLE!!
With too much data, we need techniques
for reducing it to a form usable in our
model.
With too little data, we need information
which can be represented by statistical
distributions.
Introduction

34

PROVIDE ADEQUATE AND ONGOING DOCUMENTATION


In general, programmers hate to

document. (They love to program!)


Documentation is always their lowest
priority item. (Usually scheduled for just
after the budget runs out!)
They believe that only wimps read
manuals.
What can we do?

Use self-documenting languages


Insist on built-in user instructions(help screens)
Set (or insist on) standards for coding style

Introduction

35

DEVELOP PLAN FOR ADEQUATE


MODEL VERIFICATION
Did we get the right answers?
(No such thing!!)
Simulation provides something that no
other technique does:
Step by step tracing of the model
execution.
This provides a very natural way of
checking the internal consistency of the
model.
Introduction

36

DEVELOP A PLAN FOR


MODEL VALIDATION
VALIDATION:
Doing the right
thing
Or
Asking the right
questions
How do we know our model represents
the
system under investigation?
Compare to existing system?
Deterministic Case?
Introduction

37

DEVELOP A PLAN FOR STATISTICAL


OUTPUT ANALYSIS
How much is enough?
Long runs versus Replications
Techniques for Analysis

Introduction

38

You might also like