Alejandro RagoNational University of the Center of the Buenos Aires Province | UNICEN · Instituto de Sistemas Tandil (ISISTAN)
Alejandro Rago
PhD in Computer Science
About
20
Publications
5,936
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
114
Citations
Citations since 2017
Introduction
Additional affiliations
April 2015 - present
Position
- PostDoc Position
Description
- Funded by CONICET
October 2013 - present
Position
- Graduate Teaching Assistant
Description
- Advanced Separation of Concerns
April 2012 - September 2014
Position
- Graduate Teaching Assistant
Description
- Architecture-driven Software Development
Education
October 2010 - March 2015
October 2010 - March 2013
April 2003 - June 2009
Publications
Publications (20)
Textual requirements are very common in software projects. However, this format of requirements often keeps relevant concerns (e.g., performance, synchronization, data access, etc.) from the analyst’s view, because their semantics are implicit in the text. Thus, analysts must carefully review requirements documents in order to identify key concerns...
Developing high-quality requirements specifications often demands a thoughtful analysis and an adequate level of expertise from analysts. Although requirements modeling techniques provide mechanisms for abstraction and clarity, fostering the reuse of shared functionality (e.g., via UML relationships for use cases), they are seldom employed in pract...
Quality-attribute requirements describe constraints on the development and behavior of a software system, and their satisfaction is key for the success of a software project. Detecting and analyzing quality attributes in early development stages provides insights for system design, reduces risks, and ultimately improves the developers’ understandin...
In this article, we present a semi-automated approach for identifying candidate early aspects in requirements specifications. This approach aims at improving the precision of the aspect identification process in use cases, and also solving some problems of existing aspect mining techniques caused by the vagueness and ambiguity of text in natural la...
Software requirements are often described in natural language because they are useful to communicate and validate. Due to their focus on particular facets of a system, this kind of specifications tends to keep relevant concerns (also known as early aspects) from the analysts’ view. These concerns are known as crosscutting concerns because they appe...
Engineering activities often produce considerable documentation as a by-product of the development process. Due to their complexity, technical analysts can benefit from text processing techniques able to identify concepts of interest and analyze deficiencies of the documents in an automated fashion. In practice, text sentences from the documentatio...
A key challenge of software architecture design is how to satisfy quality-attribute requirements, which often conflict with each other. This is usually a complex task, because there are several candidates for architectural solutions meeting the same requirements, and quality-attribute tradeoffs of those solutions need to be considered by the archit...
This work presents a semi-automatic tool for use case refactoring called RE-USE. This tool discovers existing quality problems in use cases and suggests a prioritized set of candidate refactorings to functional analysts. The analyst then reviews the recommendation list and selects the most important refactoring. The tool applies the chosen refactor...
This poster was presented in the 2nd School of International Joint Conference on Artificial Intelligence (IJCAI’14), co-located with the Argentine Symposium on Artificial Intelligence held at Jornadas Argentinas de Computación e Investigación Operativa (JAIIO’14)
The architecture of a software system is often described with diagrams embedded in the documentation. However, these diagrams are normally stored and shared as images, losing track of model-level architectural information and refraining software engineers from working on the architectural model later on. In this context, tools able to extract archi...
This zip contains a dataset of architectural views encoded as images collected from several software systems. The dataset was used in the paper submitted to JAIIO'14 for evaluating IMEAV (Image Extractor for Architectural Views), a tool capable of identifying the underlying model of architectural views "frozen" in static images and able to persist...
The inspection of documents written in natural language with computers has become feasible thanks to the advances in Natural Language Processing (NLP) techniques. However, certain applications require a deeper semantic analysis of the text to produce good results. In this article, we present an exploratory study of semantic-aware NLP techniques for...
This zip contains files from CRS and HWS case-studies. MSLite files are not included because project details cannot be disclosed due to confidentiality issues.
Llevar a cabo las actividades de captura y modelamiento de requerimientos no es una tarea sencilla. Ésta requiere realizar un análisis profundo de las necesidades de los clientes y demanda cierto grado de experiencia de los analistas. Para comunicar satisfactoriamente los requerimientos, se deben aprovechar los instrumentos provistos por las técnic...
Recent trends in the software engineering community advocate for the improvement of textual requirements using (semi-)automated tools. In particular, the detection of incomplete or understated concerns at early development stages hold potential, due to the negative eects of untreated concerns on the development. Assistive tools can be of great help...
Specifying good software requirement documents is a difficult task. Many software projects fail because of the omission or bad en-capsulation of concerns. A practical way to solve these problems is to use advanced separation of concern techniques, such as aspect-orientation. However, quality attributes are not completely addressed by them. In this...
Mediante el uso de aspectos es posible encapsular crosscutting concerns (CCC) que atraviesan ortogonalmente los componentes de un sistema. Incorporarlos desde etapas tempranas del desarrollo de software conlleva importantes ventajas, tales como: mejorar la trazabilidad, facilitar las estimaciones de impacto de cambio, reducir los costos de la evolu...
El Desarrollo de Software Orientado a Aspectos (DSOA) provee medios sistemáticos para la identificación, modularización, representación y composición de crosscutting concerns en unidades denominadas aspectos. La ingeniería de requerimientos orientada a aspectos intenta identificar los posibles aspectos desde las primeras etapas del ciclo de vida de...
Este trabajo presenta una técnica de identificación de aspectos candidatos dada la especificación de requerimientos. Dicha técnica fue desarrollada con el objetivo de solucionar los problemas de las propuestas ya existentes, mejorando principalmente la precisión de la identificación. El proceso propuesto define una técnica automatizada que resuelve...
Projects
Projects (2)
The main purpose of this cooperation project is to transfer knowledge between the Argentine and German groups and to capitalize on research synergies, in order to investigate new semi-automated techniques for managing quality-attribute tradeoffs in software design optimizations. In particular, this joint proposal relies on 4 aspects, namely: i) the distribution of search capabilities, ii) the modular division of design knowledge, iii) the incorporation of user preferences and uncertainty in the search process, and iv) the application of negotiation protocols for quality-attribute tradeoffs. We believe that the combined effect of these aspects, still little explored in the literature, can improve the global design exploration performed by the user.
El objetivo general de la propuesta es la integración de los enfoques, técnicas y herramientas desarrolladas en forma separada por ambos grupos (ISISTAN-UNICEN, PUC-Rio), en pos de lograr recomendaciones más efectivas de anomalías de código.
