Model-driven Development Research Articles

An analysis of user-interface creation complexity using a model-driven design approach

Model-Driven Development (MDD) is a software development approach that facilitates problem comprehension. MDD is carried out based on level of abstraction attained by working with models. When using models to create user-interfaces, development time can be reduced significantly. However, automatic user-interface generation is done with preestablished templates that might not fulfill all the requirements clients. These templates might also be too general and sometimes provide few customization options. In this paper, we review research on the usage of MDD for user-interface development. We also study how automatic user-interface generation can result in limitations as the need might arise for repeatedly modifying model and code.

Model driven transformation development (MDTD): An approach for developing model to model transformation

Abstract Context In the Model Driven Development (MDD) approach, model transformations are responsible for the semi-automation of software development process converting models between different abstraction levels. The development of model transformations involves a complexity inherent to the transformation domain, in addition to the complexity of software development in general. Therefore, the construction of model transformations requires software engineering feature such as processes and languages to facilitate its development and maintenance. Objective This paper presents a framework to develop unidirectional relational model transformation using the MDD approach itself, which integrates: (i) a software development process suitable for the model transformation domain (ii) a Domain specific language for transformation modeling (iii) a transformation chain, to (semi) automate the proposed process, and (iv) a development environment to support it. Methods The proposal systematizes the development of model transformation, following the MDD principles. An iterative and incremental process guides transformation development from requirement specification to transformation codification. The proposal has been evaluated through a case study and a controlled experiment. Results The framework enables model transformation specification at a high abstraction level and (semi) automatically transforms it into models at a low abstraction level until the transformation code. The results of the case study showed that people with different levels of knowledge of MDD, or without experience in transformation languages, were able to develop transformations through the framework and generated executable code. Conclusions The framework integrates the essential elements involved in the development of model transformation and enables the abstraction of technological details. The results of the case study and controlled experiment showed the feasibility of the proposal and its use in dealing with the complexity involved in model transformation development.

Evaluation of a Model-driven Knowledge Storage and Retrieval IDE for Interactive HRI Systems

Efficient storage and querying of long-term human–robot interaction data requires application developers to have an in-depth understanding of the involved domains. Creating syntactically and semantically correct queries in the development process is an error prone task which can immensely impact the interaction experience of humans with robots and artificial agents. To address this issue, we present and evaluate a model-driven software development approach to create a long-term storage system to be used in highly interactive HRI scenarios. We created multiple domain-specific languages that allow us to model the domain and seamlessly embed its concepts into a query language. Along with corresponding model-to-model and model-to-text transformations, we generate a fully integrated workbench facilitating data storage and retrieval. It supports developers in the query design process and allows in-tool query execution without the need to have prior in-depth knowledge of the domain. We evaluated our work in an extensive user study and can show that the generated tool yields multiple advantages compared to the usual query design approach.

Maintaining consistency in networks of models: bidirectional transformations in the large

The model-driven development of systems involves multiple models, metamodels and transformations, and relationships between them. A bidirectional transformation (bx) is usually defined as a means of maintaining consistency between “two (or more)” models. This includes cases where one model may be generated from one or more others, as well as more complex (“symmetric”) cases where models record partially overlapping information. In recent years, binary bx, those relating two models, have been extensively studied. Multiary bx, those relating more than two models, have received less attention. In this paper, we consider how a multiary consistency relation may be defined in terms of binary consistency relations and how consistency restoration may be carried out on a network of models and relationships between them. In particular, we consider the circumstances under which we can prove non-interference between several bidirectional transformations that impact on the same model and how the use of a more refined notion of consistency can help in cases where this is not possible. In the process, we develop an abstract theory of parts of a model that are read or modified by a bidirectional transformation. We relate the work to megamodelling and discuss further research that is needed.

Definition of the Criteria for Layout of the UML Use Case Diagrams

Abstract Nowadays, the topicality and applicability of model-driven development in the object-oriented development approach has increased, so it is important that created models and diagrams display not only the content, but also visually reflect information. Transparent diagram placement that influences work productivity is important for displaying information. Manual layout of diagrams is a time-consuming activity, which can also be ineffective, so in this paper the application of UML use case automatic layout is reviewed. The paper also examines the requirements of use case diagrams and placement criteria, which will serve as a basis for the creation of an automatic use case diagram layout algorithm.

A Pattern-Based Development Approach for Interaction Flow Modeling Language

