Search

Enterprise architecture is a growing trend that aims to help deal with the complexity of socio‐technical systems such as human organizations, as well as their information technology and systems areas. Nevertheless, the contribution of enterprise architecture to the field of software engineering remains unclear. The purpose of this systematic literature review is to see how enterprise architecture is used in software development and maintenance practice. To this end, we first carried out a search in the SCOPUS database and then organized the papers according to the Software Engineering Body of Knowledge to determine what areas of software engineering are covered by each research study. To understand how enterprise architecture is used, we established a classification based on ISO 42010 and TOGAF. From the systematic literature review, we noticed that the early stages of development are the most impacted by the enterprise architecture. On the other hand, we observed that enterprise architecture is of assistance in the areas of engineering management, engineering processes, and engineering models and methods; these tasks are carried out by teams or managers using different, often agile, development methods or standards. In turn, we found that the most common categories are architecture descriptions; these are often used to facilitate communication and information‐sharing between different stakeholders, in addition to frameworks, which will help to establish common practices in the organization related to the joint use of enterprise architecture and software development. [ABSTRACT FROM AUTHOR]

The object of research is a distributed order processing system for a restaurant chain. The subject of the research is the analysis of the use of Redis for managing event queues in distributed systems. When implementing a distributed order processing system in a restaurant chain with a possible load of up to 20,000 users per day, the Redis system was used. Management of 9 distributed subsystems was organized through Redis. This solution showed an increase in the performance of the system under heavy load (from 50 transactions per second), but the response time of the system in some cases of its operation was longer than without using Redis. When working systems using Redis, it is necessary to take into account the amount of data with which Redis will work, since it does not exceed the amount of RAM, the absence of differentiation into users and groups, and the absence of a query language, which is replaced by a key-value scheme. This research is aimed at analyzing the operation of the system during trial operation under real load. We compared the operation of a configured system with Redis enabled and disabled. The main indicators for the analysis were the system response time and the maximum request execution time. The research was carried out for 2 weeks, the first week using the system settings with disabled Redis, the second – with enabled Redis. We selected 2 days with a similar load on the system to each other. Especially indicative are the results of comparing the durations of the longest queries, which show an almost constant value of the duration for the system in the mode of enabled Redis. The hypothesis of an increase in the system response time at low loads was confirmed, but this value not only leveled off at a load of 500 unique users but also became less at loads of 1000 unique users. [ABSTRACT FROM AUTHOR]

The object of research is a distributed order processing system for a restaurant chain. The subject of the research is the analysis of the use of Redis for managing event queues in distributed systems. When implementing a distributed order processing system in a restaurant chain with a possible load of up to 20,000 users per day, the Redis system was used. Management of 9 distributed subsystems was organized through Redis. This solution showed an increase in the performance of the system under heavy load (from 50 transactions per second), but the response time of the system in some cases of its operation was longer than without using Redis. When working systems using Redis, it is necessary to take into account the amount of data with which Redis will work, since it does not exceed the amount of RAM, the absence of differentiation into users and groups, and the absence of a query language, which is replaced by a key-value scheme. This research is aimed at analyzing the operation of the system during trial operation under real load. We com)pared the operation of a configured system with Redis enabled and disabled. The main indicators for the analysis were the system response time and the maximum request execution time. The research was carried out for 2 weeks, the first week using the system settings with disabled Redis, the second – with enabled Redis. We selected 2 days with a similar load on the system to each other. Especially indicative are the results of comparing the durations of the longest queries, which show an almost constant value of the duration for the system in the mode of enabled Redis. The hypothesis of an increase in the system response time at low loads was confirmed, but this value not only leveled off at a load of 500 unique users but also became less at loads of 1000 unique users. [ABSTRACT FROM AUTHOR]

Modern Software Engineering thrives with innovative tools that aid developers in creating better software grounded on quality standards. Software bots are an emerging and exciting trend in this regard, supporting numerous software development activities. As an emerging trend, few studies describe and analyze different bots in software development. This research presents a systematic literature review covering the state of the art of applied and proposed bots for software development. Our study spans literature from 2003 to 2022, with 82 different bots applied in software development activities, covering 83 primary studies. We found four bot archetypes: chatbots which focus on direct communication with developers to aid them, analysis bots that display helpful information in different tasks, repair bots for resolving software defects, and development bots that combine aspects of other bot technologies to provide a service to the developer. The primary benefits of using bots are increasing software quality, providing useful information to developers, and saving time through the partial or total automation of development activities. However, drawbacks are reported, including limited effectiveness in task completion, high coupling to third-party technologies, and some prejudice from developers toward bots and their contributions. We discovered that including Bots in software development is a promising field of research in software engineering that has yet to be fully explored. [ABSTRACT FROM AUTHOR]

The term agile is frequently used in IT especially in the area of software engineering. The broad pervasiveness of the term agile is astonishing, because it is not well defined in the area of software engineering. The fuzziness of the term agile comes with the danger of ill‐founded decisions and ideological discussions. Both slow down the gain in knowledge in the domain of software engineering. The term agile should therefore not be used either in science nor in the industry. This article provides a critical discussion of the term agile. By using a three‐layered abstraction concept for software development processes, the use of the term agile can be avoided. [ABSTRACT FROM AUTHOR]

Various approaches toward the development of sustainable software systems have been proposed by the requirements engineering community over the last decade. We conducted a systematic mapping study, analyzed 55 publications, and identified 29 approaches that have been published since the year 2000. We analyzed how the approaches evolved over time and how the publications and authors are influenced by each other. Furthermore, the approaches are analyzed in terms of their supported requirements engineering activities, along with the evidence provided in the publications. Additionally, we also analyzed which sustainability definitions have been used, if an iterative application of the approaches is discussed, and if the approaches also provide a tool-support for practitioners. We noticed an increase of publications on requirements engineering approaches toward sustainability in the last years, whereas a majority discuss sustainability based on the same multi-dimensional concept. Although different case studies have been already conducted, we noticed a lack of an industrial application. Our main findings concern the need of an evaluation on how the proposed requirements engineering approaches can also be applied in agile software development processes. Additionally, we also promote the development of supporting software tools to support practitioners in adapting the proposed approaches. [ABSTRACT FROM AUTHOR]

