Model-Driven Web Engineering Research Articles

Enhanced model-driven web application development with code generation using deep learning technique

Advancements in modern technology have led to an endless reliance on the Internet. This has created a great demand for the fast and accurate development of web applications. Web development has benefitted from programming approaches such as Model-Driven Web Engineering (MDWE). MDWE allows developers to choose pre-defined models and utilize them for their requirements. This kind of structural blueprinting, called wireframing, enables efficiency in software development. However, these techniques are seldom understood by people without a technological background. Hence, much of the coding central to a project remains the responsibility of a few tech-educated people. This work proposes an approach that offloads some of the typing to a machine-based code generator. This has been achieved by pairing MDWE methods with Deep Learning capabilities. This ensures a less coding-intensive web development methodology that can be utilized even by non-web developers. This work makes several contributions to improving overall MDWE methods.

Разработка Web-приложений с учетом элементов качества данных – DQAWA

An acceptable level of quality in data is nowadays a paramount for any kind of organization or enterprise that wishes its business processes to prosper. Thus, introducing activities focused in the data quality management is a crucial requirement for the analysts if the level of quality of data for the functionality or service at hand is to be ensured. Such specialized data quality management activities should be presented as early as possible during the software development process. So far and having done a search for proposals in this field, there is still a lack of either methodological or technological proposals with which a developer could be able to design data quality aware applications in the specific field of Web application development. Considering the benefits offered in the field of Model Driven Web Engineering, this work presents a partial outcome of our research in this novel field: a metamodel and a UML profile, both able to be used as data quality artefacts during the design stage of Web applications. The main objective is to provide the designer with the tools needed to design Web applications, in order to prevent data quality issues.

Developing Web Applications with Awareness of Data Quality Elements – DQAWA

An acceptable level of quality in data is nowadays a paramount for any kind of organization or enterprise that wishes its business processes to prosper. Thus, introducing activities focused in the data quality management is a crucial requirement for the analysts if the level of quality of data for the functionality or service at hand is to be ensured. Such specialized data quality management activities should be presented as early as possible during the software development process. So far and having done a search for proposals in this field, there is still a lack of either methodological or technological proposals with which a developer could be able to design data quality aware applications in the specific field of Web application development. Considering the benefits offered in the field of Model Driven Web Engineering, this work presents a partial outcome of our research in this novel field: a metamodel and a UML profile, both able to be used as data quality artefacts during the design stage of Web applications. The main objective is to provide the designer with the tools needed to design Web applications, in order to prevent data quality issues.

Challenges for the Adoption of Model-Driven Web Engineering Approaches in Industry.

Challenges for the Adoption of Model-Driven Web Engineering Approaches in Industry.

Integrating Web-Based Collaborative Live Editing and Wireframing into a Model-Driven Web Engineering Process

Today’s Model-Driven Web Engineering (MDWE) approaches automatically generate Web applications from conceptual, domain-specific models. This enhances productivity by simplifying the design process through a higher degree of abstraction. Due to this raised level of abstraction, the collaboration on conceptual models also opens up new use cases, such as the tighter involvement of non-technical stakeholders into Web development. However, especially in the early design stages of Web applications, common practices for requirement elicitation mostly rely on wireframes instead of MDWE, created usually in analog settings. Additionally, state-of-the-art MDWE should integrate established and emerging Web development features, such as Near Real-Time (NRT) collaborative modeling and shared editing on the generated code. The combination of collaborative modeling, coding and wireframing, all in NRT, bears a lot of potential for improving MDWE practices. The challenge when covering these requirements lies with synchronizing source code, wireframes and models, an essential need to cope with regular changes in the software architecture to provide the flexibility needed for agile MDWE. In this contribution, we present a MDWE approach with live code editing and wireframing capabilities. We present the conceptual considerations of our approach, the realization of it and the integration into an overarching development methodology. Following a design science approach, we present the cyclic iterations of developing and evaluating our artifacts, which show promising results for collaborative Web development tasks that could open the gate towards novel, collaborative and agile MDWE techniques.

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.

