Models are created and used in many different contexts, including business process management, enterprise engineering, enterprise architecture management, requirements engineering, information systems engineering, software engineering, ontology engineering, etc, across science and industry (including government, NGO's, etc). These different contexts result in a rich variety of more specific types of domain models, such as enterprise (architecture) models, business process models, information models, class diagrams, value models, reference models, ontologies, knowledge graphs, semantic web specifications, etc. Depending on the context, domain models can be created with the aim of being an (as truthful as possible) representation of the conceptual structure of the domain that is modelled; leading to conceptual models. In addition, to accommodate for specific uses and contexts, domain models may also incorporate “conceptual compromises” which, for instance, result in domain models that lend themselves better for animation, simulated, execution, gamification, or automated (logic-based) reasoning. The use of domain models may, sometimes, even go unnoticed since these models do not always take the form of traditional “boxes and lines” diagrams or some other dedicated notation.
The creation, management, and use, of domain models in scientific and industrial practice is done in the context of some expected Return on Modelling Effort (RoME). In other words, it is expected that the model will provide a certain value that will offset the costs involved in the creation and maintenance of the model.
To ensure relevance of research into (the many different forms of) domain modelling, it is important to gather insights from the use of domain models in practice. To, indeed, better understand the practical needs for, and use of, domain models, it would be beneficial to have a library of cases in which domain models have played a crucial role. This desire is also shared by existing academic events including (in order of their planning in 2022):
the GI EMISA (Enterprise Modelling and Information Systems Architectures) workshop,
the IFIP 8.1 EMMSAD (Exploring Modelling Methods for Systems Analysis and Design) working conference,
the IEEE CBI (Conference on Business Informatics),
the ER conference on Conceptual Modelling,
the EEWC (Enterprise Engineering) working conference, and
the IFIP 8.1 PoEM (Practice of Enterprise Modelling) working conference.
It is the desire of these events to, at least in 2022, include explicit reports on the creation and use of domain models in practice (in science or industry) in a dedicated “Models-at-Work” track. This shared desire has now resulted in a coordinated effort to gather (and share among the events) case reports regarding the creation and use of models in scientific and industrial practice.
The longer term ambition is to create an annual “Models-at-Work” post-proceedings involving the case reports within that year. In line with this, the plan is to have an ongoing call, across the associated events, for such case reports. Each case report will be reviewed in a process similar to the submission of papers to a journal. In other words, submissions can be re-submitted based on improvements required by the reviewers. Once accepted, the case reports will be available to be presented (in virtual or physical mode) at one of the associated events. The allocation of the accepted case reports to the associated events will be done jointly by the authors and the organisers of the involved events.
The longer-term ambition is to create an annual “Models-at-Work” special issue in the EMISA-Journal, involving the case reports within that year. The resulting library of case reports could be used in (at least) three directions:
Science: challenges from the real world are made explicitly visible to researchers.
Practice: results from research are illustrated (by way of cases) to practitioners.
Teaching: case reports can be used for educational purposes.
To qualify for inclusion in the “Models-at-Work” EMISA-Journal special issue for 2022, case reports, next to undergoing a regular reviewing process, are required to have been presented at one of the associated events (EMISA workshop, EMMSAD, CBI, ER, EEWC, or PoEM). In line with this, the following process will be followed:
Authors submit a first version of their case report (version 1).
These (version 1) case reports will be subject to a first review. Based on this review, case reports will be selected for presentation at one of the upcoming events. The allocation of the accepted case reports to the associated events will be done jointly by the authors and the organisers of these events. During the event, version 1 will be available to the audience as well.
After the event, the authors are expected to provide an update of their case reports (version 2), where they will need to take the feedback of the first review into account, as well as the feedback from the discussions during the event. This version will then enter into a second review round. This may lead to further (required) improvements.
By the end of January 2023, the finally accepted case reports will be included in the special issue.