Search

Over and above technical skills, software development graduates need to also poses team-based skills, such as, leadership, oral communication and project management by the time they graduate from tertiary institutions. In order to fulfil this requirement, institutions introduced a project-based module, generally referred to as capstone, to be undertaken by students on the their final year. The essence of this module, amongst other things, is to expose students to the real-world professional experience through partnership with industry. Much research has been conducted on students software projects, but very little investigation has gone into understanding how students evaluate the success of their projects. In is in this light that this study was conducted. A systematic literature review (SLR) was performed on empirical studies published between 2000 and 2022, to establish criteria used by students in evaluating software project success. The investigation led to the discovery of one (1) paper, which identified three most important success criteria used by students. However, this study identified some short-comings (eg students had to pretend to be employed graduates when evaluating the imaginary projects) with the approach used by the abovementioned research paper in determining the students' success criteria. Beside the fact that there is only one study that was found that addresses the study's phenomenon, the identified short-comings on the paper indicate that there is a need for empirical research studies on this matter. [ABSTRACT FROM AUTHOR]

Identifying and understanding reasons for deriving software development defects is crucial for ensuring software product quality attributes such as maintainability. This paper presents a systematic literature review and the objective is to analyze the suggestions of other authors regarding software code defect prediction using machine learning, deep learning, or other artificial intelligence methods for the identification of software quality. The systemic literature review reveals that many analyzed papers considered multiple software code defects, but they were analyzed individually. However, more is needed to identify software quality attributes. The more profound analysis of code smells indicates the significance when considering multiple detected code smells and their interconnectedness; it helps to identify the software quality sub-attributes of maintainability. [ABSTRACT FROM AUTHOR]

The HCS12 microcontroller and DRAGON12-Light Trainer boards are extensively utilized in microprocessor system design education. This paper details the rationale, approach, and outcomes from implementing the DRAGON12-Light Trainer board in teaching an upper-level undergraduate microprocessors course at Oakland University. The course's primary goal is for students to acquire the skills necessary to design both hardware and software for microprocessor-based systems, with applications across various industries. The paper assesses the effectiveness of employing the Motorola HCS12 microcontroller for its real-world relevance and integrates the Freescale CodeWarrior IDE v5.1 environment for software development. This research uniquely contributes by measuring the improvement in students' practical skills, specifically in hardware and software design using assembly and C programming, through hands-on lab assignments. It reports on the development of students' abilities to engage in microprocessor-based system design and critically evaluates the applied aspects of pedagogy by incorporating the DRAGON12-Light Trainer in lab exercises, such as those involving 'Measuring Human Reaction Time' and 'Servo motor interfacing.' Quantitative results, derived from student surveys and assessments, indicate significant improvements in students' programming competencies. The paper provides statistical results showcasing the increase in students' self-rated confidence levels in assembly and C language programming before and after course completion. Additionally, qualitative insights are discussed, reflecting students' experiences and the perceived applicability of the skills they acquired. These results underscore the pedagogical value of integrating practical training devices like the DRAGON12-Light Trainer board into microprocessors curricula. [ABSTRACT FROM AUTHOR]

This paper provides a concise overview of Agile and DevOps methodologies in software engineering. It aims to introduce readers to the fundamental principles of Agile and DevOps, accompanied by brief descriptions and practical examples. The advantages and disadvantages of each methodology are discussed, followed by a comparative analysis highlighting key differences. Understanding these methodologies is crucial in today’s IT landscape, as they are commonly employed in various organizations, impacting project management, team collaboration, and product delivery. This paper serves as a valuable resource for individuals seeking a basic understanding of Agile and DevOps methodologies in software engineering. [ABSTRACT FROM AUTHOR]

Unit testing is a fundamental aspect of software development, ensuring the correctness and robustness of code implementations. Traditionally, unit tests are manually crafted by developers based on their understanding of the code and its requirements. However, this process can be time-consuming, errorprone, and may overlook certain edge cases. In recent years, there has been growing interest in leveraging large language models (LLMs) for automating the generation of unit tests. LLMs, such as GPT (Generative Pre-trained Transformer), CodeT5, StarCoder, LLaMA, have demonstrated remarkable capabilities in natural language understanding and code generation tasks. By using LLMs, researchers aim to develop techniques that automatically generate unit tests from code snippets or specifications, thus optimizing the software testing process. This paper presents a literature review of articles that use LLMs for unit test generation tasks. It also discusses the history of the most commonly used large language models and their parameters, including the first time they have been used for code generation tasks. The result of this study presents the large language models for code and unit test generation tasks and their increasing popularity in code generation domain, indicating a great promise for the future of unit test generation using LLMs. [ABSTRACT FROM AUTHOR]

The research paper represents a novel approach to the design and optimization of a compiler for a domain-specific language (DSL) focused on geometric shape creation and manipulation. The primary objective is to develop a compiler capable of generating efficient machine code while offering users a high level of abstraction. The paper begins with an overview of DSLs and compilers, emphasizing their importance in software development. Next, it outlines the specific requirements of the geometric shape DSL and proposes a compiler design that addresses them. This innovative approach considers DSL's unique features, such as shape creation and manipulation, and aims to generate high-quality machine code. The paper also discusses optimization techniques to enhance the generated code's quality and performance, including loop unrolling and instruction scheduling. These optimizations are particularly suited to the DSL, which focuses on geometric shape creation and manipulation and are integral to achieving efficient machine code generation. In conclusion, the paper emphasizes the novelty of this approach to DSL compiler design and anticipates exciting results from testing the compiler developed for the geometric shape DSL. [ABSTRACT FROM AUTHOR]

UML diagrams are a base for the planning of development in most software projects. It is used for representing different artefacts during software development and project structure. The use case is one of the diagrams in Unified Modelling Language (UML), which allows describing the dynamic flow of the system. There are a lot of tools that are used for creating this diagram before starting the actual coding process, and the diagram needs to be specific and easily understandable. Meantime, the creation of a UML use case diagram from scratch for complex systems can be time-consuming and confusing for people, which needs to be optimised. The authors of the paper attempt to solve the addressed problem. Therefore, in this research paper a new definition for UML use case diagrams will be introduced, where the main question will be whether it is possible to formalise use case modelling by introducing pre-defined use case patterns. This is academic research and discussion, which is based on the analysis of advanced UML tools, which use case diagram templates contain. The solution to this research question contains an initial set of UML use case patterns, created by analysing of the existing use case diagram templates. Moreover, in order to validate work, the pre-defined patterns were demonstrated on a developed prototype. The operation principle of the prototype focused on giving the ability to the user to construct a use case diagram by the combination of pre-defined patterns. The prototype can be useful for the development/management process in case of correct implementation. It will allow decreasing spent time on the use case diagram creation as well as avoid creating anti-patterns. [ABSTRACT FROM AUTHOR]

