Results 1 - 10
of
12
On Marrying Ontological and Metamodeling Technical Spaces
, 2007
"... In software engineering, the use of models and metamodeling approaches (e.g., MDA with MOF/UML) for purposes such as software design or software validation is an established practice. Ontologies constitute domain models formalized using expressive logic languages for class definitions and rules. Hen ..."
Abstract
-
Cited by 14 (2 self)
- Add to MetaCart
In software engineering, the use of models and metamodeling approaches (e.g., MDA with MOF/UML) for purposes such as software design or software validation is an established practice. Ontologies constitute domain models formalized using expressive logic languages for class definitions and rules. Hence, when seen from an abstract point of view, the two paradigms and their various technological spaces seem closely related. However, in the state-of-the-art research and practice the two technologies are just beginning to converge and the relationship between the two is still under exploration. In this paper, we give an outline of current ontology technologies, such as the Semantic Web standards for a Web Ontology Language (OWL). Then, we describe a domain analysis of the different technical spaces, explaining the features of the different paradigms. Eventually, we describe some avenues for integrating various ontological technical spaces into meta modeling technical spaces.
Analysis of Compositional Conflicts in Component-Based Systems
, 2005
"... Today, incompatibilities in component specifications make their composition hard to handle in practical terms. Incompatibilities can be classified into three conflict categories: type conflicts, behavioral conflicts, and property conflicts. This paper describes a framework for the identification ..."
Abstract
-
Cited by 8 (0 self)
- Add to MetaCart
Today, incompatibilities in component specifications make their composition hard to handle in practical terms. Incompatibilities can be classified into three conflict categories: type conflicts, behavioral conflicts, and property conflicts. This paper describes a framework for the identification of compositional conflicts in component-based systems that analyses conflicts of all three categories. Furthermore, the framework supports conflict analysis from within the software development process and handles component transformations between different abstraction levels.
A Feature-based Framework for Model-Driven Engineering
"... Abstract. Model-Driven Engineering (MDE) improves software engineering by providing an appropriate level of abstraction for an early review of a system design. Model transformations can be used to establish a well-regulated development process. But existing transformation approaches still lack in co ..."
Abstract
-
Cited by 1 (1 self)
- Add to MetaCart
(Show Context)
Abstract. Model-Driven Engineering (MDE) improves software engineering by providing an appropriate level of abstraction for an early review of a system design. Model transformations can be used to establish a well-regulated development process. But existing transformation approaches still lack in connecting system requirements to the models realizing them. Furthermore, it is still difficult to integrate existing tools for particular tasks in MDE to an all-embracing environment. This paper presents a framework for MDE by defining required components and data structures to establish such an environment. It combines concepts of a UML-based MDE with feature modelling from Product Line Engineering. Feature models capture characteristics of existing system components as well as requirements of a planned application. They are used to control all parts of the engineering process. 1
DOI: 10.2298/CSIS121218068R Using Reverse Engineering to Construct the Platform Independent Model of a Web Application for Student Information Systems
"... Abstract. A methodology for extracting the domain knowledge from an existing three-tier web application and subsequent formulation of the plat-form independent model (PIM) is described. As it was devised during a re-verse engineering process of an existing web application which needed to be reimplem ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. A methodology for extracting the domain knowledge from an existing three-tier web application and subsequent formulation of the plat-form independent model (PIM) is described. As it was devised during a re-verse engineering process of an existing web application which needed to be reimplemented on a new platform using new technology, it focuses on the domain knowledge and business functions. It produces the business model and the hypertext model leaving the presentation model aside. The methodology is semi-automated — the generation of the activity diagrams and parts of the hypertext model must be in part performed by an analyst, preferably the one with some domain knowledge. As the paper is primar-ily aimed at practitioners, a case study illustrating the application of the presented method is included.
4 Reverse Engineering Platform Independent Models from Business Software Applications
"... ..."
(Show Context)
Model-Driven transformation with approach by modeling: From UML to N-tiers Web Model
"... Today, the N-tiers applications have become the norm for building enterprise software. In this paper we are going to present a model-driven approach to the development of N-tiers web applications based on the UML class diagram. The transformation language is the MOF 2.0 QVT (Meta-Object Facility 2.0 ..."
Abstract
- Add to MetaCart
(Show Context)
Today, the N-tiers applications have become the norm for building enterprise software. In this paper we are going to present a model-driven approach to the development of N-tiers web applications based on the UML class diagram. The transformation language is the MOF 2.0 QVT (Meta-Object Facility 2.0 Query-View-Transformation) standard which defines the meta-model for the development of model transformation. The transformation rules defined in this paper can generate, from the class diagram, an XML file containing the layers of N-tiers web application respecting a MVC2 (Model-View-Controller), DI (Dependency Injection) and DAO (Data Access Object) patterns. This file can be used to generate the end-to-end necessary code of a web application
unknown title
, 2004
"... Component composition is an important objective of software engineering. It promises component reuse and therefore a productivity gain, because of shorter time-to-market and improved quality. Unfortunately, composition is difficult to achieve in practical terms, because of technological incompatibil ..."
Abstract
- Add to MetaCart
(Show Context)
Component composition is an important objective of software engineering. It promises component reuse and therefore a productivity gain, because of shorter time-to-market and improved quality. Unfortunately, composition is difficult to achieve in practical terms, because of technological incompatibilities and diverging component specifications. The objective of this report is to define an Ontology-Based Framework for Identification of Compositional Conflicts in Component-Based Systems that serves as a basis of component integration. The framework provides a platform independent component model and a customizable basis for conflict identification. Within the framework, conflict identification is based on the analysis of structural and behavioral aspects of component descriptions. It also takes property-based descriptions of communicational requirements and technological aspects into account. Analysis identifies mismatched behavior by evaluating customizable relationships in each context. Examples of predefined relationships are subtypes, simulation and bisimulation
Parameterized Transformation of Platform Independent Component Models to Platform Specific Component Models with EJB Technology
"... ii Mapping technology between PIM and PSM is an important concept in the area of Model Driven Architecture (MDA). Establishing MDA application mainly includes building PIMs in UML and generating PSMs based on different platform technologies. These two steps are, till now, well-defined. Yet, the most ..."
Abstract
- Add to MetaCart
(Show Context)
ii Mapping technology between PIM and PSM is an important concept in the area of Model Driven Architecture (MDA). Establishing MDA application mainly includes building PIMs in UML and generating PSMs based on different platform technologies. These two steps are, till now, well-defined. Yet, the most important part involves in MDA approach – Mapping of PIM to PSM, is not mature. Most of the mapping tools on the market only provide one-to-one mapping between the source model and the code generation. Consequently, considerable amount of time is needed for defining different source models in order to obtain the aimed target code. And reuse of component is almost unattainable as the source models are only defined for a specific code generation. The objective of this paper is to propose a customizable mapping of PICM and PSCM. By providing the selection of a particular mapping according to the user requirement, customization of the transformation is feasible. MDA identifies four types of model-to-model transformations within the software development lifecycle. In this paper, we focus on the type PIM-to-PSM transformation. We attempt to propose a parameterized model
Science, Johannes-
"... In software engineering, the use of models and metamodeling approaches (e.g., MDA with MOF/UML) for purposes such as software design or software validation is an established practice. Ontologies constitute domain models formalized using expressive logic languages for class definitions and rules. Hen ..."
Abstract
- Add to MetaCart
(Show Context)
In software engineering, the use of models and metamodeling approaches (e.g., MDA with MOF/UML) for purposes such as software design or software validation is an established practice. Ontologies constitute domain models formalized using expressive logic languages for class definitions and rules. Hence, when seen from an abstract point of view, the two paradigms and their various technological spaces seem closely related. However, in the state-of-the-art research and practice the two technologies are just beginning to converge and the relationship between the two is still under exploration. In this paper, we give an outline of current ontology technologies, such as the Semantic Web standards for a Web Ontology Language (OWL). Then, we describe a domain analysis of the different technical spaces, explaining the features of the different paradigms. Eventually, we describe some avenues for integrating various ontological technical spaces into meta modeling technical spaces.
Model-View-Controller Architecture Specific Model Transformation
"... In this paper, we propose a model-driven development technique specific to the Model-View-Controller architecture domain. Even though a lot of application frameworks and source code generators are available for implementing this architecture, they do depend on implementation specific concepts, which ..."
Abstract
- Add to MetaCart
(Show Context)
In this paper, we propose a model-driven development technique specific to the Model-View-Controller architecture domain. Even though a lot of application frameworks and source code generators are available for implementing this architecture, they do depend on implementation specific concepts, which take much effort to learn and use them. To address this issue, we define a UML profile to capture architectural concepts directly in a model and provide a bunch of transformation mappings for each supported platform, in order to bridge between architectural and implementation concepts. By applying these model transformations together with source code generators, our MVC-based model can be mapped to various kind of platforms. Since we restrict a domain into MVC architecture only, automating model transformation to source code is possible. We have prototyped a supporting tool and evaluated feasibility of our approach through a case study. It demonstrates model transfor-mations specific to MVC architecture can produce source code for two different platforms.
