Leandro Antonelli 0001

dblp:15/4063 · also Leandro R. Antonelli · DBLP profile ↗
← Back
11ranked-venue papers
4as first author
4since 2021 · last 2023
0000-0003-1388-0337ORCID · verified

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 8 · 3 first-author · 2 since 2021Applied, interdisciplinary, general and emerging computing · 2 · 1 first-author · 1 since 2021Artificial intelligence and machine learning · 1Databases, data management, data science and information retrieval · 1Graphics, computer vision, multimedia, augmented reality and games · 1 · 1 since 2021
YearPublicationVenuePosition
2023 Multidimensional modeling driven from a domain language
Leandro Antonelli 0001, Sandro Bimonte, Stefano Rizzi
Autom. Softw. Eng.1
2023 Development iterations based on web augmentation and context tasks
Lucy Gutierrez Marticorena, Leonardo Morales, Leandro Antonelli 0001, Gustavo Rossi, Diego Firmenich
Multim. Tools Appl.3
2022 Tracing User Stories and Source Code Using the Language Extended Lexicon
Matias Urbieta, Leandro Antonelli 0001, Javier Guerra, Gustavo Rossi
WorldCIST (2)2
2021 Requirements-driven data warehouse design based on enhanced pivot tables
Sandro Bimonte, Leandro Antonelli 0001, Stefano Rizzi
Requir. Eng.2
2020 The impact of using a domain language for an agile requirements management
Matias Urbieta, Leandro Antonelli 0001, Gustavo Rossi, Julio César Sampaio do Prado Leite
Inf. Softw. Technol.2
2019 Semantic Support for Scenarios to Improve Communication in Agribusiness
Leandro Antonelli 0001, Diego Torres, Mariángeles Hozikian, Jorge Esteban Hernández Hormazabal
PRO-VE1
2018 Conflict Management in the Collaborative Description of a Domain Language (S)
abstract
The identification and specification of the requirements of a software system is a difficult task that has the goal of obtaining requirements as correct and complete as possible.It is extremely important that Requirements Engineers understand a domain language in order to write high-quality requirements.Moreover, they must describe (and discuss) the language in a collaborative way in order to consider the different points of view of all stakeholders to assure that the resulting requirements will have more chances to meet their needs.However, collaborative construction implies the occurrence of conflicts that are unavoidable because of ambiguity, overlapping and misunderstanding natural language descriptions.This article relies on the Language Extended Lexicon in order to describe the application domain.Although it is a semi-structured glossary and this characteristic helps to reduce the conflicts, our experience shows that conflicts arise anyway.Thus, in order to mitigate this problem, this article presents a catalogue with a set of conflicts that could appear during a collaborative construction of the Language Extended Lexicon and proposes alternatives for their resolution.
Claudia S. Litvak, Gustavo Rossi, Leandro Antonelli 0001
SEKE3
2018 CrowdMock: an approach for defining and evolving web augmentation requirements
Diego Firmenich, Sergio Firmenich, José Matías Rivero, Leandro Antonelli 0001, Gustavo Rossi
Requir. Eng.4
2015 Early identification of crosscutting concerns with the Language Extended Lexicon
Leandro Antonelli 0001, Gustavo Rossi, Julio César Sampaio do Prado Leite, João Araújo 0001
Requir. Eng.1
2014 A Platform for Web Augmentation Requirements Specification
Diego Firmenich, Sergio Firmenich, José Matías Rivero, Leandro Antonelli 0001
ICWE4
2014 Language Extended Lexicon points: Estimating the size of an application using its language
abstract
Estimating the size of a software system is a critical task due to the implications the estimation has in the management of the development project. There are some widely accepted estimation techniques: Function Points, Use Case Points and Cosmic Points, but these techniques can only be applied after the availability of a requirements specification. In this paper, we propose an approach to estimate the size of an application previous to its requirements specification by using the application language itself, captured by the Language Extended Lexicon (LEL). Our approach is based on Use Case Points and on a technique which derives Use Cases from the LEL. The proposed approach provides a measure of the application's size earlier than the usual techniques, thus reducing the effort needed to apply them. An initial experiment was conducted to evaluate the proposal.
Leandro Antonelli 0001, Gustavo Rossi, Julio César Sampaio do Prado Leite, Alejandro Oliveros
RE1