This research paper explores the role of code analyzer that takes the help of tokenization in its working. To assure code quality and maintainability, code analysis is essential in software development. In the context of the Java programming language, this paper provides a creative approach to code analysis utilizing tokenization. Our code analyzer allows for an accurate assessment of code structure, dependencies, and patterns by tokenizing source code into understandable units. The suggested analyzer, which uses token-based methodologies, aids in the correct identification of possible defects, and performance bottlenecks. It provides vital information for developers to improve code readability, modularization, and best practices adherence. The experimental findings show that the tokenization-based technique is successful and efficient in increasing overall code quality and maintainability. [ABSTRACT FROM AUTHOR]

Scaled agile development approaches are now used widely in modern software engineering, allowing businesses to improve teamwork, productivity, and product quality. The incorporation of artificial intelligence (AI) into scaled agile development methods (SADMs) has emerged as a potential strategy in response to the ongoing demand for simplified procedures and the increasing complexity of software projects. This paper explores the intersection of AI-driven assistants within the context of the scaled agile framework (SAFe) for large-scale software development, as it stands out as the most widely adopted framework. Our paper pursues three principal objectives: (1) an evaluation of the challenges and impediments encountered by organizations during the implementation of SADMs, (2) an assessment of the potential advantages stemming from the incorporation of AI in large-scale contexts, and (3) the compilation of aspects of SADMs that AI-driven assistants enhance. Through a comprehensive systematic literature review, we identified and described 18 distinct challenges that organizations confront. In the course of our research, we pinpointed seven benefits and five challenges associated with the implementation of AI in SADMs. These findings were systematically categorized based on their occurrence either within the development phase or the phases encompassing planning and control. Furthermore, we compiled a list of 15 different AI-driven assistants and tools, subjecting them to a more detailed examination, and employing them to address the challenges we uncovered during our research. One of the key takeaways from this paper is the exceptional versatility and effectiveness of AI-driven assistants, demonstrating their capability to tackle a broader spectrum of problems. In conclusion, this paper not only sheds light on the transformative potential of AI, but also provides invaluable insights for organizations aiming to enhance their agility and management capabilities. [ABSTRACT FROM AUTHOR]

The paper casts a spotlight on one of the manifold legal questions that arise with the proliferation of artificial intelligence. This new technology is attractive for many fields, including public administration, where it promises greater accuracy and efficiency, freeing up resources for better interaction and engagement with citizens. However, public powers are bound by certain constitutional constraints that must be observed, regardless of whether decisions are made by humans or machines. This includes the non-delegation principle, which aims to limit the delegation and sub-delegation of decisions affecting citizens' rights in order to ensure governmental accountability, reviewability, and contestability. This puts some constraints on the automation of decision-making by public entities, as algorithmic decision-making entails delegating decisions to software development companies on the one hand, and to algorithms on the other. The present paper reveals and explains these constraints and concludes with suggestions to navigate these conflicts in a manner that satisfies the rule of law while maximizing the benefits of new technologies. [ABSTRACT FROM AUTHOR]

What is project management leadership? If we consider the most important traits, can some of them be replaced by artificial intelligence? We'll explore some of the tools you can use today to streamline your administrative burden. Will these tools replace a human in the loop managing the actual project, or just enhance their ability to lead? To answer that question, we first have to ask what we think leadership is, can it be reduced to a checklist, and what tools are available today to make those decisions? The term "AI" covers many tasks including machine learning and deep learning. Every software vendor seems to claim it now has AI, and is the best solution. The output is still determined by processing data and looking for patterns and decisions were made during software development on priorities and guardrails. If we consider repetitive tasks, or ones that need to process vast amounts of data, the tools seem tailor made for projects. By definition, a project is a one-time event. It may be close in execution to other projects, but each is stand alone. It doesn't mean you can't learn, but it does mean there is a new path to blaze. Will we let computers make decisions? Will we require each decision to have human oversight? What if the computer (that has been programmed) makes what we consider to be a faulty decision? Who is to blame? As project management practices evolve, organizations are increasingly turning to innovative technologies to address the complexities of project execution. Artificial Intelligence (AI) offers a transformative approach to project management, providing intelligent automation, predictive analytics, and data-driven insights. This paper explores the role of AI in revolutionizing traditional project management methodologies. [ABSTRACT FROM AUTHOR]

In the rapid development of urban construction, underground pipelines play a crucial role. However, the current underground pipelines have poor association with relevant management departments, and there are deficiencies in data completeness, accuracy, and information content. Managing and sharing information resources is relatively difficult, transforming the constructed 3D underground pipeline geographic information systems into an 'Information silo'. This results in redundant construction and resource wastage of underground utilities. The complex distribution characteristics of underground utilities make rapid batch modeling and post-model maintenance challenging. Therefore, researching a 3D spatial data fusion model for urban underground utilities becomes particularly important. Given the above problem, this paper proposes a spatial data fusion model for underground pipeline scene modeling. It elaborates on the geometric, semantic, and temporal characteristics of underground pipelines, encapsulating these features. With underground pipeline objects as the core and pipeline characteristics as the foundation, a spatial data fusion model integrating multiple characteristics of underground pipelines has been constructed. Through software development, the data model designed in this paper facilitates rapid construction of underground pipeline scenes. This further enhances the consistency and integrity of underground pipeline data, enabling shared resources and comprehensive supervision of facility operations on a daily basis. [ABSTRACT FROM AUTHOR]

In recent years, microservices, as an emerging technology in software development, have been favored by developers due to their lightweight and low-coupling features, and have been rapidly applied to the Internet of Things (IoT) and Internet of Vehicles (IoV), etc. Microservices deployed in each unit of the IoV use wireless links to transmit data, which exposes a larger attack surface, and it is precisely because of these features that the secure and efficient placement of microservices in the environment poses a serious challenge. Improving the security of all nodes in an IoV can significantly increase the service provider's operational costs and can create security resource redundancy issues. As the application of reinforcement learning matures, it is enabling faster convergence of algorithms by designing agents, and it performs well in large-scale data environments. Inspired by this, this paper firstly models the placement network and placement behavior abstractly and sets security constraints. The environment information is fully extracted, and an asynchronous reinforcement-learning-based algorithm is designed to improve the effect of microservice placement and reduce the security redundancy based on ensuring the security requirements of microservices. The experimental results show that the algorithm proposed in this paper has good results in terms of the fit of the security index with user requirements and request acceptance rate. [ABSTRACT FROM AUTHOR]

