Fiche du document
8 novembre 2016
- handle: 10670/1.my70ks
- hal: hal-01653505
- doi: 10.1007/978-3-319-48393-1_28
Ce document est lié à :
info:eu-repo/semantics/altIdentifier/doi/10.1007/978-3-319-48393-1_28
http://creativecommons.org/licenses/by/ , info:eu-repo/semantics/OpenAccess
Mots-clés
Enterprise engineering Design principle Modeling principle Enterprise ontology Normalized systems theorySujets proches
Natural science Sciences Science of science Scientific research Science research Science--Research Being Molding (Clay, plaster, etc.) Clay modeling Modelling Construction Trade Voluntary organizations Networks (Associations, institutions, etc.) Organizations Voluntary associations Institutions, associations, etcCiter ce document
Tetsuya Suga et al., « Separation of Modeling Principles and Design Principles in Enterprise Engineering », HAL-SHS : sciences de l'information, de la communication et des bibliothèques, ID : 10.1007/978-3-319-48393-1_28
Métriques
Partage / Export
Résumé
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.