More About Creating / Editing Models

Guideline

The model-format; how to create a model - Sample-model
The following items should addressed when describing a new model:

• Abstraction / specification; one should name the abstract model from which it is a specification, and refer to that page (see Setup of Co-designs)
• Assumptions or theories that are supposed to be true to make the model work.
• Goals or desired effects of the model, and preferably also the higher goals which these goals fulfill (the goal-network). See more on goal-networks
• Potential undesirable side-effects, and ways to avoid them.
• Elements of the model and the way the elements work together to create or avoid the above effects.
• Modelar relations (if any)
  • ‘Genetic’ relations; models are often inspired on other models, no problem there. Just describe the ‘parent’-model(s) that it uses and intends to improve on.
    • Single-parent; it is simply a new version; give the model a sequential version-number (ex. 1.4). See also: more on naming and ID-codes.
    • Multi-parent; name the parents and use a new author-date-code.
  • Network-relations or interfaces; the connections the model has with other models. For example a new kind of train (model 1) might require new rails (model 2) to ride on.

Change-proposals and -log; these are only relevant if changes to the model were requested)

So here you can take another look at an sample-model.
The reviewing and changing of a model may take some care and diplomacy.