An ontology-based Enterprise Architecture

Kang, Dong-Woo; Lee, Jeong-Soo; Choi, Sungchul; Kim, Kwangsoo

doi:10.1016/j.eswa.2009.06.073

Cited by 89 publications

(45 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although well structured, EAs are described in natural language fostering ambiguity and lacking of formalization. (Kang et al, 2010) criticize EAs for the lack of detailed models for the components, of modelling the relationship between the components and the lack of a model for implementation. To overcome that drawbacks (Kang et al, 2010) remodelled the EA with ontologies.…”

Section: How To Represent Enterprise Architecturesmentioning

confidence: 99%

“…(Kang et al, 2010) criticize EAs for the lack of detailed models for the components, of modelling the relationship between the components and the lack of a model for implementation. To overcome that drawbacks (Kang et al, 2010) remodelled the EA with ontologies. They took the Federal Enterprise Architecture, that is based on Zachmann's, used the structure of WordNet to describe terms and SBVR to structure the relationships.…”

Section: How To Represent Enterprise Architecturesmentioning

confidence: 99%

“…Therefore (Kang et al, 2010) propose to relate enterprise ontology to an Enterprise Architecture Model. Even though there are many Enterprise Architectures likewise for companies and the public sector available they are designed for humans, to understand the various areas of an enterprise and the relations amongst them but are not 'understandable' for machines.…”

Section: How To Use Enterprise Architecturementioning

confidence: 99%

See 2 more Smart Citations

The Role of Content and Context in Enterprise Repositories

Hinkelmann¹,

Merelli

Thönssen

2010

Proceedings of the International Joint Workshop on Technologies for Context-Aware Business Process Management, Advanced Enterpr

View full text Add to dashboard Cite

Abstract.In this paper we show how to utilize enterprise architectures to model relations between information sources of an enterprise. With our approach the enterprise architecture models are not passive entities anymore but can be operationalized to identify dependencies between the various models and to integrate information sources. It thus is the basis for agile enterprises. We show that the elements of an enterprise architecture and the referenced data can take the role of both context and content depending on the objectives of their use. We present two independent approaches for modeling an enterprise ontology.

show abstract

Section: How To Represent Enterprise Architecturesmentioning

confidence: 99%

Section: How To Represent Enterprise Architecturesmentioning

confidence: 99%

Section: How To Use Enterprise Architecturementioning

confidence: 99%

See 1 more Smart Citation

The Role of Content and Context in Enterprise Repositories

Hinkelmann¹,

Merelli

Thönssen

2010

Proceedings of the International Joint Workshop on Technologies for Context-Aware Business Process Management, Advanced Enterpr

View full text Add to dashboard Cite

show abstract

“…He tries to provide meaningful information for the enterprise users, along with their needs and functional scope. Kang et al [17] presented an ontology-based three-level Enterprise Architecture in order to solve the lack of semantic understanding in common among different systems and between human and system and among stakeholders in the enterprise. It emphasizes to use Semantics of Business Vocabulary and Business Rules (SBVR) and Fact-oriented approach.…”

Section: Related Workmentioning

confidence: 99%

“…Firstly, there has not been common and exactly semantic understanding between human and system yet and it causes communication problems among humans or among systems or between human and system [17]. In addition, data collected in developing Enterprise Architecture are not based on a common definition of concepts and data communication; for example planner has one definition for action and the developer has another definition; in some cases a specific data is called with different names.…”

Section: Introductionmentioning

confidence: 99%

Enterprise Architecture Development Based on Enterprise Ontology

Rajabi¹,

Minaei

Seyyedi

2013

J. theor. appl. electron. commer. res.

View full text Add to dashboard Cite

Enterprises choose Enterprise Architecture (EA) solution, in order to overcome dynamic business challenges and in order to coordinate various enterprise elements. In this article, a solution is suggested for the Enterprise Architecture based on a conceptual model of Enterprise Ontology (EO). Enterprise Ontology provides a common structure for data collection. First, conceptual model of Enterprise Ontology based on the Zachman Framework is presented. Then, the Enterprise Architecture development process based on Enterprise Ontology is proposed. Using this solution, Staffs, stakeholders, users, architects, and systems achieved a common understanding of enterprise concepts and relationships and therefore, architecture data are collected in a correct way. The primary focus is collecting accurate architecture data instead of developing architecture artifacts; also meet the decision maker's needs by fit for purpose modeling. Finally, we demonstrate our solution in a case study and show the appropriate results and conclusions.

show abstract

An Interoperable Enterprise Architecture to Support Decentralized Collaborative Planning Processes in Supply Chain Networks

Hernández

Mula

2010

Enterprise Interoperability IV

View full text Add to dashboard Cite

An ontology-based Enterprise Architecture

Cited by 89 publications

References 7 publications

The Role of Content and Context in Enterprise Repositories

The Role of Content and Context in Enterprise Repositories

Enterprise Architecture Development Based on Enterprise Ontology

An Interoperable Enterprise Architecture to Support Decentralized Collaborative Planning Processes in Supply Chain Networks

Contact Info

Product

Resources

About