Successful Software Development Research Articles

Perceived impact of agile principles: Insights from a survey-based study on agile software development project success

ContextAgile methodology has emerged as a fundamental framework guiding software development projects, emphasizing values and principles for achieving successful project outcomes. Despite the widespread recognition of the importance of agile principles, there remains a gap in empirical research investigating their actual impact on agile project success. ObjectiveThis research aims to examine the relationship between agile principles and project outcomes and provide empirical evidence supporting the importance of agile principles in achieving success in agile software development (ASD) projects. MethodA total of 298 Agile project practitioners participated in an online survey between August and September 2023 to test this study's research model using the partial least square structural equation modeling (PLS-SEM) method. ResultsWe find a significant relationship between adopting agile principles and project success, with regular delivery, technical excellence, team member proactivity, and customer collaboration showing the highest impact on Agile project success. However, process simplicity was found not to be significant in the study. ConclusionsOur analysis verifies the importance of Agile principles and suggests areas for further study to successfully understand their impact on Agile projects. The findings contribute to the ongoing discourse on agile principles and their impact on software development project success, opening avenues for future research and the refinement of agile methodologies. These insights could assist organizations in optimizing Agile practices and decision-making, leading to more successful and efficient software development projects.

Evaluation and Assessment of Software Security Risks and Vulnerabilities Within the Realm of Secure DevOps.

Security plays a vital role in successful software development and consistency, especially in a modern, fast-expanding world dominated by technologies. It guarantees that all privacy, integrity, and accessibility of information, coding, and services are protected. Achieving such requires a consistent consideration of security throughout all developmental stages of software. Although several methods for improving the quality of software have been created, there is still no clear method for effectively integrating security throughout each stage of the software developmental process. The inability to give adequate attention to security has been identified as the main cause of common flaws. Many forward-thinking businesses frequently employ a "patch and infiltrate” technique, taking security into consideration only after the execution of the task. Higher costs, project delays, neglect of verification and integration during the development life cycle of the project, reliance on external tools and parts, and ignorance among all factors contribute to the disregard of security during the SDLC. Nevertheless, Secure-DevOps is indispensable for the survival of companies in the Information and Communication Technology (ICT) landscape. Consequently, applying an effective approach that deals with security within every level of the SDLC is crucial. To bridge this gap, a comprehensive examination of effective techniques for developing secure software was presented, taking into account the financial and time constraints of a project. A framework for ensuring security built upon Secure-DevOps practices, which seamlessly integrates the best security measures into different stages of the SDLC, was identified. To validate this framework, a mathematical model has been employed. The study concludes that effectively incorporating Secure-DevOps practices throughout the Software developmental process, minimizes security risks and vulnerabilities.

SDLC Big Bang dan Waterfall : Perbandingan Pendekatan dalam Pengembangan Perangkat Lunak

The development of software necessitates the selection of appropriate methodologies to ensure effectiveness and quality. This research aims to assess the strengths and weaknesses of the Big Bang and Waterfall methodologies through the analysis of diverse case studies. The Big Bang approach allows teams to begin work swiftly without detailed initial planning, yet it often results in products with inconsistent quality and susceptibility to bugs. Conversely, the Waterfall method provides a structured, sequential approach but lacks flexibility in accommodating changes. Choosing the right methodology should be tailored to meet the specific needs and characteristics of each project. It is essential for professionals to have a comprehensive understanding of each methodology to increase the likelihood of success in software development. This study lays a robust foundation for future advancements, emphasizing the importance of empirical research and exploring hybrid approaches.

A systematic literature review on characteristics of the front-end phase of agile software development projects and their connections to project success

ContextSoftware development of new products and services often involves a front-end phase where user needs are analysed, costs and benefits are estimated, and initial plans are created. GoalThis study aims to learn more about how the introduction of agile software development has affected practices and outcomes related to cost and benefit estimation in this front-end phase and to understand better what would improve this phase. MethodWe identified, reviewed and aggregated the results from 42 relevant research articles by searching literature databases and snowballing relevant articles. ResultsThe front-end phase of agile was found to be, on average, similar and just as comprehensive as that of non-agile software development. This may be unfortunate, given the finding that more successful agile software development is connected with less detail in cost estimation and planning-related activities. A less comprehensive front-end phase may be especially beneficial for low-risk agile software development. ConclusionThe results of this review suggest that agile principles, so far, have had a limited influence on the front-end phase. We recommend more flexibility and context-dependency in how the front-end phase of agile software development is conducted, including less comprehensive estimation and planning activities for low-risk software development contexts.

