Models Versus Model Descriptions

Abstract

In the development of computer-based systems, modelling is often advocated in addition to programming, in that it helps in reflecting the application domain and that it makes the design and experiment activities of development more efficient. However, there is disagreement about what models are and how they can be used in software systems development. In this paper, we present the Scandinavian approach to modelling, which makes a clear distinction between models and model descriptions. This paper explains the connections between models, descriptions, systems, and executions. Combining the Scandinavian approach with the Kiel notion of model, we establish that both descriptions and executions are closely connected instruments with different roles. The paper argues that (program) executions are the models of dynamic systems, not their descriptions in terms of diagrams and text. So in a general sense programming is about writing descriptions for systems. In particular the paper clarifies when programming is also modelling.

Validation: Conceptual versus Activity Diagram Approaches

“…In Fig. 3,  The user creates (circle 1) a drink selection that flows to the machine (2), where it is sent to a module that finds the (drink, price) record (3). The drink data are found by extracting records (drink, price) (4) one by one and comparing the input drink with the drink data in the matching record.…”

“…A conceptual model is a mathematical/logical/verbal representation (mimic) of a domain (real or proposed), situation, policy, or phenomenon developed for a particular study [1][2] [3]. A conceptual (in contrast to an intentional mental representation such as sensation [4]) model describes "how we conceive of that domain" [5].…”