2013
DOI: 10.4067/s0718-18762013000200007
|View full text |Cite
|
Sign up to set email alerts
|

Enterprise Architecture Development Based on Enterprise Ontology

Abstract: 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 o… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 15 publications
(7 citation statements)
references
References 11 publications
0
5
0
Order By: Relevance
“…J. Zachman himself adapted his framework several times to the developing IT (Information Technology) industry, and today it is considered a kind of reference concept harmonizing information technology and business needs [27,28]. At the same time, a number of experts, including J. Zachman, tend to consider this as a framework rather than an ontology [29,30]. In Zachman's modern view, his framework is a kind of Mendeleev's Table [31], which helps "assemble" "elementary particles" by means of certain processes in certain combinations into the required results.…”
Section: Methodsmentioning
confidence: 99%
“…J. Zachman himself adapted his framework several times to the developing IT (Information Technology) industry, and today it is considered a kind of reference concept harmonizing information technology and business needs [27,28]. At the same time, a number of experts, including J. Zachman, tend to consider this as a framework rather than an ontology [29,30]. In Zachman's modern view, his framework is a kind of Mendeleev's Table [31], which helps "assemble" "elementary particles" by means of certain processes in certain combinations into the required results.…”
Section: Methodsmentioning
confidence: 99%
“…Generally, the aim of enterprise ontologies is to support structuring of enterprise information and knowledge management [10], [31]. Due to the fact that enterprise ontologies are application ontologies within enterprises for structuring of information [10], [30]- [32], they aim to provide a common structure for data collection by offering a collection of terms and definitions relevant to business enterprises [30], [33]. The extended information is included in section 2.2.…”
Section: Possibilities Of Using Ontology In the Se Domainmentioning
confidence: 99%
“…Ontology-based solutions both in the form of Enterprise Ontology (EO) and Enterprise Architecture (EA) ontology are suggested and also successfully applied in many works [11], [20], [24], [33], [35]. The terms Enterprise Ontology and Enterprise Architecture currently belong to the standard vocabulary to designing and (re) engineering enterprises [11], [19], [20], [33], thereby exploiting modern information and communication technologies for innovating sustainable products and services [11], [36] as well as for optimizing operational performance [30]. The scope of EO is to ensure in particular acquisition, representation, and manipulation of enterprise knowledge [10], proposing a consistent core of basic concepts and language constructs [32].…”
Section: Possibilities Of Using Ontology In the Se Domainmentioning
confidence: 99%
“…Moreover, [6] studied Enterprise modeling based on ontology and presented a case study for a software producing firm in Iran. Finally, [15] employed an interpretive case study approach to explore the interoperability challenges resulting from EA implementation for a hospital in Denmark. [12] describe ZFW as a comprehensive matrix that is composed of six rows, representing the "Perspectives" of different stakeholders and include: Planner, Owner, Designer, Builder, Implementer, and Actual system, and six columns, representing the "Aspects/Abstractions" which identify different types of information (textual/ drawings) and are characterized by questions What, How, Where, Who, When, and Why.…”
Section: Previous Workmentioning
confidence: 99%