Universal Resource Lifecycle Management

This paper presents a model and a tool that allows Web users to define, execute, and manage lifecycles for any artifact available on the Web. In the paper we show the need for lifecycle management of Web artifacts, and we show in particular why it is important that non-programmers are also able to do this. We then discuss why current models do not allow this, and we present a model and a system implementation that achieves lifecycle management for any URI-identifiable and accessible object. The most challenging parts of the work lie in the definition of a simple but universal model and system (and in particular in allowing universality and simplicity to coexist) and in the ability to hide from the lifecycle modeler the complexity intrinsic in having to access and manage a variety of resources, which differ in nature, in the operations that are allowed on them, and in the protocols and data formats required to access them

Taming the interoperability challenges of complex IoT systems

of communication protocols and data formats; hence ensuring diverse devices can interoperate with one another remains a significant challenge. Model-driven development and testing solutions have been proposed as methods to aid software developers achieve interoperability compliance in the face of this increasing complexity. However, current approaches often involve complicated and domain specific models (e.g. web services described by WSDL). In this paper, we explore a lightweight, middleware independent, model-driven development framework to help developers tame the challenges of composing IoT services that interoperate with one another. The framework is based upon two key contributions: i) patterns of interoperability behaviour, and ii) a software framework to monitor and reason about interoperability success or failure. We show using a case-study from the FI-WARE Future Internet Service domain that this interoperability framework can support non-expert developers address interoperability challenges. We also deployed tools built atop the framework and made them available in the XIFI large-scale FI-PPP test environment

CYCLONE Unified Deployment and Management of Federated, Multi-Cloud Applications

Various Cloud layers have to work in concert in order to manage and deploy complex multi-cloud applications, executing sophisticated workflows for Cloud resource deployment, activation, adjustment, interaction, and monitoring. While there are ample solutions for managing individual Cloud aspects (e.g. network controllers, deployment tools, and application security software), there are no well-integrated suites for managing an entire multi cloud environment with multiple providers and deployment models. This paper presents the CYCLONE architecture that integrates a number of existing solutions to create an open, unified, holistic Cloud management platform for multi-cloud applications, tailored to the needs of research organizations and SMEs. It discusses major challenges in providing a network and security infrastructure for the Intercloud and concludes with the demonstration how the architecture is implemented in a real life bioinformatics use case

Enabling Communication Technologies for Automated Unmanned Vehicles in Industry 4.0

Within the context of Industry 4.0, mobile robot systems such as automated guided vehicles (AGVs) and unmanned aerial vehicles (UAVs) are one of the major areas challenging current communication and localization technologies. Due to stringent requirements on latency and reliability, several of the existing solutions are not capable of meeting the performance required by industrial automation applications. Additionally, the disparity in types and applications of unmanned vehicle (UV) calls for more flexible communication technologies in order to address their specific requirements. In this paper, we propose several use cases for UVs within the context of Industry 4.0 and consider their respective requirements. We also identify wireless technologies that support the deployment of UVs as envisioned in Industry 4.0 scenarios.Comment: 7 pages, 1 figure, 1 tabl

Model-driven interoperability: engineering heterogeneous IoT systems

Interoperability remains a significant burden to the developers of Internet of Things systems. This is because resources and APIs are dynamically composed; they are highly heterogeneous in terms of their underlying communication technologies, protocols and data formats, and interoperability tools remain limited to enforcing standards-based approaches. In this paper, we propose model-based engineering methods to reduce the development effort towards ensuring that complex software systems interoperate with one another. Lightweight interoperability models can be specified in order to monitor and test the execution of running software so that interoperability problems can be quickly identified, and solutions put in place. A graphical model editor and testing tool are also presented to highlight how a visual model improves upon textual specifications. We show using case-studies from the FIWARE Future Internet Service domain that the software framework can support non-expert developers to address interoperability challenges

Web Application Weakness Ontology Based on Vulnerability Data

Web applications are becoming more ubiquitous. All manner of physical devices are now connected and often have a variety of web applications and web-interfaces. This proliferation of web applications has been accompanied by an increase in reported software vulnerabilities. The objective of this analysis of vulnerability data is to understand the current landscape of reported web application flaws. Along those lines, this work reviews ten years (2011 - 2020) of vulnerability data in the National Vulnerability Database. Based on this data, most common web application weaknesses are identified and their profiles presented. A weakness ontology is developed to capture the attributes of these weaknesses. These include their attack method and attack vectors. Also described is the impact of the weaknesses to software quality attributes. Additionally, the technologies that are susceptible to each weakness are presented, they include programming languages, frameworks, communication protocols, and data formats

