Results 1 -
6 of
6
Reusable MDA Components: A Testing-for-Trust Approach
- in "proceedings of the MoDELS/UML 2006
, 2006
"... Abstract. Making model transformations trustable is an obvious target for model-driven development since they impact on the design process reliability. Ideally, model transformations should be designed and tested so that they may be used and reused safely as MDA components. We present a method for b ..."
Abstract
-
Cited by 21 (9 self)
- Add to MetaCart
(Show Context)
Abstract. Making model transformations trustable is an obvious target for model-driven development since they impact on the design process reliability. Ideally, model transformations should be designed and tested so that they may be used and reused safely as MDA components. We present a method for building trustable MDA components. We first define the notion of MDA component as composed of its specification, one implementation and a set of associated test cases. The testing-for-trust approach checks the consistency between these three facets using the mutation analysis. It points out the lack of efficiency of the tests and the lack of precision of the specification. The mutation analysis thus gives a rate that evaluates: the level of consistency between the component’s facets and the level of trust we can have in a component. Relying on this estimation of the component trustability, developers can consciously trade reliability for resources. 1
Model-Driven User Requirements Specification using SysML
- Journal of Software
, 2008
"... Abstract — Requirements engineering is an important phase in a system’s life cycle. When poorly performed, various problems may occur, such as failures, cost overrun and delays. The increasing complexity of systems makes require-ments engineering activities both more important and more difficult. Mo ..."
Abstract
-
Cited by 7 (1 self)
- Add to MetaCart
(Show Context)
Abstract — Requirements engineering is an important phase in a system’s life cycle. When poorly performed, various problems may occur, such as failures, cost overrun and delays. The increasing complexity of systems makes require-ments engineering activities both more important and more difficult. Model-driven engineering, in which models are the main artifact during system development, is an emergent approach that tries to address system complexity by the intense use of models. This article proposes a model-driven approach to requirements engineering based on SysML Requirements and Use Case Diagrams. The main advantages are that user requirements are graphically modeled, their relationships are explicitly mapped, and system decomposi-tion is considered in the early system development activities. In addition, requirements traceability is enhanced by using the SysML Requirements tables. The approach is illustrated by a list of user requirements for a road traffic management system.
Do We Need Metamodels AND Ontologies for Engineering Platforms
- In Proceedings of the 1st ICSE Int. Workshop on Global Integrated Model Management
, 2006
"... In this paper we show how the joint use of metamodeling and ontologies allows to describe domain knowledge for a complex domain. Ontologies are used as stabilized descriptions of the business domain while metamodels allow a fine description of the domain (to be constructed in the initial phases of m ..."
Abstract
-
Cited by 6 (1 self)
- Add to MetaCart
(Show Context)
In this paper we show how the joint use of metamodeling and ontologies allows to describe domain knowledge for a complex domain. Ontologies are used as stabilized descriptions of the business domain while metamodels allow a fine description of the domain (to be constructed in the initial phases of modeling). We propose to use an ontology for anticipated categorization, i.e., as a “natural ” complement of the formal system which is induced by the metamodel. 1
A Metamodeling Framework for Promoting Flexibility and Creativity Over Strict Model Conformance
"... Abstract. This paper defines FlexiMeta, a metamodeling framework intended to promote more flexibility and creativity while not compromising validation through model conformance. It advocates less coupling between models and metamodels in order to make the creation of models and user-defined metamod ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. This paper defines FlexiMeta, a metamodeling framework intended to promote more flexibility and creativity while not compromising validation through model conformance. It advocates less coupling between models and metamodels in order to make the creation of models and user-defined metamodels possible in an arbitrary order. It comes along with a generic process structured into several phases. For each phase, a proper balance between flexibility and validation is found in order to bridge the gap between creativity and strict model conformance.
A Levels-based Approach for Defining Software Measurement Architectures
"... Abstract. During the execution of software projects, it is necessary to collect, store and analyze data to support project and organizational decisions. Software measurement is a fundamental practice for project management and process improvement. It is present in the main models and standards that ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. During the execution of software projects, it is necessary to collect, store and analyze data to support project and organizational decisions. Software measurement is a fundamental practice for project management and process improvement. It is present in the main models and standards that address software process improvement, such as ISO/IEC 12207, CMMI and MR MPS.BR. In order to effectively perform software measurement, it is necessary an infrastructure to support data collection, storage and analysis. This infrastructure can be defined by means of an architecture, which describes the components necessary to support software measurement. In this paper we present the main results obtained from a systematic mapping study that investigated software measurement architectures and an approach proposed aiming to help organizations define software measurement architectures.
OntMDE approach: Enhancing AIM with architectural ontology
"... Abstract:- Model-driven engineering (MDE) is a software development approach that mainly focus on models design and transformation. Models are basically built to represent different software system views and could be refined and evolved into lowered abstract level. This paper is a first investigatio ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract:- Model-driven engineering (MDE) is a software development approach that mainly focus on models design and transformation. Models are basically built to represent different software system views and could be refined and evolved into lowered abstract level. This paper is a first investigation of the model-driven paradigm enactment using established architecture-centric concepts. His goal is to provide an OntMDE approach for model transformations in the context of MDE. The OntMDE attempts to combine both architecture-centric and model-driven paradigms. It is based on two ideas. Firstly, the architecture of model is independent from any platform implementation. Therefore, the architectural considerations that are independent of platforms’ considerations must be dealt with at Platform Independent Model (PIM) level. For that, PIM will be decomposed into two models: an Architecture Independent Model (AIM) and an Architecture Dependent Model (ADM). Secondly, domain ontology is used as marking technique to label the AIM and architectural ontology description is provided to generate an ADM. Key-Words:- MDE, ontology, architectural styles, model transformations. 1