Reviewerly/exHarmony huggingface dataset:
Encryption Algorithm of Distributed Ledger in Engineering Settlement Application

In this paper, an encryption algorithm of distributed ledger is proposed in engineering settlement application. In order to solve the problems of unclear settlement objectives in each stage, complex and variable financial operation process, and leakage of important information data transmission, by applying distributed ledger technology to traditional engineering settlement, and optimizing the encryption module, all stages of settlement are made transparent, the efficiency of settlement is improved, and information security can be ensured. The experimental results show that the optimized encryption module can solve the key transport security problem in the symmetric encryption algorithm. It can ensure the password encryption speed and transport security. Meanwhile, the network information security is greatly increased in the construction settlement.
Modern Intelligent Health Systems: Queueing, Simulation

The Internet of Things and machine learning promise a new era in healthcare. The advent of transformative technologies such as implantable and wearable medical devices (IWMDs) has made it possible to collect and analyze physiological signals from any person at any time. Machine learning allows us to identify patterns in these signals and make health predictions in both every day and clinical situations. This expands healthcare coverage from common clinical contexts to widespread everyday scenarios, from passive data collection to active decision making. Despite the existence of an extensive literature on IWMD-based and clinical health systems, the fundamental problems associated with the design and implementation of smart health systems have not been adequately addressed. The main objectives of this article are to define a standard framework for smart health, designed for both every day and clinical settings, to explore modern smart health systems and their constituent components. Queuing theory provides robust methods to evaluate alternative designs for modeling organization smart healthcare.
Development of Online Support Tools for Creating STEM Educational Materials

In this study, online support tools were proposed for creating STEM educational materials. Online education has received an impetus because of the COVID-19 pandemic. However, expressing mathematical expression digitally is difficult, and creating educational materials for teachers in science and engineering courses at secondary schools and universities is cumbersome. Therefore, in this study, a support framework was developed for creating online STEM educational materials for expressing mathematical expressions easily. Two tools, a graph maker and a text generator, were introduced for text-to-speech systems.
Problems of Vanet Networks

This article deals with the problems of VANET networks, which is a network of motor vehicles. Attention will be paid to such problems as: aggregation, clustering, broadcasting, routing, quality of service, security, etc. The article also discusses the process of transmitting and relaying data, and in order to reduce the load on the relay node, an algorithm will be proposed.
3D Visualization Enhancement of Art Image based on Virtual Reality Technology

In order to enhance the 3d visualization of art images, this paper studies the 3D visual enhancement of fashion art images based on image virtual reality technology. The 3D feature detection and data acquisition of virtual scene are realized by the method of dark channel color scene parameter acquisition and information fusion. The distributed parameter model of fashion art image is established, the virtual reality scene of fashion art image is reconstructed, and the 3d filtering and feature analysis model is established. Feature analysis and RGB pixel reorganization are carried out by image information enhancement and parameter feedback compensation. Through exposure fusion and white balance control, the stereo visual enhancement of fashion art image is realized. The simulation results show that the research improves the reconstruction and recognition ability of fashion style art images, and the three-dimensional expression ability of art images is better, and the scene fidelity is higher.
Philosophical Comprehension of the Psychological and Information Influence Technologies in the Modern World

The concepts of “information influence” and “psychological influence” in the light of the history of philosophy allow us to record that their formation was greatly influenced by the sociocultural transformations that influenced the formation of a new philosophical image of the world, gradually preparing the consideration of such influences as information influence and psychological influence.The supremacy of information technology has created a new reality with new rules. Information warfare between countries and an “information” economy is based on a number of views. Both information and psychological influences play a key role in the above mentioned. Each information influence implies a psychological influence and vice versa: the psychological influence, in turn, becomes the basis for an information influence. In this research, the authors have attempted to make a “3D” observation of the issue. First, the authors highlighted the philosophical foundations of information and psychological influences. Second, they showed the mechanisms that cause information and psychological influences. Third, the issue of information security was brought forward, and the issue of dealing with various means of manipulation was raised. The authors considered the information influence from the point of view of its turning into psychological influence, considering the issue in a new light.
Does Code Smell Frequency Have a Relationship with Fault-proneness?

