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

2013 ◽  
pp. 142-159
Author(s):  
María-Cruz Valiente ◽  
Cristina Vicente-Chicote ◽  
Daniel Rodríguez
Keyword(s):  
Domain Knowledge ◽  
Service Management ◽  
Management Systems ◽  
Model Transformations ◽  
Software Systems ◽  
Incident Management ◽  
Model Driven ◽  
Technology Service ◽  
High Level ◽  
Requirements Models

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 Service Management Systems (ITSMSs). This approach allows for: (1) formalizing the knowledge associated to the ITSM processes contained in an ITSMS; (2) modeling the semantics of the activities associated to these processes in terms of workflows; (3) automatically generating the high-level requirements models of the workflow-based software systems needed to support (part of) the ITSM processes; and (4) from the latter, obtaining lower-level models (and eventually code) by means of automated model transformations. A real case study describing the use of this proposal to model an Incident Management System is also included to demonstrate the feasibility and the benefits of the proposed approach.

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

2011 ◽  
Vol 2 (2) ◽  
pp. 65-81 ◽  
Author(s):  
María-Cruz Valiente ◽  
Cristina Vicente-Chicote ◽  
Daniel Rodríguez
Keyword(s):  
Domain Knowledge ◽  
Service Management ◽  
Management Systems ◽  
Model Transformations ◽  
Software Systems ◽  
Incident Management ◽  
Model Driven ◽  
Technology Service ◽  
High Level ◽  
Requirements Models

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 Service Management Systems (ITSMSs). This approach allows for: (1) formalizing the knowledge associated to the ITSM processes contained in an ITSMS; (2) modeling the semantics of the activities associated to these processes in terms of workflows; (3) automatically generating the high-level requirements models of the workflow-based software systems needed to support (part of) the ITSM processes; and (4) from the latter, obtaining lower-level models (and eventually code) by means of automated model transformations. A real case study describing the use of this proposal to model an Incident Management System is also included to demonstrate the feasibility and the benefits of the proposed approach.

Migrating JAVA to Mobile Platforms through HAXE

2016 ◽  
pp. 240-268 ◽  
Author(s):  
Pablo Nicolás Díaz Bilotto ◽  
Liliana Favre
Keyword(s):  
Programming Language ◽  
Mobile Applications ◽  
Software Evolution ◽  
Wide Spectrum ◽  
The Other ◽  
Model Transformations ◽  
Mobile Platforms ◽  
Model Driven ◽  
Definition Of ◽  
High Level

Software developers face several challenges in deploying mobile applications. One of them is the high cost and technical complexity of targeting development to a wide spectrum of platforms. The chapter proposes to combine techniques based on MDA (Model Driven Architecture) with the HaXe language. The outstanding ideas behind MDA are separating the specification of the system functionality from its implementation on specific platforms, managing the software evolution, increasing the degree of automation of model transformations, and achieving interoperability with multiple platforms. On the other hand, HaXe is a very modern high level programming language that allows us to generate mobile applications that target all major mobile platforms. The main contributions of this chapter are the definition of a HaXe metamodel, the specification of a model-to-model transformation between Java and HaXe and, the definition of an MDA migration process from Java to mobile platforms.

Concern Separation for Adaptive QoS Modeling in Distrbuted Real-Time Embedded Systems

2010 ◽  
pp. 85-113 ◽  
Author(s):  
Jeff Gray ◽  
Sandeep Neema ◽  
Jing Zhang ◽  
Yuehua Lin ◽  
Ted Bapty ◽  
...  
Keyword(s):  
Real Time ◽  
Graphical Models ◽  
Model Transformations ◽  
Modeling Language ◽  
Model Driven ◽  
Trade Offs ◽  
Design Alternatives ◽  
Domain Specific Modeling ◽  
High Level ◽  
Qos Adaptation

The development of distributed real-time and embedded (DRE) systems is often challenging due to conflicting quality-of-service (QoS) constraints that must be explored as trade-offs among a series of alternative design decisions. The ability to model a set of possible design alternatives—and to analyze and simulate the execution of the representative model—helps derive the correct set of QoS parameters needed to satisfy DRE system requirements. QoS adaptation is accomplished via rules that specify how to modify application or middleware behavior in response to changes in resource availability. This chapter presents a model-driven approach for generating QoS adaptation rules in DRE systems. This approach creates high-level graphical models representing QoS adaptation policies. The models are constructed using a domain-specific modeling language—the adaptive quality modeling language (AQML)—which assists in separating common concerns of a DRE system via different modeling views. The chapter motivates the need for model transformations to address crosscutting and scalability concerns within models. In addition, a case study is presented based on bandwidth adaptation in video streaming of unmanned aerial vehicles.

Foundations for MDA Case Tools

2010 ◽  
pp. 242-252
Author(s):  
Liliana María Favre ◽  
Claudia Teresa Pereira ◽  
Liliana Inés Martinez
Keyword(s):  
Specific Model ◽  
Model Transformations ◽  
Software Systems ◽  
Object Management Group ◽  
Model Driven ◽  
Management Group ◽  
Requirement Specifications ◽  
Technical Framework ◽  
Use Of Models ◽  
Independent Model