Mobile application (app) development is a subset of software development distinguished by a short development life cycle, rapidly changing business requirements, mobile device technical specifications, and operating system compatibility. The study presents a V‐model mobile app development technique that combines two fuzzy quality function deployment (FQFD) phases. In mobile app development, user requirements are often misunderstood, resulting in poor mobile app design. The research motivation for employing FQFD is to obtain more accurate deductions of human (user or design team) inputs affected by intrinsic vagueness and ambiguity in linguistics. The combination hence delivers synergistic benefits, where FQFDs more effectively solicits and breaks down the voice of the customer (VOC) and system requirements, and the V‐model aligns the development to the broken‐down requirements. The development of an online statistical process control app was demonstrated. FQFD structurally related user requirements, system requirements, and design strategies in the V‐model's verification phases. The validation phases used test plans created during the verification phases to detect and correct programming errors. In the final validation stage, the focus group agreed that the mobile app met all of the user requirements. This study adds to the methodology's novelty by proposing and demonstrating the integration of the FQFD and V‐model into the development of mobile apps. As a result of the limitation, other areas of software engineering, such as time and resource coordination and release management, are not considered. [ABSTRACT FROM AUTHOR]

This paper describes an OWL-based ontology to manage the data and artifacts created as part of software development projects based on the ECSS-E-ST-40C standard for SW development. ECSS standards are the main reference in aerospace projects. ECSS-E-ST-40C establishes the process, activities, requirements, and work products that must be generated. As part of its requirements, ECSS-E-ST-40C implicitly refers to specific data that must be generated, collected, and managed. The ontology identifies these data and the relationships that are inferred from the requirements in the standard, intending to set up the basis for building advanced information systems where data coming from different projects can be integrated and connected into a coherent set. The definition of this ontology provides the conceptual framework to develop data exchange processes and interfaces between the different tools and information systems used by the different players in the aerospace industry. [ABSTRACT FROM AUTHOR]

Software development for data reduction and analysis at large research facilities is increasingly professionalized, and internationally coordinated. To foster software quality and sustainability, and to facilitate collaboration, representatives from software groups of European neutron and muon facilities have agreed on a set of guidelines for development practices, infrastructure, and functional and non-functional product properties. These guidelines have been derived from actual practices in software projects from the EU funded consortium 'Science and Innovation with Neutrons in Europe in 2020' (SINE2020), and have been enriched through extensive literature review. Besides guiding the work of the professional software engineers in our computing groups, we hope to influence scientists who are willing to contribute their own data treatment software to our community. Moreover, this work may also provide inspiration to scientific software development beyond the neutron and muon field. [ABSTRACT FROM AUTHOR]

Software systems play an ever more important role in our lives and software engineers and their companies find themselves in a position where they are held responsible for ethical issues that may arise. In this paper, we try to disentangle ethical considerations that can be performed at the level of the software engineer from those that belong in the wider domain of business ethics. The handling of ethical problems that fall into the responsibility of the engineer has traditionally been addressed by the publication of Codes of Ethics and Conduct. We argue that these Codes are barely able to provide normative orientation in software development. The main contribution of this paper is, thus, to analyze the normative features of Codes of Ethics in software engineering and to explicate how their value-based approach might prevent their usefulness from a normative perspective. Codes of Conduct cannot replace ethical deliberation because they do not and cannot offer guidance because of their underdetermined nature. This lack of orientation, we argue, triggers reactive behavior such as "cherry-picking," "risk of indifference," "ex-post orientation," and the "desire to rely on gut feeling." In the light of this, we propose to implement ethical deliberation within software development teams as a way out. [ABSTRACT FROM AUTHOR]

The object of research is a distributed order processing system for a restaurant chain. The subject of the research is the analysis of the use of Redis for managing event queues in distributed systems. When implementing a distributed order processing system in a restaurant chain with a possible load of up to 20,000 users per day, the Redis system was used. Management of 9 distributed subsystems was organized through Redis. This solution showed an increase in the performance of the system under heavy load (from 50 transactions per second), but the response time of the system in some cases of its operation was longer than without using Redis. When working systems using Redis, it is necessary to take into account the amount of data with which Redis will work, since it does not exceed the amount of RAM, the absence of differentiation into users and groups, and the absence of a query language, which is replaced by a key-value scheme. This research is aimed at analyzing the operation of the system during trial operation under real load. We compared the operation of a configured system with Redis enabled and disabled. The main indicators for the analysis were the system response time and the maximum request execution time. The research was carried out for 2 weeks, the first week using the system settings with disabled Redis, the second – with enabled Redis. We selected 2 days with a similar load on the system to each other. Especially indicative are the results of comparing the durations of the longest queries, which show an almost constant value of the duration for the system in the mode of enabled Redis. The hypothesis of an increase in the system response time at low loads was confirmed, but this value not only leveled off at a load of 500 unique users but also became less at loads of 1000 unique users. [ABSTRACT FROM AUTHOR]

