Guideline
Reviewing the model
In a model-review one can ask two questions:
1) do I agree with the goal-network.
2) to what degree do the methods of the model realize the goals.
Changing the model
If the review is inspiring a better design, or one just wants to points some weak points, one can change the model or just add something to the change-log. But remember that when people design something it is often a thing they feel strongly about. There are often emotions involved. Those must be respected. Therefore it is important to find out a way to improve a model without destroying (to much of) the original idea.
Roughly, for small, incremental changes it is recommended to change the model. For larger changes it is recommended to copy the model and create a new version of it:
Small changes:
Add a change-request on the bottom of the model, wait for some time. Either the original author adopts the request and changes it or, when nothing happens, edit the model, and edit the change-proposal so that it becomes a change-log.
The change-section should contain the following info:
- Author-date-code (ADC),
- changes made,
- and new version number.
A neater way may be to follow a request-procedure. Make an ADC with -depending on your role- either a:
- change-proposal.
- in-redesign-acknowlegdement (by author)
- discussion-request (on forum); where and with whom?
- change-implementation plus new version-number.
- change-rejection (give reason).
Large changes:
To avoid sensitive issues, you can also copy the model, change it to you wishes, and give it a new name, new ADC-code and new version.
