The rising popularity of the Internet of Things (IoT) has led to a plethora of highly heterogeneous, geographically dispersed devices. In recent years, IoT platforms have been used to provide a variety of services to applications such as device discovery, context management, and data analysis. However, the lack of standardization currently means that each IoT platform comes with its own abstractions, APIs, and interactions. As a consequence, programming the interactions between an application and an IoT platform is often time consuming, error prone, and depends on the developers’ level of knowledge about the IoT platform. To address these issues, we propose offering to application developers on the client side the possibility to declare variables that are automatically mapped to sensors and whose values are transparently updated with sensor observations. For this purpose, we introduce IoTVar, a middleware between IoT applications and platforms. In IoTVar, all the necessary interactions with IoT platforms are managed by proxies. This paper presents IoTVar integrated with the FIWARE platform, which is used for developing IoT Future Internet applications. We also report results of some experiments performed to evaluate IoTVar, showing IoTVar reduces the effort required to declare and manage IoT variables and its impact in terms of CPU, memory, and energy.
Este artigo propõe uma abordagem baseada em modelos para gerência da evolução de pointcuts em aplicações orientada a aspectos. A abordagem é centrada na definição de pointcuts com base em visões conceituais. Na abordagem os pointcuts são especificados como parte de visões do modelo conceitual e o processo é apoiado por uma ferramentas baseada em Model-Driven Architecture (MDA). Como prova de conceito, o artigo apresenta duas versões de um estudo de caso, configurando um cenário de evolução que mostra como o uso de pointcuts baseados em visões conceituais auxiliam na detecção e minimização da fragilidade de pointcuts. Para avaliação da proposta é usada o Goal/Question/Metric (GQM) juntamente com métricas para análise da eficiência na definição dos pointcuts.
On the one hand, ACME is a language designed in the late 90s as an interchange format for software architectures. The need for recon guration at runtime has led to extend the language with speci c support in Plastik. On the other hand, PDDL is a predicative language for the description of planning problems. It has been designed in the AI community for the International Planning Competition of the ICAPS conferences. Several related works have already proposed to encode software architectures into PDDL. Existing planning algorithms can then be used in order to generate automatically a plan that updates an architecture to another one, i.e., the program of a recon guration. In this paper, we improve the encoding in PDDL. Noticeably we propose how to encode ADL types and constraints in the PDDL representation. That way, we can statically check our design and express PDDL constraints in order to ensure that the generated plan never goes through any bad or inconsistent architecture, not even temporarily.