Analisa Perbandingan Penggunaan Metodologi Pengembangan Perangkat Lunak (Waterfall, Prototype, Iterative, Spiral, Rapid Application Development (RAD))

Methodology is a very important basic framework in the design and development of professional software, aimed at creating an information system that meets the business needs of an organization. Success in software development relies heavily on managing the software project as a whole. Establishing a methodology includes high dynamics in the design stages of a model that describes the activities and life cycle of a system. SDLC (Systems Development Life Cycle) or Systems Development Life Cycle, in the context of systems and software engineering, is a process that includes the creation and modification of systems, as well as the models and methodologies used to develop them. This discussion will explain the analysis of selecting software development methodologies, including waterfall, prototype, iterative, spiral, and rapid application development (RAD). It is hoped that the results of this discussion can provide considerations in choosing and using the right methodology based on each individual's needs, strengths and weaknesses, as well as other factors such as familiarity with technology, system complexity, system reliability, and short and precise time requirements, as well as referencing several scientific journals.

Holistic personas to increase the novice developer productivity

A deeper understanding and integration with system users' thoughts and emotional experiences are required for user-engaged development. User experience (UX) journey integrates user requirements and problem-solving approaches. The integration of data-driven techniques and user-centric approaches in software development is investigated in this study. It focuses on using the Markov chain model to predict developer productivity based on data gathered while creating personas across three projects. Organizations can gain valuable insights into user needs and requirements by conducting purposeful activities such as strength, weaknesses, opportunities, and threats (SWOT) analysis, competitor analysis, hypothesis formulation, identification of behavioral variables, mapping interviews, and defining characteristics and objectives. The model has predictive capabilities that allow for more informed decision-making, more efficient resource allocation, and better project planning. The goal of the activity and the model ensure the development of software products that effectively meet the needs of users, resulting in a higher success rate for software development initiatives. This study emphasizes the importance of integrating quantitative and qualitative analysis to drive successful software development projects and increase productivity while meeting user needs. According to the findings of the research conducted from the three projects completed, the proposed methods have similarities, and predictions using the Markov chain can determine the success of novice developers.

ProgEdu4Web: An automated assessment tool for motivating the learning of web programming course

AbstractThe expanding software industry has increased the demand for proficient programming professionals. However, more than technical expertise is needed for successful software development; code quality assurance and effective teamwork are also indispensable. Unfortunately, recent graduates often exhibit deficiencies in programming, code quality assurance, and teamwork skills, highlighting the need for improvements in these areas. In response to these challenges, this study presents ProgEdu4Web, an innovative Automated Programming Assessment System designed to evaluate code quality and teamwork proficiency in web programming. The system integrates automatic source code evaluation tools for static code analysis, ensuring timely feedback on coding quality issues. To assess the effectiveness of ProgEdu4Web, a questionnaire and hypothesis model was employed, surveying a cohort of 111 students enrolled in web programming classes. The study's findings demonstrate that the system significantly alleviated instructor workload while motivating students to enhance their web programming with good code quality and teamwork abilities.

Exploring issues of story-based effort estimation in Agile Software Development (ASD)

