|
|
|
|
| LEADER |
00000naa a2200000 a 4500 |
| 003 |
AR-LpUFIB |
| 005 |
20250423183228.0 |
| 008 |
230201s2016 xx o 000 0 eng d |
| 024 |
8 |
|
|a DIF-M7774
|b 7992
|z DIF007103
|
| 040 |
|
|
|a AR-LpUFIB
|b spa
|c AR-LpUFIB
|
| 100 |
1 |
|
|a Firmenich, Diego
|9 49681
|
| 245 |
1 |
0 |
|a CrowdMock :
|b an approach for defining and evolving web augmentation requirements
|
| 300 |
|
|
|a 1 archivo (6,3 MB)
|
| 500 |
|
|
|a Formato de archivo PDF. -- Este documento es producción intelectual de la Facultad de Informática - UNLP (Colección BIPA/Biblioteca)
|
| 520 |
|
|
|a Web Applications are accessed by millions of users with different needs, goals, concerns or preferences. Several well-known Web Applications provide personalized features, e.g. they recommend specific content to users by contemplating individual characteristics or requirements. However, since most Web Application cannot consider all users? requirements, many developers started to create their own mechanisms for adapting existing applications. One of the most popular techniques for third party applications adaptation is Web Augmentation, which is based on the alteration of its original user interface, generally by using scripts running at the client-side (e.g. the browser). In the context of Web Augmentation, two user roles have emerged: scripters who are those users able to create a new augmentation artefact, and end-users without programming skills, that just consume the artefacts that may satisfy totally or partially their needs. Scripters and end-users generally do not know each other and they have rarely a contact, beyond the fact that they use the same script repositories. When end-users cannot get their needs covered with existing artefacts, they claim for new ones by specifying their requirements (called Web Augmentation requirements) using textual descriptions, which are usually hard to interpret by scripters. Web Augmentation requirements are a very particular kind of Web requirements for which there partially exist a solution implemented by the Web site owner, but still users need to change or augment that implementation with very specific purposes that they desire to be available in such site. In this paper, we propose an approach for defining and evolving Web Augmentation requirements using rich visual prototypes and textual descriptions that can be automatically mapped onto running software artefacts. We present a tool implemented to support this approach and we show an evaluation of both the approach and the tool.
|
| 534 |
|
|
|a Requirements Engineering, 23(1), pp. 33-61.
|
| 650 |
|
4 |
|a INGENIERÍA DE REQUERIMIENTOS
|9 48824
|
| 650 |
|
4 |
|a APLICACIONES WEB
|9 44733
|
| 700 |
1 |
|
|a Firmenich, Sergio Damián
|9 46161
|
| 700 |
1 |
|
|a Rivero, José Matías
|9 46758
|
| 700 |
1 |
|
|a Antonelli, Rubén Leandro
|9 44748
|
| 700 |
1 |
|
|a Rossi, Gustavo Héctor
|9 44094
|
| 856 |
4 |
0 |
|u http://dx.doi.org/10.1007/s00766-016-0257-3
|
| 942 |
|
|
|c CP
|
| 952 |
|
|
|0 0
|1 0
|4 0
|6 A0930
|7 3
|8 BD
|9 82349
|a DIF
|b DIF
|d 2025-03-11
|l 0
|o A0930
|r 2025-03-11 17:04:53
|u http://catalogo.info.unlp.edu.ar/meran/getDocument.pl?id=1675
|w 2025-03-11
|y CP
|
| 999 |
|
|
|c 56878
|d 56878
|
