Incremental compilation and deployment for OutSystems Platform

OutSystems Platform is used to develop, deploy, and maintain enterprise web an mobile web applications. Applications are developed through a visual domain specific language, in an integrated development environment, and compiled to a standard stack of web technologies. In the platform’s core, there is a compiler and a deployment service that transform the visual model into a running web application. As applications grow, compilation and deployment times increase as well, impacting the developer’s productivity. In the previous model, a full application was the only compilation and deployment unit. When the developer published an application, even if he only changed a very small aspect of it, the application would be fully compiled and deployed. Our goal is to reduce compilation and deployment times for the most common use case, in which the developer performs small changes to an application before compiling and deploying it. We modified the OutSystems Platform to support a new incremental compilation and deployment model that reuses previous computations as much as possible in order to improve performance. In our approach, the full application is broken down into smaller compilation and deployment units, increasing what can be cached and reused. We also observed that this finer model would benefit from a parallel execution model. Hereby, we created a task driven Scheduler that executes compilation and deployment tasks in parallel. Our benchmarks show a substantial improvement of the compilation and deployment process times for the aforementioned development scenario.

User-centric product derivation in software product lines

Software Product Line (SPL) engineering aims at achieving efficient development of software products in a specific domain. New products are obtained via a process which entails creating a new configuration specifying the desired product’s features. This configuration must necessarily conform to a variability model, that describes the scope of the SPL, or else it is not viable. To ensure this, configuration tools are used that do not allow invalid configurations to be expressed. A different concern, however, is making sure that a product addresses the stakeholders’ needs as best as possible. The stakeholders may not be experts on the domain, so they may have unrealistic expectations. Also, the scope of the SPL is determined not only by the domain but also by limitations of the development platforms. It is therefore possible that the desired set of features goes beyond what is possible to currently create with the SPL. This means that configuration tools should provide support not only for creating valid products, but also for improving satisfaction of user concerns. We address this goal by providing a user-centric configuration process that offers suggestions during the configuration process, based on the use of soft constraints, and identifying and explaining potential conflicts that may arise. Suggestions help mitigating stakeholder uncertainty and poor domain knowledge, by helping them address well known and desirable domain-related concerns. On the other hand, automated conflict identification and explanation helps the stakeholders to understand the trade-offs required for realizing their vision, allowing informed resolution of conflicts. Additionally, we propose a prototype-based approach to configuration, that addresses the order-dependency issues by allowing the complete (or partial) specification of the features in a single step. A subsequent resolution process will then identify possible repairs, or trade-offs, that may be required for viabilization.

Proposta de um modelo de medição e análise da satisfação de clientes em empresas de software : caso prático do ambiente business-to-business

Os estudos da satisfação e lealdade do cliente em ambiente Business-to-Business têm emergido devido ao interesse práctico e académico. Recorreu-se a um caso práctico de uma empresa de software internacional, ESRI, a operar em Portugal com modelo de negócio B2B e comportamento de compra extensivo. Desenvolveu-se um modelo estrutural com 11 variáveis latentes: lealdade; satisfação; imagem; atmosfera; cooperação; adaptação; processos; tecnologia; orientação ao cliente; competências; colaboradores e comunicação. Foram analisadas 304 respostas ao questionário de satisfação e de seguida aplicou-se o modelo a seis grupos de clientes segmentados de acordo com a contribuição do cliente para as receitas e o comportamento no processo de decisão de compra. Recorreu-se a modelos SEM (Structural Equation Modelling) com estimação dos parâmetros através da metodologia PLS (partial Least Squares). Os resultados mostram nos seis segmentos, que os valores da empresa, a cooperação através da competência dos colaboradores e da orientação ao cliente e a tecnologia são factores mais importantes para a satisfação e lealdade dos clientes.