The proposed project objective is to rewrite an existing user interface, written in
VB.NET.
This UI works quite well and does a lot, but is insufficiently supportive and user-friendly.
Its mission is to assist users to employ comprehensive and detailed ‘virtual systems’
(heuristic causal simulation models) to manage and plan for the modeled systems.
Each model will be used to

predict system behaviour, paths and outcomes;
 devise and undertake controlled ‘what if’ experimentation;

generate and process simulation output; and

analyse reasons for actual and simulated outcomes.
Models associated with the UI are based on system dynamics. SD is a branch of management science whereby complex managed systems are modeled from information about their stocks and flows, actual v desired entities, randomness, nonlinearities, and delays etc. Considerable detail and disaggregation are built into these models.
An internationally-distributed modeling software package, known as Vensim, is employed to develop and run models. Vensim models are accessed through the existing UI. So are the many external ASCII data files (integer and float) used by each model.
Users need to be shielded from model and both input and output complexity to the greatest feasible extent. They should not have to grapple with the actual model directly.
It should be amended and run from the UI, but in a more-supportive manner than at present. Drop-down menus and other best-practice measures therefore need to be introduced to a greater extent. Various keystroke sequences need to be automated.
The future UI must be web-enabled.
An additional requirement is to process and access selective simulation output from the
UI, in graphical and tabular forms. Model use significantly comprises comparing output from alternative simulation runs in other media such as Excel. Vensim output can be exported for this purpose.
Customised graphs and tables can also be designed and generated within Vensim.

2
Each decision-support model employs the same UI code and layout. The manner of using the UI is broadly the same between the various models. Content of course differs between the latter.
Advice has been received that VB.NET is not the best technical platform for the task.
Wxpython has been suggested as a more-flexible and
–suitable alternative. The writer is not qualified to know which is the best platform. The overall requirement is that selection should be based on technical criteria, as to which platform will best deliver a
UI that is fully user-friendly in terms of contemporary international best practice.
Detailed redevelopment requirements would be agreed in discussion between the writer and persons potentially interested in undertaking the project. For initial consideration a short Powerpoint illustration of the existing UI for one of the models is provided.
Screens in that file are as follows:
 The UI’s entry screen, showing lists of model entities and experimentation topics, both in functional order.

A parameter associated with an experimentation topic. The data file editor and the data file for the parameter are shown.

The editor for maximum array dimension values.

The tree editor for entities.
 The ‘Model’ drop-down menu.
 The ‘View’ drop-down menu.
 The ‘Simulation’ drop-down menu.

The runtime screen of the Vensim modeling software, accessed through the UI.
Brief notes are provided for each of the above screens.
I expect that the proposed project can be completed within the 1500-2000 person hours stipulated for the ANU scheme.
This is a real project which is expected to offer challenges and interesting features to those undertaking it.
The contact with the project team would be Dr John Weldon (contact particulars below).
Email: corp_dyn@iimetro.com.au
Tel: 02 6286 6728
March 2007