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

2016 ◽  
Author(s):  
Gustavo Rossi ◽  
Matias Urbieta ◽  
Damiano Distante ◽  
Jose Matias Rivero ◽  
Sergio Firmenich
Keyword(s):  
Development Process ◽  
Web Applications ◽  
Conceptual Models ◽  
Early Years ◽  
Modeling Languages ◽  
Flow Modeling ◽  
Web Engineering ◽  
Model Driven ◽  
The Web ◽  
Important Milestone

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.

Task Modelling for the Web (Aufgabenmodellierung für interaktive Webanwendungen)

i-com ◽  
2008 ◽  
Vol 6 (3/2007) ◽  
pp. 23-29 ◽  
Author(s):  
Birgit Bomsdorf
Keyword(s):  
Task Performance ◽  
Web Application ◽  
Development Process ◽  
Web Applications ◽  
Web Engineering ◽  
Time Usage ◽  
Build Time ◽  
Object Models ◽  
The Web ◽  
Modelling Approach

SummaryTask modelling has entered the development process of web applications, strengthening the usage-centred view within the early steps in Web-Engineering (WE). In current approaches, however, this view is not kept up during subsequent activities to the same degree as this is the case in the field of Human-Computer-Interaction (HCI). The modelling approach presented in this contribution combines models as known from WE with models used in HCI to change this situation. Basically the WE-HCI-integration is supported by combining task and object models as known from HCI with conceptual modelling known from WE. In this paper, the main focus is on the WebTaskModel, a task model adapted to web application concerns, and its contribution towards a task-related web user interface. The main difference to existing task models is the build-time and run-time usage of a generic task lifecycle. Hereby the description of exceptions and erroneous situations during task performance (caused by, e.g., the stateless protocol or Browser interaction) is enabled and at the same time clearly separated from the flow of correct action.

scholarly journals A Pattern-Based Development Approach for Interaction Flow Modeling Language

2019 ◽  
Vol 2019 ◽  
pp. 1-15 ◽  
Author(s):  
Roberto Rodriguez-Echeverria ◽  
Juan C. Preciado ◽  
Álvaro Rubio-Largo ◽  
José M. Conejero ◽  
Álvaro E. Prieto
Keyword(s):  
Web Application ◽  
Web Applications ◽  
Modeling Language ◽  
Flow Modeling ◽  
Application Development ◽  
Web Engineering ◽  
Productivity Improvement ◽  
Model Driven ◽  
Key Factor ◽  
Development Approach

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.

scholarly journals Extensibility Interaction Flow Modeling Language Metamodels to Develop New Web Application Concerns

2017 ◽  
Vol 2 (3) ◽  
pp. 172-177 ◽  
Author(s):  
Karzan Wakil ◽  
Dayang N.A. Jawawi
Keyword(s):  
User Interface ◽  
Web Application ◽  
Web Applications ◽  
Systematic Approach ◽  
Modeling Language ◽  
Flow Modeling ◽  
Web Engineering ◽  
New Model ◽  
New Models ◽  
The Web

Web engineering is a systematic approach to develop web applications, and numerous web engineering methods have been proposed. These methods were extended through defining new models by using different mechanisms to capture the web application concepts. Due to the complexity rising of web applications, the web engineering methods cannot provide web solutions anymore. Even though Interaction Flow Modeling Language (IFML) is recently proposed as a new method for developing web applications, it has limitations. Therefore these methods need to be improved. In this paper, we present the ability of IFML extensibility to support new concerns from web applications. Moreover, we extend IFML through UML mechanisms to support new concerns from the context to the user interface. The new IFML solves the lack of context web application through defining a new model and becomes a new direction to develop concerns modern web applications.

Focused Requirements Engineering Method for Web Application Development

2010 ◽  
pp. 1537-1545
Author(s):  
Ala M. Abu-Samaha ◽  
Lana S. Al-Salem
Keyword(s):  
Requirements Engineering ◽  
System Application ◽  
Business Strategy ◽  
Web Application ◽  
Web Applications ◽  
Application Development ◽  
Web Engineering ◽  
Business Objectives ◽  
Application Requirements ◽  
The Web