General-purpose Petri Net Simulator (GPenSIM) is a new tool for modelling and simulating discrete systems. GPenSIM was developed using the Iterative Approach, which divides the software development life-cycle into smaller tasks. In each iteration, we add more functionality. However, GPenSIM was created to model industrial applications and academic purposes (teaching and research). Hence, in each iteration, some industrial, real-life, and large discrete systems are modelled, and the experiences received from these projects are also incorporated into the tool development. This paper follows the development of GPenSIM through three major iterations and explains the importance and lessons learned during these iterations. [ABSTRACT FROM AUTHOR]

Test-driven development (TDD) is an agile practice of writing test code before production code, following three stages: red, green, and refactor. In the red stage, the test code is written; in the green stage, the minimum code necessary to make the test pass is implemented, and in the refactor stage, improvements are made to the code. This practice is widespread across the industry, and various studies have been conducted to understand its benefits and impacts on the software development process. Despite its popularity, TDD studies often focus on the technical aspects of the practice, such as the external/internal quality of the code, productivity, test smells, and code comprehension, rather than the context in which it is practiced. In this paper, we present a systematic literature review using Scopus, Web of Science, and Google Scholar that focuses on the TDD practice and the influences that lead to the introduction of test smells/anti-patterns in the test code. The findings suggest that organizational structure influences the testing strategy. Additionally, there is a tendency to use test smells and TDD anti-patterns interchangeably, and test smells negatively impact code comprehension. Furthermore, TDD styles and the relationship between TDD practice and the generation of test smells are frequently overlooked in the literature. [ABSTRACT FROM AUTHOR]

Effort estimation is a crucial aspect of software development, as it helps project managers plan, control, and schedule the development of software systems. This research study compares various machine learning techniques for estimating effort in software development, focusing on the most widely used and recent methods. The paper begins by highlighting the significance of effort estimation and its associated difficulties. It then presents a comprehensive overview of the different categories of effort estimation techniques, including algorithmic, model-based, and expert-based methods. The study concludes by comparing methods for a given software development project. Random Forest Regression algorithm performs well on the given dataset tested along with various Regression algorithms, including Support Vector, Linear, and Decision Tree Regression. Additionally, the research identifies areas for future investigation in software effort estimation, including the requirement for more accurate and reliable methods and the need to address the inherent complexity and uncertainty in software development projects. This paper provides a comprehensive examination of the current state-of-the-art in software effort estimation, serving as a resource for researchers in the field of software engineering. [ABSTRACT FROM AUTHOR]

Purpose: This study identifies the main area and current dynamics of Corporate Philanthropy (CP) and offers recommendations for future research directions. Design/methodology/approach: Using bibliometrics, we examined a sample of 558 studies from Scopus, an online abstract and citation repository, to examine the research activities relating to CP between 1955 and 2022. Articles and authors with high citation impact scores are identified based on the publication’s position and significance within the field. We then explore contemporary issues, identify possible limitations towards the development of the literature, and propose new lines of inquiry for future studies. Findings: In addition to providing an in-depth analysis, this study discusses recent discoveries and shifts in mindsets pertaining to Corporate Philanthropy, taking into account previously documented findings which regarded CP disadvantageous to many companies mainly due to money outflow. The ‘agency theory’ considers the relationship between a principal and its hired representative. Past reports cited managers leveraging on CP as a way to justify unnecessary expenses. Meanwhile, the latest studies discovered that CP brings in various advantages to the companies such as additional profit avenues, enhanced visibility, and stronger market presence, benefiting its stakeholders and securing the sustainability of those companies. Future research on CP can be expanded through our suggested research directions. Research limitations/implications: This study focuses on using the Scopus database as the primary source of the journals. Hence, our findings may differ from the studies conducted using other databases. Originality/value: This is among the pioneer studies using Harzing and VOSviewer software to analyse the development of CP studies. Several future research agendas are generated due to the review, which focuses on annual publication trends, the most prolific authors, the most cited papers, the most prolific countries, the most prolific institutions and the most abundant sources. [ABSTRACT FROM AUTHOR]

Artificial intelligence (AI) has witnessed an exponential increase in use in various applications. Recently, the academic community started to research and inject new AI-based approaches to provide solutions to traditional software-engineering problems. However, a comprehensive and holistic understanding of the current status needs to be included. To close the above gap, synthetic knowledge synthesis was used to induce the research landscape of the contemporary research literature on the use of AI in software engineering. The synthesis resulted in 15 research categories and 5 themes—namely, natural language processing in software engineering, use of artificial intelligence in the management of the software development life cycle, use of machine learning in fault/defect prediction and effort estimation, employment of deep learning in intelligent software engineering and code management, and mining software repositories to improve software quality. The most productive country was China (n = 2042), followed by the United States (n = 1193), India (n = 934), Germany (n = 445), and Canada (n = 381). A high percentage (n = 47.4%) of papers were funded, showing the strong interest in this research topic. The convergence of AI and software engineering can significantly reduce the required resources, improve the quality, enhance the user experience, and improve the well-being of software developers. [ABSTRACT FROM AUTHOR]

Recent advancements in Large Language Models (LLMs) like ChatGPT and Copilot have led to their integration into various educational domains, including software development education. Regular use of LLMs in the learning process is still not well-researched; thus, this paper intends to fill this gap. The paper explores the nuanced impact of informal LLM usage on undergraduate students' learning outcomes in software development education, focusing on React applications. We carefully designed an experiment involving thirty-two participants over ten weeks where we examined unrestricted but not specifically encouraged LLM use and their correlation with student performance. Our results reveal a significant negative correlation between increased LLM reliance for critical thinking-intensive tasks such as code generation and debugging and lower final grades. Furthermore, a downward trend in final grades is observed with increased average LLM use across all tasks. However, the correlation between the use of LLMs for seeking additional explanations and final grades was not as strong, indicating that LLMs may serve better as a supplementary learning tool. These findings highlight the importance of balancing LLM integration with the cultivation of independent problem-solving skills in programming education. [ABSTRACT FROM AUTHOR]

This paper extends the FAIR (Findable, Accessible, Interoperable, Reusable) guidelines to provide criteria for assessing if software conforms to best practices in open source. By adding "USE" (User-Centered, Sustainable, Equitable), software development can adhere to open source best practice by incorporating user-input early on, ensuring front-end designs are accessible to all possible stakeholders, and planning long-term sustainability alongside software design. The FAIR-USE4OS guidelines will allow funders and researchers to more effectively evaluate and plan open-source software projects. There is good evidence of funders increasingly mandating that all funded research software is open source; however, even under the FAIR guidelines, this could simply mean software released on public repositories with a Zenodo DOI. By creating FAIR-USE software, best practice can be demonstrated from the very beginning of the design process and the software has the greatest chance of success by being impactful. Author summary: This research builds on the FAIR principles to ensure research software adheres to open-source development best practice, which includes community engagement and early planning for long-term sustainability. By creating guidelines ("FAIR-USE4OS") that can be followed, funders and researchers are in a stronger position to evaluate and create research software with maximal chance of success. This research is important as open-source software that is not "FAIR-USE" has a lower probability of long-term impact. These guidelines will help benefit and impact society once they are widely accepted by researchers and funders, which could happen within a relatively short time period given good evidence that funders are actively including and updating open source policies, which directly impact upon how research is conducted. [ABSTRACT FROM AUTHOR]