Development and deployment technologies for data-intensive web applications have considerably evolved in the last years. Domain-specific frameworks or model-driven web engineering approaches are examples of these technologies. They have made possible to face implicit problems of these systems such as quick evolving business rules or severe time-to-market requirements. Both approaches propose the automation of redundant development tasks as the key factor for their success. The implementation of CRUD operations is a clear example of repetitive and recurrent task that may be automated. However, although web application frameworks have provided mechanisms to automate the implementation of CRUD operations, model-driven web engineering approaches have generally ignored them, so automation has not been properly faced yet. This paper presents a pattern-based development approach for the Interaction Flow Modeling Language as a way to finally automate repetitive specification tasks. Our approach is illustrated by defining and applying IFML patterns for CRUD operations. Additionally, a supporting tool, which enables automation, is shown. The suitability of our approach and the utility of its tool have been evaluated by its application into several real projects developed by a software company specialized in model-driven web application development. The results obtained present evidence of a significant productivity improvement obtained by the automation of the IFML specification of CRUD operations.

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

Context: Managing Non-Functional Requirements (NFRs) in software projects is challenging, and projects that adopt Model-Driven Development (MDD) are no exception. Although several methods and techniques have been proposed to face this challenge, there is still little evidence on how NFRs are handled in MDD by practitioners. Knowing more about the state of the practice may help researchers to steer their research and practitioners to improve their daily work. Objective: In this paper, we present our findings from an interview-based survey conducted with practitioners working in 18 different companies from 6 European countries. From a practitioner's point of view, the paper shows what barriers and benefits the management of NFRs as part of the MDD process can bring to companies, how NFRs are supported by MDD approaches, and which strategies are followed when (some) types of NFRs are not supported by MDD approaches. Results: Our study shows that practitioners perceive MDD adoption as a complex process with little to no tool support for NFRs, reporting productivity and maintainability as the types of NFRs expected to be supported when MDD is adopted. But in general, companies adapt MDD to deal with NFRs. When NFRs are not supported, the generated code is sometimes changed manually, thus compromising the maintainability of the software developed. However, the interviewed practitioners claim that the benefits of using MDD outweight the extra effort required by these manual adaptations. Conclusion: Overall, the results indicate that it is important for practitioners to handle `NFRs in MDD, but further research is necessary in order to lower the barrier for supporting a broad spectrum of NFRs with MDD. Still, much conceptual and tool implementation work seems to be necessary to lower the barrier of integrating the broad spectrum of NFRs in practice.

Reasoning about clinical guidelines based on algebraic data types and constraint logic programming.

Previously, the authors presented an overall framework aimed at improving the representation, quality and application of clinical guidelines in daily clinical practice. Regarding the quality improvement of guidelines, we developed a proposal to verify specific requirements in guidelines, using the SPIN model checker as verification tool. Additionally, we established a pattern-based approach for defining commonly occurring types of requirements in guidelines, in order to help non experts in their formal specification. In particular, among such patterns, we identified several which could not be verified by using such a proposal, thus leaving their verification as future work. In this paper, we provide a revised and extended version of that work by providing an overall proposal which mainly addresses previous shortcomings, while providing additional verification functionalities. More specifically, we have defined a complementary proposal to the previous one regarding the verification of guidelines. This proposal uses Formula, a model finding and design space exploration tool that is based on Algebraic Data Types (ADT) and Constraint Logic Programming (CLP). The main contributions of this paper are twofold: (1) providing a more complete set of patterns for defining commonly occurring types of requirements in guidelines, and (2) supporting the verification of a wider range of patterns by combining the use of our previous proposal, based on the SPIN model checker, with our Formula-based method. More specifically, our Formula-based proposal provides us with a solution to the verification of those patterns we were not able to verify previously. Additionally, our proposal has been implemented as an Eclipse plug-in developed based on Model Driven Development (MDD) techniques, which enables us to automatically generate the Formula specification of a guideline, making the process faster and less error-prone than a manual translation. This Formula specification, together with the requirements to be checked in the guideline, are finally taken as input of the Formula tool to check whether the guideline verifies the requirements. We show the feasibility of our overall approach by verifying properties in different clinical guidelines with encouraging results.

A methodology for designing mobile, pervasive, seamless and IoT-based learning scenarios: language, process and supporting tools

A significant interest and a considerable attention have been given, in recent years, to the mobile pervasive and the Internet of Things (IoT) throughout different fields such as education. However, there are only few empirical examples regarding the use of those technologies in learning design and there is a scarcity of theoretical researches and studies within the literature. This paper seeks to fill this gap by investigating features required in designing such TEL scenarios and by proposing a methodology that allows teachers to design, simulate, enact and track, innovative learning scenarios. The strengths of our approach lie in the fact that it takes into account both design and run-time phases by combining mobile and IoT Key elements, Model-driven development, Activity theory and Tin-Can Api specification. We have conducted two researches at the Tunisian Bardo National Museum to verify the utility of applying the proposed methodology. The paper concludes with a discussion of how the methodology meets the challenges.