As part of the evolution of the Space market in the last years – globally referred to as Space 2.0 - small companies are playing an increasingly relevant role in different aerospace projects. Business incubators established by European Space Agency (ESA) and similar entities are evidence of the need of moving initiatives to small companies characterized by greater flexibility to develop specific activities. Software is a key component in most aerospace projects, and the success of the initiatives and projects usually depends on the capability of developing reliable software following well-defined standards. But small entities face some difficulties when adopting software development standards that have been conceived thinking on larger organizations and big programs. The need of defining software development standards tailored to small companies and groups is a permanent subject of discussion not only in the aerospace field, and has led in recent years to the publication of the ISO/IEC 29110 series of systems and software engineering standards and guides, aimed to solve the issues that Very Small Entities (VSEs) () – settings having up to twenty-five people -, found with other standards like CMMI® or SPICE. This paper discusses the tailoring defined by different aerospace organizations for VSEs in the aerospace industry, and presents a conceptual arrangement of the standard based on meta-modeling languages that allow the extension and full customization with the incorporation of specific software engineering requirements and practices from ECSS (European Cooperation for Space Standardization). [ABSTRACT FROM AUTHOR]

The object of research is a distributed order processing system for a restaurant chain. The subject of the research is the analysis of the use of Redis for managing event queues in distributed systems. When implementing a distributed order processing system in a restaurant chain with a possible load of up to 20,000 users per day, the Redis system was used. Management of 9 distributed subsystems was organized through Redis. This solution showed an increase in the performance of the system under heavy load (from 50 transactions per second), but the response time of the system in some cases of its operation was longer than without using Redis. When working systems using Redis, it is necessary to take into account the amount of data with which Redis will work, since it does not exceed the amount of RAM, the absence of differentiation into users and groups, and the absence of a query language, which is replaced by a key-value scheme. This research is aimed at analyzing the operation of the system during trial operation under real load. We compared the operation of a configured system with Redis enabled and disabled. The main indicators for the analysis were the system response time and the maximum request execution time. The research was carried out for 2 weeks, the first week using the system settings with disabled Redis, the second – with enabled Redis. We selected 2 days with a similar load on the system to each other. Especially indicative are the results of comparing the durations of the longest queries, which show an almost constant value of the duration for the system in the mode of enabled Redis. The hypothesis of an increase in the system response time at low loads was confirmed, but this value not only leveled off at a load of 500 unique users but also became less at loads of 1000 unique users. [ABSTRACT FROM AUTHOR]

The use of biometric data (BD) records promises to advance the software engineering field. The rapid adoption of wearable computing technology has widely increased the amount of BD records available. Several aspects about the use of BD records in software engineering field are unknown, such as body measurements used to support daily tasks, and empirical methods that are used to evaluate their benefits. Consequently, a thorough understanding of state-of-the-art techniques still remains limited. This article, therefore, aims at providing a classification and a thematic analysis of studies on the use of BD records in the context of software development. Moreover, it seeks to introduce a classification taxonomy, and pinpoints research gaps, challenges and trends. A systematic mapping of the literature was designed and performed based on well-established practical guidelines. In total, 40 primary studies were analysed and categorised, which were selected by applying a careful filtering process from a sample of 3930 studies to answer seven research questions. Over 77% of articles use more than one biometric aspect to analyse tasks performed by developers; over 47% of articles used eye-track sensor to analyse biometric factors, followed by brain-wearable sensors with 40%, skin sensor with 22%, cardiac sensor with 20%, and others fewer representatives; most studies analysed had their quality assessed as high; most studies were published in journal. This study provides a systematic map of studies that use BD records in software engineering, thereby serving as a basis for future research. [ABSTRACT FROM AUTHOR]

Software development is extremely complex, requiring collaboration between teams and developers who collaborate on various tasks; these activities lead to the generation of an implicit developer social network (DSN). The authors' aim to understand the development process in terms of collaboration between developers. In this work, they conducted an empirical study on mining social collaboration patterns of DSNs for open source software projects based on an integrated approach involving the identification of global and local collaboration patterns among developers based on social network analysis. The bug tracking system‐based DSN (BTS‐DSN) is chosen as an example over the other DSNs since it incorporates larger collaboration activities and actors. The empirical results show that the DSNs, specifically BTS‐DSN, exhibits three different coordination pattern levels (Plan, Aware, and Reflexive) based on their collaboration activities. The mean time to repair metric proves that the Reflexive level occupies the fastest bug fixing time, then the Plan level comes secondly, and lastly the Aware level. In addition, each level group shows different collaboration behaviours among developers; thus, this information can be useful as a resource for better understanding of developer collaboration and collaboration awareness. [ABSTRACT FROM AUTHOR]

In software development, smells are parts of source code that suggest a deeper problem in the system such as duplicated code. Specific knowledge and skills are required for identifying, correcting, and preventing bad code (smells) in the software development process. Such knowledge and skills can be learned, trained, and tuned. Some researchers have evidence about the usage of educational games for motivating, teaching, training, and improving several skills. By using principles of educational games, some authors propose strategies for software development teams to adopt good practices, but these proposals suffer to show different types of code smells and strategies to correct them. In this paper we propose Smellware as a game for teaching best practices in the software development process. The paper describes the game structure and the results of its app. ication in students of software engineering. This proposal aims to strengthen the skills of software developers for identifying and addressing several types of bad code smells and raise awareness about the effects of these bad practices in software development. [ABSTRACT FROM AUTHOR]

Natural user interface (NUI) is considered a recent topic in human–computer interaction (HCI) and provides innovative forms of interaction, which are performed through natural movements of the human body like gestures, voice, and gaze. In the software development process, usability and user eXperience (UX) evaluations are a relevant step, since they evaluate several aspects of the system, such as efficiency, effectiveness, user satisfaction, and immersion. Thus, the goal of the authors' systematic mapping study (SMS) is to identify usability and UX evaluation technologies used by researchers and developers in software with NUIs. Their SMS selected 56 papers containing evaluation technologies for NUI. Overall, the authors identified 30 different usability and UX evaluation technologies for NUI. The analysis of these technologies reveals most of them are used to evaluate software in general, without considering the specificities of NUI. Besides, most technologies evaluate only one aspect, Usability or UX. In other words, these technologies do not consider Usability and UX together. For future work, they intend to develop an evaluation technology for NUIs that fills the gaps identified in their SMS and combining Usability and UX. [ABSTRACT FROM AUTHOR]