The requirements phase of the system/application development process typically involves the activities of requirements elicitation, analysis, validation, and specification. The main goal of such a process is “to develop a requirements speci- fication document which defines the system to be procured and which can act as a basis for the system design” (Sawyer, Sommerville, & Viller, 1996). Hence the underpinning assumption of the requirements engineering (RE) process is to transform the operational needs of an organisation into complete, consistent, and unambiguous system/application specifications through an iterative process of definition and validation (Pohl ,1994). The Web engineering (WE) literature provides a limited number of methods and techniques that can be used to manage the RE process in a Web development context [e3-value framework (Gordijn, Akkermans, & van Vliet, 2000), SOARE approach (Bleistein, Aurum, Cox, & Ray, 2004), e-prototyping (Bleek, Jeenicke, & Klischewski, 2002), AWARE (Bolchini & Paolini, 2004), and SSM/ICDT (Meldrum & Rose, 2004)]. Despite the availability of such a limited number of Web requirements engineering (WRE) methods, many researchers criticised such methods for their failure to address the necessity to align the Web application’ requirements to the organisation’s business strategy. Hence, the recommendation of many researchers (Al-Salem & Abu- Samaha, 2005a; Bleistein 2005; Bleistein, Cox, & Verner, 2004; Vidgen, Avison, Wood, & Wood-Harper, 2002) is to utilise a general WRE framework for the development of Web applications that can align the application’s requirements to the organisation’s business needs and its future vision. The objective of such a WRE framework is to incorporate the elicitation/analysis of business strategy as part of the application’s RE process. This chapter presents a WRE method that extends Sommerville and Kotonya’s viewpoint-oriented requirements definition (VORD) and Kaplan and Norton’s balanced scorecard (BSC) to elicit the Web application’ requirements and to plan/analyze the business strategy, respectively. In addition, eWARE (extended Web application requirements engineering) deploys the concept of “requirements alignment” to attain business objectives during the requirements discovery, elicitation, and formalisation process to identify the services of the Web application that will achieve the business objectives in order to improve the organisation’s profitability and competitiveness. The chapter is organised into a number of sections. The second section of this chapter provides a background to Web applications in terms of defi- nition and differentiating characteristics. The third section provides a discussion of eWARE method in terms of phases and activities. This section is divided into two subsections to cover the activities of the two prominent phases of the eWARE process in more detail. The fourth and fifth sections provide a discussion of possible future trends in WRE and a number of concluding remarks.

Context-Aware Applications for the Web

2011 ◽  
pp. 417-440
Author(s):  
Florian Daniel
Keyword(s):  
Context Awareness ◽  
Web Applications ◽  
User Profile ◽  
Expressive Power ◽  
Context Aware ◽  
Web Engineering ◽  
Runtime Adaptation ◽  
Model Driven ◽  
Context Data ◽  
Development Approach

Adaptivity (the runtime adaptation to user profile data) and context-awareness (the runtime adaptation to generic context data) have been gaining momentum in the field of Web engineering over the last years, especially in response to the ever growing demand for highly personalized services and applications coming from end users. Developing context-aware and adaptive Web applications requires addressing a few design concerns that are proper of such kind of applications and independent of the chosen modeling paradigm or programming language. In this chapter we characterize the design of context-aware Web applications, the authors describe a conceptual, model-driven development approach, and they show how the peculiarities of context-awareness require augmenting the expressive power of conceptual models in order to be able to express adaptive application behaviors.

Context-Aware Applications for the Web

2010 ◽  
pp. 59-82 ◽  
Author(s):  
Florian Daniel
Keyword(s):  
Context Awareness ◽  
Web Applications ◽  
User Profile ◽  
Context Aware ◽  
Web Engineering ◽  
Runtime Adaptation ◽  
Model Driven ◽  
Personalized Services ◽  
Context Data ◽  
Development Approach

Adaptivity (the runtime adaptation to user profile data) and context-awareness (the runtime adaptation to generic context data) have been gaining momentum in the field of Web engineering over the last years, especially in response to the ever growing demand for highly personalized services and applications coming from end users. Developing context-aware and adaptive Web applications requires addressing a few design concerns that are proper of such kind of applications and independent of the chosen modeling paradigm or programming language. In this chapter we characterize the design of context-aware Web applications, the authors describe a conceptual, model-driven development approach, and they show how the peculiarities of context-awareness require augmenting the expressivepower of conceptual models in order to be able to express adaptive application behaviors.

Modeling Content Quality for the Web 2.0 and Follow-on Applications

2010 ◽  
pp. 371-386 ◽  
Author(s):  
Roberto Sassano ◽  
Luis Olsina ◽  
Luisa Mich
Keyword(s):  
Web Sites ◽  
Web Application ◽  
Web Applications ◽  
Integrated Approach ◽  
Web Engineering ◽  
Quality Requirements ◽  
Content Quality ◽  
The Web ◽  
Quality In Use

