Oblivious integration of volatile functionality in web application interfaces
Web applications are used to fast and continuous evolution. In response to new or changing requirements, additional code is developed and existing one is properly modified. When new requirements are temporary, i.e., when they specify some volatile functionality that is expected to be online only for...
Guardado en:
| Publicado: |
2009
|
|---|---|
| Materias: | |
| Acceso en línea: | https://bibliotecadigital.exactas.uba.ar/collection/paper/document/paper_15409589_v8_n1_p25_Ginzburg http://hdl.handle.net/20.500.12110/paper_15409589_v8_n1_p25_Ginzburg |
| Aporte de: |
| id |
paper:paper_15409589_v8_n1_p25_Ginzburg |
|---|---|
| record_format |
dspace |
| spelling |
paper:paper_15409589_v8_n1_p25_Ginzburg2023-06-08T16:21:05Z Oblivious integration of volatile functionality in web application interfaces OOHDM Separation of concerns User interfaces Volatile functionality Web engineering Web applications are used to fast and continuous evolution. In response to new or changing requirements, additional code is developed and existing one is properly modified. When new requirements are temporary, i.e., when they specify some volatile functionality that is expected to be online only for some time and then removed, the additions and changes are destined to be later rolled back. This way to proceed, apart from being time and effort demanding, by involving the intrusive editing of the application's source code, brings along the risk of polluting it and introducing mistakes. In this paper, we present an approach to deal with volatile functionality in Web applications at the presentation level, based on oblivious composition of Web user interfaces. Our approach, which is inspired by well- known techniques for advanced separation of concerns such as aspect-oriented software design, allows to clearly separate the design of the application's core user interface from the one corresponding to more volatile functionality. Both core and volatile user interfaces are oblivious from each other and can be seamlessly composed using a transformation language. We show that in this way we simplify the application's evolution by preventing intrusive edition of the user interface code. Using some illustrative examples, we focus both on design and implementation issues, presenting an extension of the OOHDM design model that supports modular design of volatile functionality. © Rinton Press. 2009 https://bibliotecadigital.exactas.uba.ar/collection/paper/document/paper_15409589_v8_n1_p25_Ginzburg http://hdl.handle.net/20.500.12110/paper_15409589_v8_n1_p25_Ginzburg |
| 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 Separation of concerns User interfaces Volatile functionality Web engineering |
| spellingShingle |
OOHDM Separation of concerns User interfaces Volatile functionality Web engineering Oblivious integration of volatile functionality in web application interfaces |
| topic_facet |
OOHDM Separation of concerns User interfaces Volatile functionality Web engineering |
| description |
Web applications are used to fast and continuous evolution. In response to new or changing requirements, additional code is developed and existing one is properly modified. When new requirements are temporary, i.e., when they specify some volatile functionality that is expected to be online only for some time and then removed, the additions and changes are destined to be later rolled back. This way to proceed, apart from being time and effort demanding, by involving the intrusive editing of the application's source code, brings along the risk of polluting it and introducing mistakes. In this paper, we present an approach to deal with volatile functionality in Web applications at the presentation level, based on oblivious composition of Web user interfaces. Our approach, which is inspired by well- known techniques for advanced separation of concerns such as aspect-oriented software design, allows to clearly separate the design of the application's core user interface from the one corresponding to more volatile functionality. Both core and volatile user interfaces are oblivious from each other and can be seamlessly composed using a transformation language. We show that in this way we simplify the application's evolution by preventing intrusive edition of the user interface code. Using some illustrative examples, we focus both on design and implementation issues, presenting an extension of the OOHDM design model that supports modular design of volatile functionality. © Rinton Press. |
| title |
Oblivious integration of volatile functionality in web application interfaces |
| title_short |
Oblivious integration of volatile functionality in web application interfaces |
| title_full |
Oblivious integration of volatile functionality in web application interfaces |
| title_fullStr |
Oblivious integration of volatile functionality in web application interfaces |
| title_full_unstemmed |
Oblivious integration of volatile functionality in web application interfaces |
| title_sort |
oblivious integration of volatile functionality in web application interfaces |
| publishDate |
2009 |
| url |
https://bibliotecadigital.exactas.uba.ar/collection/paper/document/paper_15409589_v8_n1_p25_Ginzburg http://hdl.handle.net/20.500.12110/paper_15409589_v8_n1_p25_Ginzburg |
| _version_ |
1768546366393417728 |