A methodology for designing mobile, pervasive, seamless and IoT-based learning scenarios: language, process and supporting tools

A significant interest and a considerable attention have been given, in recent years, to the mobile pervasive and the Internet of Things (IoT) throughout different fields such as education. However, there are only few empirical examples regarding the use of those technologies in learning design and there is a scarcity of theoretical researches and studies within the literature. This paper seeks to fill this gap by investigating features required in designing such TEL scenarios and by proposing a methodology that allows teachers to design, simulate, enact and track, innovative learning scenarios. The strengths of our approach lie in the fact that it takes into account both design and run-time phases by combining mobile and IoT Key elements, Model-driven development, Activity theory and Tin-Can Api specification. We have conducted two researches at the Tunisian Bardo National Museum to verify the utility of applying the proposed methodology. The paper concludes with a discussion of how the methodology meets the challenges.

An Integrated Modeling, Simulation and Analysis Framework for Engineering Complex Systems

The discipline of component-based modeling and simulation offers promising gains in reducing cost, time, and the complexity of model development through the (re)use of modular components. Model-driven development suggests 1) the realization of a complex system using a conceptual model; 2) its automatic transformation into an executable form using transformation rules, and; 3) its automatic verification using a formal analysis technique for an accurate assessment of its correctness. Both approaches have numerous complementary benefits in rapid prototyping of complex systems using model reuse. In this paper, we propose a framework grounded in a combination of component-based and model-driven approaches to promote rapid prototyping of complex systems through the effective reuse of the simulation models. Our proposed process allows developers to 1) build or select existing components and compose them to formulate the conceptual models of complex systems; 2) automatically transform the conceptual models for the rapid implementation and simulation, and; 3) automatically verify them as per the requirement specifications. We propose the use of the extended finite-state machine (EFSM) as conceptual modeling formalism, anylogic simulation platform for the implementation, and probabilistic model checking technique using communicating sequential process (CSP) formalism for the verification. Finally, we present a case study of a real-time adaptive cruise control system to demonstrate the functionality of our framework. Our proposed component-based model-driven approach facilitates rapid prototyping and effective meaningful reuse of complex system models, which further accelerates the modeling, simulation, and analysis process of real-time systems and aids in complex engineering designs and implementations.

Model-driven development of agent-based cyber-physical systems

In order to achieve its goal in using intelligent adaptive and predictive technical systems with self-X functions and cognitive information processing in continuous interaction with environment, the Industry 4.0 initiative implies integration of Cyber-Physical Systems (CPS), the Internet of Things (IoT) and cloud computing leading to what is called "smart factory". This, in turn, faces the CPS with new challenges in terms of increasing the degree of distribution, autonomy, mobility, communication and security of the systems and their components, as well as expanding their functionality in the direction of data analytics, information and knowledge extraction, and increasing their intelligence. The main aim of the paper is to define a software process model for model-driven development of agent-based CPS using the Organization-based multi-agent software engineering process framework O-MaSE. CPS are developed as layer-based Multi Agent Systems (MAS) that enable the division of system elements into levels, reduce the coupling between modules and facilitates abstractions as well as the distributions of responsibilities. The suggested approach is illustrated with an example for model-driven development of pilot batch reactor as an agent-based CPS based on O-MaSE methodology and agentTool III.

Customized code generation based on user specifications for simulation and optimization

Model-driven software engineering is a well-known concept in computer science, but scarcely applied in chemical engineering. This contribution presents a first implementation of model-driven development of customized code for simulation and optimization based on equation-oriented models in process science. Transferring the model-driven approach to chemical engineering allows for transformations or discretizations before automated code generation. The customization of this concept poses additional challenges regarding flexibility and tailoring for the user’s needs. We propose the so-called “User-defined Language Specificators (UDLS)”, based on free standards (MathML, XML), to combine the benefits of automated code generation with the flexibility of customization, therefore still avoiding error-prone manual model implementation. The case studies show the successful application of this approach for equation-based flowsheet simulation (using CAPE-OPEN interfaces) as well as optimization.

Model Driven Development Applied to Complex Event Processing for Near Real-Time Open Data.