Software practitioners use various methods in Requirements Engineering (RE) to elicit, analyze, and specify the requirements of enterprise products. The methods impact the final product characteristics and influence product delivery. Ad-hoc usage of the methods by software practitioners can lead to inconsistency and ambiguity in the product. With the notable rise in enterprise products, games, and so forth across various domains, Virtual Reality (VR) has become an essential technology for the future. The methods adopted for RE for developing VR products requires a detailed study. This article presents a mapping study on RE methods prescribed and used for developing VR applications including requirements elicitation, requirements analysis, and requirements specification. Our study provides insights into the use of such methods in the VR community and suggests using specific RE methods in various fields of interest. We also discuss future directions in RE for VR products. [ABSTRACT FROM AUTHOR]

The National Education Policy promotes moving from the conventional content-heavy and memorization learning practice towards holistic learning/integrated learning. It imparts a creative and multidisciplinary curriculum that focuses equally on curriculum and assessment. All educational establishments assess students using written examinations, quizzes, seminars, term paper writing, and course projects. A semester typically includes 4-5 courses, and students must earn credits for these courses by scoring a good Cumulative Grade Point Average (CGPA). As course projects offer depth knowledge/holistic learning/lifelong learning of a course for the student, many courses include course projects as one of the activities in the course. If all the courses are intended to include course projects as a mandatory pedagogy, it will be difficult for students to acquire in-depth knowledge and required skills while also dealing with stress. So we are proposing an integrated learning framework by applying the theory and practices of two core courses- Software Engineering and Web Technologies to develop a web application. This integrated learning focuses on developing software development and software testing skills in computer science for undergraduate students pursuing a bachelor of engineering degree. This framework alleviated the pressure on students during placement and created job opportunities in software development. The framework consists of three important phases- The first phase includes the identification of the problem as a need for customers, writing requirements and analyzing the same. Students apply modular design principles and break down the codebase into distinct modules. This technique enhances code organization, reusability, and maintainability. The second phase focused on developing the front end by harnessing the power of Angular, a leading web framework, to craft a sleek and interactive user interface. The backend is built using Node.js, which serves as the foundation, enabling the software system to cater to highperformance server environments. These modules communicated seamlessly through well-defined APIs, facilitating the integration of various components within the application, ultimately delivering a seamless and responsive user experience. An industry expert conducted a workshop on Angular This paper was submitted for review on Sept 10, 2023. It was accepted on Nov, 15, 2023. Corresponding author: Padmashree Desai, Department, K.L.E. Technological University, Karnataka India. Address: Hubblii-580031 (e-mail: padmashri@kletech.ac.in). Copyright © YYYY JEET. and React to get hands-on experience. The third phase focused on software testing using appropriate testing tools such as Selenium, Jmeter, TestComplete and Appium to test the web application. A software testing workshop was conducted for students by industry experts to expose the students to designing test cases, test plans, and testing strategies. The hands-on experience on testing tools was provided during the workshop. Faculty reviews are conducted on each phase, and rubrics-based assessment is done on each phase. Approximately sixty teams created web-based applications for real-world scenarios. Positive aspects of the framework in feedback indicated that more than 87% of the students agreed that they could apply Software engineering principles and practices such as requirements management. modular design and testing in web applications. Also, more than 85% of students acquire skills from code-to-web design mastery by developing web applications in Angular Node.js and backend implementation. This framework helped to improve teamwork, presentation and communication skills. Confidence in software development improved to a greater extent. The design and implementation of the framework met the stated outcome of the courses. The student's academic performance improved by 10% compared to the previous year when students were not involved in the integrated project development. [ABSTRACT FROM AUTHOR]

The onset of cloud computing brought with it an adoption of containerization—a lightweight form of virtualization, which provides an easy way of developing and deploying solutions across multiple environments and platforms. This paper describes the current use of containers and complementary technologies in software development and the benefits it brings. Certain applications run into obstacles when deployed on the cloud due to the latency it introduces or the amount of data that needs to be processed. These issues are addressed by edge intelligence. This paper describes edge intelligence, the deployment of artificial intelligence close to the data source, the opportunities it brings, along with some examples of practical applications. We also discuss some of the challenges in the development and deployment of edge intelligence solutions and the possible benefits of applying containerization in edge intelligence. [ABSTRACT FROM AUTHOR]

As virtual teamwork became widespread, the importance of the usability of groupware has increased, as groupware must have high usability in order to properly support teamwork. Several studies have focused on the usability evaluation of groupware, yet, both in terms of science and practice, there is a lack of a method that, like existing empirical single-user methods, can be routinely applied in software development practice. The new Team Usability Testing method differs from previous methods in that it is an empirical method for evaluating synchronous (real-time) collaborative software that explores the team usability problems with the help of real or potential users. The method consists of questionnaires, screen recording videos and group interviews, and the framework of data processing is based on the theory of the mechanics of collaboration. In the four steps of the development of the method, empirical studies under laboratory conditions and real working conditions, and then, for validation purposes, analytical, heuristic evaluation with the involvement of usability experts were performed. During the development and the application of the method, the communication patterns of different teams were examined in terms of their relationship to software usability. In this paper we present the results of the second laboratory study and the heuristic evaluation in details. Overall, the method is able to explore team usability problems of different types of teams, making it a valuable element in existing methods for evaluating the usability of groupware. [ABSTRACT FROM AUTHOR]