Fault-proneness is an indication of programming errors that decreases software quality and maintainability. On the contrary, code smell is a symptom of potential design problems which has impact on fault-proneness. In the literature, negative impact of code smells on fault-proneness has been investigated. However, it is still unclear that how frequency of each code smell type impacts the fault-proneness. To mitigate this research gap, we present an empirical study to identify whether frequency of individual code smell types has a relationship with the fault-proneness. The results show that Anti Singleton, Blob and Class Data Should Be Private smell types have strong relationship with fault-proneness though their frequencies are not very high. On the other hand, comparatively high frequent code smell types such as Complex Class, Large Class and Long Parameter List have moderate relationship with fault-proneness. These findings will assist developers to prioritize and refactor code smells to improve software quality.
Perceived Trust in Blockchain Systems: An Interview-based Survey

Blockchain systems have received increased interest over the past few years, and several new fields of use, such as supply chain systems, are being investigated. Since blockchain is still a new technology, various papers have explored how to apply it to support use cases outside the limited scope of digital currencies. Systems require solid technological implementation and perceived trust among users to ensure their interests and successful usage in practice. This study aimed to understand what graphic user interface (GUI) elements of a blockchain-based system make users trust that their best interests, such as security and privacy, are maintained in the systems. As a case study, we developed a few blockchain-based supply chain GUI mockups with different elements that reflect the security and privacy features of the system. We then conducted 30 interviews in Norway and China to collect the users’ opinions on whether the information presented in the GUIs helps them trust the system. The results show that users want access to as much information and data as the system can provide. The users’ trust in the system increases if the GUI features give users the impression that the inner workings of the blockchain-based system are transparent. However, users prefer the information presented as more conceptual than technical in the first place. However, users appreciate the possibility of clicking on the conceptual explanation and getting more in-depth blockchain-related technical information if needed.
Decentralised Autonomous Organisations for Public Procurement

Blockchain has been recognised as a technological breakthrough with the ability to support new decentralised security-based solutions in sectors such as information technology and finance. Blockchain allows different communities to create Decentralised Autonomous Organisations (DAOs), which are self-organised democratic organisations controlled by smart contracts. This paper presents a new DAO model for the procurement of services by public organisations, such as government agencies. To demonstrate the advantages of this solution, this work looks specifically at current public procurement systems that resort to third-party contractors that manage these negotiations. Third parties lack the transparency, security, and democratic representation that a DAO can provide. We present the implementation of a DAO as a set of smart contracts executed on Ethereum-compatible permissionless blockchains, supported by a consensus algorithm, replacing third-party contractors.
Functional Size Measurement in Agile Development

Agile teams measure their velocity for performance, based on Story Points. However, such velocity does not allow predicting when the product will be finished. Story points measure effort only. They do not discriminate between creating functionality and other tasks. Non-functional requirements (NFR), such as enhancing product quality, test coverage, removing technical debt, as well as process-related NFR such as agreeing with stakeholders, getting requirements right, or documenting, consume effort but do not add functionality. Thus, it remains unclear whether the product makes any progress, or the team is just looping around. Euro Project Office has therefore developed a method how to complement a product backlog by functional size, indicating progress and completeness in unambiguous terms. The method is based on the international standard ISO/IEC 14143 and ISO/IEC 19761. NFR are understood as in . Tools are available as open source and can be used by development teams with minimum investment into training.
Analyzing Bug Life Cycles to Derive Practical Insights

In this study, we assess bug life cycles to identify bottlenecks in the bug tracking processes, and examine the effectiveness of bug tracking system usage practices linked to bug states and state transitions. To achieve this, we examined the bug life cycles of three open-source software projects which use Bugzilla as their bug tracking system. In total, we have analyzed 106.196 bugs gathered from these projects. We started by looking at the temporal and quantitative aspects of these projects’ bug life cycles. After that, we collected data about how bug life cycles differ over time. Finally, we inspected the frequency of reopened and state-looping bugs in these projects. After our analysis, we have deduced that the presented temporal and quantitative analysis of bug life cycles is useful for finding bottlenecks and undesired behaviors in the bug tracking processes. We also inferred that examining the changes in bug life cycles over time can provide insights into how bug tracking practices changed throughout the project’s lifetime, and it can be used as a parameter to assess whether the bug tracking system usage has improved. Lastly, we deducted that analyzing undesired state trails’ frequency provides insights into the performance of bug tracking processes. Based on the insights gained from analyzing bug life cycles with the presented methods, we believe that decision makers can improve their workflow by introducing or removing new states to the bug life cycle and adding new rules and restrictions to their bug tracking process.
Identification of Influential Factors for Successful Adoption of DevOps and Cloud

