Search

Decision making in agriculture increasingly relies on software, for example to gather important information or to weight alternatives. Information systems innovation in agriculture is a challenging and very active area. Existing software products, frequently implemented as web applications, are found to lack functionality, for example to support collaboration. Augmenting the web is a widely adopted technique for enhancing existing applications with new features which are not available out-of-the-shelf. Design thinking has proven to be an effective tool to support innovation on many domains. Collaboration Engineering is an effective means to reuse design experience of collaboration strategies. This work presents an approach to involve end-users in enhancing exiting web software to produce incremental innovations. The approach relies on Design Thinking, Web Augmentation and Collaboration Engineering. The approach was successfully tried in a case study letting end-users add collaboration support to a system that did not provide it. Laboratorio de Investigación y Formación en Informática Avanzada

Mobile applications changed unexpectedly people life and business models around the world. Nevertheless, there are old applications, called legacies, without adaptation to mobile devices, because this adaptation or migration have a considerable cost in dependence of software scope. Currently, most users bring constantly their smartphones and other devices with them, especially millennials. For that reason, some approaches try to solve this portabilization, generating certain improvements. However, in the majority of these solutions there is not a direct participation of users; do not consider their visual identity, analysis of feeling or mining of opinion. This paper proposes getting the behavior web application model with Markov heuristics from the widgets closeness matrix, prior to adaptation in order to include the user logic. Ponencia presentada en: 7th World Conference on Information Systems and Technologies, WorldCist'19 (España, abril de 2019). Laboratorio de Investigación y Formación en Informática Avanzada

Web applications must quickly adapt to new business demands to keep clients onboard. When unexpected and unforeseen requirements appear, the changes pose challenges to software engineers as they were not considered in the application design and such new functionality can be only valid only for a period in certain situations. This work presents a comparison of maintenance consequences in the software quality when using a Model-Driven approach against a Code-Based one where changes are managed in an ad hoc way. We used the removal of volatile functionality as case of study due to the fact that its characteristics stress the development process. We considered both external and internal quality of deliverables. For assessing the quality of deliverables, we evaluated the production of more than 35 students using both approaches considering their perception gathered through questionnaires and their deliverables. We present the preliminary evidence that there is no significant difference between approaches. Model-Driven performed slightly better than Code-Based, but both responded negatively in terms of deliverables' quality. Results show that maintenance tasks are detrimental to software quality where Model-Driven approach does not excel over Code-Based approach. The Model-Driven approach only highlighted on productivity. Fil: Urbieta, Mario Matías. Consejo Nacional de Investigaciones Científicas y Técnicas; Argentina. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina Fil: Frajberg, Darian. Politecnico di Milano; Italia. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina Fil: Rossi, Gustavo Héctor. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina. Consejo Nacional de Investigaciones Científicas y Técnicas; Argentina

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 (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 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., Laboratorio de Investigación y Formación en Informática Avanzada (LIFIA)

La popularidad y facilidad de acceso de las aplicaciones Web expone a una aplicación Web a exigencias de nuevas características realizadas por sus usuarios que ésta debe proveer para mantener cautivo al usuario implantando un estado de constante evolución. La evolución requiere usualmente modificaciones de funcionalidad existente o nueva funcionalidad para mejorar la experiencia del usuario en la aplicación Web. Muchas veces estos cambios son requeridos para mantener vigente a la aplicación, es decir acompañar a las tendencias del mercado. Los cambios introducidos pueden corresponder a un tipo de funcionalidad llamado volátil caracterizado por ser temporal, surgir de improviso y muchas veces por deber ser incorporada a la brevedad. Cuando esta funcionalidad es temporal, se incorpora al sistema para luego ser retirada de forma planificada en base a una fecha determinada o de forma espontanea en base a un evento de negocio. En este escenario, entre otras variables, se ve comprometida la mantenibilidad y estabilidad de la aplicación. Por otro lado, su inesperado surgimiento usualmente no permite una adopción fácil y económica ya que la aplicación no fue diseñada teniendo en cuenta esta nueva funcionalidad. En esta tesis se presenta una metodología modular para dar solución a los requerimientos volátiles en aplicaciones Web. La metodología abordará el problema desde las etapas análisis brindando herramientas conceptuales para su adecuado diseño y posterior implementación. Es modular ya que puede complementar las metodologías de ingeniería Web más maduras; en esta tesis se utilizara como metodología de referencia OOHDM. En la etapa de análisis de requerimientos, se proveerán herramientas que permitan identificar, aislar, y gestionar inconsistencias de requerimientos volátiles. Para las tareas de diseño se proveerán herramientas teóricas que faciliten el modelado de los requerimientos de las aplicaciones Web brindando instrumentos para los diferentes modelos involucrados: conceptual, navegacional, y de interfaz. Finalmente, se proveerá una guía de implementación de éste tipo de funcionalidad con un análisis comparativo con la implementación de funcionalidad volátil ad-hoc., Facultad de Informática

Workflow plays a major role in nowadays business and therefore its requirement elicitation must be accurate and clear for achieving the solution closest to business’s needs. Due to Web applications popularity, the Web is becoming the standard platform for implementing business workflows. In this context, Web applications and their workflows must be adapted to market demands in such a way that time and effort are minimize. As they get more popular, they must give support to different functional requirements but also they contain tangled and scattered behaviour. In this work we present a model-driven approach for modelling workflows using a Domain Specific Language for Web application requirement called WebSpec. We present an extension to WebSpec based on Pattern Specifications for modelling crosscutting workflow requirements identifying tangled and scattered behaviour and reducing inconsistencies early in the cycle.