Modeling, deploying, and controlling volatile functionalities in web applications

One of the main characteristics of most Web applications is their high dynamism. Once implemented and deployed for the first time, new functionalities are added to meet new or changed requirements. Some of these functionalities may appear on the Web in response to an unexpected event, or phenomena (...

Descripción completa

Guardado en:
Detalles Bibliográficos
Publicado: 2012
Materias:
Acceso en línea:https://bibliotecadigital.exactas.uba.ar/collection/paper/document/paper_02181940_v22_n1_p129_Urbieta
http://hdl.handle.net/20.500.12110/paper_02181940_v22_n1_p129_Urbieta
Aporte de:
id paper:paper_02181940_v22_n1_p129_Urbieta
record_format dspace
spelling paper:paper_02181940_v22_n1_p129_Urbieta2023-06-08T15:21:21Z Modeling, deploying, and controlling volatile functionalities in web applications OOHDM volatile concern volatile functionality Web application Web engineering OOHDM volatile concern volatile functionality WEB application Web engineering Artificial intelligence Software engineering World Wide Web One of the main characteristics of most Web applications is their high dynamism. Once implemented and deployed for the first time, new functionalities are added to meet new or changed requirements. Some of these functionalities may appear on the Web in response to an unexpected event, or phenomena (such as a natural calamity) after which they are removed. Some others are activated periodically, to coincide with a particular date, or period of the year (such as, return to school, Christmas holidays, etc.). Implementing such volatile functionalities usually impacts on a number of aspects of a Web application, including content, navigation, presentation, business processes, and user operations. Their cyclic activation/deactivation, which requires repetitive changes in the application code, may be the cause of waste of effort and application quality deterioration, up to incorrect functioning. In this paper, we present an approach to decouple the design and implementation of volatile functionalities from that of stable ones, i.e. the core functionalities of the application. The approach is instantiated in the context of the Object-Oriented Hypermedia Design Method (OOHDM), but its principles and related techniques are generally applicable to any other Web engineering method. We show how our approach enables the deployment and removal of these functionalities in a cost-effective and safe way and at runtime, thus providing business agility. A framework to classify volatile functionalities and a number of examples are also reported. © 2012 World Scientific Publishing Company. 2012 https://bibliotecadigital.exactas.uba.ar/collection/paper/document/paper_02181940_v22_n1_p129_Urbieta http://hdl.handle.net/20.500.12110/paper_02181940_v22_n1_p129_Urbieta
institution Universidad de Buenos Aires
institution_str I-28
repository_str R-134
collection Biblioteca Digital - Facultad de Ciencias Exactas y Naturales (UBA)
topic OOHDM
volatile concern
volatile functionality
Web application
Web engineering
OOHDM
volatile concern
volatile functionality
WEB application
Web engineering
Artificial intelligence
Software engineering
World Wide Web
spellingShingle OOHDM
volatile concern
volatile functionality
Web application
Web engineering
OOHDM
volatile concern
volatile functionality
WEB application
Web engineering
Artificial intelligence
Software engineering
World Wide Web
Modeling, deploying, and controlling volatile functionalities in web applications
topic_facet OOHDM
volatile concern
volatile functionality
Web application
Web engineering
OOHDM
volatile concern
volatile functionality
WEB application
Web engineering
Artificial intelligence
Software engineering
World Wide Web
description One of the main characteristics of most Web applications is their high dynamism. Once implemented and deployed for the first time, new functionalities are added to meet new or changed requirements. Some of these functionalities may appear on the Web in response to an unexpected event, or phenomena (such as a natural calamity) after which they are removed. Some others are activated periodically, to coincide with a particular date, or period of the year (such as, return to school, Christmas holidays, etc.). Implementing such volatile functionalities usually impacts on a number of aspects of a Web application, including content, navigation, presentation, business processes, and user operations. Their cyclic activation/deactivation, which requires repetitive changes in the application code, may be the cause of waste of effort and application quality deterioration, up to incorrect functioning. In this paper, we present an approach to decouple the design and implementation of volatile functionalities from that of stable ones, i.e. the core functionalities of the application. The approach is instantiated in the context of the Object-Oriented Hypermedia Design Method (OOHDM), but its principles and related techniques are generally applicable to any other Web engineering method. We show how our approach enables the deployment and removal of these functionalities in a cost-effective and safe way and at runtime, thus providing business agility. A framework to classify volatile functionalities and a number of examples are also reported. © 2012 World Scientific Publishing Company.
title Modeling, deploying, and controlling volatile functionalities in web applications
title_short Modeling, deploying, and controlling volatile functionalities in web applications
title_full Modeling, deploying, and controlling volatile functionalities in web applications
title_fullStr Modeling, deploying, and controlling volatile functionalities in web applications
title_full_unstemmed Modeling, deploying, and controlling volatile functionalities in web applications
title_sort modeling, deploying, and controlling volatile functionalities in web applications
publishDate 2012
url https://bibliotecadigital.exactas.uba.ar/collection/paper/document/paper_02181940_v22_n1_p129_Urbieta
http://hdl.handle.net/20.500.12110/paper_02181940_v22_n1_p129_Urbieta
_version_ 1768544683952177152