Enhancing theWeb WithAdvanced Engineering

Enhancing theWeb WithAdvanced Engineering

AutoCRUD: Automatic generation of CRUD specifications in interaction flow modelling language

Data-intensive Web applications are usually developed by means of specific Web application frameworks, which provide, among other features, the proper tools to automate redundant tasks, e.g. the implementation of CRUD operations. However, although Model-Driven Web Engineering (MDWE) approaches have defined specific languages and tools to significantly reduce development efforts, the provision of such automation tools has been traditionally neglected. This paper presents AutoCRUD, a WebRatio plug-in automating the generation of CRUD operations in OMG Interacting Flow Modelling Language (IFML). It has been developed as a joint effort by academia and industry to assess its validity in a real scenario. • A MDWE tool (WebRatio plugin) to automatically generate CRUD operations specification in IFML by pattern instantiation. • New patterns may be defined to enlarge its default repository. • For teaching purposes, a step-by-step generation of IFML may be performed. • Easy and guided visual instantiation of patterns. • It may significantly increase development team productivity.

Applying a model-based methodology to develop web-based systems of systems

Systems of Systems (SoS) are emerging applications composed by subsystems that interacts in a distributed and heterogeneous environment. Web-based technologies are a current trend to achieve SoS user interaction. Model Driven Web Engineering (MDWE) is the application of Model Driven Engineering (MDE) into the Web development domain. This paper presents a MDWE methodology to include Web-based interaction into SoS development. It's composed of ten models and seven model transformations and it's fully implemented in a support tool for its usage in practice. Quality aspects covered through the traceability from the requirements to the nal code are exposed. The feasibility of the approach is validated by its application into a real-world project. A preliminary analysis of potential bene ts (reduction of e ort, time, cost; improve of quality; design vs code ratio, etc) is done by comparison to other project as an initial hypothesis for a future planned experimentation research.

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

Model-Driven Web Engineering (MDWE) approaches aim to improve the Web applications development process by focusing on modeling instead of coding, and deriving the running application by transformations from conceptual models to code. The emergence of the Interaction Flow Modeling Language (IFML) has been an important milestone in the evolution of Web modeling languages, indicating not only the maturity of the field but also a final convergence of languages. In this paper we explain the evolution of modeling and design approaches since the early years (in the 90’s) detailing the forces which drove that evolution and discussing the strengths and weaknesses of some of those approaches. A brief presentation of the IFML is accompanied with a thorough analysis of the most important achievements of the MDWE community as well as the problems and obstacles that hinder the dissemination of model-driven techniques in the Web engineering field.

Preface to the CIbSE 2016 Special Issue

This special issue of the CLEI Electronic Journal consists of an invited paper on 25 years of Model-Driven Web Engineering as well as extended and revised versions of the Selected Papers presented at the XIX Ibero-American Conference on Software Engineering (CIbSE 2016).

Automated design of multi-layered web information systems

In the development of web information systems, design tasks are commonly used in approaches for Model-Driven Web Engineering (MDWE) to represent models. To generate fully implemented prototypes, these models require a rich representation of the semantics for actions (e.g., database persistence operations). In the development of some use case scenarios for the multi-layered development of web information systems, these design tasks may consume weeks of work even for experienced designers. The literature pointed out that the impossibility for executing a software project with short iterations hampers the adoption of some approaches for design in some contexts, such as start-up companies. A possible solution to introduce design tasks in short iterations is the use of automated design techniques, which assist the production of models by means of transformation tasks and refinements. This paper details our methodology for MDWE, which is supported by automated design techniques strictly associated with use case patterns of type CRUD. The novelty relies on iterations that are possible for execution with short time-scales. This is a benefit from automated design techniques not observed in MDWE approaches based on manual design tasks. We also report on previous experiences and address open questions relevant for the theory and practice of MDWE.