DevOps is a software development approach that emphasize collaboration, communication and integration between development and operation teams to improve the speed and efficiency of software delivery. DevOps aims to automate and streamline the software development and deployment process. Nevertheless, when a software organization adopts DevOps, several challenges on infrastructure management, limited agility, scalability, increased cost, inconsistent environment, and security risks are faced. A solution is to adopt DevOps and Cloud together, but the integration requires advice because implementing new approaches for development and operations at the same time is also a challenge. The aim of this study is to identify and categorize success factors that positively influence the adoption of DevOps and Cloud in software organization and propose an integrated framework for factors of both dimensions. A systematic literature review (SLR) was conducted to collect the primary studies related to both fields for analysis. After the SLR, 40 success factors related to DevOps and Cloud are collected. These identified factors are further categorized into Technical, Organizational, and Social & Culture areas. The proposed framework can help practitioners and researchers to concentrate on the crucial areas that are essential for the successful adoption of DevOps and Cloud.
U Owns the Code That Changes and How Marginal Owners Resolve Issues Slower in Low-Quality Source Code

[Context] Accurate time estimation is a critical aspect of predictable software engineering. Previous work shows that low source code quality increases the uncertainty in issue resolution times. [Objective] Our goal is to evaluate how developers’ project experience and file ownership are related to issue resolution times. [Method] We mine 40 proprietary software repositories and conduct an observational study. Using CodeScene, we measure source code quality and active development time connected to Jira issues. [Results] Most source code changes are made by either a marginal or dominant code owner. Also, most changes to low-quality source code are made by developers with low levels of ownership. In low-quality source code, marginal owners need 45% more time for small changes, and 93% more time for large changes. [Conclusions] Collective code ownership is a popular target, but industry practice results in many dominant and marginal owners. Marginal owners are particularly hampered when working with low-quality source code, which leads to productivity losses. In codebases plagued by technical debt, newly onboarded developers will require more time to complete tasks.
Do Developers Benefit from Recommendations when Repairing Inconsistent Design Models? a Controlled Experiment

Repairing design models is a laborious task that requires a considerable amount of time and effort from developers. Repair recommendation (RR) approaches focus on reducing the effort and improving the quality of the repairs performed. Such approaches have been evaluated in terms of scalability, correctness, and minimalism. These evaluations, however, have not investigated how developers can benefit from using RRs and how they perceive the difficulty of applying RRs. Investigating and discussing the use of RRs from the developers’ perspective is important to demonstrate the benefits of applying such approaches in practice. We explore this opportunity by conducting a controlled experiment carried out with 24 developers where they repaired UML design models in eight different tasks, with and without RRs. The findings indicate that developers can benefit from RRs in complex tasks by improving their effectiveness and efficiency. The results also evidence that the use of RRs does not impact the developers’ perceived difficulty and confidence when repairing models. Furthermore, our findings show that not all developers choose the same RR, but rather, have varied preferences. Thus, the provision of RRs leads to developers considering additional alternatives to repair an inconsistency.
Replication and Extension of Schnappinger’s Study on Human-level Ordinal Maintainability Prediction Based on Static Code Metrics

As a part of a research project concerning software maintainability assessment in collaboration with the development team, we wanted to explore dissensions between developers and the confounding effect of size. To this end, this study replicated and extended a recent study from Schnappinger et al. with the public part of its dataset and the metrics extracted from the graph-based tool Javanalyser. The entire processing pipeline was automated, from metrics extraction to the training of machine learning models. The study was extended by predicting the continuous maintainability to take account of dissensions. Then, all experimental shots were duplicated to evaluate the overall influence of the class size. In the end, the original study was successfully replicated. Moreover, good performance was achieved on the continuous maintainability prediction. Finally, the class size was not sufficient for fine-grained maintainability prediction. This study shows the necessity to explore the nature of what is measured by code metrics, and is also the first step in the construction of a maintainability model.
Assessing the Impact of File Ordering Strategies on Code Review Process

