•The overview approach.
•The detailed approach.
Which of these you choose will depend on your goals for the user's learning. The simulation model interface combined with the overview approach gives the generalities of the model, the overall lessons. Editing boxes, sliders and switches alter a few key model assumptions and policy levers, and graphs and displays show a few select variables. The user might also choose in-depth analysis of the model behavior (looking at any or all model variables). The overview approach encourages users to make a single important change (or experiment), or just a few changes, and observe these changes on the behavior of key variables. The old scientific maxim — change one thing at once — gives excellent insight into model behavior.
The detailed approach is often more useful when the user wants the simulator to closely represent reality. The detailed approach can be useful while playing a game through the gaming interface. This high level of detail, mimicking reality, comes at a price. The user is essentially in the real world, though with an accelerated time span, and the outcomes generated in the model might not be traceable to actual individual policies (or even groups of policies) if many things were changed at once.
In a simulation model, a highly detailed simulator can overwhelm the user and stifle the learning process, especially if the user is changing a lot of things together during each experiment (simulation run).
Start simple, try it out on people, then move to detailed
Building a Venapp often progresses iteratively. Starting simple allows you to get something up and running quickly, and allows users an introduction. Build the Venapp following the overview approach first, then move towards the detailed approach as users (or the builder) get comfortable with the Venapp.
