Combining DEMO and Normalized Systems for Developing Agile Enterprise Information Systems

Krouwel, Marien R.; Land, Martin Op ’t

doi:10.1007/978-3-642-21058-7_3

Cited by 14 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One of the research topics in the field of DEMO is the integration and combination of other modelling methods and notations [25,19,16,17]. When we follow the recommendations of these publications, the best way to support the combination of modelling methods is to have a tool that supports various modelling methods and notations.…”

Section: Requirement 2 the Tool Must Be Fully Compliant With The Demo...mentioning

confidence: 99%

See 1 more Smart Citation

Towards Enterprise-Grade Tool Support for DEMO

Mulder

Proper

2020

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

The Design and Engineering Methodology for Organisations (DEMO) method is a core method within the discipline of Enterprise Engineering (EE). It enables the creation of so-called essential models of organisations, which are enterprise models focusing on the organisational essence of an organisation, primarily in terms of the actor roles involved, and the business transactions between these actor roles. The DEMO method has a firm theoretical foundation. At the same time, there is an increasing uptake of DEMO in practice. With the increased uptake of DEMO also comes a growing need for enterprisegrade tool support. In this paper, we therefore report on a study concerning the selection, configuration, and extension, of an enterprise-grade tool platform to support the use of DEMO in practice. The selection process resulted in the selection of Sparx Enterprise Architect for further experimentation in terms of configuration towards DEMO. The configuration of this tool framework to support DEMO modelling, also provided feedback on the consistency and completeness of the DEMO Specification Language (DEMOSL), the specification language that accompanies the DEMO method.

show abstract

Section: Requirement 2 the Tool Must Be Fully Compliant With The Demo...mentioning

confidence: 99%

“…When going through DEMO models in published papers, we find incompleteness, structural incorrectness, and syntactic failures in various models [16,11,10]. To solve this problem, the model should be verified against the specification language.…”

Section: Requirement 3 the Tool Must Support Multiple Modelling Metho...mentioning

confidence: 99%

Towards Enterprise-Grade Tool Support for DEMO

Mulder

Proper

2020

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…Put another way, whether combinatorial effects may occur within the ontological model and even how to remove combinatorial effects remain beyond the scope of the study. [12] also studies an alignment and combination of EO and NS by establishing a linkage and collaboration between agile enterprises (realized with EO), and agile automated information systems (developed with NS). This research proposes mappings of concepts in EO onto elements of NS with wider coverage than [11].…”

Section: Related Workmentioning

confidence: 99%

“…[13] is another work with an approach different from the previous two studies [11,12], in which NS elements for software are directly compared and mapped to EO. Instead of the direct approach, this study compares EO concepts and not NS elements for software but the guidelines of NS Business Processes (NSBP), which are derived from NS theorems for the business process domain.…”

Section: Related Workmentioning

confidence: 99%

Separation of Modeling Principles and Design Principles in Enterprise Engineering

Suga

Bruyn

Huysmans

et al. 2016

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Part 3: Short PapersInternational audienceAn 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

show abstract

“…Moreover, other attempts have been made to integrate Normalized Systems and Enterprise Ontology theory more directly (Huysmans et al, 2010;Krouwel and Op't Land, 2011;Op 't Land et al, 2011). It should be noted that in these efforts, an inductive approach based on concrete artifacts is used, which can be contrasted to a more theoretical approach.…”

Section: Is It Possible To Compare Bothmentioning

confidence: 99%

Consistency, Complementalness, or Conflictation of Enterprise Ontology and Normalized Systems Business Process Guidelines

Huysmans¹,

Nuffel²,

Bruyn³

2013

Proceedings of the Third International Symposium on Proceedings of the Third International Symposium on Business Modeling and S

View full text Add to dashboard Cite

Both Enterprise Ontology and Normalized Systems can be considered as design theories, which provide prescriptive guidelines to design systems. Enterprise Ontology explicitly focuses on the design of organizations as being social systems. Originally, Normalized Systems focused on the design of evolvable software systems. However, it has been shown that, building on the Normalized Systems design knowledge, prescriptions for other domains, such as the business process domain, can be proposed as well. This domain seems to overlap at least partially with the domain of Enterprise Ontology, which is used to establish claims concerning process design in various publications. However, both theories are based on completely different kernel theories. Therefore, this paper analyzes to which extent the guidelines proposed for the Normalized Systems Business Processes are consistent, complementing or conflicting with prescriptions from Enterprise Ontology. A consistent set of prescriptions could lead to a more integrated approach for designing integrated organizations, business processes and software systems.

show abstract

Combining DEMO and Normalized Systems for Developing Agile Enterprise Information Systems

Cited by 14 publications

References 6 publications

Towards Enterprise-Grade Tool Support for DEMO

Towards Enterprise-Grade Tool Support for DEMO

Separation of Modeling Principles and Design Principles in Enterprise Engineering

Consistency, Complementalness, or Conflictation of Enterprise Ontology and Normalized Systems Business Process Guidelines

Contact Info

Product

Resources

About