Synchronous uses event-driven approach, asynchronous uses fixed steps

Synchronous is only used for M/M/1 queues.

Asynchronous cannot handle multiple events.

Synchronous moves the clock in fixed increments, asynchronous jumps to event times.

The simulation clock used to schedule events.

A list of all past events in the simulation.

A variable used only for computing performance statistics.

A set of variables that fully describe the system at a specific moment in simulated time.

Initialize the state descriptor.

Store past events.

Schedule only the next departure event.

Keep track of the types and times of all future events.

The clock moves in fixed time steps regardless of events.

The clock jumps directly to the next event, updating the system only when events occur.

It wastes computer time because many steps have no events.

It is rarely used in discrete-event simulation.

A method for solving systems of differential equations using numerical approximation.

A simulation method where the system state changes only at specific event times, rather than continuously.

A simulation method that tracks every moment in continuous time without skipping any intervals.

A bus leaves a station.

The temperature in a room increases continuously over time.

A hospital patient finishes treatment.

A customer arrives at a store.

A single integer representing the number of customers in the system.

The list of scheduled events in the system.

The total service time of all customers.

A vector of components with attributes.

Customer arrival

Customer daydreaming

Temperature rising

Background music playing

Only event times.

Components and their attributes describing system status.

Single variable only.

Only statistical counters.

The internal clock jumps to the event time, and the state descriptor is updated.

The simulation clock is paused until the next step.

The system state remains unchanged.

The system randomly selects the next event to occur.