ContextEffort estimation based on user stories plays a pivotal role in agile software development, where accurate predictions of project efforts are vital for success. While various supervised ML tools attempt to estimate effort, the prevalence of estimation errors presents significant challenges, as evidenced by the CHAOS report by the Standish Group, which highlights incorrect estimations contributing to a substantial percentage of failed agile projects. ObjectivesThis research delves into the domain of user story-based effort estimation in agile software development, aiming to explore the issues arising from inaccurate estimations. The primary goal is to uncover these issues comprehensively and propose potential solutions, thus enhancing the efficacy of the user story-based estimation method. MethodsTo achieve the research objectives, a systematic literature review (SLR) is conducted, surveying a wide range of sources to gather insights into issues surrounding user story-based effort estimation. The review encompasses diverse estimation methods, user story attributes, and the array of challenges that can result from inaccurate estimations. ResultsThe SLR reveals a spectrum of issues undermining the accuracy of user story-based effort estimation. It identifies internal factors like communication, team expertise, and composition as crucial determinants of estimation reliability. Consistency in user stories, technical complexities, and task engineering practices also emerge as significant contributors to estimation inaccuracies. The study underscores the interconnectedness of these issues, emphasizing the need for a standardized protocol to minimize inaccuracies and enhance estimation precision. ConclusionIn light of the findings, it becomes evident that addressing the multi-dimensional factors influencing user story-based effort estimation is imperative for successful agile software development. The study underscores the interplay of various aspects, such as team dynamics, task complexity, and requirement engineering, in achieving accurate estimations. By recognizing these challenges and implementing recommended solutions, software development processes can avoid failures and enhance their prospects of success in the agile paradigm.

TeReKG: A temporal collaborative knowledge graph framework for software team recommendation

Successful software development requires a cohesive team with the right mix of technical skills and the ability to collaborate effectively. However, forming a software team that can execute tasks with precision and efficiency requires a deep understanding of each member’s competence, experience, and cooperation history. Previously, automated software team selection has evaluated technical skills, cohesion, and cooperation history. However, the previous method had some limitations. Particularly, local features directly calculated from team members were subjective to the researchers’ views, and the method ignored the temporal aspect of open-source software development. To overcome these limitations, this paper proposes a knowledge-graph software team recommendation framework called TeReKG. This framework encapsulates temporal collaboration patterns and uses a temporal knowledge graph to encode software collaboration history, technical abilities, task dependencies, and project structure. TeReKG was against state-of-the-art team recommendation algorithms using three popular open-source software projects: Moodle, Apache, and Atlassian. The evaluation results show that TeReKG outperforms the state-of-the-art baselines in both single-role and team recommendation tasks. These findings demonstrate that knowledge graph embedding can be effectively utilized in automated recommendation tasks in software engineering. Additionally, this highlights the potential for knowledge graphs to capture global information that can benefit various software development applications, including impact prediction of software repositories, code clone detection, and source code retrieval.

A Multivocal Literature Review on Non-Technical Debt in Software Development: {A}n Insight into Process, Social, People, Organizational, and Culture Debt

Software development encompasses various factors beyond technical considerations. Neglecting non-technical elements like individuals, processes, culture, and social and organizational aspects can lead to debt-like characteristics that demand attention. Therefore, we introduce the non-technical debt (NTD) concept to encompass and explore these aspects. This indicates the applicability of the debt analogy to non-technical facets of software development. Technical debt (TD) and NTD share similarities and often arise from risky decision-making processes, impacting both software development professionals and software quality. Overlooking either type of debt can lead to significant implications for software development success. The current study conducts a comprehensive multivocal literature review (MLR) to explore the most recent research on NTD, its causes, and potential mitigation strategies. For analysis, we carefully selected 40 primary studies among 110 records published until October 1, 2022. The study investigates the factors contributing to the accumulation of NTD in software development and proposes strategies to alleviate the adverse effects associated with it. This MLR offers a contemporary overview and identifies prospects for further investigation, making a valuable contribution to the field. The findings of this research highlight that NTD’s impacts extend beyond monetary aspects, setting it apart from TD. Furthermore, the findings reveal that rectifying NTD is more challenging than addressing TD, and its consequences contribute to the accumulation of TD. To avert software project failures, a comprehensive approach that addresses NTD and TD concurrently is crucial. Effective communication and coordination play a vital role in mitigating NTD, and the study proposes utilizing the 3C model as a recommended framework to tackle NTD concerns.

Determinants of Software Development Success: Individual Factors as Moderator

Determinants of Software Development Success: Individual Factors as Moderator

Road surface damages allocation with RTI-IMS software based on YOLO V5 model