In recent years, due to significant evolution in adopting new technologies and development methodologies in the field of software engineering, the developers and researchers are striving to optimize the accuracy of software effort estimation (SEE). The overestimation and underestimation both are the key challenges for software progress; hence, there is a continuous need for an accurate SEE. This paper highlights a systematic review of studies associated with the best practices of use case point (UCP) and expert judgment–based software development effort estimation techniques. The primary aim and contribution of this paper are to support the researchers through an extensive review to ease to other researcher's search for effort estimation studies. We have performed state‐of‐the‐art review from five viewpoints of reference: (a) review of studies concerning UCPs and expert judgment–based effort estimation, (b) research contribution and future recommendation in different novelties, (c) usage of the dataset, (d) availability of accuracy metrics, and (e) findings of the studies. We have performed a systematic review of studies which are published in the period of 2000 to 2019. We have selected a total of 34 primary studies of UCP and expert judgment–based estimation techniques to report the research questions stated in this review. In expert judgment–based technique, the team's skill level is considered to be the most important factor. The researchers prefer to use industrial dataset due to availability of ease. It was investigated that using diverse evaluation accuracy metrics produces conflicting results. On the basis of our studies, we cannot state the results of the UCP method in algorithmic and machine learning approaches to be the most promising. Nevertheless, the SEE accuracy is dependent on the use of datasets, techniques, and evaluation metrics. [ABSTRACT FROM AUTHOR]

The source code suggestions provided by current integrated development environment (IDEs) are mostly dependent on static type learning. These suggestions often end up proposing irrelevant suggestions for a peculiar context. Recently, deep learning-based approaches have shown great potential in the modelling of source code for various software engineering tasks. However, these techniques lack adequate generalisation and resistance to acclimate the use of such models in a real-world software development environment. This Letter presents DeepVS, an end-to-end deep neural code completion tool that learns from existing codebases by exploiting the bidirectional gated recurrent unit (BiGRU) neural net. The proposed tool is capable of providing source code suggestions instantly in an IDE by using pre-trained BiGRU neural net. The evaluation of this work is two-fold, quantitative and qualitative. Through extensive evaluation on ten real-world open-source software systems, the proposed method shows significant performance enhancement and its practicality. Moreover, the results also suggest that DeepVS tool is capable of suggesting zero-day (unseen) code tokens by learning coding patterns from real-world software systems. [ABSTRACT FROM AUTHOR]

The source code suggestions provided by current integrated development environment (IDEs) are mostly dependent on static type learning. These suggestions often end up proposing irrelevant suggestions for a peculiar context. Recently, deep learning‐based approaches have shown great potential in the modelling of source code for various software engineering tasks. However, these techniques lack adequate generalisation and resistance to acclimate the use of such models in a real‐world software development environment. This Letter presents DeepVS, an end‐to‐end deep neural code completion tool that learns from existing codebases by exploiting the bidirectional gated recurrent unit (BiGRU) neural net. The proposed tool is capable of providing source code suggestions instantly in an IDE by using pre‐trained BiGRU neural net. The evaluation of this work is two‐fold, quantitative and qualitative. Through extensive evaluation on ten real‐world open‐source software systems, the proposed method shows significant performance enhancement and its practicality. Moreover, the results also suggest that DeepVS tool is capable of suggesting zero‐day (unseen) code tokens by learning coding patterns from real‐world software systems. [ABSTRACT FROM AUTHOR]

Image‐processing software has always been an integral part of structure determination by cryogenic electron microscopy (cryo‐EM). Recent advances in hardware and software are recognized as one of the key factors in the so‐called cryo‐EM resolution revolution. Increasing computational power has opened many possibilities to consider more demanding algorithms, which in turn allow more complex biological problems to be tackled. Moreover, data processing has become more accessible to many experimental groups, with computations that used to last for many days at supercomputing facilities now being performed in hours on personal workstations. All of these advances, together with the rapid expansion of the community, continue to pose challenges and new demands on the software‐development side. In this article, the development of emcore and emvis, two basic software libraries for image manipulation and data visualization in cryo‐EM, is presented. The main goal is to provide basic functionality organized in modular components that other developers can reuse to implement new algorithms or build graphical applications. An additional aim is to showcase the importance of following established practices in software engineering, with the hope that this could be a first step towards a more standardized way of developing and distributing software in the field. [ABSTRACT FROM AUTHOR]

Today, one of the challenges in software engineering is utilising application lifecycle management (ALM) tools effectively in software development. In particular, it is hard for software developers to engage with the work items that are appointed to themselves in these ALM tools. In this study, the authors have focused on bug tracking in ALM where one of the most important metrics is mean time to resolution that is the average time to fix a reported bug. To improve this metric, they developed a serious game application based on an auction‐based reward mechanism. The ultimate aim of this approach is to create an incentive structure for software practitioners to find and resolved bugs that are auctioned where participants are encouraged to solve and test more bugs in less time and improve quality of software development in a competitive environment. They conduct hypothesis tests by performing a Monte Carlo simulation. The preliminary results of this research support the idea that using a gamification approach for an issue tracking system enhances the productivity and decreases mean time to resolution. [ABSTRACT FROM AUTHOR]

