Aligning the Constructs of Enterprise Ontology and Normalized Systems

Huysmans, Philip; Bellens, David; Nuffel, Dieter Van; Ven, Kris

doi:10.1007/978-3-642-13048-9_1

Cited by 11 publications

(7 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[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]. It also points out that aspects such as user interfaces and non-functional requirements, which are not presented in EO, are considered as aspects in crosscutting concerns, which should be addressed separately from the functional requirements in NS.…”

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%

See 1 more Smart Citation

Separation of Modeling Principles and Design Principles in Enterprise Engineering

Suga

Bruyn

Huysmans

et al. 2016

Lecture Notes in Business Information Processing

Self Cite

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

Section: Related Workmentioning

confidence: 99%

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

Self Cite

View full text Add to dashboard Cite

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

“…A major challenge is to maintain the integrity of EA and its consistency with the continuously changing organization [63]. More formal and prescriptive approaches may be necessary to address this challenge [76]. Also new aspects may need to be considered, such as value [60] and culture [105] in order to make EA more effective for business innovation.…”

Section: Enterprise Engineering Challengesmentioning

confidence: 99%

“…• Solution Implementation: a) implementation for interoperability [123] and [52] b) thorough and dependable testing [55] and [76]. Together, these practices address some key decision-making that occurs during the SDLC, and provide a three-way benefit to project stakeholders.…”

Section: Positive Changes To the System Development Life Cycle (Sdlc)mentioning

confidence: 99%

e-Business Challenges and Directions: Important Themes from the First ICE-B Workshop

Marca

Bulander

Kruslin³

et al. 2012

Communications in Computer and Information Science

View full text Add to dashboard Cite

A three-day asynchronous, interactive workshop was held at ICE-B'10 in Piraeus, Greece in July of 2010. This event captured conference themes for e-Business challenges and directions across four subject areas: a) e-Business applications and models, b) enterprise engineering, c) mobility, d) business collaboration and e-Services, and e) technology platforms. Quality Function Deployment (QFD) methods were used to gather, organize and evaluate themes and their ratings. This paper summarizes the most important themes rated by participants: a) Since technology is becoming more economic and social in nature, more agile and context-based application develop methods are needed. b) Enterprise engineering approaches are needed to support the design of systems that can evolve with changing stakeholder needs. c) The digital native groundswell requires changes to business models, operations, and systems to support Prosumers. d) Intelligence and interoperability are needed to address Prosumer activity and their highly customized product purchases. e) Technology platforms must rapidly and correctly adapt, provide widespread offerings and scale appropriately, in the context of changing situational contexts.

show abstract

Aligning the Constructs of Enterprise Ontology and Normalized Systems

Cited by 11 publications

References 10 publications

Separation of Modeling Principles and Design Principles in Enterprise Engineering

Separation of Modeling Principles and Design Principles in Enterprise Engineering

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

e-Business Challenges and Directions: Important Themes from the First ICE-B Workshop

Contact Info

Product

Resources

About