ABSTRACT Research on applying artificial intelligence to autonomously detect road surface damages contributes positively to road traffic maintenance and management. This study introduces the Road Traffic Infrastructure Intelligent Management System (RTI IMS) software, utilizing the Yolo V5 programming platform. This software is designed to automatically identify road surface damages during operation. Based on machine learning image recognition technology, the model is trained with a diverse database of road surface damage images from Japan, India, and Vietnam. Additionally, to improve the inference efficiency of the RTI IMS software, the study uses the Mosaic method, tripling the variation to diversify input data during training, thereby minimizing prediction errors. The research results in the successful development of the RTI IMS software, capable of autonomously detecting road surface damages and providing corresponding images to traffic management authorities. This study significantly contributes to the modernization of current road traffic management practices.

Seismic design methods for concrete buildings

Earthquake is a devastating natural disaster that can easily cause buildings to collapse, posing a serious threat to human life. Concrete, as a widely used building material, is of significant concern for its seismic performance. This paper mainly presents how seismic resistance can be considered in concrete building design and proposes two main solutions, the use of high-performance materials and rational structural placement. Through comparison and analysis, it finds that rationalization of the structural placement is the preferred and feasible solution for the future between the two. The successful development of computer software has dramatically reduced the workload of structural modeling and analysis. At the same time, the combination of considering the use of high-performance materials and rationalizing the structural placement is a highly effective approach, which requires more time from the researcher to solve the difficulties and challenges. This paper provides a clear direction for research into seismic problems in concrete buildings.

Development of the SIDEM Application (Advanced Village Information System) as an Administrative Management System for Kedawung Village

PPK Ormawa is a community service and empowerment program initiated by student organizations. In particular, PPK Ormawa HMJ Informatics at the Widya Gama Lumajang Institute of Technology and Business devised SIDEM, a village administration system for Kedawung Village. SIDEM utilizes Agile methods, allowing swift and successful software development. The system's outcome is a user-friendly design benefiting both village officials and communities. The application of Agile methods facilitated flexibility, promptly adapting to evolving requirements and incorporating feedback. This approach ensured the system's functionality while aligning with Kedawung Village's specific needs. Agile's rapid development further enabled timely implementation, potentially significantly improving village administration and communication. SIDEM's design emphasis on usability demonstrates a commitment to user-centered development, empowering local stakeholders. Ultimately, the success of SIDEM's Agile-driven development underscores the significance of agility and user-centric design in community service initiatives. This model serves as a valuable example for future technology-based community empowerment projects.

The key factors contribute to time pressure in software development projects: A review

The success of software development projects is often hindered by time pressure (TP), leading to decreased productivity, compromised quality, and increased risk of failure. To address this issue, it is crucial to understand the key factors contributing to TP in software development projects. In line with the study's objectives, the review methodology followed the Kitchenham and Charters criteria, and a search strategy encompassed four primary digital databases, namely IEEE, ACM Digital Library, Science Direct, and Springers, resulting in 4,500 relevant sources. After applying inclusion and exclusion criteria, a total of 128 papers were selected for analysis. This paper offers a comprehensive overview of the factors contributing to TP in software development. This study synthesizes the findings from multiple studies to guide practitioners in improving their project management approaches and highlights the significance of enhancing various aspects of the development process. The findings highlight the importance of improving project management, estimation techniques, knowledge, and skills to effectively manage TP. Additionally, managing requirements volatility, setting clear goals and objectives, and reducing distractions and interruptions emerge as crucial strategies for mitigating TP and enhancing project success. Furthermore, selecting software developers based on their personality traits is recommended to foster a work environment conducive to reduced TP and improved software development outcomes. By understanding and addressing these factors, software development teams can alleviate TP and increase the likelihood of successful software products. Implementing these recommendations can contribute to reduced TP, improved project outcomes, and enhanced overall success in software development.

The characteristics of successful military IT projects: a cross-country empirical study