Many systems and software processes overfocus on getting a project and product from an initial set of requirements to an Initial Operational Capability (IOC). Examples are most waterfall and V models. Projects following such processes may pass acceptance tests for functionality and performance, but may leave the product with serious maintainability shortfalls. Many agile processes focus on users' initial usage priorities, but often make development commitments for earlier needs that are incompatible with achieving later critical needs (eg, security, safety). Incremental development process models can do better, but often later increments may find that the earlier increments have not prepared them for ease of modification and repair. Besides increasing Total Ownership Costs (TOCs), long mean times to repair result in long downtimes, which can be critical to an organization's income and reputation. Furthermore, many of these shortfalls take the form of Technical Debt (TD), in that the later they are fixed, the more slow and expensive will be the fixes. This paper summarizes three process frameworks and tools providing more anticipatory ways to improve systems and software maintainability and life‐cycle cost‐effectiveness. The first framework is an Opportunity Tree for identifying and anticipating such ways. The second framework, Software Quality Understanding by Analysis of Abundant Data (SQUAAD), is a toolset for tracking a software project's incremental code commits, and analyzing and visualizing each commit's incremental and cumulative TD. The third framework is a Software/Systems Maintenance Readiness Framework (SMRF), that identifies needed maintenance readiness levels at development decision reviews, similar to the Technology Readiness Levels (TRLs) framework. [ABSTRACT FROM AUTHOR]

Requirement for formation of collaborations has been on increase for the software development industry, especially for smaller to medium sized firms, due to rapid technological advancements, requirements for diversified skills, ever enhancing demands for innovation and fierce competition. Collaborative product development in an alliance enables the firms to benefit from each other’s diversified skills and the experience as a result of which they can develop products more rapidly and of better quality as well resulting in a higher payoff. Also, the development costs decrease. However, to avoid undesired results, selection of an appropriate partner firm for collaboration is of utmost importance keeping in view the objectives of alliance formation of both the strategic partners. One-way partner selection techniques available in the literature are impractical as they enable a firm to rank potential partners only from its own perspective while ignoring their objectives. This problem is addressed by the two-way partner selection techniques, however, they either ignore the payoff distribution criteria or the proposed criteria is unfair. More importantly, existing techniques consider that firm collaborate only with the objective to enhance their financial payoff which might not always be the case. The fact that collaborating firms may have one but different objectives for collaboration, or, each may have multiple objectives is largely neglected. To address the scenarios in which firms may collaborate due to multiple and possibly different objectives, this work proposes a bi-objective game-theoretic model that enables a firm to select an appropriate partner based on the individual preferences of both on the following two objectives: 1) learning and 2) financial revenue. Moreover, this model calculates the pay-off that each firm should get whether only monetary, only in the form of learning or both. The calculation of payoff share is based on the following parameters: 1) individual goals of collaboration of partner selecting firms on the said two objectives, 2) their level of cost contribution, 3) cooperation ratio and 4) knowledge investment difference. Comprehensive analysis of various scenarios is done for the proposed Nash Bargaining payoff distribution model to find the optimum strategy of collaborating firms for each scenario. [ABSTRACT FROM AUTHOR]

Introduction- Software engineering, as a discipline, is represented in a series of subdisciplines and good practices. One of these is software quality assurance, and within it, requirements quality. This research explores and describes the situation in the Eje Cafetero (Colombia), contrasts it with the international literature and proposing lines of action to improve the software development process from the point of view of requirements quality assurance. Objective- Characterize the practices of the local software industry and its relationship to quality assurance, particularly in the requirements phase. Methodology- The methodology used in the research was mainly descriptive and exploratory, in which a non-probabilistic sample was used for convenience in which 23 companies participated and the information was collected through a survey. Results- Input data for the formulation of a model for quality assurance requirements in the local software industry. Conclusions- Most of the projects that are undertaken in the local industry are in the hands of unipersonal organizations or MiPYMES; organizations that mostly avoid following standards or methodologies accepted and recognized worldwide, taking then the definition of requirements, for the case that occupies this article, to a minimum expression and thus increasing the statistics of failed projects. [ABSTRACT FROM AUTHOR]

The authors reflect on some simple rules for scientific software firms to successfully host internship programs for students based on employers' perspective. Among the tips are conducting a thorough interview, planning for the interns' arrival by selecting projects in advance, and introducing the work environment and common tools used. Also cited is the need to assess the interns' performance to determine if they can return for another internship or they can be future hires.

Developing new software tools for analysis of large-scale biological data is a key component of advancing modern biomedical research. Scientific reproduction of published findings requires running computational tools on data generated by such studies, yet little attention is presently allocated to the installability and archival stability of computational software tools. Scientific journals require data and code sharing, but none currently require authors to guarantee the continuing functionality of newly published tools. We have estimated the archival stability of computational biology software tools by performing an empirical analysis of the internet presence for 36,702 omics software resources published from 2005 to 2017. We found that almost 28% of all resources are currently not accessible through uniform resource locators (URLs) published in the paper they first appeared in. Among the 98 software tools selected for our installability test, 51% were deemed “easy to install,” and 28% of the tools failed to be installed at all because of problems in the implementation. Moreover, for papers introducing new software, we found that the number of citations significantly increased when authors provided an easy installation process. We propose for incorporation into journal policy several practical solutions for increasing the widespread installability and archival stability of published bioinformatics software. [ABSTRACT FROM AUTHOR]

Pallet is a very important innovation in logistics industry. Pallets are so widely used that we can find them in nearly every logistical operation scenario. In order to manage pallets efficiently, researchers have developed several pallet management strategies (PMS). The most common and widely accepted PMS includes extensive management of pallets (EMP), transfer of pallet's ownership (TPO), and pallet rent (PR). This paper addresses mainly on how to help pallet managers choose a certain kind of PMS from the perspective of supply chain cost. Firstly, cost models of three kinds of PMS are presented. Secondly, all parameters involved in the models are valued based on data that is collected from industry survey. The results show that the cost of PR is constantly lower than EMP, and also lower than TPO when the operation period is no more than 37 months. Finally, the effect of several important parameters on the cost is studied by sensitivity analysis. The selection strategies of PMS are proposed based on the results. [ABSTRACT FROM AUTHOR]

