Enhancing the System Dynamics Modeling Process With a Domain Modeling Method

Abstract

Defining complex system dynamics (SD) models in complex organizational settings is hard. This is so because the numbers of variables to consider are many and the question of causation is complicated to untangle. Second, SD models are ambiguous and hard to conceptualize. In this paper, we explore the use of a domain modeling method object-role modeling (ORM) in the process of developing SD models. We do so, because domain modeling methods help to identify relationships among entities within the scope of the problem domain and provide a structural view of the domain. The addition of a domain modeling method to the process of developing SD models is to improve SD model conceptualization, enable transformation and reuse of information plus underpin SD with a domain modeling method that allows creation of database. To realize this, we come up with a procedure in our overall research which we refer to as grounded system dynamics (GSD) a combination of ORM and SD. To reason about the combination of SD with a domain modeling method (ORM), we identify and evaluate relationships between their constructs. Basing on the identified relations, ORM to stock and flow diagram (SFD) steps are defined and applied to a real-life case study national medical stores (NMS) situated in Uganda. On completion, we draw conclusions.

System dynamics applied in enterprise engineering – a systematic literature review

“…A very small percentage of the papers (3%) also investigated the adaptation of existing SD tools. For example, Tulinayo et al (2013) applied object-role modelling to SD concepts to translate object-role models to SFDs.…”

Modelling workforce employability pipelines for organisational resilience

“…to enrich systems dynamics with end user problem representations and research methodologies 10,21,28 ; to combine dynamic (behavioural, event thinking; process) and static (structural thinking, content) constructs [28][29][30][31] ; to address qualitative and quantitative factors 10,32 ; to visualise emergent properties not available with static display 29,33 ; to evaluate the model design process and validate the resulting models 21,34 ; and to provide a structured approach to the model development process. 10,32,34 The review reinforced the Jnitova et al 19 finding that the model development projects often result in one-off M&S applications, that are not reused, not shared and not supported by reports of their actual workplace implementation.…”

“…to combine dynamic (behavioural, event thinking; process) and static (structural thinking, content) constructs 28 –31 ;…”

“…Examples of rationales for the combined use of conceptual modelling and systems dynamics are as follows: to enrich systems dynamics with end user problem representations and research methodologies 10,21,28 ; to combine dynamic (behavioural, event thinking; process) and static (structural thinking, content) constructs 28 –31 ; to address qualitative and quantitative factors 10,32 ; to visualise emergent properties not available with static display 29,33 ; to evaluate the model design process and validate the resulting models 21,34 ; and to provide a structured approach to the model development process. 10,32,34 …”