Model-Driven Consistency Checking of Behavioural Specifications

2007 ◽  
Author(s):  
Bas Graaf ◽  
Arie van Deursen
Keyword(s):  
Consistency Checking ◽  
Model Driven

Ontological Analysis of KAOS using Separation of References

2011 ◽  
pp. 37-54 ◽  
Author(s):  
Raimundas Matulevicius ◽  
Patrick Heymans ◽  
Andreas L. Opdahl
Keyword(s):  
Information System ◽  
Information Systems ◽  
Modeling Languages ◽  
Consistency Checking ◽  
Goal Modeling ◽  
Model Driven ◽  
Language Interoperability ◽  
Ontological Analysis ◽  
View Synchronization ◽  
Structured Approach

Goal modeling is emerging as a central requirements engineering (RE) technique. Unfortunately, current goal-oriented languages are not interoperable with one another or with modeling languages that address other modeling perspectives. This problematic because the emerging generation of model-driven information systems is likely to depend on coordinated use of several modeling languages to represent different perspectives of the enterprise and its proposed information system. The chapter applies a structured approach to describe a well-known goal oriented language, KAOS, by mapping it onto a philosophically grounded ontology. The structured approach facilitates language interoperability because when other languages are described using the same approach, they become mapped onto the same ontology. The approach thereby provides an intermediate language for comparison, consistency checking, update reflection, view synchronization and, eventually, model-to-model translation, both between goal-oriented languages and between different languages.

ONTOLOGY-DRIVEN SOFTWARE ENGINEERING: BEYOND MODEL CHECKING AND TRANSFORMATIONS

2012 ◽  
Vol 06 (02) ◽  
pp. 205-242 ◽  
Author(s):  
ARTEM KATASONOV
Keyword(s):  
Software Engineering ◽  
Policy Enforcement ◽  
Consistency Checking ◽  
Model Driven Engineering ◽  
Model Driven ◽  
Software Engineers ◽  
Reference Implementation ◽  
Ontological Modeling ◽  
Support Software ◽  
Intended Use

This paper introduces a novel framework for Ontology-Driven Software Engineering. This framework is grounded on the prior related work that studied the interplay between the model-driven engineering and the ontological modeling. Our framework makes a contribution by incorporating a more flexible means for ontological modeling that also has a higher performance in processing, and by incorporating a wider range of ontology types into ODSE. As a result, it extends the power and speed of the classification and the model consistency checking ontological services enabled by the prior work, and brings new ontological services: semantic search in model repositories, three kinds of semi-automated model composition services: task-based, result-based, and opportunistic, and the policy enforcement service. The primary intended use for this framework is to be implemented as part of model-driven engineering tools to support software engineers. We describe our reference implementation of such a tool called Smart Modeller, and report on a performance evaluation of our framework carried out with the help of it.

scholarly journals Applied Artifact-Based Analysis for Architecture Consistency Checking

2020 ◽  
pp. 61-85
Author(s):  
Timo Greifenberg ◽  
Steffen Hillemacher ◽  
Katrin Hölldobler
Keyword(s):  
Software Development ◽  
Agile Development ◽  
Development Projects ◽  
Consistency Checking ◽  
Solution Domain ◽  
Model Driven ◽  
Complexity Management ◽  
Model Driven Software Development ◽  
Closing The Gap ◽  
High Degree

AbstractThe usage of models within model-driven software development aims at facilitating complexity management of the system under development and closing the gap between the problem and the solution domain. Utilizing model-driven software development (MDD) tools for agile development can also increase the complexity within a project. The huge number of different artifacts and relations, their different kinds, and the high degree of automation hinder the understanding, maintenance, and evolution within MDD projects. A systematic approach to understand and manage MDD projects with a focus on its artifacts and corresponding relations is necessary to handle the complexity. The artifact-based analysis presented in this paper is such an approach. This paper gives an overview of different contributions of the artifact-based analysis but focuses on a specific kind of analysis: architecture consistency checking of model-driven development projects. By applying this kind of analyses, differences between the desired architecture and the actual architecture of the project at a specific point in time can be revealed.

Use of Business Models within Model Driven Architecture

2009 ◽  
Vol 38 (38) ◽  
pp. 119-130
Author(s):  
Erika Asnina
Keyword(s):  
Business Models ◽  
Business Processes ◽  
Use Cases ◽  
Separation Of Concerns ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Development Processes ◽  
Business Requirements ◽  
Complex Computer ◽  
Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

Sign in / Sign up

Export Citation Format

Share Document