A Review of Enterprise Modelling Studies
---
paper_title: Multi-perspective Enterprise Modeling (MEMO) - Conceptual Framework and Modeling Languages

paper_content:

For many companies, the strategic as well as the organizational fit of their information systems is a pivotal factor for staying competitive. At the same time, there is an increasing demand for integrating business processes and informations systems with those of customers and suppliers. The resulting need for organizational changes and the introduction of corresponding information systems is a challenging task. The complexity of the task requires a separation of concerns. At the same time it causes language barriers between various stakeholders, especially between business people and information technology professionals. Enterprise models provide various abstractions that help with the design of corporate information systems which are in line with a company's organization and its long term strategy. They also promise to provide a common conceptual foundation to foster the communication between people with different professional backgrounds. In this paper we introduce a model for enterprise modelling that is based on an extendable set of special purpose modeling languages, e.g. for describing corporate strategies, business processes, resources or information. The visual languages provide intuitive abstractions for various observers. The languages are defined in metamodels which in turn are specified through a common meta-metamodel. Similar to a specialized technical language, they provide concepts that help with structuring and analyzing a domain according to specific objectives. Since the languages are specified in a semi formal way, the models allow for the generation of software prototypes. The languages share common concepts which allow for a tight integration of the various parts of an enterprise model. In addition to offering specialized modeling languages, the modeling method also includes examples, case studies and reference models - to promote the re-use of concepts and artefacts. The use of the method is illustrated by an example, where two different partial models are being integrated.
---
paper_title: Systematic mapping studies in software engineering

paper_content:

BACKGROUND: A software engineering systematic map is a defined method to build a classification scheme and structure a software engineering field of interest. The analysis of results focuses on frequencies of publications for categories within the scheme. Thereby, the coverage of the research field can be determined. Different facets of the scheme can also be combined to answer more specific research questions. ::: ::: OBJECTIVE: We describe how to conduct a systematic mapping study in software engineering and provide guidelines. We also compare systematic maps and systematic reviews to clarify how to chose between them. This comparison leads to a set of guidelines for systematic maps. ::: ::: METHOD: We have defined a systematic mapping process and applied it to complete a systematic mapping study. Furthermore, we compare systematic maps with systematic reviews by systematically analyzing existing systematic reviews. ::: ::: RESULTS: We describe a process for software engineering systematic mapping studies and compare it to systematic reviews. Based on this, guidelines for conducting systematic maps are defined. ::: ::: CONCLUSIONS: Systematic maps and reviews are different in terms of goals, breadth, validity issues and implications. Thus, they should be used complementarily and require different methods (e.g., for analysis).
---
paper_title: TOWARDS THE ENTERPRISE ENGINEERING APPROACH FOR INFORMATION SYSTEM MODELLING ACROSS ORGANISATIONAL AND TECHNICAL BOUNDARIES

paper_content:

Enterprise Engineering proved to be useful when a generally accepted intentional description of information system is not available. A blueprint of enterprise infrastructure provides a basis for system analysis of the organizational and technical processes. It is sometimes referred as enterprise architecture. The major effort of this paper is the demonstration of how to bridge a gap among various levels (syntactic, semantic and pragmatic) of enterprise engineering. Most information system engineering methodologies are heavily centred on system development issues at the implementation level. Thus, such methodologies are restrictive in a way that a supporting technical system specification can not be motivated or justified in the context of organizational process models. Enterprise models provide a basis for gradual understanding of why and how various technical system components come about. Some undesirable qualities of enterprise engineering are sketched in this paper.
---

Title: A Review of Enterprise Modelling Studies

Section 1: INTRODUCTION
Description 1: Write an introduction explaining the purpose, importance, and application of enterprise modelling.

Section 2: REVIEW PROCESS
Description 2: Describe the steps followed in conducting the review, including scope definition, inclusion criteria, identification, and classification of papers.

Section 3: Scope Definition
Description 3: Explain the issues addressed in the study and provide a detailed outline of the primary research questions.

Section 4: Inclusion Criteria
Description 4: Define the criteria used for selecting journal papers included in the review and mention any exclusions.

Section 5: Identification of Papers
Description 5: Describe the process and databases used to identify relevant papers, including the refinement and selection process.

Section 6: Classification of Papers
Description 6: Explain how papers were classified into different typologies and the purpose of this classification.

Section 7: ANALYSIS
Description 7: Present the results of the classification, including an analysis of distribution among journals, publication sources, efforts over the years, research topics, categories, modelling languages, applications, and quantitative approaches.

Section 8: THREATS TO VALIDITY
Description 8: Describe the main threats to the validity of the review and how they were managed or acknowledged.

Section 9: CONCLUSIONS
Description 9: Summarize the findings of the review and their implications for future enterprise modelling research, including suggestions for future work.