Popular modern code review tools (e.g., Gerrit and GitHub) sort files in a code review in alphabetical order. A prior study (on open-source projects) shows that the changed files’ positions in the code review affect the review process. Their results show that files placed lower in the order have less chance of receiving reviewing efforts than the other files. Hence, there is a higher chance of missing defects in these files. This paper explores the impact of file order in the code review of the well-known industrial project IntelliJ IDEA. First, we verify the results of the prior study on a big proprietary software project. Then, we explore an alternative to the default Alphabetical order: ordering changed files according to their code diff. Our results confirm the observations of the previous study. We discover that reviewers leave more comments on the files shown higher in the code review. Moreover, these results show that, even with the data skewed toward Alphabetical order, ordering changed files according to their code diff performs better than standard Alphabetical order regarding placing problematic files, which needs more reviewing effort, in the code review. These results confirm that exploring various ordering strategies for code review needs more exploration.
Aggregating N-fold Requirements Inspection Results

Requirements validation is an important aspect for ensuring high quality software. Commonly used are requirements inspections, where the specification is read from different persons assuming different roles or applying different reading techniques, partly accompanied by checklists. Actual defect detection with requirements inspection is costly, and defect detection rates must be considered low. Therefore, repeated validation is used or validation with multiple inspection groups - known as N-fold inspections. However, this does not only yield more defects found, but also more false positives. In this paper, we investigate how defect aggregation can be used to improve the overall quality of validation. Therefore, we conducted an experiment with 22 N-fold inspection groups consisting of four to five reviewers each. Results show that simple aggregation of all results leads to a number of false positives that can actually negatively impact the validation task, while the use of more tailored aggregation strategies can considerably improve the validation of requirements with N-fold inspections.
Team Composition in Software Engineering Education

One of the objectives of software engineering education is to make students to learn essential teamwork skills. This is done by having the students work in groups for course assignments. Student team composition plays a vital role in this, as it significantly affects learning outcomes, what is learned, and how. The study presented in this paper aims to better understand the student team composition in software engineering education and investigate the factors affecting it in the international software engineering education context. Those factors should be taken into consideration by software engineering teachers when they design group work assignments in their courses. In this paper, the initial findings of the ongoing Action research study are presented. The results give some identified principles that should be considered when designing student team composition in software engineering courses.
Functional Size Measurement in Agile Development

Agile teams measure their velocity for performance, based on Story Points. However, such velocity does not allow predicting when the product will be finished. Story points measure effort only. They do not discriminate between creating functionality and other tasks. Non-functional requirements, such as agreeing with stakeholders, designing, testing, or documenting, consume effort but do not add functionality. Thus, it remains unclear whether the product makes any progress, or the team is just looping around technical debt and unclear requirements. Euro Project Office has therefore developed a method how to complement a product backlog by functional size, indicating progress and completeness in unambiguous terms. The method is based on the international standard ISO/IEC 14143 [1] and ISO/IEC 19761 [2]. Tools are available as open source and can be used by development teams with minimum investment into training.
A Study on Management Challenges and Practices in DevOps

DevOps is a widely adopted practice to consistently develop and upgrade a system that is already in use. Between software development and operations, DevOps presupposes cross-functional cooperation and automation. The adoption and execution of DevOps in businesses are complicated since it necessitates adjustments to organizational, technical, and cultural factors. The implementation of DevOps in practice is thoroughly described in this systemic literature review (SLR). The study focuses on the identification of the manager's challenges in the DevOps environment and also intends to find the mitigation practices. In this article, SLR has been performed to identify the manager's challenges and the state-of-the-art mitigation strategies. This study identifies twenty challenges from the manager's perspective and the applied mitigation strategies to overcome the challenges. The findings of the current work would be beneficial in comprehending the DevOps idea, methods, and perceived impacts, particularly among managers while adopting DevOps in the organization.
Artifact Traceability in DevOps: An Industrial Experience Report

In DevOps, the traceability of software artifacts is critical to the successful development and operation of project delivery to stakeholders. Before the introduction of end-to-end traceability in DevOps at a Data Analytics team at bp (BP plc), an international integrated energy company, the tracing of artifacts throughout a project life cycle was manual and time-consuming. This changed when traceability become more automated with end-to-end traceability capability as an offering on the platform. This paper reports on the ways of working and the experience of developers implementing DevOps for developing and putting in production a Javascript React web application, with a focus on traceability management of artifacts produced throughout the life cycle. This report highlights key opportunities and challenges in traceability management from the development stage to production.