Author summary Improvements in technology often drive scientific discovery. Therefore, research requires sustained investment in the latest equipment and training for the researchers who are going to use it. Prioritising and administering infrastructure investment is challenging because future needs are difficult to predict. In the past, highly computationally demanding research was associated primarily with particle physics and astronomy experiments. However, as biology becomes more quantitative and bioscientists generate more and more data, their computational requirements may ultimately exceed those of physical scientists. Computation has always been central to bioinformatics, but now imaging experiments have rapidly growing data processing and storage requirements. There is also an urgent need for new modelling and simulation tools to provide insight and understanding of these biophysical experiments. Bioscience communities must work together to provide the software and skills training needed in their areas. Research-active institutions need to recognise that computation is now vital in many more areas of discovery and create an environment where it can be embraced. The public must also become aware of both the power and limitations of computing, particularly with respect to their health and personal data. [ABSTRACT FROM AUTHOR]

Three-dimensional electron microscopy techniques like electron tomography provide valuable insights into cellular structures, and present significant challenges for data storage and dissemination. Here we explored a novel method to publicly release more than 11,000 such datasets, more than 30 TB in total, collected by our group. Our method, based on a peer-to-peer file sharing network built around a blockchain ledger, offers a distributed solution to data storage. In addition, we offer a user-friendly browser-based interface, , for anyone interested to explore and download our data. We discuss the relative advantages and disadvantages of this system and provide tools for other groups to mine our data and/or use the same approach to share their own imaging datasets. [ABSTRACT FROM AUTHOR]

Purpose: The aim of this paper is to show how a specialized planning and guidance application called Fraxinus, can be built on top of the CustusX platform (), which is an open source image-guided intervention software platform. Fraxinus has been customized to meet the clinical needs in navigated bronchoscopy. Methods: The application requirements for Fraxinus were defined in close collaboration between research scientists, software developers and clinicians (pulmonologists), and built on top of CustusX. Its superbuild system downloads specific versions of the required libraries and builds them for the application in question, including the selected plugins. New functionality is easily added through the plugin framework. The build process enables the creation of specialized applications, adding additional documentation and custom configurations. The toolkit’s libraries offer building blocks for image-guided applications. An iterative development process was applied, where the clinicians would test and provide feedback during the entire process. Results: Fraxinus has been developed and is released as an open source planning and guidance application built on top of CustusX. It is highly specialized for bronchoscopy. The proposed workflow is adapted to the different steps in this procedure. The user interface of CustusX has been modified to enhance information, quality assurance and user friendliness with the intention to increase the overall yield for the patient. As the workflow of the procedure is relatively constant, some actions are predicted and automatically performed by the application, according to the requirements from the clinicians. Conclusions: The CustusX platform facilitates development of new and specialized applications. The toolkit supports the process and makes important extension and injection points available for customization. [ABSTRACT FROM AUTHOR]

Software as a Service reflects a 'service‐oriented' approach to software development that is based on the notion of composing applications by discovering and invoking network‐available services to accomplish some task. However, as more business organisations adopt service‐oriented solutions and the demands on them grow, the problem of ensuring that the software systems can adapt fast and effectively to changing business needs, changes in their runtime environment and failures in provided services has become an increasingly important research problem. Dynamic adaptation has been proposed as a way to address the problem. However, for adaptation to be effective several other factors need to be considered. This study identifies the key factors that influence runtime adaptation in service‐oriented systems (SOSs) and examines how well they are addressed in 29 adaptation approaches intended to support SOSs. [ABSTRACT FROM AUTHOR]

In the field of assisted reproductive techniques (ART), computer-assisted sperm analysis (CASA) systems have proved their utility and potential for assessing sperm quality, improving the prediction of the fertility potential of a seminal dose. Although most laboratories and scientific centers use commercial systems, in the recent years certain free and open-source alternatives have emerged that can reduce the costs that research groups have to face. However, these open-source alternatives cannot analyze sperm kinetic responses to different stimuli, such as chemotaxis, thermotaxis or rheotaxis. In addition, the programs released to date have not usually been designed to encourage the scalability and the continuity of software development. We have developed an open-source CASA software, called OpenCASA, which allows users to study three classical sperm quality parameters: motility, morphodmetry and membrane integrity (viability) and offers the possibility of analyzing the guided movement response of spermatozoa to different stimuli (useful for chemotaxis, thermotaxis or rheotaxis studies) or different motile cells such as bacteria, using a single software. This software has been released in a Version Control System at Github. This platform will allow researchers not only to download the software but also to be involved in and contribute to further developments. Additionally, a Google group has been created to allow the research community to interact and discuss OpenCASA. For validation of the OpenCASA software, we analysed different simulated sperm populations (for chemotaxis module) and evaluated 36 ejaculates obtained from 12 fertile rams using other sperm analysis systems (for motility, membrane integrity and morphology modules). The results were compared with those obtained by Open-CASA using the Pearson’s correlation and Bland-Altman tests, obtaining a high level of correlation in all parameters and a good agreement between the different used methods and the OpenCASA. With this work, we propose an open-source project oriented to the development of a new software application for sperm quality analysis. This proposed software will use a minimally centralized infrastructure to allow the continued development of its modules by the research community. [ABSTRACT FROM AUTHOR]