Global software development (GSD) refers to developing software with a distributed team spanning multiple locations and time zones. Based on relationships, there are four types of outsourcing: dyadic (one client–one vendor), multi‐vendor (one client–many vendors), co‐sourcing (many clients–one vendor), and complex outsourcing (many clients–many vendors). Compared to the other types of outsourcing contracts, complex outsourcing contracts are the hardest to work on and have the highest risk of project failure. This paper presents a model, the complex outsourcing relationships management model (CORMM), to assist the complex outsourcing stakeholders (both the clients and vendors) in managing their relationships in the context of GSD. This paper aims to develop a CORMM to assist the complex outsourcing relationships management stakeholders in GSD. Also, we are interested in identifying the applicability and effectiveness of the CORMM in the real‐world industry. The research approach follows a structured methodology comprising multiple phases. Initially, it leverages a systematic literature review (SLR) as its primary research method. The second phase involves the validation of the SLR findings via an empirical study. Subsequently, in the third phase, a model is developed. Finally, the proposed research approach is validated by incorporating two industrial case studies to assess the organization's relationship management utilizing the Motorola tool. The case study results show that CORMM can successfully point out relationship management issues in a complex outsourcing context. The feedback received from the participants of both companies indicates several positive and valuable insights about the CORMM and its application in the context of complex outsourcing relationships. The results highlight that CORMM serves as an assessment tool for evaluating an organization's relationship management capability and a means for organizations to enhance their position. Through CORMM, complex outsourcing organizations (many clients–many vendors) can identify strengths and weaknesses in their relationship management practices, enabling targeted improvement efforts. [ABSTRACT FROM AUTHOR]

The adoption and popularity of mobile devices by end-users is partially driven by the increasing development and availability of mobile applications that can aid solving different problems and provide access to services in a wide range of domains or categories, namely healthcare, education, e-commerce or entertainment. While these applications use and benefit from the combination of a wide panoply of technologies from the Internet of Things, fog and cloud computing, data security and privacy are typically not fully taken into account before the creation of many mobile applications or during the software development phases. This paper presents an in-depth approach to modeling attacks on the specific cloud and mobile ecosystem, given its importance in the process of secure application development. Moreover, aiming at bridging the knowledge gap between developers and security experts, this paper presents an alpha version of the security by design for cloud and mobile ecosystem (secD4CloudMobile) framework. secD4CloudMobile is a set of tools that covers cloud and mobile security requirement elicitation (CMSRE), cloud and mobile security best practices guidelines (CMSBPG), cloud mobile attack modeling elicitation (CMAME), and cloud mobile security test specification and tools (CM2ST). The purpose of the framework is to provide cloud and mobile application developers useful readily applicable information and guidelines, striving to bring security engineering and software engineering closer, in a more accessible and automated manner, aiming at the incorporation of security by construction. Finally, the paper presents some preliminary results and discussion. [ABSTRACT FROM AUTHOR]

Blockchain technology has created a new software development context, with its own peculiarities, mainly due to the guarantees that the technology must satisfy, that is, immutability, distributability, and decentralization of data. Its rapid evolution over the last decade implied a lack of adequate verification tools, exposing developers and users to critical vulnerabilities and bugs. This paper clarifies the extent of block chain-oriented software (BoS), that goes well beyond smart contracts. Moreover, it provides an overview of the challenges related to software verification in the blockchain context, encompassing smart contracts, blockchain layers, cross-chain applications, and, more generally, BoS. This study aims to highlight the shortcomings of the state-of-art and of the state-of-practice of software verification in that context and identify, at the same time, new research directions. [ABSTRACT FROM AUTHOR]

Organizations creating software commonly utilize software development lifecycles (SDLCs) to structure development activities. Secure development lifecycles (SDLs) integrate into SDLCs, adding security or compliance activities. They are widely used and have been published by industry leaders and in literature. These SDLs, however, were mostly designed before or while cloud services and other hosted solutions became popular. Such offerings widen the provider's responsibilities, as they not only deliver software but operate and decommission it as well. SDLs, however, do not always account for this change. Security maturity models (SMMs) help to assess SDLs and identify improvements by introducing a baseline to compare against. Multiple of these models were created after the advent of hosted solutions and are more recent than commonly referenced SDLs. Recent SMMs and SDLs may therefore support hosted solutions better than older proposals do. This paper compares a set of current and historic SDLs and SMMs in order to review their support for hosted solutions, including how support has changed over time. Security, privacy, and support for small or agile organizations are considered, as all are relevant to hosted solutions. The SDLs analyzed include Microsoft's SDL, McGraw's Touchpoints, the Cisco's SDL, and Stackpole and Oksendahl's SDL2. The SMMs reviewed are OWASP's Software Assurance Maturity Model 2 and DevSecOps Maturity Model. To assess the support for hosted solutions, the security and privacy activities foreseen in each SDLC phase are compared, before organizational compatibility, activity relevance, and efficiency are assessed. The paper further demonstrates how organizations may select and adjust a suitable proposal. The analyzed proposals are found to not sufficiently support hosted solutions: Important SDLC phases, such as solution retirement, are not always sufficiently supported. Agile practices, such as working in sprints, and small organizations are often not sufficiently considered as well. Efficiency is found to vary based on the application context. A clear improvement trend from before the proliferation of hosted solutions cannot be identified. Future work is therefore found to be required. [ABSTRACT FROM AUTHOR]

Source code complexity of legacy object-oriented (OO) software has a trickle-down effect over the key activities of software development and maintenance. Package-based OO design is widely believed to be an effective modularization. Recently, theories and methodologies have been proposed to assess the complementary aspects of legacy OO systems through package-modularization metrics. These package-modularization metrics basically address non-API-based object-oriented principles, like encapsulation, commonality-of-goal, changeability, maintainability, and analyzability. Despite their ability to characterize package organization, their application towards cost-effective fault-proneness prediction is yet to be determined. In this paper, we present theoretical illustration and empirical perspective of non-API-based package-modularization metrics towards effort-aware fault-proneness prediction. First, we employ correlation analysis to evaluate the relationship between faults and package-level metrics. Second, we use multivariate logistic regression with effort-aware performance indicators (ranking and classification) to investigate the practical application of proposed metrics. Our experimental analysis over open-source Java software systems provides statistical evidence for fault-proneness prediction and relatively better explanatory power than traditional metrics. Consequently, these results guide developers for reliable and modular package-based software design. [ABSTRACT FROM AUTHOR]

In pandemic preparedness and response, a Functional Exercise (FX) is used to simulate a situation as close to a real‐life event as possible without the deployment of resources. Participants are drawn from public health emergency operations centres, and work through a scenario script to test possible responses to a novel pathogen outbreak. This paper summarises the role of system dynamics modelling in the design and implementation of a functional exercise, which involved the Dutch and German national public health institutes in March 2023. The findings confirm the value of the system dynamics method in integrating disease and hospital models, and also highlights how well the method aligns with modern software development processes. The paper concludes with a discussion of what worked well, and presents areas for future enhancements of management flight simulators to support functional exercises. © 2024 The Author(s). System Dynamics Review published by John Wiley & Sons Ltd on behalf of System Dynamics Society. [ABSTRACT FROM AUTHOR]