Mockup-Driven Development: Providing agile support for Model-Driven Web Engineering

ContextAgile software development approaches are currently becoming the industry standard for Web Application development. On the other hand, Model-Driven Web Engineering (MDWE) methodologies are known to improve productivity when building this kind of applications. However, current MDWE methodologies tend to ignore important aspects of Web Applications development supported by agile processes, such as constant customer feedback or early design of user interfaces. ObjectiveIn this paper we analyze the difficulties of supporting agile features in MDWE methodologies. Then, we propose an approach that eases the incorporation of well-known agile practices to MDWE. MethodWe propose using User Interface prototypes (usually known as mockups) as a way to start the modeling process in the context of a mixed agile-MDWE process. To assist this process, we defined a lightweight metamodel that allows modeling features over mockups, interacting with end-users and generating MDWE models. Then, we conducted a statistical evaluation of both approaches (traditional vs. mockup-based modeling). ResultsFirst we comment on how agile features can be added to MDWE processes using mockups. Then, we show by means of a quantitative study that the proposed approach is faster, less error-prone and still as complete as traditional MDWE processes. ConclusionThe use of mockups to guide the MDWE process helps in the reduction of the development cycle as well as in the incorporation of agile practices in the model-driven workflow. Complete MDWE models can be built and generated by using lightweight modeling over User Interface mockups, and this process suggests being more efficient, in terms of errors and effort, than traditional modeling in MDWE.

Editorial to the theme issue on model-driven service engineering

During the last years, Model-Driven Engineering (MDE) has started to have a direct influence in other research fields. Under the light of the premise that everything is a model, coined by Jean Bezivin in 2004 and adopted by the MDE community since then, practitioners from other areas have discovered that they were able to express their problems in terms of models and then take advantage of MDE techniques to solve them—or at least simplify them, either by increasing the level of automation or by raising the abstraction level at which solutions are planned and developed. The scope varies widely, from generic domains, likeWeb Engineering (see the previous SoSyM Theme Issue on Model-Driven Web Engineering), to more specific ones, like DB schema matching or domotics. Out of doubt, one of the areas that has more decisively benefited from MDE advances has been Service Engineering. It aims at bringing together the benefits of Service Orientation and Business Process Management, therefore making the most of Service Orientation to help organizations deliver sustainable business value with increased agility and cost effectiveness. To that end, services are widely used as software systems, and the focus is shifted to business process as

Re-engineering legacy Web applications into RIAs by aligning modernization requirements, patterns and RIA features

Rich Internet Applications (RIAs) have become a common platform for Web developments. Its adoption has been accelerated thanks to different factors, among others, the appearance of patterns for typical RIA behaviors and the extension of different Model Driven Web Engineering methodologies to introduce RIA concepts. The real fact is that more and more developers are switching to RIA technologies and, thus, the modernization of legacy Web applications into RIAs has become a trend topic. However, this modernization process lacks of a systematic approach. Currently, it is done in an ad hoc manner, being expensive and error-prone. This work presents a systematic process to modernize legacy Web applications into RIAs. The process is based on the use of traceability matrices that relate modernization requirements, RIA features and patterns. Performing some operations on these matrices, they provide the analyst with the necessary information about the suitability of a pattern or set of patterns to address a given requirement. This work also introduces two measures, the degree of requirement realization and the degree of pattern realization, which are used to discuss the pattern selection. Finally, the applicability of the approach is evaluated by using it in several Web systems.

Capturing data quality requirements for web applications by means of DQ_WebRE

