Retaining and Maintaining Soft System Models

Conclusions This paper has made a case for retaining and maintaining SSM models. This should not be interpreted as a mandatory requirement for every use of SSM but there certainly seem to be advantages to the client in all circumstances. Where the models are explicit, perhaps developed collaboratively with the client, the case for retention is particularly strong. To be able to retain models effectively some recommendations should be made for an SSM presentation model standard. This would be used in published examples of SSM models and would encourage tool support to help in the management of model development. It would also be of educational benefit, as novices prefer clear guidelines when learning a new notation or technique. Retaining and maintaining SSM models reduces scope for creativity and the identification of beneficial change but the approach is already so rich that some loss is tolerable. Overall, the impression is that if SSM models are worth building they are worth retaining. There are resulting constraints to be accepted but these have little significant effect and may well help promote SSM in other problem solving areas, such as engineering.