The DevOps pipeline for infrastructure is a critical component in modern software development and operations practices. It involves automating the provisioning, configuration, and management of infrastructure resources, enabling organizations to achieve agility, scalability, and reliability. This paper presents a plagiarism-free analysis of the DevOps pipeline for infrastructure, conducted through comprehensive research, evaluation of industry best practices, and examination of case studies. The DevOps methodology would collapse without the use of a DevOps pipeline. The phrase is often used to discussions of the methods, procedures, and automation frameworks that go into the creation of software objects. Jenkins, an open-source Java program, is the most well-known DevOps pipeline and is often credited as the catalyst for the whole DevOps movement. Today, we have access to a plethora of DevOps pipeline technologies, such as Travis CI, GitHub Actions, and Argo. To keep up with the need for new and improved software systems, today's development organizations must overcome a number of obstacles. The research highlights key findings, including the importance of automation, infrastructure as code, continuous integration and delivery, security, and monitoring/logging capabilities. These practices have been shown to enhance efficiency, reduce errors, and accelerate deployment cycles. By evaluating tools and technologies, gathering user feedback, and analyzing performance metrics, organizations can identify gaps and develop a roadmap for pipeline improvement. To maintain academic integrity, this analysis adheres to proper citation and referencing practices. Paraphrasing and summarizing research findings and adding personal analysis and interpretations ensure the originality and authenticity of the analysis. Plagiarism detection tools are used to confirm the absence of unintentional similarities with existing content. [ABSTRACT FROM AUTHOR]

Featured Application: This software design pattern can be used in OOP programming in order to promote conceptual clarity, reduce coupling, and facilitate system scalability. Object-oriented programming (OOP) has long been a dominant paradigm in software development, but it is not without its challenges. One major issue is the problem of tight coupling between objects, which can hinder flexibility and make it difficult to modify or extend code. Additionally, the complexity of managing inheritance hierarchies can lead to rigid and fragile designs, making it hard to maintain and evolve the software over time. This paper introduces a software development pattern that seeks to offer a renewed approach to writing code in object-oriented (OO) environments. Addressing some of the limitations of the traditional approach, the Puzzle Pattern focuses on extreme modularity, favoring writing code exclusively in building blocks that do not possess a state (e.g., Java interfaces that support concrete methods definitions in interfaces starting from version 8). Concrete classes are subsequently assembled through the implementation of those interfaces, reducing coupling and introducing a new level of flexibility and adaptability in software construction. The highlighted pattern offers significant benefits in software development, promoting extreme modularity through interface-based coding, enhancing adaptability via multiple inheritance, and upholding the SOLID principles, though it may pose challenges such as complexity and a learning curve for teams. [ABSTRACT FROM AUTHOR]

Model-driven architecture (MDA) has demonstrated significant potential in automating code generation processes, yet its application often falls short in addressing the complexities of modern architectural styles, notably microservices. Microservice architecture, characterized by its decomposition of applications into small, independently deployable services, presents unique challenges and opportunities that traditional MDA approaches struggle to accommodate. In this paper, Zynerator, a novel framework that bridges the gap between model-driven architecture and microservice development, is presented. By integrating semantic decorators into the PIM, Zynerator empowers end-users to express intricate functional and non-functional requirements, laying the foundation for the generation of contextually appropriate code. Moreover, Zynerator goes beyond traditional MDA capabilities by offering a solution for microservice architecture integration, enabling the generation of service gateways, service discovery mechanisms, and other essential components inherent to microservice ecosystems. This integration not only streamlines the development process but also ensures the scalability, resilience, and maintainability of microservice-based applications. Through Zynerator, a flexible and comprehensive solution is presented that leverages the strengths of model-driven architecture (MDA), while addressing the evolving needs of modern software architecture, particularly in the realm of microservice development. Empirical results showed that Zynerator enhances code generation alignment to functional requirements by 55%, reduces microservice adoption in terms of communication and deployment times by 30%, and increases system scalability by supporting up to 10,000 concurrent users, without performance degradation. [ABSTRACT FROM AUTHOR]

Requirements Engineering (RE) has undergone several transitions over the years, from traditional methods to agile approaches emphasising increased automation. In many software development projects, requirements are expressed in natural language and embedded within large volumes of text documents. At the same time, RE activities aim to define software systems' functionalities and constraints. However, manually executing these tasks is time-consuming and prone to errors. Numerous research efforts have proposed tools and technologies for automating RE activities to address this challenge, which are documented in published works. This review aims to examine empirical evidence on automated RE and analyse its impact on the RE sub-domain and software development. To achieve our goal, we conducted a Systematic Literature Review (SLR) following established guidelines for conducting SLRs. We aimed to identify, aggregate, and analyse papers on automated RE published between 1996 and 2022. We outlined the output of the support tool, the RE phase covered, levels of automation, development approach, and evaluation approaches. We identified 85 papers that discussed automated RE from various perspectives and methodologies. The results of this review demonstrate the significance of automated RE for the software development community, which has the potential to shorten development cycles and reduce associated costs. The support tools primarily assist in generating UML models (44.7%) and other activities such as omission of steps, consistency checking, and requirement validation. The analysis phase of RE is the most widely automated phase, with 49.53% of automated tools developed for this purpose. Natural language processing technologies, particularly POS tagging and Parser, are widely employed in developing these support tools. Controlled experimental methods are the most frequently used (48.2%) for evaluating automated RE tools, while user studies are the least employed evaluation method (8.2%). This paper contributes to the existing body of knowledge by providing an updated overview of the research literature, enabling a better understanding of trends and state-of-the-art practices in automated RE for researchers and practitioners. It also paves the way for future research directions in automated requirements engineering. [ABSTRACT FROM AUTHOR]

Crowdsource software development has become more and more popular in recent years in the software industry. Crowdsourcing is an open‐call technique for outsourcing tasks to a broad and undefined crowd. Crowdsourcing provides numerous advantages including reduced costs, fast project completion, talent identification, diversity of solutions, top‐quality, and access to problem‐solving creativity. Despite of the benefits gained from crowdsourcing, there are numerous issues like lack of experienced workers, lack of confidentiality, copyright issues, software sustainability, and so forth. There is also less focus on the long‐term sustainability of software development because of new ideas emerging in crowdsourcing software development. Furthermore, in literature, lack of guidelines towards sustainable software crowdsourcing is highlighted as one of the limitations in the software standards. This study aims to identify the factors that influence sustainability aspects in crowdsourced software development. We have conducted a systematic literature review for identification of these factors. In this paper, we present findings of the systematic literature review in the form of a list of 11 factors extracted from a sample of 45 finally selected papers. Among these factors, six of the factors are ranked as critical factors. These critical factors are "Lack of coding standard in documentation," "Use of popular programming tools," "Crowd Lack of knowledge and awareness about sustainability," "Energy‐efficient coding," "Lack of awareness about sustainable software engineering practices," and "Lack of coordination/communication between client and crowd." [ABSTRACT FROM AUTHOR]