Towards a Model of Determinants of Web Services Platform Adoption by Complementers

The recent surge of interest in web services has called attention to the increasingly intense competition between owners of the platforms on which these services run. Given that widely adopted operating systems and middleware platforms have yielded sizable economic returns for their owners, many web services platform owners are aggressively pursuing strategies that can give them a competitive advantage and, it is hoped, similarly sizable returns. A review of the broader literature on software platform competition reveals widespread acceptance of network effect theory as an explanatory framework. Network effect theory posits that the value of a software platform to a potential user is associated positively with the number of existing users of the platform (who generate direct network effects) and the number of developers of complementary software applications (who generate indirect network effects) (see, e.g., Katz and Shapiro, 1986; Zhu et al., 2006). Users realize direct network effects when, for example, they share compatible files with other users (Gao and Iyer, 2006; Lin and Kulatilaka, 2006) or participate in ???trading communities??? (Zhu et al., 2006). Indirect network effects are realized through the availability of useful, innovative and compatible software applications (Lin and Kulatilaka, 2006). Users of widely adopted software platforms also gain value from the reduced likelihood of being ???stranded with a failed and unsupported platform??? and consequent switching costs (Gallaugher and Wang, 2002, p. 306). In the presence of network effects, then, software platform owners pursue strategies that will secure them an ???installed base??? of users and complementers that is sufficiently large to attract more and more new users (Shapiro and Varian, 1998; Suarez, 2005). While one set of strategies is aimed at promoting adoption by new users, another set emphasizes the value generated for users by indirect network effects and aims instead at promoting adoption by complementers. (This distinction reflects the idea that platform markets are two-sided, with (end) users populating one side and complementers populating the other.) There appears to be considerably more research on strategies for increasing user adoption (see Gallaugher and Wang (2002), von Westarp (2003) and Zhu and Iansiti (2007) for reviews) than on complementer adoption strategies. Nonetheless, three studies of the latter merit mentioning here. First, in their study of the U.S. video game industry from 1976 to 2002, Venkatraman and Lee (2003) find that platform dominance (i.e., largest installed base), together with complementers??? path dependency and level of experience with platform architecture, largely determine platform adoption by complementers. Second, in his investigation of how software platform owners maintain a balance between ???adoption and appropriation,??? West (2003) concludes that software platform owners who disclose some proprietary code will attract more complements (thereby fostering innovation), but cautions against disclosing any code that confers a competitive advantage. Finally, Cusumano and Gawer???s (2002) landmark study of Intel???s platform management strategies culminated in the endorsement of four ???levers??? for platform leadership, with one of these levers aimed at managing relations with ???external complementers???. Specific strategies include building a consensus on technical specifications and standards, handling potential conflicts of interest and letting complementers keep any intellectual property they develop on the platform. Both West (2003) and Cusumano and Gawer (2002) also underscore the importance of providing complementers with an interface to connect to the platform. Beyond West???s (2003, p. 1260) suggestion that software platform owners ???create and evolve application programming interfaces (APIs),??? though, the varied ways in which these APIs might influence a complementer???s choice to adopt have not been sufficiently explored by these or other authors. The research-in-progress described in the following section aims to bolster the somewhat scant literature on software platform adoption by complementers. More specifically, the proceeding research design outlines a proposed investigation of the determinants of complementer adoption of geo-mapping web services platforms. The reasons for including independent variables are discussed, and some methodological details are introduced. The paper concludes with a brief discussion of anticipated outcomes of the study

An overview of IoT architectures, technologies, and existing open-source projects

Financiado para publicación en acceso aberto: Universidade da Coruña/CISUG[Abstract]: Today’s needs for monitoring and control of different devices in organizations require an Internet of Things (IoT) platform that can integrate heterogeneous elements provided by multiple vendors and using different protocols, data formats and communication technologies. This article provides a comprehensive review of all the architectures, technologies, protocols and data formats most commonly used by existing IoT platforms. On this basis, a comparative analysis of the most widely used open source IoT platforms is presented. This exhaustive comparison is based on multiple characteristics that will be essential to select the platform that best suits the needs of each organization.This research/work has been supported by GAIN (Galician Innovation Agency) and the Regional Ministry of Economy, Employment and Industry, Xunta de Galicia under grant COV20/00604 through the ERDF Galicia 2014-2020; and by grant PID2019-104958RB-C42 (ADELE) funded by MCIN/AEI/10.13039/501100011033 . Funding for open access charge: Universidade da Coruña/CISUG.Xunta de Galicia; COV20/0060