Nowadays, data are being produced like never before because the use of the Internet of Things, social networks, and communication in general are increasing exponentially. Many of these data, especially those from public administrations, are freely offered using the open data concept where data are published to improve their reutilisation and transparency. Initially, the data involved information that is not updated continuously such as budgets, tourist information, office information, pharmacy information, etc. This kind of information does not change during large periods of time, such as days, weeks or months. However, when open data are produced near to real-time such as air quality sensors or people counters, suitable methodologies and tools are lacking to identify, consume, and analyse them. This work presents a methodology to tackle the analysis of open data sources using Model-Driven Development (MDD) and Complex Event Processing (CEP), which help users to raise the abstraction level utilised to manage and analyse open data sources. That means that users can manage heterogeneous and complex technology by using domain concepts defined by a model that could be used to generate specific code. Thus, this methodology is supported by a domain-specific language (DSL) called OpenData2CEP, which includes a metamodel, a graphical concrete syntax, and a model-to-text transformation to specific platforms, such as complex event processing engines. Finally, the methodology and the DSL have been applied to two near real-time contexts: the analysis of air quality for citizens’ proposals and the analysis of earthquake data.

Evaluating user interface generation approaches: model-based versus model-driven development

Advances in software design possibilities have led to a growing interest in the study of user interfaces (UIs). Many Model-Based User Interface Development Environments (MB-UIDEs) have been proposed to deal with the generation of the UIs (semi-) automatically by using models with different levels of abstraction. Often, this generation is limited to the UI part of an application. However, achieving true model-driven development (MDD) requires the co-development of application and UI and, hence, needs to go a step further. This paper analyzes a large set of existing MB-UIDEs, evaluates, from a critical perspective, to what extent they can be considered full MDD environments, and adequately addresses the co-design of UI and application. Following the guidelines proposed by Kitchenham and Charters (Engineering 2, 2007), we performed a systematic literature review. A total of 96 papers were examined. Based on these papers, an assessment framework containing 10 criteria with specific metrics to evaluate MB-UIDEs was defined and 30 different environments were evaluated following these criteria. The evaluation identifies several gaps in the existing state of the art and highlights the areas of promising improvement. The evaluation shows that, although a strong progress has being achieved over the last years, the existing environments do not yet fully exploit the benefits and potentialities of MDD, nor do they adequately integrate UI design with application logic design and generation. Further research needs to be done to support the MDD of UIs and the co-design of the underlying application. The difficulty of use of the existing MB-UIDEs, the lack of UI design flexibility, and the lack of complete and integrated development support are the main research gaps that need to be addressed.

UML activity diagram transformation into BPEL integration flow

The growing interest of companies in integration and interoperability between information systems has caused increase in significance of Service-Oriented Architecture which provides tools for Enterprise Application Integration. In that architecture, Enterprise Service Bus provides technical possibilities of communication between IT systems. A key element in the communication are integration flows. Objective: The aim of this article is to present a new transformation Integration2BPEL, which automates the development of executable integration flow expressed in the Web Services Business Process Execution Language (WS-BPEL) based on the model of the integration flow presented in the Unified Modelling Language (UML) activity diagram. Method: The author proposes a transformation of the type of model-to-code type which generates integration flow expressed in WS-BPEL, which can be executed in any BPEL-compliant process engine. The integration flow is modelled using UML activity diagram with stereotypes from ‘UML Profile for Integration Flows’ profile in an IBM Rational Software Architect (RSA). Using Integration2BPEL transformation a complete, executable integration flow is generated, which is composed of many mediation mechanisms. Generated integration flows have been executed on OpenESB. Results: The ability to generate a complete integration flow in BPEL, which without any additions can be run on enterprise service bus. Implementation phase of an integration flow construction was automated. Each of integration flows is implemented according to the same rules. In addition, it allows to avoid mistakes made by designers and programmers. Conclusions: Model-Driven Development is an approach that leads to the automation of the design and programming phases. Integration2BPEL transformation is a uniform mechanism to design integration flow. Potentially, it also allows to avoid implementation errors. Keywords: Web Services Business Process Execution Language (BPEL), Enterprise Service Bus (ESB), Unified Modelling Language (UML), UML activity diagram, Model-Driven Development (MDD), Transformation. null

Dependable Model-driven Development of CPS