Selecting the most suitable agile software development method is a challenging task due to the variety of available methods, each with its strengths and weaknesses. To achieve project goals effectively, factors such as project needs, team size, complexity, and customer involvement should be carefully evaluated. Choosing the appropriate agile method is crucial for achieving high client satisfaction and effective team management, but it can be a challenging task for project managers and higher-level management officials. This paper presents a solution aiming to help them in selecting the most suitable software development method for their project. In this regard, this solution includes a pre-project management approach model and a decision tree that considers the unique requirements of the project. In the proposed solution results, Scrum was found to be suitable for both small and large projects, on the condition that roles and responsibilities are clearly defined and that the approach is people-centric. Furthermore, high-risk mitigation measures should be added for small projects. To facilitate the use of our model, a software application has been developed which implements the decision-making tree. [ABSTRACT FROM AUTHOR]

Code assistance refers to the utilization of various tools, techniques, and models to help developers in the process of software development. As coding tasks become increasingly complex, code assistant plays a pivotal role in enhancing developer productivity, reducing errors, and facilitating a more efficient coding workflow. This assistance can manifest in various forms, including code autocompletion, error detection and correction, code generation, documentation support, and context-aware suggestions. Language models have emerged as integral components of code assistance, offering developers the capability to receive intelligent suggestions, generate code snippets, and enhance overall coding proficiency. In this paper, we propose new hybrid models for code generation by leveraging pre-trained language models BERT, RoBERTa, ELECTRA, and LUKE with the Marian Causal Language Model. Selecting these models based on their strong performance in various natural language processing tasks. We evaluate the performance of these models on two datasets CoNaLa and DJANGO and compare them to existing state-of-the-art models. We aim to investigate the potential of pre-trained transformer language models to revolutionize code generation, offering improved precision and efficiency in navigating complex coding scenarios. Additionally, conducting error analysis and refining the generated code. Our results show that these models, when combined with the Marian Decoder, significantly improve code generation accuracy and efficiency. Notably, the RoBERTaMarian model achieved a maximum BLEU score of 35.74 and an exact match accuracy of 13.8% on CoNaLa, while LUKE-Marian attained a BLEU score of 89.34 and an exact match accuracy of 78.50% on DJANGO. Implementation of this work is available at https://github.com/AhmedSSoliman/Leveraging-Pretrained-Language-Models-for-Code-Generation. [ABSTRACT FROM AUTHOR]

The advent of Generative Artificial Intelligence is opening essential questions about whether and when AI will replace human abilities in accomplishing everyday tasks. This issue is particularly true in the domain of software development, where generative AI seems to have strong skills in solving coding problems and generating software source code. In this paper, an empirical evaluation of AI-generated source code is performed: three complex coding problems (selected from the exams for the Java Programming course at the University of Insubria) are prompted to three different Large Language Model (LLM) Engines, and the generated code is evaluated in its correctness and quality by means of human-implemented test suites and quality metrics. The experimentation shows that the three evaluated LLM engines are able to solve the three exams but with the constant supervision of software experts in performing these tasks. Currently, LLM engines need human-expert support to produce running code that is of good quality. [ABSTRACT FROM AUTHOR]

Software cost estimation (SCE), estimating the cost and time required for software development, plays a highly significant role in managing software projects. A somewhat accurate SCE is necessary for a software project to be successful. It allows effective control of construction time and cost. In the past few decades, various models have been presented to evaluate software projects, including mathematical models and machine learning algorithms. In this paper, a new model based on the hybrid of the artificial fish swarm algorithm (AFSA) and the artificial bee colony (ABC) algorithm is presented for SCE. The initial population of AFSA, which includes the values of the effort factors, is generated using the ABC algorithm. ABC algorithm is used to solve the problems of the AFSA algorithm such as population diversity and getting stuck in a local optimum. ABC algorithm achieves the best solutions using observer and scout bees. The evaluation of the combined method has been implemented on eight different data sets and evaluated based on eight different criteria such as mean magnitude of relative error and PRED (0.25). The proposed method is more error-free than current SCE methods, according to the results. The error value of the proposed method is lower on NASA60, NASA63, and NASA93 datasets. [ABSTRACT FROM AUTHOR]

This analysis embarks on a comprehensive exploration of the .NET ecosystem’s evolution, with a spotlight on the transition from .NET Core to the unified .NET platform, culminating in the release of .NET 8. It meticulously examines the performance enhancements, feature evolutions, and migration strategies that underscore this transition, providing a lens through which the future trajectory of .NET, including the anticipation of .NET 9, can be discerned. By offering a deep dive into the comparative performance metrics and the introduction of novel features across versions, this paper caters to IT professionals, students, and technology aficionados seeking to grasp the full extent of .NET’s capabilities and its strategic direction. The findings aim to not only delineate the technical advancements but also to contextualize the platform’s ongoing innovation within the broader software development ecosystem. [ABSTRACT FROM AUTHOR]

Today's users expect to be able to interact with the products they own without much effort and also want to be excited about them. The development of a positive user experience must therefore be managed. We understand management in general as a combination of a goal, a strategy, and resources. When applied to UX, user experience management consists of a UX goal, a UX strategy, and UX resources. We conducted a tertiary study and examined the current state of existing literature regarding possible requirements. We want to figure out, what requirements can be derived from the literature reviews with the focus on UX and agile development. In total, we were able to identify and analyse 16 studies. After analysing the studies in detail, we identified different requirements for UX management. In summary, we identified 13 requirements. The most frequently mentioned requirements were prototypes and UX/usability evaluation. Communication between UX professionals and developers was identified as a major improvement in the software development process. In summary, we were able to identify requirements for UX management of People/Social, Technology/Artifacts, and Process/Practice. However, we could not identify requirements for UX management that enabled the development and achievement of a UX goal. [ABSTRACT FROM AUTHOR]

This study presents three structures for clearly expressing functional requirements (FRs) and quantitative non-functional requirements (qt-NFRs). Expressing requirements with these structures will allow the understanding of requirements by stakeholders and software developers. The first structure is the SURE format, which is composed of three main sections: a title, a short definition, and a detailed description. The second proposed structure is a template to facilitate the definition of the title and description of unambiguous FRs. It is based on the application of CRUD operations on a certain entity, calling it the "CRUDE" structure. Finally, the third structure serves as a template to make it easier to clearly define the description and title of qt-NFRs. It is based on the application of system properties to computer events or actions, calling it the "PROSE" structure. In this, it is very important to specify those metric values that are desired or expected by the stakeholder. To know how much the definition of FRs and qt-NFRs improved when the proposed structures were used, 46 requirement specification documents elaborated as homework by students of the "Requirement Engineering" course offered at the University of Guayaquil between 2020 and 2022 were evaluated by five experts with more than 10 years of experience in software development for Ecuadorian companies. The findings showed that students reduced the percentage of unambiguous FRs and qt-NFRs from over 80% to about 10%. In conclusion, the findings demonstrate how crucial the three structures proposed in this paper are to helping students develop the ability to clearly express requirements. [ABSTRACT FROM AUTHOR]

