|
|
Deborah A. Sadowski ,Mark R. Grabau
" J4 P& L- T# C4 r$ @: a# JThere'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,
6 E1 [) t x* C9 V3 a# X6 vgrowing in scope as the model progresses. * F2 }9 H* D5 H
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-+ h, }2 e5 J8 f0 E9 _# Q2 R
ment, analyze, or think. 5 r1 i* U+ A$ |5 O
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. |
|