The model driven architecture (MDA) is an initiative proposed by the object management group (OMG), which is emerging as a technical framework to improve productivity, portability, interoperability, and maintenance (MDA, 2003). MDA promotes the use of models and modelto- model transformations for developing software systems. All artifacts, such as requirement specifications, architecture descriptions, design descriptions, and code are regarded as models. MDA distinguishes four main kinds of models: computation independent model (CIM), platform independent model (PIM), platform specific models (PSM), and implementation specific model (ISM).

Model-Driven Engineering, Services and Interactive Real-Time Applications

2014 ◽  
pp. 178-202
Author(s):  
Luis Costa ◽  
Neil Loughran ◽  
Roy Grønmo
Keyword(s):  
Software Engineering ◽  
Language Development ◽  
Real Time ◽  
Software Systems ◽  
Model Driven Engineering ◽  
Model Driven ◽  
Future Developments ◽  
Real Time Applications ◽  
High Level

Model-driven software engineering (MDE) has the basic assumption that the development of software systems from high-level abstractions along with the generation of low-level implementation code can improve the quality of the systems and at the same time reduce costs and improve time to market. This chapter provides an overview of MDE, state of the art approaches, standards, resources, and tools that support different aspects of model-driven software engineering: language development, modeling services, and real-time applications. The chapter concludes with a reflection over the main challenges faced by projects using the current MDE technologies, pointing out some promising directions for future developments.

ITIL 2011: Maturity Level of Service Operation

2019 ◽  
Vol 6 (1) ◽  
pp. 50-54
Author(s):  
Rekha Bella Novia ◽  
Wella .
Keyword(s):  
Information Technology ◽  
Service Quality ◽  
Service Management ◽  
Information Services ◽  
Incident Management ◽  
Access Management ◽  
Technology Infrastructure ◽  
Problem Management ◽  
Technology Service ◽  
Service Operation

Service quality is a measurement from users’ hope to the company in fulfilling their needs and desires also service delivery accuracy. Technology and information services can help the company in supporting the company’s business operations. Therefore, the company needs to apply ITSM (Information Technology Service Management) as an operational approach of technology and information services to keep the service quality in the company. The framework that is focusing on providing technology and information services which can be used as a guide is the ITIL framework (Information Technology Infrastructure Library). This research is conducted at PT Pertamina (Persero). The research is conducted using the 2011 ITIL framework on Domain Service Operation with 5 processes in it which are Incident Management, Request Fulfillment, Event Management, Access Management, and Problem Management. The methods that are used in this research are interview and questionnaires. This research is conducted based on research steps by Gallegos 2008, which consist of 5 steps such as the planning, the field checking, the report, and the follow-up. Based on the research conducted there are three processes that are stopped at level 1 which is Incident Management with score 62.54%, Problem Management with score 79.08% and Request Fulfillment with score 81.09%. Meanwhile, on the Access Management process achieve 86.00% and Access Management is stopped at level 2 with score 77,23%.

Bug Localization in Model-Based Systems in the Wild

2022 ◽  
Vol 31 (1) ◽  
pp. 1-32
Author(s):  
Lorena Arcega ◽  
Jaime Font Arcega ◽  
Øystein Haugen ◽  
Carlos Cetina
Keyword(s):  
Model Transformations ◽  
Bug Localization ◽  
Model Driven ◽  
Design Time ◽  
Model Based ◽  
In The Wild ◽  
Software Engineers ◽  
The Right ◽  
High Level ◽  
Wrong Place

The companies that have adopted the Model-Driven Engineering (MDE) paradigm have the advantage of working at a high level of abstraction. Nevertheless, they have the disadvantage of the lack of tools available to perform bug localization at the model level. In addition, in an MDE context, a bug can be related to different MDE artefacts, such as design-time models, model transformations, or run-time models. Starting the bug localization in the wrong place or with the wrong tool can lead to a result that is unsatisfactory. We evaluate how to apply the existing model-based approaches in order to mitigate the effect of starting the localization in the wrong place. We also take into account that software engineers can refine the results at different stages. In our evaluation, we compare different combinations of the application of bug localization approaches and human refinement. The combination of our approaches plus manual refinement obtains the best results. We performed a statistical analysis to provide evidence of the significance of the results. The conclusions obtained from this evaluation are: humans have to be involved at the right time in the process (or results can even get worse), and artefact-independence can be achieved without worsening the results.

Model-Driven Engineering, Services and Interactive Real-Time Applications

2011 ◽  
pp. 16-40
Author(s):  
Luis Costa ◽  
Neil Loughran ◽  
Roy Grønmo
Keyword(s):  
Software Engineering ◽  
Language Development ◽  
Real Time ◽  
Software Systems ◽  
Model Driven Engineering ◽  
Model Driven ◽  
Future Developments ◽  
Real Time Applications ◽  
High Level

Model-driven software engineering (MDE) has the basic assumption that the development of software systems from high-level abstractions along with the generation of low-level implementation code can improve the quality of the systems and at the same time reduce costs and improve time to market. This chapter provides an overview of MDE, state of the art approaches, standards, resources, and tools that support different aspects of model-driven software engineering: language development, modeling services, and real-time applications. The chapter concludes with a reflection over the main challenges faced by projects using the current MDE technologies, pointing out some promising directions for future developments.

Sign in / Sign up

Export Citation Format

Share Document