IAB201 Lecture Notes - Lecture 13: Modeling Language, Pragmatics, System Dynamics
Document Summary
A good model should be: appropriate, complete, conceptually clean, consistent, constructible, correct, executable, expressive, modifiable, precise, testable, traceable, understandable, unambiguous, minimal, etc. Listing and further analysing properties of a model is a good start, but this approach comes with certain weaknesses, for instance: List is unstructured and the properties tend to "overlap: many definitions are vague or complicated, model properties, language properties, and method properties get intermixed. A model quality framework that offers a more in-depth treatment of quality properties should: Separate model quality properties from language quality and method quality, Separate quality goals and the means to reach them: propose precise interpretations of the quality properties, and, address properties that relate to the model building phase and are independent of later deliverables. Model consists of all statements actually made about the (modelling) problem: model components are the explicit model and implicit model, explicit model consists of all statements explicitly made.
