Proposed Model workflow
These are mockups of how I would like Model to function. The idea is to capture as much of the modelling process, and its iterations, in the activity. This is an easy way to generate documentation for models, and encourages best practices. What is not shown is a method for navigating through the process, but this could probably be accomplished on a toolbar at the top of the screen
01
back | next
The startup page of model, visible when started from the home view, contains a simple choice to document the whole process or jump straight to modeling.
02
back | next
We want to enable kids to express themselves and think about the problem at hand in different ways. When describing the problem to be modelled, we would like them to be able to not only write a description, but also draw or take pictures.
03
back | next
This is probably one of the less interesting panels, but it is important to identify the relevant stocks and flows of the system.
04
back | next
There should be an easy way for kids to specify, and understand, the time horizon of the simulation. Using several natural language constructs, such as 'now' instead of '0', could help with this. It would also be nice to allow access to things like the save-step and time-step, but these are probably not helpful for the beginner so they will be hidden by default.
05
back | next
Behaviour over time graphs are very powerful tools for developing systems thinking. I want to allow kids to select a stock and put key points on the graph, with lines being added automatically. After we have a running simulation, these behaviour graphs can be overlaid with the actual structure of the model to see how they match up, naturally bringing kids back to evaluate their original thinking.
06
back | next
Finally, we want to be able to draw causal loop diagrams of some sort. These will probably not be used for simulation, but do allow you to get a broad overview of the processes at work in a system.
07
back | next
Finally, this is how the modelling canvas will look for stock and flow drawings. It uses common symbols so that proficiencies can be transferred across programs. The most notable thing is that when you are modelling collaboratively, structure added by other people will show up in the color of their XO, at least for a short period of time.