Search

BackgroundAimMethod & ProceduresOutcomes & ResultsConclusionsAphasia therapy software: aninvestigation of the research literature and the challenges of software developmentDigital aphasia therapy has become increasingly popular over the past years. However, not all software described in the literature appears to reach clinical practice. It is currently unclear why this is the case.We had two aims. First, we aimed to create an overview of the digital aphasia therapy described and its clinical availability bysystematically searching and reviewing the research literature. Second, we aimed to investigate the experiences of researchers/developers of aphasia therapy software.We conducted a systematic search and review, screening references against our inclusion criteria. Clinical availability of the software was established through reading literature, conducting internet searches, and by contacting the researchers/developers who were associated with the software. Researchers/developers of the reported software were surveyed about their experiences with software development. Responses were the matically analysed into themes and subthemes.We identified a total of 63 unique pieces of software across 125 references. The software was mainly developed for English speakers and mainly focused on word retrieval or a combination of language skills. We established clinical availability with certainty for 35 pieces of software, with the remaining software (likely) currently clinically unavailable. From the survey data, we identified five recurring themes: 1) software development can be expensive and insufficient funding hinders their clinical availability; 2) commercialisation of software is often new and daunting to researchers but essential for making software available; 3) clinicians and people with aphasia are valuable sources of feedback; 4) working with software developers can be difficult; and 5) aphasia therapy software should combine both the evidence base and current clinical need.Aminority of aphasia therapy software described in the literature reaches clinical practice. It is clear that the development and subsequent dissemination of aphasia therapy software requires large amounts of time, energy, and funds but we conclude that this is essential for successful clinical implementation. [ABSTRACT FROM AUTHOR]

Organisations are becoming concerned with effectively dealing with privacy-related requirements. Existing Requirements Engineering methods based on structured natural language suffer from several limitations both in eliciting and specifying privacy requirements. In our previous study, we proposed a structured natural-language approach called the "Privacy Criteria Method" (PCM), which demonstrates potential advantages over user stories. Our goal is to present a PCM evaluation that focused on the opinions of software practitioners from different companies on PCM's ability to support the specification of privacy requirements and the quality of the privacy requirements specifications produced by these software practitioners. We conducted a multiple case study to evaluate PCM in four different industrial contexts. We gathered and analysed the opinions of 21 practitioners on PCM usage regarding Coverage, Applicability, Usefulness, and Scalability. Moreover, we assessed the syntactic and semantic quality of the PCM artifacts produced by these practitioners. PCM can aid developers in elaborating requirements specifications focused on privacy with good quality. The practitioners found PCM to be useful for their companies' development processes. PCM is considered a promising method for specifying privacy requirements. Some slight extensions of PCM may be required to tailor the method to the characteristics of the company. [ABSTRACT FROM AUTHOR]

Historically, activities related to software development have been led by men, with weak participation from women. Currently, initiatives have been promoted to increasingly integrate women into this discipline. However, despite the known benefits of gender diversity in innovation and team performance, the visibility of women in this field remains weak. The primary objective of this article is to analyze strategies to attract female talent to the software development industry, aiming to reduce the gender gaps that women face. The methodology used in this work is based on several steps of systematic literature mapping, which seeks to provide a comprehensive overview of the literature on this topic, classify the findings, and offer a framework for future research in this area. The main findings highlight the need for organizational policies and work practices that promote gender equality, as well as the importance of early education and training in retaining female talent in the software industry. This study not only contributes to academic discourse but also suggests practical measures for industry professionals to foster a more inclusive and equitable work environment. [ABSTRACT FROM AUTHOR]

The goal of this research study was to identify and prioritize the significant cybersecurity challenges that vendor firms encounter during software development. Using Systematic Literature Reviews (SLRs), 13 significant challenges were found, including “Security issues/Access of Cyberattacks”, “Lack of Right Knowledge”, “Cost Security Issues”, and “Lack of Confidentiality and Trust” among others. To address these concerns, a multifaceted strategy that prioritizes continuing education, training, and investment in cybersecurity measures, as well as cross‐industry cooperation and coordination with government entities, is required. These challenges were ranked using the Fuzzy Analytic Hierarchy Process (F‐AHP). We obtained the following results after applying the Fuzzy Analytic Hierarchy Process: CSC1 (Cyber Security Challenge‐1) “Security Issues/Access of Cyber Attacks”, CSC2 “Lack of Right Knowledge”, and CSC3 “Framework” are the top most critical cyber security challenges, with weightages of 0.1687, 0.1672, and 0.1194, respectively. This study lays the groundwork for future research and assists vendor organizations in addressing the cybersecurity concerns they face during software development. The study also emphasizes the significance of addressing cybersecurity during the software development process in order to avoid the financial and reputational losses associated with cyber intrusions. [ABSTRACT FROM AUTHOR]

Quantum computing is tipped to lead the future of global technological progress. However, the obstacles related to quantum software development are an actual challenge to overcome. In this scenario, this work presents an implementation of the quantum search algorithm in Atos Quantum Assembly Language (AQASM) using the quantum software stack my Quantum Learning Machine (myQLM) and the programming development platform Quantum Learning Machine (QLM). We present the creation of a virtual quantum processor whose configurable architecture allows the analysis of induced quantum noise effects on the quantum algorithms. The codes are available throughout the manuscript so that readers can replicate them and apply the methods discussed in this article to solve their own quantum computing projects. The presented results are consistent with theoretical predictions and demonstrate that AQASM and QLM are powerful tools for building, implementing, and simulating quantum hardware. [ABSTRACT FROM AUTHOR]

