Dealing with Conflicts Between Non-functional Requirements of UbiComp and IoT Applications

2017 ◽  
Author(s):  
Rainara Maia Carvalho
Keyword(s):  
Functional Requirements ◽  
Iot Applications

scholarly journals IoTEF: A Federated Edge-Cloud Architecture for Fault-Tolerant IoT Applications

2020 ◽  
Vol 18 (1) ◽  
pp. 57-80 ◽  
Author(s):  
Asad Javed ◽  
Jérémy Robert ◽  
Keijo Heljanko ◽  
Kary Främling
Keyword(s):  
Internet Of Things ◽  
Data Processing ◽  
Fault Tolerant ◽  
Network Connectivity ◽  
Functional Requirements ◽  
Long Distance ◽  
Network Bandwidth ◽  
Iot Applications ◽  
Layered Design ◽  
Hostile Environments

AbstractThe evolution of Internet of Things (IoT) technology has led to an increased emphasis on edge computing for Cyber-Physical Systems (CPS), in which applications rely on processing data closer to the data sources, and sharing the results across heterogeneous clusters. This has simplified the data exchanges between IoT/CPS systems, the cloud, and the edge for managing low latency, minimal bandwidth, and fault-tolerant applications. Nonetheless, many of these applications administer data collection on the edge and offer data analytic and storage capabilities in the cloud. This raises the problem of separate software stacks between the edge and the cloud with no unified fault-tolerant management, hindering dynamic relocation of data processing. In such systems, the data must also be preserved from being corrupted or duplicated in the case of intermittent long-distance network connectivity issues, malicious harming of edge devices, or other hostile environments. Within this context, the contributions of this paper are threefold: (i) to propose a new Internet of Things Edge-Cloud Federation (IoTEF) architecture for multi-cluster IoT applications by adapting our earlier Cloud and Edge Fault-Tolerant IoT (CEFIoT) layered design. We address the fault tolerance issue by employing the Apache Kafka publish/subscribe platform as the unified data replication solution. We also deploy Kubernetes for fault-tolerant management, combined with the federated scheme, offering a single management interface and allowing automatic reconfiguration of the data processing pipeline, (ii) to formulate functional and non-functional requirements of our proposed solution by comparing several IoT architectures, and (iii) to implement a smart buildings use case of the ongoing Otaniemi3D project as proof-of-concept for assessing IoTEF capabilities. The experimental results conclude that the architecture minimizes latency, saves network bandwidth, and handles both hardware and network connectivity based failures.

scholarly journals INTEGRATION OF IOT SENSORS TO 3D INDOOR MODELS WITH INDOORGML

2020 ◽  
Vol XLIV-4/W1-2020 ◽  
pp. 135-142
Author(s):  
A. Sarmiento ◽  
A. A. Diakité
Keyword(s):  
Data Model ◽  
Functional Requirements ◽  
Sensor Applications ◽  
Multiple Sensors ◽  
Iot Applications ◽  
Systems Research ◽  
Potential Scale ◽  
Efficient Data ◽  
Sensor Information ◽  
Conceptual Data

Abstract. Sensors are the vehicle through which Internet of Things (IoT) applications collect timely data of which are communicated to objects, or “Things”, to make them aware of their environment. With multiple sensors within an IoT system sending continuous streams of data, the potential scale of data is large, so efficient data management and useful representation is a key concern. As the information required from sensors benefit from a spatial context, 3D indoor models, such as IndoorGML, have been identified to support this condition. As it stands, a standardised structure to the amalgamation of sensors with IndoorGML has not been defined. The goal of this paper is to explore this opportunity by firstly, reviewing previous approaches to the integration of the two systems. Research into the interpretations of sensor information through existing standards is conducted before narrowing these attributes down into a minimal profile according to identified functional requirements of sensor applications. Finally, this knowledge is organised into a conceptual data model and presented as a thematic module in IndoorGML.

Security and Privacy Requirements for the Internet of Things

2021 ◽  
Vol 2 (1) ◽  
pp. 1-37
Author(s):  
Nada Alhirabi ◽  
Omer Rana ◽  
Charith Perera
Keyword(s):  
Software Engineering ◽  
Internet Of Things ◽  
Development Process ◽  
Security And Privacy ◽  
Functional Requirements ◽  
Application Development ◽  
Privacy Requirements ◽  
Iot Applications ◽  
Different Types ◽  
Software And Hardware

The design and development process for internet of things (IoT) applications is more complicated than that for desktop, mobile, or web applications. First, IoT applications require both software and hardware to work together across many different types of nodes with different capabilities under different conditions. Second, IoT application development involves different types of software engineers such as desktop, web, embedded, and mobile to work together. Furthermore, non-software engineering personnel such as business analysts are also involved in the design process. In addition to the complexity of having multiple software engineering specialists cooperating to merge different hardware and software components together, the development process requires different software and hardware stacks to be integrated together (e.g., different stacks from different companies such as Microsoft Azure and IBM Bluemix). Due to the above complexities, non-functional requirements (such as security and privacy, which are highly important in the context of the IoT) tend to be ignored or treated as though they are less important in the IoT application development process. This article reviews techniques, methods, and tools to support security and privacy requirements in existing non-IoT application designs, enabling their use and integration into IoT applications. This article primarily focuses on design notations, models, and languages that facilitate capturing non-functional requirements (i.e., security and privacy). Our goal is not only to analyse, compare, and consolidate the empirical research but also to appreciate their findings and discuss their applicability for the IoT.

An Integrated Approach for a Knowledge-based Clinical Workstation: Architecture and Experience

1998 ◽  
Vol 37 (01) ◽  
pp. 16-25 ◽  
Author(s):  
P. Ringleb ◽  
T. Steiner ◽  
P. Knaup ◽  
W. Hacke ◽  
R. Haux ◽  
...  
Keyword(s):  
Decision Support ◽  
Information Systems ◽  
Patient Care ◽  
Hospital Information Systems ◽  
Medical Decision ◽  
Daily Routine ◽  
Functional Requirements ◽  
Support Functions ◽  
Knowledge Based ◽  
Clinical Workstation

Abstract:Today, the demand for medical decision support to improve the quality of patient care and to reduce costs in health services is generally recognized. Nevertheless, decision support is not yet established in daily routine within hospital information systems which often show a heterogeneous architecture but offer possibilities of interoperability. Currently, the integration of decision support functions into clinical workstations is the most promising way. Therefore, we first discuss aspects of integrating decision support into clinical workstations including clinical needs, integration of database and knowledge base, knowledge sharing and reuse and the role of standardized terminology. In addition, we draw up functional requirements to support the physician dealing with patient care, medical research and administrative tasks. As a consequence, we propose a general architecture of an integrated knowledge-based clinical workstation. Based on an example application we discuss our experiences concerning clinical applicability and relevance. We show that, although our approach promotes the integration of decision support into hospital information systems, the success of decision support depends above all on an adequate transformation of clinical needs.

Sign in / Sign up

Export Citation Format

Share Document