Background: Many medical imaging techniques utilize fitting approaches for quantitative parameter estimation and analysis. Common examples are pharmacokinetic modeling in dynamic contrast-enhanced (DCE) magnetic resonance imaging (MRI)/computed tomography (CT), apparent diffusion coefficient calculations and intravoxel incoherent motion modeling in diffusion-weighted MRI and Z-spectra analysis in chemical exchange saturation transfer MRI. Most available software tools are limited to a special purpose and do not allow for own developments and extensions. Furthermore, they are mostly designed as stand-alone solutions using external frameworks and thus cannot be easily incorporated natively in the analysis workflow. Results: We present a framework for medical image fitting tasks that is included in the Medical Imaging Interaction Toolkit MITK, following a rigorous open-source, well-integrated and operating system independent policy. Software engineering-wise, the local models, the fitting infrastructure and the results representation are abstracted and thus can be easily adapted to any model fitting task on image data, independent of image modality or model. Several ready-to-use libraries for model fitting and use-cases, including fit evaluation and visualization, were implemented. Their embedding into MITK allows for easy data loading, pre- and post-processing and thus a natural inclusion of model fitting into an overarching workflow. As an example, we present a comprehensive set of plug-ins for the analysis of DCE MRI data, which we validated on existing and novel digital phantoms, yielding competitive deviations between fit and ground truth. Conclusions: Providing a very flexible environment, our software mainly addresses developers of medical imaging software that includes model fitting algorithms and tools. Additionally, the framework is of high interest to users in the domain of perfusion MRI, as it offers feature-rich, freely available, validated tools to perform pharmacokinetic analysis on DCE MRI data, with both interactive and automatized batch processing workflows. [ABSTRACT FROM AUTHOR]

People typically rely heavily on visual information when finding their way to unfamiliar locations. For individuals with reduced vision, there are a variety of navigational tools available to assist with this task if needed. However, for wayfinding in unfamiliar indoor environments the applicability of existing tools is limited. One potential approach to assist with this task is to enhance visual information about the location and content of existing signage in the environment. With this aim, we developed a prototype software application, which runs on a consumer head-mounted augmented reality (AR) device, to assist visually impaired users with sign-reading. The sign-reading assistant identifies real-world text (e.g., signs and room numbers) on command, highlights the text location, converts it to high contrast AR lettering, and optionally reads the content aloud via text-to-speech. We assessed the usability of this application in a behavioral experiment. Participants with simulated visual impairment were asked to locate a particular office within a hallway, either with or without AR assistance (referred to as the AR group and control group, respectively). Subjective assessments indicated that participants in the AR group found the application helpful for this task, and an analysis of walking paths indicated that these participants took more direct routes compared to the control group. However, participants in the AR group also walked more slowly and took more time to complete the task than the control group. The results point to several specific future goals for usability and system performance in AR-based assistive tools. [ABSTRACT FROM AUTHOR]

For a long time, it has been tried to delimit the professionalization in the practice of the software and paradigms like programmer, engineer, architect, and developer have been proposed to specify the work of creating computer programs. In an attempt to try to control this work, in many countries professional license is required for those who work with software. All this motivates the present article, in which is analyzed and discusses the struggle to define the software production and explores the possibility that Software Engineering is neither software, nor engineering, nor architecture, nor development, but an integration harmonica of all. [ABSTRACT FROM AUTHOR]

This paper provides a real example of applying COCOMO II as an estimation technique for the required software development effort in a safety-critical software application project following the DO-178C processes. The main goal and contribution of the case study is to support the research on software effort estimation and to provide software practitioners with useful data based on a real project. We applied the method as it is, by correlating the effort multiplier factors with the complexity and objectives introduced by the DO-178C level A application, resulting in an estimated effort. The rationales for each scale factor and effort multiplier selection were also described in detail. By comparing the estimated values with the actual required data, we found a magnitude of relative error (MRE) of 40% and provided alternatives for future work in order to increase the effort estimation accuracy in safety-critical software projects. [ABSTRACT FROM AUTHOR]

The article presents rules to make software that is impactful and usable by using software engineering best practices. It mentions that modern integrated development environments will frequently generate documentation strings automatically as researchers write code, that takes the burden of the need to remember to write comments. It states that people more probably to use it as part of their research if they can quickly start playing with the tool.

Open source software is becoming crucial in the design and testing of quantum algorithms. Many of the tools are backed by major commercial vendors with the goal to make it easier to develop quantum software: this mirrors how well-funded open machine learning frameworks enabled the development of complex models and their execution on equally complex hardware. We review a wide range of open source software for quantum computing, covering all stages of the quantum toolchain from quantum hardware interfaces through quantum compilers to implementations of quantum algorithms, as well as all quantum computing paradigms, including quantum annealing, and discrete and continuous-variable gate-model quantum computing. The evaluation of each project covers characteristics such as documentation, licence, the choice of programming language, compliance with norms of software engineering, and the culture of the project. We find that while the diversity of projects is mesmerizing, only a few attract external developers and even many commercially backed frameworks have shortcomings in software engineering. Based on these observations, we highlight the best practices that could foster a more active community around quantum computing software that welcomes newcomers to the field, but also ensures high-quality, well-documented code. [ABSTRACT FROM AUTHOR]

This paper presents an open-source package developed in Python that controls and drives a programmable Josephson array to synthesize dc and ac quantum-accurate voltages. Programmable arrays are devices subdivided into independent subsections, each counting a number of series connected Josephson junctions that follows a binary sequence (1, 2, 4, 8, …) to control the output voltage. Our software allows to independently measure the current-voltage characteristics of each subsection by means of a set of arbitrary waveform generators and a nanovoltmeter that measures the voltage across the whole array with high sensitivity. A quantization test tool is also provided to check with sub-microvolt resolution whether the array is operating on its quantum margins. The code is modular and easily expandable with the support of many libraries, allowing prompt reconfiguration for different calibration and testing purposes. It is aimed at being a starting point for cooperation between National Metrology Institutes towards the realization of a shared quantum voltage calibration infrastructure. [ABSTRACT FROM AUTHOR]

