This paper describes the potential impact of the Internet of Things (IoT) technologies and architecture on factory automation. Whereas, IoT use cases range from intelligent infrastructure and smart cities to health care and shopping assistants, it is important to note that factory automation could benefit as well from an IoT approach. In this paper, we argue that there will not be one IoT but many IoTs that could differ in the type of infrastructure they are running or applications they support. In IoT@Work we focus on the potential of making manufacturing environments more agile and flexible. We explain how the IoT-centric architecture for manufacturing also needs a deep understanding of the manufacturing system and its state today. We, therefore, do a reverse engineering based on the requirements and the description of the agility expected in the automation system itself.
Runtime monitoring is performed during system execution to detect whether the system's behaviour deviates from that described by requirements. To support this activity we have developed a monitoring framework that expresses the requirements to be monitored in event calculus - a formal temporal first order language. Following an investigation of how this framework could be used to monitor security requirements, in this paper we propose patterns for expressing three basic types of such requirements, namely confidentiality, integrity and availability. These patterns aim to ease the task of specifying confidentiality, integrity and availability requirements in monitorable forms by non-expert users. The paper illustrates the use of these patterns using examples of an industrial case study.
Research on Software Architectures has been active since the early nineties, leading to a number of different architecture description languages (ADL). Given their importance in facilitating the communication of crucial system properties to different stakeholders and their analysis early on in the development of a system this is understandable. After all these years one would have hoped that we could point to a handful of ADLs as the clear winners as the languages of choice of practitioners for specifying software system architectures. However it seems that ADLs have still not entered the mainstream. We believe this is so because practitioners find the current offering either too difficult to use or not supporting automated analysis commensurate to the level of effort they require for specifying a system, especially so for complex systems. In this paper we present a comparative analysis of a number of ADLs, both of first generation and more recent ones, against a small set of language properties that we believe are crucial for an ADL that would be easy for practitioners to adopt in their design and development practices. These properties are: formal semantics, usability, and realizability.
This development environment enables the specification, automated composition, and quality analysis of flexible, configurable middleware architectures, notably in distributed systems.