Separation of Modeling Principles and Design Principles in Enterprise Engineering
An agile enterprise requires evolvable information systems and organizational structures. Some design theories, e.g. Normalized Systems theory, which were originally developed for designing information systems, have been generalized and extended for the d
- PDF / 529,870 Bytes
- 12 Pages / 439.37 x 666.142 pts Page_size
- 109 Downloads / 265 Views
Tokyo Institute of Technology, 2-12-1 Ookayama, Meguro-ku, Tokyo 152-8550, Japan [email protected] 2 University of Antwerp, Prinsstraat 13, 2000 Antwerp, Belgium {peter.debruyn,philip.huysmans,jan.verelst,herwig.mannaert}@uantwerp.be
Abstract. An agile enterprise requires evolvable information systems and organizational structures. Some design theories, e.g. Normalized Systems theory, which were originally developed for designing information systems, have been generalized and extended for the design of organizations. In addition to information systems, Normalized Systems theory has recently expanded its applicability into the organizational level, including business process. This resulted in a set of 25 design guidelines for Normalized Systems Business Processes. On the other hand, Enterprise Ontology provides advantages in understanding the essence of organizations for massive abstraction and complexity reduction. Since these two streams of research apparently have similar goals, i.e. designing enterprises, using different approaches, some early studies tried to compare or combine them. However, most of them achieved limited success. This research investigates the literature, looking for a new way to connect them. It concludes that it may be possible to sequentially utilize those two artifacts in two different phases of enterprise engineering. Keywords: Enterprise engineering · Design principle · Modeling principle · Enterprise ontology · Normalized systems theory
1
Introduction
Enterprise engineering is an emerging sub-discipline of systems engineering that studies enterprises from an engineering perspective. Loosely summarized, enterprise engineering has attempted to view enterprises from the perspective of engineering and then (re)design and (re)implement them. Many researchers and practitioners have been working on this new challenge and have produced a variety of artifacts, such as ArchiMate [1], Enterprise Ontology (EO) [2], 4EM [3], MEMO [4], Normalized Systems theory (NS) [5], S-BPM [6], and so on. On the other c IFIP International Federation for Information Processing 2016 Published by Springer International Publishing Switzerland 2016. All Rights Reserved J. Horkoff et al. (Eds.): PoEM 2016, LNBIP 267, pp. 362–373, 2016. DOI: 10.1007/978-3-319-48393-1 28
Separation of Modeling Principles and Design Principles
363
hand, some of those artifacts seem to exhibit some overlap in purpose. However, since they have been developed to achieve their own specific goals, they have their own aptitudes by nature. Instead of pursuing the ultimate and apparently arduous goal of unifying them into a single theory, it seems both feasible and valuable to explore a way to combine some of those artifacts in a beneficial manner. Therefore, this paper tries to find a possible way to combine two artifacts that have recently raised interest, namely EO and NS, rather than unifying them. Indeed, there are several existing studies which tried to compare and potentially find a clue to the unification of the two artifacts in
Data Loading...