The consistent modeling of quality requirements for Web sites and applications at different stages of the life cycle is still a challenge to most Web engineering researchers and practitioners. In the present chapter, we propose an integrated approach to specify quality requirements to Web sites and applications. By extending the ISO 9126-1 quality views characteristics, we discuss how to model internal, external quality, and quality in use views taking into account not only the software features, but also the own characteristics of Web applications. Particularly, we thoroughly analyze the modeling of the content characteristic for evaluating the quality of information–so critical for the whole Web application eras. The resulting model represents a first step towards a multi-dimensional integrated approach to evaluate Web sites at different lifecycle stages.

ANALISIS KEMAMPUAN WEBRATIO UNTUK PENGEMBANGAN APLIKASI WEB MENGGUNAKAN INTERACTION FLOW MODELING LANGUAGE (IFML)

2020 ◽  
Vol 3 (2) ◽  
Author(s):  
Joe Lian Min
Keyword(s):  
Web Applications ◽  
Transformation Process ◽  
Modeling Language ◽  
Modeling Languages ◽  
Functional Requirements ◽  
Application Development ◽  
Model Driven ◽  
Measurement Results ◽  
Mdd Method

The model-driven development (MDD) method is a method that can accelerate the application development process. With this method, the model can be immediately transformed into an executable application. Model-driven architecture is one kind of MDD approaches. MDA has a standard modeling language that is used to facilitate the transformation process. One of the modeling languages in MDA is Interaction Flow Management Language (IFML). IFML models an application based on the interaction flow and interface of the application. This paper explains the capabilities of WebRatio in developing Web applications and their effectiveness. The effectiveness is calculated from the effort required for the development. On the other side, the effort is calculated from the line of code (LOC) generated from the model. The experiment's case study is a  simple web-shop application, with some functional and non-functional requirements. The measurement results show that to develop a web-shop, the effort required is quite efficient, only 13% of the total application. However, another study still needs to be done because many variables affect the productivity of application development.

Tool to Support the Design Methdology

2009 ◽  
pp. 253-286
Author(s):  
Roberto Paiano ◽  
Anna Lisa Guido ◽  
Andrea Pandurino
Keyword(s):  
Code Generation ◽  
Web Application ◽  
Business Processes ◽  
Web Applications ◽  
Model Driven ◽  
Design And Implementation ◽  
Intrinsic Complexity ◽  
Automatic Code ◽  
Machine Readable ◽  
The Web

As it will be clearer subsequently, two different technologies will be used for realizing the generation of the code; the first one predominantly focused on the generation of code for the Web applications that do not have an underlying business process, and that they do not require, therefore, the management of the relative problems. The second technology has been selected instead, to also keep in mind the business processes. In order to provide support to the designer in the design of the whole complex Web information system, it is essential to provide a suitable tool that hides the intrinsic complexity of the methodology supporting the designer in the application of the same that is often complex, and the tool has to be able to translate the design made up in a machine readable format to be able to use this design in the following automatic code generation of the Web application according to a model-driven approach. In this chapter, we introduce the design and implementation of the editor made up mainly of the architecture presented (and based on Eclipse™ Platform as illustrated in the preceding chapter) and on the methodological steps of integration among the several editors for the design and implementation of these guidelines.

The Use of Metamodels in Web Requirements to Assure the Consistence

2011 ◽  
pp. 363-377
Author(s):  
M.J. Escalona ◽  
G. Aragón
Keyword(s):  
Development Process ◽  
Methodological Approach ◽  
Model Driven Engineering ◽  
Quality Of Results ◽  
Model Driven ◽  
Critical Phase ◽  
Methodological Approaches ◽  
The Many ◽  
The Web

The increasing complexity and the many different aspects that should be treated at the same time require flexible but powerful methodologies to support the development process. Every day, the requirements treatment in Web environments is becoming a more critical phase because developers need suitable methods to capture, define, and validate requirements. However, it is very important that these methods assure the quality of these requirements. The model-driven engineering is opening a new way to define methodological approaches that allow control and relate concepts that have to be treated. This chapter presents a Web methodological approach to deal with requirements, NDT (navigational development techniques) based on model-driven engineering. As it is presented, NDT proposes a set of procedures, techniques, and models to assure the quality of results in the Web requirements treatment.

Sign in / Sign up

Export Citation Format

Share Document