Simulink is widely used for model-driven development (MDD) of cyber-physical systems. Typically, the Simulink-based development starts with Stateflow modeling, followed by simulation, validation, and code generation mapped to physical execution platforms. However, recent trends have raised the demands of rigorous verification on safety-critical applications to prevent intrinsic development faults and improve the system dependability, which is unfortunately challenging. Even though the constructed Stateflow model and the generated code pass the validation of Simulink Design Verifier and Simulink Polyspace, respectively, the system may still fail due to some implicit defects contained in the design model (design defect) and the generated code (implementation defects). In this article, we bridge the Stateflow-based MDD and a well-defined rigorous verification to reduce development faults. First, we develop a self-contained toolkit to translate a Stateflow model into timed automata, where major advanced modeling features in Stateflow are supported. Taking advantage of the strong verification capability of Uppaal, we can not only find bugs in Stateflow models that are missed by Simulink Design Verifier but also check more important temporal properties. Next, we customize a runtime verifier for the generated non-intrusive VHDL and C code of a Stateflow model for monitoring. The major strength of the customization is the flexibility to collect and analyze runtime properties with a pure software monitor, which offers more opportunities for engineers to achieve high reliability of the target system compared with the traditional act that only relies on Simulink Polyspace. In this way, safety-critical properties are both verified at the model level and at the consistent system implementation level with physical execution environment in consideration. We apply our approach to the development of a typical cyber-physical system-train communication controller based on the IEC standard 61375. Experiments show that more ambiguousness in the standard are detected and confirmed and more development faults and those corresponding errors that would lead to system failure have been removed. Furthermore, the verified implementation has been deployed on real trains.

Methodology for the model-driven development of service oriented IoT applications

Abstract The main problem with the current technology solutions for Internet of Things (IoT) is located at the application level, in which there is still a lack of software components, frameworks, and tools which can help end-users to easily develop IoT applications and to manage the things or objects. These requirements lead to the use of the principles of Model-Driven Development (MDD) and Service-Oriented Architecture (SOA) for the construction of software applications, allowing the generation of models at different levels of abstraction, with the possibility of generating software implementation artifacts (code) on different platforms, as well as allow the decomposition of complex and monolithic systems into loosely coupled components. In this paper, we propose a methodology based on the MDD for solving the challenges in the IoT system developments. The methodology is composed of four phases with different levels of abstraction, viewpoint, granularity, and service-oriented. Furthermore, a set of MDD methods for the transformation of models using formal rules are proposed. We present a smart vehicle scenario in which the methodology and methods are implemented, allowing the generation of executable code as a component of a real-time system. In addition, an architecture for IoT systems composed of four layers is presented, which is based on the SOA approach. In this way, the methodology and the architecture allow the interoperability (from the perspective of models and software components) between heterogeneous devices to be guaranteed in multiple ways, establishing a bridge between the digital and physical world of the IoT domain .

Non-functional requirements in model-driven development of service-oriented architectures

Any software development process needs to consider non-functional requirements (NFR) in order to deliver a system that complies with its stakeholders' expectations. In a previous mapping study about model-driven development (MDD) for service-oriented architectures (SOA) we found a limited number of approaches managing NFR. The present work aims at analyzing in detail the state of the art in the management of NFR in MDD processes which produce SOA. We have conducted a systematic literature review following a rigorous protocol. We have taken as initial point the mapping study mentioned above and have used the subset of the 31 papers from this study (clustered into 15 approaches) that referred to NFR. We have analyzed them qualitatively in order to answer six research questions. We have built a Software Engineering theory to formalize this analysis. As result we highlight that most of approaches focus exclusively on security and reliability and we observe that NFR are expressed mainly as annotations of functional models represented in UML. From our perspective, existing research on the topic of this study is still scarce and without any evidence of transferability to industry. This situation suggests the need for further investigation efforts in order to produce validated MDD methods capable of generating SOA satisfying NFR stated by stakeholders. • Any software development process needs to consider non-functional requirements (NFR) to fulfill stakeholders' expectations. • A systematic literature review on the management of NFR in MDD processes which produce SOA systems has been conducted. • Most of approaches focus on security and reliability and express NFR as annotations of functional models represented in UML. • Existing research seems to be still scarce and without any evidence of transferability to industry.

Model-Driven Approach to develop Rich Web Applications

Many Web applications have among their features the possibility of distributing their data and their business logic between the client and the server, also allowing an asynchronous communication between them. These features, originally associated with the arrival of Rich Internet Applications (RIA), remain particularly relevant and desirable. In the area of RIA, there are few proposals that simultaneously consider these features, adopt Model-Driven Development (MDD), and use implementation technologies based on scripting. In this work, we start from MoWebA, an MDD approach to web application development, and we extend it by defining a specific architecture model with RIA functionalities, supporting the previously mentioned features. We have defined the necessary metamodels and UML profiles, as well as transformation rules that allow you to generate code based on HTML5, Javascript, jQuery, jQuery Datatables and jQuery UI. The preliminary validation of the proposal shows positive evidences regarding the effectiveness, efficiency and satisfaction of the users with respect to the modeling and code generation processes of the proposal.