Graduation projects play an important role in computer engineering careers in which students are expected to draw upon their knowledge and skills that were acquired since admission. To manage the activities of graduation projects, an iterative and incremental approach which aims continuous improvement is proposed as an alternative to a controversial delivery model. However, such integration brings up a set of challenges to be taken into account: e.g. multiple project deliveries, more labor-intensive effort from instructors, and ultimately continuous learning for all participants. One promising way to achieve such an integrated and continuous deployment velocity is to eliminate potential bottlenecks by giving student teams to receive early and continuous feedback. To this end, we propose a continuous feedback and delivery mechanism for managing the life-cycle of a graduation project through draft proposal, literature review, requirements gathering, design, implementation and testing which should produce intermediate outputs at predefined intervals. Most importantly, our approach makes it possible to quantify most of the activities involved in life-cycle process with various rubrics (i.e. measurement scales) that have been purposefully developed. The proposed model promotes the fact that all improvements should be monitored, evaluated and documented. The results of this study indicate that students who were managed using this approach produced better project deliverables and ultimately have delivered better and successful projects. [ABSTRACT FROM AUTHOR]

We analyzed and compared the decision-making processes underlying two approaches that academics might use to decide whether to pursue a professorship or an alternative career: academic coaching (a paid service that supports academics with career-related issues) and decision analysis (a method for applying decision theory to real-world decision problems). To this end, we conducted in-depth expert interviews with seven out of 11 academic coaches known to work in Berlin to examine empirically the career decision-making process that they use. Moreover, we demonstrate theoretically how decision analysis can be applied to an academic’s hypothetical career choice problem. A comparison of the two approaches showed that they both advise (i) structuring the decision problem by dividing it into smaller components, (ii) using the academic’s objectives to generate career alternatives, and (iii) quantifying the uncertainty of decision outcomes using subjective probabilities. Moreover, the observed differences in the way the two approaches structure the decision problem suggest ways in which they could inform each other: (i) they could make use of each other’s techniques to help academics define their objectives and generate career alternatives; (ii) academic coaching could, in addition, use decision trees (a hallmark of decision analysis) to represent the structure of the career decision problem, and use simple measurement scales to quantify how much the career options contribute to the academic’s objectives. [ABSTRACT FROM AUTHOR]

Effy Vayena and colleagues argue that machine learning in medicine must offer data protection, algorithmic transparency, and accountability to earn the trust of patients and clinicians. [ABSTRACT FROM AUTHOR]

In recent years, the explosion of genomic data and bioinformatic tools has been accompanied by a growing conversation around reproducibility of results and usability of software. However, the actual state of the body of bioinformatics software remains largely unknown. The purpose of this paper is to investigate the state of source code in the bioinformatics community, specifically looking at relationships between code properties, development activity, developer communities, and software impact. To investigate these issues, we curated a list of 1,720 bioinformatics repositories on GitHub through their mention in peer-reviewed bioinformatics articles. Additionally, we included 23 high-profile repositories identified by their popularity in an online bioinformatics forum. We analyzed repository metadata, source code, development activity, and team dynamics using data made available publicly through the GitHub API, as well as article metadata. We found key relationships within our dataset, including: certain scientific topics are associated with more active code development and higher community interest in the repository; most of the code in the main dataset is written in dynamically typed languages, while most of the code in the high-profile set is statically typed; developer team size is associated with community engagement and high-profile repositories have larger teams; the proportion of female contributors decreases for high-profile repositories and with seniority level in author lists; and, multiple measures of project impact are associated with the simple variable of whether the code was modified at all after paper publication. In addition to providing the first large-scale analysis of bioinformatics code to our knowledge, our work will enable future analysis through publicly available data, code, and methods. Code to generate the dataset and reproduce the analysis is provided under the MIT license at . Data are available at . [ABSTRACT FROM AUTHOR]

Objective: There is a need for structure to achieve functional patient engagement within mental healthcare organizations, and for clarification on how to proceed on a strategic level. The aim of this paper is to shed light on the implementation of a strategic organizational structure for patient engagement in mental health by examining why and how to implement a structure, the organizational and environmental factors that facilitate or limit the process, and the perceived consequences of the implementation. Method: This paper evaluates the implementation of a strategic committee for patient engagement in a mental healthcare organization in Montreal (Quebec, Canada). The research was designed as a qualitative single case study using a deductive approach by means of a conceptual framework. Data sources consisted in ten semi-structured interviews, three focus groups, and organizational documents. Results: The strategic committee for patient engagement was implemented as a means to formalize patient partner participation, following the introduction of a vision of full citizenship. Important aspects of its implementation included its composition and role, the elaboration of a framework for patient partner participation, and finally, ongoing application and evaluation of the framework. Several facilitating factors were identified, including executive management support, leadership, and a vision behind the participation. Limiting factors mainly consisted of resistance towards patient participation and the existence of stigma. Consequences included increased and improved patient engagement, as well as reduced stigma within the organization. Conclusion: This study shows that the implementation of a strategic organizational structure for patient engagement is comprehensive. It further shows the importance of a vision and an articulate leadership involving several actors. Further research is needed regarding the impact of this type of strategic structure on a clinical level. [ABSTRACT FROM AUTHOR]

Modern bioinformatics and computational biology are fields of study driven by the availability of effective software required for conducting appropriate research tasks. Apart from providing reliable and fast implementations of different data analysis algorithms, these software applications should also be clear and easy to use through proper user interfaces, providing appropriate data management and visualization capabilities. In this regard, the user experience obtained by interacting with these applications via their Graphical User Interfaces (GUI) is a key factor for their final success and real utility for researchers. Despite the existence of different packages and applications focused on advanced data visualization, there is a lack of specific libraries providing pertinent GUI components able to help scientific bioinformatics software developers. To that end, this paper introduces GC4S, a bioinformatics-oriented collection of high-level, extensible, and reusable Java GUI elements specifically designed to speed up bioinformatics software development. Within GC4S, developers of new applications can focus on the specific GUI requirements of their projects, relying on GC4S for generalities and abstractions. GC4S is free software distributed under the terms of GNU Lesser General Public License and both source code and documentation are publicly available at [ABSTRACT FROM AUTHOR]