In the armed forces, successful digitalization is crucial to ensure effective operations. Much of the existing literature on project factors during the planning and execution phases of public IT projects do not focus specifically on military sector projects. Therefore, the paper aims to provide empirical insights into the characteristics of successful military IT projects. Data from such projects in NATO countries and agencies were collected through interviews and project documents. The findings relating to the main variable of interest, “delivery of client benefit,” supported previous findings on IT project performance. Medium-sized projects performed better than small and large projects, and the agile development method delivered more client benefit than traditional methods. Client involvement apparently had a positive effect on project success. Clearly specified objectives had a statistically significant effect on project success in terms of clients’ benefits. The paper contributes to the gap in research on military IT projects and broadens the project management literature’s focus on time and cost to include delivery of client benefit as a success variable. The use of cross-country data provided unique insights for academics and practitioners regarding which project characteristics affect the successful development and adoption of new software by the armed forces.

Prioritizing Use Cases: A Systematic Literature Review

The prioritization of software requirements is necessary for successful software development. A use case is a useful approach to represent and prioritize user-centric requirements. Use-case-based prioritization is used to rank use cases to attain a business value based on identified criteria. The research community has started engaging use case modeling for emerging technologies such as the IoT, mobile development, and big data. A systematic literature review was conducted to understand the approaches reported in the last two decades. For each of the 40 identified approaches, a review is presented with respect to consideration of scenarios, the extent of formality, and the size of requirements. Only 32.5% of the reviewed studies considered scenario-based approaches, and the majority of reported approaches were semiformally developed (53.8%). The reported result opens prospects for the development of new approaches to fill a gap regarding the inclusive of strategic goals and respective business processes that support scenario representation. This study reveals that existing approaches fail to consider necessary criteria such as risks, goals, and some quality-related requirements. The findings reported herein are useful for researchers and practitioners aiming to improve current prioritization practices using the use case approach.

On Fuzzy and Case-Based Dynamic Software Development Process Modeling and Simulation Approach

The software development process (SDP) is complex because it uses specific knowledge, skills, tools, and techniques to deliver value to people, and the user’s needs are always growing and becoming more complex. Practitioners and academics have proposed different approaches for improving the successful implementation of the SDP. This remains a non-trivial task, and the number of successful software development projects increases only slightly each year. This paper proposes a new approach for adapting the classical SDP to a dynamic, knowledge-intensive, and context-dependent model by applying the case-handling and fuzzy inference approaches for SDP modeling and simulation. The advantages and novelties of this approach consist in: SDP dynamicity modeling using the case-handling approach; the inclusion of human factor uncertainty into the execution of SDP activities through fuzzification; and agent-based simulation, which allows for the inclusion of human actors in SDP simulations. Modeling and simulation of Agile SDPs were carried out using this prototype. Experiments show the correspondence of the proposed approach to the needs of dynamically changing and human-factor-dependent SDPs, as well as the possibilities for modeling and simulating the SDP, predicting SDP execution, and observing possible risks.

COMPARATIVE ANALYSIS OF AGGREGATION AND INHERITANCE STRATEGIES IN INCREMENTAL PROGRAM DEVELOPMENT

Programming computers has been a herculean task for most programmers especially when codes grow into complex and larger software systems with multiple subprograms. Object Oriented Programming (OOP) has reduced the difficulty in the development of elegant and scalable software by presenting robust concepts such as composition, inheritance and aggregation. All these concepts have enormous assistance to the software developer in code reuse. Also these techniques can be used to build applications which can be delivered to customers in a record time. In this research a critical study, review and implementation of software building and enhancement using aggregation and inheritance. A module is built with attributes defining it properties and methods its characteristics. Incrementally more modules were added to the previous modules using either aggregation or inheritance technique. This incremental approach has proven tremendous success in software development. This as buttressed by many software development theories have shown that: software is built not manufactured; software is a collection of programs with functions and attributes based on its enhancement, also incremental software development which involves building systems from sub-systems gives a better understanding of software development process. Also the process of writing bug-free programs can be achieved with lesser difficulty which can be achieved when programs are built using modular or incremental software development approach, which employs mostly aggregation while moderately using inheritance only if all the properties and methods of those modules are needed wholesomely in classes. The result from the research will help programmers to enhance codes with much mastery.

The Influence of Organizational, Process and Individual Factors on Software Development Success

The Influence of Organizational, Process and Individual Factors on Software Development Success