2011
DOI: 10.4018/jssmet.2011040104
|View full text |Cite
|
Sign up to set email alerts
|

An Ontology-Based and Model-Driven Approach for Designing IT Service Management Systems

Abstract: Currently, few projects applying a Model-Driven Engineering (MDE) approach start from high-level requirements models defined exclusively in terms of domain knowledge and business logic. Ontology Engineering (OE) aims to formalize and make explicit the knowledge related to a particular domain. In this vein, this paper presents a modeling approach, formalized in ontological terms, for defining high-level requirements models of software systems that provide support for the implementation of Information Technology… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 31 publications
0
4
0
Order By: Relevance
“…There is an approach known as Ontology-Driven Software Development (ODSD) in software engineering. This approach, as well as Domain-Driven Design (DDD) approach (Evans, 2015), follows the concept of Model-Based Software Development, the main idea of which is how to better integrate high-level domain models into the software development life cycle (Valiente et al, 2011). The purpose of the ODSD is the same, but unlike DDD, it applies this idea in a much more radical way: domain models are used not only to generate code but also as executable artifacts at runtime (Knublauch, 2004;Lavbič & Bajec, 2011).…”
Section: Requirement's Formalization Automation Issuementioning
confidence: 99%
“…There is an approach known as Ontology-Driven Software Development (ODSD) in software engineering. This approach, as well as Domain-Driven Design (DDD) approach (Evans, 2015), follows the concept of Model-Based Software Development, the main idea of which is how to better integrate high-level domain models into the software development life cycle (Valiente et al, 2011). The purpose of the ODSD is the same, but unlike DDD, it applies this idea in a much more radical way: domain models are used not only to generate code but also as executable artifacts at runtime (Knublauch, 2004;Lavbič & Bajec, 2011).…”
Section: Requirement's Formalization Automation Issuementioning
confidence: 99%
“…Valiente et al [8] design an ontology representing the best practices of the management processes based on ITIL V3. Wong, A. et al [9] provide a similar work taking eTOM as service process framework.…”
Section: Related Workmentioning
confidence: 99%
“…The Model -driven approach (MDA) for a system development was suggested, which is a variant of this refinementbased software development in which models are no longer loosely coupled, but connected in a systematic way: that is, model elements must be traceable from a more abstract model to a more concrete model and vice versa [17][18][19][20][21][22][23]. This is achieved through meta-modelling: meta-models define sets of valid models, facilitating their transformation, serialization, and exchange.…”
Section: Model -Driven Approach In Service Systems Designmentioning
confidence: 99%