Copyright of ABI Technik is the property of De Gruyter and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Copyright of Bearing is the property of Bearing Editorial Office and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Copyright of Journal of Irrigation & Drainage is the property of Journal of Irrigation & Drainage Editorial Office and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

The responsibility for creating accessible software within the development of digital services is important for multiple reasons, mainly equity and inclusion. However, adopting and sustaining the development of accessible digital solutions has always been challenging, more so in countries that are relatively new to the concept of universal design, and physical and digital accessibility, and where legal sanctions are not yet established. This work investigates the technology scene in the State of Kuwait and analyses the responses of computing professionals with regard to their skills, best practices and procurement of accessible tech and to their level of awareness toward people with disabilities. The findings reveal a low level of awareness among tech professionals with regard to disabilities and digital accessibility-related standards. The findings also highlight a lack of available guidance for developing inclusive design and accessibility. Additionally, time constraints, lack of training, legal enforcement and fundamentals concepts during undergraduate and higher education contributed to observed weaknesses. Participants were keen to learn more and benefited from flyers and free professional development courses offered as incentives for survey completion. [ABSTRACT FROM AUTHOR]

During scrum iterations, it is possible to apply cost forecasting for software testing and operation, if the data from previous iterations are known. Since the data for estimating the scope of work and the deadline within one sprint are accumulated during the project execution, it is possible to use such data to build a forecasting algorithm for the estimated parameters of the subsequent sprints. The approach is based on refining the assessment provided by the development team and the scrum master in a specific metric. The main parameters for evaluation are the execution time and the amount of work performed. As a result of forecasting, it is possible to obtain clarifications for the team’s assessment regarding the scope of work for the next sprint. This estimate is based on planned and actual data from the previous sprints. The article discusses the method of least squares and the proposed code for a machine learning model based on this method. An example and graphs for iterations in scrum and corresponding forecasting for the next sprints are presented. The use of the least squares method allows creating a mathematical model that can be adapted to different project conditions, providing flexibility and accuracy in forecasting. For example, the study uses the real data from the previous sprints, which includes the team’s resource assessment and actual expenditures. Based on these data, a model was built that demonstrates a high correlation between predicted and actual costs, confirming the effectiveness of using the least squares method. So, the least squares method is an effective tool for forecasting software development costs in scrum iterations. This method allows development teams to better plan their resources and timelines, contributing to the overall efficiency of the project [ABSTRACT FROM AUTHOR]

In this study, we explore the future of work by examining differences in productivity when teams are composed of only humans or both humans and machine agents. Our objective was to characterize the similarities and differences between human and human–machine teams as they work to coordinate across their specialized roles. This form of research is increasingly important given that machine agents are becoming commonplace in sociotechnical systems and playing a more active role in collaborative work. One particular class of machine agents, bots, is being introduced to these systems to facilitate both taskwork and teamwork. We investigated the association between bots and productivity outcomes in open source software development through an analysis of hundreds of project teams. The presence of bots in teams was associated with higher levels of productivity and higher work centralization in addition to greater amounts of observed communication. The adoption of bots in software teams may have tradeoffs, in that doing so may increase productivity, but could also increase workload. We discuss the theoretical and practical implications of these findings for advancing human–machine teaming research. This research characterizes the changing landscape of collaborative work brought on by the increasing presence of autonomous machine agents in teams. We report on a multidimensional analysis of work in software development projects examining differences between human‐only and human‐bot teams. [ABSTRACT FROM AUTHOR]

Software development projects face significant risks of going over budget, over schedule, and of failing to deliver expected benefits. These risks have endured despite methodological changes within the industry, such as the rise in popularity of Agile. This research looks outside of the software industry and seeks inspiration from film production, which has developed different management strategies to address challenges similar to those faced by software development projects. First, an analysis of film production project management reveals four principles, each evidenced by a set of practices used throughout the industry. Next, we identify sets of practices that would enable software development projects to also align to those same four principles. The synthesis of each principle from its set of supporting film production practices is then validated through structured interviews with veteran film producers. Lastly, the derivation of each principle to a parallel set of supporting practices within the context of software development is validated in a second series of interviews with experienced software development project managers. In total, this research identifies a set of software development project management practices that mirror film production practices. These practices offer a framework for software development project managers to consider when seeking to tailor existing methodologies, particularly in scenarios that present challenges similar to those encountered in film production. [ABSTRACT FROM AUTHOR]

Copyright of Revista Espacios is the property of Talleres de Impresos Oma and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Over the last thirty years, In the field of digital philology, several generic IT tools have been developed to produce digital scholarly editions (DSE). However, the majority of DSEs continue to be produced using custom-developed tools. This trend is unsustainable, but it is because generic tools are often less usable, difficult to customize, and unsuitable for the scientific objectives of scholars. The scientific community has been exploring how to create flexible and effective tools for digital philology. Two main responses have emerged in the literature: the need for shared editorial models that represent philologists’ desiderata, and the adoption of software engineering practices to produce more robust, durable, and easily maintainable tools. This article presents a modeling strategy that considers both perspectives and is based on the creation of a network of editorial models, each one theoretically framed within the philological approach in which it has emerged. The editorial models, formalized as ontologies, can be applied as conceptual models to determine the logical organization and functioning of a tool for digital philology, thanks to the principles of domain-driven design.