Code readability is critical to software development and has a significant impact on maintenance and collaboration in evolving technology landscapes. With the increasing complexity of projects and the diversity of developers' coding styles, the need for automated tools to improve code readability has become more apparent. This paper presents an innovative automated system designed to improve code readability by modeling and enforcing consistent formatting standards. The approach uses techniques such as Long Short-Term Memory (LSTM) networks and N-gram models, allowing the system to adapt to different coding styles and preferences. The system works autonomously by analyzing code styling within a project, identifying deviations from established standards and providing actionable recommendations for consistent styling. To validate our approach, several evaluations were performed on a large dataset of Java files. The results demonstrate the system's effectiveness in detecting and correcting formatting errors, identifying a formatting error within the first five predictions more than 90% of the time, while providing the correct fix nearly 96% of the time, regardless of formatting convention or programming language. By offering a solution tailored to the specific needs of different teams, our system represents a significant advance in automated code formatting and readability improvement. [ABSTRACT FROM AUTHOR]

Copyright of An-Najah University Journal for Research, B: Humanities is the property of An-Najah National University 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.)

This research explores the incorporation of green computing variables into the rational unified process (RUP) methodology, specifically focusing on sustainable development goal (SDGs) 12-responsible consumption and production. Supported by three additional papers using the preferred reporting items for systematic reviews and meta-analyses (PRISMA) method. Our study aims to promote eco-friendly software development practices and tools (artifacts) aligned with green computing principles to support SDGs throughout RUP development phases. We conducted a matrix thorough analysis of existing green computing adaptability within RUP, yielding key findings: a system charter for inception, system requirement specification for elaboration, software development result for construction, and software test report/user acceptance test for transition. As a result, we've compiled comprehensive phase-specific documents, emphasizing the need for educational initiatives to foster green computing adoption among developers. This study advocates for cross-disciplinary collaboration to ensure successful implementation of eco-friendly software development processes. [ABSTRACT FROM AUTHOR]

Agile software development has reached wide adoption in various countries including Turkey, even though from which its original cultural backgrounds differ. In Turkey, many organizations have started to adopt Agile approaches more and more in their software development processes. This interest in the country's software development is parallel to what the academic literature on Agile in the country exhibits. However, despite the prevalence of Agile in Turkey, there is a lack of sufficient secondary research and comprehensive review on Agile in Turkey, which poses a significant necessity for further investigation. Considering this gap, we performed a quantitative bibliometric analysis of Agile software development publications produced by Turkish organizations in a holistic and broad approach both for scholars and practitioners. We provide a summary of relevant academic studies that emerged in Agile research in Turkey by focusing on many aspects including bibliometric properties of papers, researchers, affiliations, venues, and thematic contents that are separated into 15 sub‐research questions. After delivering results based on the questions, we discuss the results and findings of our study and present implications regarding the findings. The main contributions of our work are twofold. First, the paper may help the readers to have a quick idea, understand the subject, and gain insight from a large volume of scientific data. Second, the paper can help readers to use these analyses to form future research. [ABSTRACT FROM AUTHOR]

The objective of this study is to analyze the current perspective as regards knowledge related to what causes stress or motivates developers, how these two aspects are related to each other, and how this in turn affects their performance in the sphere of Global Software Development and how these can be controlled. This paper presents the results obtained after conducting a systematic mapping study of literature in order to analyze how stress, motivation, and performance affect the project members in Global Software Development teams. We carried out a systematic mapping of published studies dealing with stress, motivation, and performance in global software engineering. A total of 118 papers dealing with this subject were found. The literature analyzed provided a relatively significant quantity of data referring to the impact that the characteristics of distributed software development projects have on the performance and productivity of teams, along with the actions taken to improve that performance. However, when focusing on the analysis of the impact of this type of projects on team members' motivation, and on the actions that can be taken to improve that motivation, we discovered that the number of works decreases considerably and that works referring to the impact of this kind of development on developers' stress were virtually non‐existent, as were those concerning ways in which to improve that stress. We are, therefore, of the opinion that it is necessary to carry out in‐depth research into the aspects of working in distributed teams that may have a negative impact on developers' levels of motivation and stress, along with what could be beneficial in order to improve levels of motivation and decrease levels of stress. [ABSTRACT FROM AUTHOR]

Software has become an essential and important part of every domain system. Developing quality software is critical to maintaining a stable and secure system. Most of the existing software defect prediction tasks focus on the various kinds of defects leftover in the software system, but they do not focus on the most common and frequent software defects that developers most commonly do and which have a significant effect on the quality of software development. These unnoticeable defects have a considerable impact on the functionality and also on development time, effort, and cost of the software. This paper propose a frequent software defects prediction (FSDP) mechanism based on defects Correlation learning method (CLM) utilizing various defects metrics. The aim of this work is to assist developers in accurately identifying software defects and support project managers in ensuring software quality by minimizing the presence of defect-prone code during development. The evaluation of FSDP was performed using NASA datasets in comparison with the conventional Naive Bayes, Support Vector Machine, and Random Forest classifiers and also compare with the state-of-the-arts methods to measure accuracy, precision, recall and F-Score to understand the impact of the prediction accuracy. The proposed FSDP achieves 98.88% accuracy and 98.86% precision in compare to state-of-the-arts classifiers methods indicates the effectiveness of the proposed approach in defect prediction. [ABSTRACT FROM AUTHOR]

Purpose: The aim of this article was to present the typology of information technology standards and to explore their importance for programmers. Design/methodology/approach: The research was exploratory in nature, and based on grounded theory and ethnography. The tool used to collect data were interviews. Findings: On the basis of the research it is concluded that standards were of utmost importance to the respondents, and were a thing that allowed them to work efficiently. Research limitations/implications: The conducted research was qualitative and inductive. For this reason, there is limited possibility of making generalizations about the results. Originality/value: The paper presents important findings that might increase the work efficiency of programmers. Additionally the research was conducted using a relatively uncommon approach in IT and management field (grounded theory, ethnography, qualitative methods, interviews). [ABSTRACT FROM AUTHOR]