Journal Article•
NFR catalogues for RFID middleware
01 Oct 2014-Journal of Computer Science and Technology (Facultad de Informática)-Vol. 14, Iss: 2, pp 102-108
TL;DR: This study presents the preparation of non-functional requirements catalogues for RFID middleware supported by Non-Functional Requirements Framework (NFR-Framework) and the effectiveness of the reuse of the catalogues.
Abstract: Non-functional requirements (NFR) are related to the user satisfaction about the quality attributes of the information system. In some cases these requirements are ignored or implemented by the end of the project in a chaotic way. It happens because, in many cases, the user does not have enough contact with the information system to solve these requirements, such as nonfunctional requirements for Radio-Frequency Identification (RFID) middleware. This study presents the preparation of non-functional requirements catalogues for RFID middleware supported by Non-Functional Requirements Framework (NFR-Framework). Two case studies were performed to evaluate the Requirements Engineering process in the creation of the NFR catalogues and the effectiveness of the reuse of the catalogues. As a result, a set of non-functional requirements are presented and organized into catalogues that work as the foundation for RFID system developers in the identification and validation of non-functional requirements for RFID middleware in information systems context.
Citations
More filters
01 Sep 2021
TL;DR: In this paper, explainability has been identified as an emerging non-functional requirement (NFR) that has a significant impact on system quality, and a model and a catalogue for explainability is proposed.
Abstract: The growing complexity of software systems and the influence of software-supported decisions in our society awoke the need for software that is transparent, accountable, and trust-worthy. Explainability has been identified as a means to achieve these qualities. It is recognized as an emerging non-functional requirement (NFR) that has a significant impact on system quality. However, in order to incorporate this NFR into systems, we need to understand what explainability means from a software engineering perspective and how it impacts other quality aspects in a system. This allows for an early analysis of the benefits and possible design issues that arise from interrelationships between different quality aspects. Nevertheless, explainability is currently under-researched in the domain of requirements engineering and there is a lack of conceptual models and knowledge catalogues that support the requirements engineering process and system design. In this work, we bridge this gap by proposing a definition, a model, and a catalogue for explainability. They illustrate how explainability interacts with other quality aspects and how it may impact various quality dimensions of a system. To this end, we conducted an interdisciplinary Systematic Literature Review and validated our findings with experts in workshops.
37 citations
01 Aug 2020
TL;DR: This work aims at capturing and cataloging invisibility correlations for UbiComp and IoT systems, and proposes to systematize the definition of correlations using the following well-defined research methods: Interview, Content Analysis and Questionnaire.
Abstract: The advance of Ubiquitous Computing (UbiComp) and Internet of Things (IoT) brought a new set of Non-Functional Requirements (NFRs), especially related to Human-Computer Interaction (HCI). Invisibility is one of these NFRs, and it refers to either the merging of technology in the user environment or the decrease of the interaction workload. This new NFR may impact traditional NFRs (e.g., Usability), revealing positive correlations, when one NFR helps another, and negative correlations, when a procedure favors an NFR but creates difficulty for another one. Software engineers need to know about these correlations, so they can select appropriate strategies to satisfy Invisibility and traditional NFRs. Correlations between NFRs are usually stored in catalogs, which is a well-defined body of knowledge gathered from previous experience. Although Invisibility has been recently cataloged with development strategies, the literature still lacks catalogs with correlations for this NFR. Therefore, this work aims at capturing and cataloging invisibility correlations for UbiComp and IoT systems. To do that, we also propose to systematize the definition of correlations using the following well-defined research methods: Interview, Content Analysis and Questionnaire. As a result, we defined a catalog with 110 positive and negative correlations with 9 NFRs. This well-defined body of knowledge is useful for supporting software engineers to select strategies to satisfy Invisibility and other NFRs related to user interaction.
6 citations
Cites background from "NFR catalogues for RFID middleware"
...The literature has several catalogs that generally focus on correlations that are generic to any system [13] [17] [18] [19], but it lacks catalogs with Invisibility for the domain of UbiComp and IoT systems....
[...]
TL;DR: In this paper , the authors propose four artifacts: a definition of explainability, a conceptual model, a knowledge catalogue, and a reference model for explainable systems to support software and requirements engineers in understanding explainability and how it interacts with other quality aspects.
Abstract: Abstract The growing complexity of software systems and the influence of software-supported decisions in our society sparked the need for software that is transparent, accountable, and trustworthy. Explainability has been identified as a means to achieve these qualities. It is recognized as an emerging non-functional requirement (NFR) that has a significant impact on system quality. Accordingly, software engineers need means to assist them in incorporating this NFR into systems. This requires an early analysis of the benefits and possible design issues that arise from interrelationships between different quality aspects. However, explainability is currently under-researched in the domain of requirements engineering, and there is a lack of artifacts that support the requirements engineering process and system design. In this work, we remedy this deficit by proposing four artifacts: a definition of explainability, a conceptual model, a knowledge catalogue, and a reference model for explainable systems. These artifacts should support software and requirements engineers in understanding the definition of explainability and how it interacts with other quality aspects. Besides that, they may be considered a starting point to provide practical value in the refinement of explainability from high-level requirements to concrete design choices, as well as on the identification of methods and metrics for the evaluation of the implemented requirements.
4 citations
01 Nov 2015
TL;DR: A design of architecture for general application program interface (API) is introduced, which shields the diversity and complexity of RFID equipment and realizes the integrated link management between applications and RFID read-write devices, which can greatly improve the management efficiency of information collection, analysis, processing and automatic operation.
Abstract: In the field of the Internet of things, the RFID (Radio Frequency Identification) electronic tags has been increasingly widely used, but also face the shortcomings including diversity of data interface, the complexity of access and so on. In this paper, the authors introduce a design of architecture for general application program interface (API), which shields the diversity and complexity of RFID equipment. Also it realizes the integrated link management between applications and RFID read-write devices, which can greatly improve the management efficiency of information collection, analysis, processing and automatic operation. According to actual test, it realizes the design of seamless integration middleware, and can greatly promote the industry application of RFID. KEYWORD: Internet of Things; Radio Frequency Identification; Middleware; Architecture design
2 citations
Cites background from "NFR catalogues for RFID middleware"
...(6) Capacity to integrate with other technologies; Effective architecture to handle large amounts of data; Security access to data; Interoperability with various devices and high reliability to critical missions[9]....
[...]
01 Jan 2016
TL;DR: The fault tolerant system design is universally compatible with any devices to read, and it is available in the digital library an online access to it is set as public so you can get it instantly.
Abstract: Thank you very much for reading fault tolerant system design. As you may know, people have search hundreds times for their chosen novels like this fault tolerant system design, but end up in malicious downloads. Rather than enjoying a good book with a cup of tea in the afternoon, instead they are facing with some malicious virus inside their computer. fault tolerant system design is available in our digital library an online access to it is set as public so you can get it instantly. Our books collection spans in multiple countries, allowing you to get the most less latency time to download any of our books like this one. Merely said, the fault tolerant system design is universally compatible with any devices to read.
1 citations
References
More filters
04 Jul 2009
TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Abstract: Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
2,443 citations
TL;DR: A new model of viewpoints called Preview is introduced which is flexible, generic entities which can be used in different ways and in different application domains and how well this approach addresses some outstanding problems in requirements engineering (RE) and the practical industrial problems of introducing new requirements engineering methods.
Abstract: The paper includes a survey and discussion of viewpointdoriented approaches to requirements engineering and a presentation of new work in this area which has been designed with practical application in mind. We describe the benefits of viewpointdoriented requirements engineering and describe the strengths and weaknesses of a number of viewpointdoriented methods. We discuss the practical problems of introducing viewpointdoriented requirements engineering into industrial software engineering practice and why these have prevented the widespread use of existing approaches.
We then introduce a new model of viewpoints called Preview. Preview viewpoints are flexible, generic entities which can be used in different ways and in different application domains. We describe the novel characteristics of the Preview viewpoints model and the associated processes of requirements discovery, analysis and negotiation. Finally, we discuss how well this approach addresses some outstanding problems in requirements engineering (RE) and the practical industrial problems of introducing new requirements engineering methods.
244 citations
"NFR catalogues for RFID middleware" refers methods in this paper
...The first case study was performed in a paper and cellulose industry and its goal was to build an RFID middleware to track the loading of raw material, using the traditional method [12][13][14], and to build NFR catalogues along with the requirements engineering process....
[...]
TL;DR: This short tutorial introduces the fundamental activities of RE (requirements engineering) and discusses how it has evolved as a part of the software engineering process, rather than focusing on the established RE techniques.
Abstract: This short tutorial introduces the fundamental activities of RE (requirements engineering) and discusses how it has evolved as a part of the software engineering process. However, rather than focusing on the established RE techniques, the author discusses how the changing nature of software engineering has led to the new challenges in RE. The author then introduces a number of new techniques that helps us to meet these challenges by integrating RE more closely with other systems implementation activities.
197 citations
"NFR catalogues for RFID middleware" refers methods in this paper
...The first case study was performed in a paper and cellulose industry and its goal was to build an RFID middleware to track the loading of raw material, using the traditional method [12][13][14], and to build NFR catalogues along with the requirements engineering process....
[...]
TL;DR: Information interchange issues of identifier-based operations in supply-chains are discussed as well, while the last part of the paper presents a framework for choosing an auto-ID technique in a supply chain.
183 citations
"NFR catalogues for RFID middleware" refers background in this paper
...Therefore the creation of catalogues to non-functional requirements has a deserved importance, considering the historical cases of projects that were affected by the absence or lack of understanding of such requirements [2][8]....
[...]
TL;DR: In this article, a measure for accuracy and precision in a passive RFID localization system with regard to RFID tag distribution is defined, and an exponential-based function is derived from experimental measurements, which reflects the relationship between RFID tags distribution and localization precision.
Abstract: Radio-frequency identification (RFID) technology has been widely used in passive RFID localization application due to its flexible deployment and low cost. However, current passive RFID localization systems cannot achieve both highly accurate and precise moving object localization task owing to tag collisions and variation of the behavior of tags. Most researchers increase the density of tag distribution to improve localization accuracy and then consider using either anti-collision process embedded in the hardware of the RFID reader or advanced localization algorithms to enhance localization precision. However, advanced anti-collision processes for RFID devices are challenged by the physical constraint characteristics of radio frequency; and improved localization algorithm cannot fundamentally reduce the impacts of tag collision on localization precision. This research work attempts to improve localization precision of a passive RFID localization system by using sparsely distributed RFID tags. This paper first defines a measure for accuracy and precision in a passive RFID localization system with regard to RFID tag distribution. An exponential-based function is then derived from experimental measurements, which reflects the relationship between RFID tag distribution and localization precision. This function shows that localization precision is mainly determined by tag density of RFID tag distribution. Based on the experimental findings, a sparse RFID tag distribution approach is proposed. The results show that in comparison with the conventional RFID tag distribution, passive RFID localization system with sparse RFID tag distribution can deliver a higher localization precision for the required accuracy.
174 citations