The number of Web applications which are part of Business Intelligence (BI) applications has grown exponentially in recent years, as has their complexity. Consequently, the amount of data used by these applications has also increased. The larger the number of data used, the greater the chance to make errors is. That being the case, managing data with an acceptable level of quality is paramount to success in any organizational business process. In order to raise and maintain adequate levels of Data Quality (DQ), it is indispensable for Web applications to be able to satisfy specific DQ requirements. To do so, DQ requirements should be captured and introduced into the development process of the Web Application, together with the other software requirements needed in the applications. In the field of Web application development, however, there appears to us to exist a lack of proposals aimed at managing specific DQ software requirements. This paper considers the MDA (Model Driven Architecture) approach and, principally, the benefits provided by Model Driven Web Engineering (MDWE), putting forward a proposal for two artifacts. These consist of a metamodel and a UML profile for the management of Data Quality Software Requirements for Web Applications (DQ_WebRE).

Model-driven web engineering methods: a literature review

This paper presents some of the model-driven Web engineering methods that have been proposed, and discusses and analyzes the advantages and disadvantages of such methods regarding current tendencies and best practices on model-driven engineering. The idea is to present each approach and analyze the models they propose to represent Web applications, the architectural aspects in the transformations, and the use of current Web user interface technologies in the generated code. This is done in order to depict possible research lines for future works on the model-driven Web engineering area.

Quality evaluation for Model-Driven Web Engineering methodologies

ContextThere are lots of approaches or methodologies in the Model-Driven Web Engineering (MDWE) context to develop Web Applications without reaching a consensus on the use of standards and scarcity of both, practical experience and tool support. ObjectiveModel-Driven Web Engineering (MDWE) methodologies are constantly evolving. Moreover, Quality is a very important factor to identify within a methodology as it defines processes, techniques and artifacts to develop Web Applications. For this reason, when analyzing a methodology, it is not only necessary to evaluate quality, but also to find out how to improve it. The main goal of this paper is to develop a set of Quality Characteristics and Sub-Characteristics for MDWE approaches based on ISO/IEC standards. MethodFrom the software products context, some widely standards proposed, such as ISO/IEC 9126 or ISO/IEC 25000, suggest a Quality Model for software products, although up to now, there are no standard methods to assess quality on MDWE methodologies. Such methodologies can be organized into Properties, thus, a methodology has artifacts, processes and techniques. Then, each item is evaluated through a set of appropriate Quality Characteristics, depending on its nature. This paper proposes to evaluate a methodology as a product itself. ResultsThis paper recommends a set of Quality Characteristics and Sub-Characteristics based on these standards in order to evaluate MDWE methodologies quality. Additionally, it defines an agile way to relate these Quality Sub-Characteristics to Properties with the sole purpose of not only analyzing, but also assessing and improving MDWE methodologies. ConclusionsThe application of these Quality Characteristics and Sub-Characteristics could promote efficiency in methodologies since this kind of assessment enhances both the understanding of strengths and weaknesses of approaches.

A quality management based on the Quality Model life cycle

Managing quality is a hard and expensive task that involves the execution and control of processes and techniques. For a good quality management, it is important to know the current state and the objective to be achieved. It is essential to take into account with a Quality Model that specifies the purposes of managing quality. QuEF (Quality Evaluation Framework) is a framework to manage quality in MDWE (Model-driven Web Engineering). This paper suggests managing quality but pointing out the Quality Model life cycle. The purpose is to converge toward a quality continuous improvement by means of reducing effort and time.

A Framework for the Quality Evaluation of MDWE Methodologies and Information Technology Infrastructures

Diverse development web methodologies currently exist in the field of Model-Driven Web Engineering (MDWE), each of which covers different Levels of Abstraction on Model-Driven Architecture (MDA): Computation Independent Model (CIM), Platform Independent Model (PIM), Platform Specific Model (PSM), and Code. Given the high number of methodologies available, it has become necessary to define objective evaluation tools to enable development teams to improve their methodological environment and help designers of web methodologies design new effective and efficient tools, processes and techniques. Since proposals are constantly evolving, the need may arise not only to evaluate the quality but also to find out how it can be improved. This paper presents an approach named QuEF (Quality Evaluation Framework) oriented towards evaluating, through objectives measures, the quality of information technology infrastructure, mainly in MDWE methodology environments.