2009
DOI: 10.1007/978-3-642-00282-3
|View full text |Cite
|
Sign up to set email alerts
|

Model Driven Engineering and Ontology Development

Abstract: The use of general descriptive names, registered names, trademarks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 15 publications
(6 citation statements)
references
References 0 publications
0
6
0
Order By: Relevance
“…One possible knowledge base concept -amongst others -for representing knowledge are ontologies which consist of classes, relations, and axioms, and which provide " ... the basic structure or armature around which a knowledge base can be built' [33] and have useful characteristics as e.g. different fonus of representation, possibilities for knowledge sharing, or reasoning [34].…”
Section: A Knowledge Engineeringmentioning
confidence: 99%
“…One possible knowledge base concept -amongst others -for representing knowledge are ontologies which consist of classes, relations, and axioms, and which provide " ... the basic structure or armature around which a knowledge base can be built' [33] and have useful characteristics as e.g. different fonus of representation, possibilities for knowledge sharing, or reasoning [34].…”
Section: A Knowledge Engineeringmentioning
confidence: 99%
“…DevOps practices, model is still expected to hold an important role in a business and software-oriented engineering process (Babar et al, 2015). The use of the metamodel might be minimized in certain areas, but its usage pattern suggests the existence of communication and collaboration space where the model will persist, or even take a central role, such as envisioned by the modeldriven engineering approach (Gasevic et al, 2009).…”
Section: Discussionmentioning
confidence: 99%
“…Since the adoption of flowchart (Gelinas, Sutton and Fedorowicz, 2004), the modelling approach has shifted on several occasions, from the structured programming paradigm (DeMarco, 1979), to object-oriented (Rumbaugh et al, 1991), and more recently towards service-oriented approach (Papazoglou and Georgakopoulos, 2003). The importance of modelling in software engineering is further strengthened by the emergence of model-driven engineering (Gasevic et al, 2009), in which model becomes the core element of an engineering.…”
Section: Introductionmentioning
confidence: 99%
“…Ontology can be defined as "an explicit specification of a concept definition", which means that the concepts in a domain and the existing relationships among them are formalized in ontologies (Gruber, 1995). Thus, the common understanding about a domain is formalized in ontologies, mostly for the purpose of applying, sharing and exchanging information (Gašević, Djuric and Devedžic, 2009). Ontologies also enable integration of knowledge by unifying Databases, Data Warehouses, and knowledge bases vocabularies (Djellali, 2013).…”
Section: Ontologies and Semantic Reasoningmentioning
confidence: 99%