|
|
Deborah A. Sadowski ,Mark R. Grabau9 i0 O4 V5 q0 p7 B; n& Z
There's a common misconception that performing a simulation study involves a sequence of steps (e.g., project definition, model formulation, verification, validation, analysis). To the contrary, all elements of a simulation project should be performed repeatedly throughout the effort, * ^/ X! |# L8 S" q6 p1 M
growing in scope as the model progresses. : p$ Z1 t- z& L- \3 @, |9 i
In the traditional view, projects suffer from too strong a focus on the model (and perhaps the animation), so that after the inevitable delays and problems, there's no time left to run scenarios. Instead, the analyst is faced with a presentation deadline that's firm and little time to experi-
. ^7 z7 b# Q" k' F) Ement, analyze, or think. # F) y( M! b* s0 d) m
Instead, you should schedule the project in complete phases. Intermediate milestones, spaced no more than about two weeks apart in a medium to large project, should include specific goals for the model, animation, data, and analysis. By the time you reach the last 25% of your time on the project, you should have addressed the basic analysis issues of run length, warm-up time, etc. and should already have performed preliminary analysis on the model for a number of different scenarios. |
|