Software Development Life Cycle Research Articles

Transforming Software Development Through Generative AI : A Systematic Analysis of Automated Development Practices

This article presents a comprehensive analysis of the transformative impact of Generative Artificial Intelligence (GenAI) on software development practices. Through systematic evaluation of implementations across multiple development environments, this article demonstrates how GenAI technologies significantly enhance four critical areas of the software development lifecycle: code generation, automated testing, intelligent code review, and predictive failure analysis. The findings indicate a 45% reduction in initial code development time through automated code generation, 60% improvement in test coverage through AI-driven test case creation, and 30% decrease in post-deployment issues through predictive failure analysis. The article employs a mixed-methods approach, combining quantitative analysis of development metrics from 50 software projects with qualitative assessments from 200 professional developers across diverse organizational contexts. Results reveal that organizations implementing GenAI-assisted development workflows experience a mean productivity increase of 37% while maintaining or improving code quality metrics. Additionally, the article identifies key integration challenges and provides a framework for effective GenAI adoption in software development environments. These findings contribute to the growing body of knowledge on AI-assisted software development and offer practical insights for organizations seeking to optimize their development processes through GenAI integration.

PERANCANGAN SISTEM INFORMASI ANALIS BREAK EVEN POINT DAN STOK PADA BUDIDAYA AYAM POTONG BERBASIS WEB

Although broiler chicken farming offers many benefits, there are also risks of losses, especially when production costs are not accurately recorded, leading to inaccurate per-unit pricing that can harm farmers. To assist farmers in accurately determining the Break Even Point (BEP) price for each chicken, a web-based cost and stock management information system for broiler farming has been developed. To provide a clear and sequential software lifecycle approach, this system was built using the waterfall method, which includes the stages of requirements analysis, design specifications, coding, testing, and maintenance. Each stage produces measurable outcomes before proceeding to the next. The development results indicate that the system successfully records the total production costs, including detailed costs for feed, medicine, operational expenses, and chicken stock. By using the formula BEP = total production cost/number of live chickens, the system achieves accurate pricing for broiler chickens. Based on these findings, future research is suggested to improve the user interface for greater appeal, optimize system accessibility on mobile devices, and integrate this system with other systems.

Forecasting of Menstruation using a Calendar-based Method based on a Web Application

Accurately predicting menstrual dates is valuable for women, yet it poses a significant challenge, particularly for those with irregular cycles. This study introduces a web application that utilises a calendar-based method to predict upcoming menstrual dates while offering additional features such as tracking past periods, logging symptoms, and providing personalised health advice. Using the software development life cycle approach, the critical contribution of this work is the development of a user-friendly tool that not only aids in menstrual tracking but also highlights the limitations of calendar-based predictions, especially for women with irregular cycles. Our findings suggest that while the method provides accurate predictions for women with regular cycles, it is less reliable for those with irregular cycles due to its dependence on a fixed cycle length range. This study underscores the need for more adaptive models to improve prediction accuracy for a broader population.

Evaluating the Role of Data Privacy Regulations in Secure Software Development Life Cycles (SDLC)

Evaluating the Role of Data Privacy Regulations in Secure Software Development Life Cycles (SDLC)

DevSecOps practices and tools

Nowadays, software development happens at a fast pace. At the same time, Information Technology organizations face higher demands and competition while struggling with external threats such as cyberattacks. Therefore, many organizations adopt DevOps as a working culture to improve their Software Development Lifecycle (SDL). However, the success of DevOps adoption remains inconsistent, and recently, IEEE introduced a DevOps standard that might help improve DevOps adoption. The standard mentions DevSecOps as the security aspect of DevOps, adding security practices to the SDL from inception, but what are these practices or capabilities? Which tools can be used to implement these practices? Therefore, a Multivocal Literature Review was performed to identify DevSecOps practices and their definitions, and which tools can be used to implement them.

Comparison of Multi-Agent Platform Usability for Industrial-Grade Applications

Modern systems often employ decentralised and distributed approaches. This can be attributed, among others, to the increasing complexity of system processes, which go beyond the capabilities of singular components. Additionally, with the growth in demand for system automation and high-level coordination, solutions belonging to the decentralised Artificial Intelligence and collaborative decision-making are often applied. It can be observed that these concerns fall within the domain of multi-agent systems. However, even though MAS concepts emerged more than 40 years ago, despite their obvious advantages and continuous efforts of the scientific community, agents remain rarely used in industrial-grade applications. In this context, the goal of this contribution is to analyse the reasons for the lack of adoption of agent solutions in the real world. During the analysis, all pertinent aspects of the modern software development life cycle are examined and compared to what is currently available in the agent system domain. Specifically, the study focuses on identifying gaps that are often overlooked when it comes to scientific applications of MAS, but are critical in terms of potential for large-scale system development in practice.

Examining the Effectiveness of Continuous Integration and Continuous Deployment (CI/CD) Within SDLC Frameworks

Continuous Integration and Continuous Deployment frameworks have been a subject of significant discussion among numerous software development cycles however their impact on Software Development Life Cycles has not been investigated in detail in this research. With survey data collected from the subjects and interviews conducted on the pre-researched parameters of software quality, time-to-market of the product, and interteam collaboration, the study compares the firms that use CI/CD with those that use more conventional software development approaches. The study shows that CI/CD integration enhances software quality since defects are reduced from 1.5 to 0.5 per thousand lines of code. Furthermore, CI/CD teams have 10 releases per month against 3 of traditional and time-to-market that reduces from 6 weeks to 2 weeks. The improvement of collaboration is very visible, the CI/CD teams said that they had more meetings and their job satisfaction scores increased. As with any change, transitioning to CI/CD has potential drawbacks such as resistance to change, but these can be managed especially through training and what has been said in the article specific practices. Therefore, this research offers important insights to organisations aiming at improving their software development processes and preparedness in a relatively dynamic market environment

Integrating Generative AI into the Software Development Lifecycle: Impacts on Code Quality and Maintenance

Recent advances in generative AI have depicted it as a revolutionary approach in the software development technologies pioneered to improve the codes' reliability and sustain their quality and performance. Generative AI tools can help develop code independently, suggest intelligent solutions and ideas, and enhance several development procedures thanks to superior algorithms and machine learning features. This paper discusses how generative AI can/has been applied within software development to achieve the following three goals: First, to increase the code quality using automated code generation/review. Second, the code maintainability should be improved through standards and documentation. Third, to increase the up-to-speed development productivity due to AI-based automation, namely the automation of repetitive tasks and fast prototyping. The paper also considers issues and difficulties that can be tied to AI in this context: problems of dependence on AI, ethical and security issues, and technical imperfections. Finally, the implications of generative AI in software development in the future are presented, which can open a new direction in the development of software products while primarily pointing to the processes of managing the introduction of generative AI. Using the evaluation of the current possibilities and future perspectives of generative AI presented in this paper, one can conclude its impact on the future of software engineering.

Enhancing integration testing efficiency through AI-driven combined structural and textual class coupling metric

Integration testing, a critical and resource-intensive phase in the software development lifecycle, can account for up to a high percentage of the total testing cost. Identifying classes with high coupling is crucial for efficient integration testing, as these classes are more susceptible to the impact of maintenance-related changes. This research introduces a novel metric called <i>combined structural and textual class coupling</i> (CSTCC), which harnesses the power of artificial intelligence (AI) techniques to predict and rank the most critical classes in an object-oriented software system. CSTCC integrates structural coupling metrics with <i>latent semantic indexing</i> (LSI)-based textual coupling, providing a comprehensive measure of class coupling. LSI, an information retrieval technique, analyses the semantic relationships between classes based on their textual content, enabling CSTCC to capture both structural and conceptual dependencies, resulting in a more accurate identification of high-risk classes. The effectiveness of the proposed approach is rigorously evaluated using mutation testing on four Java open-source projects, and the results demonstrate that test cases developed based on CSTCC achieve high mutation scores, indicating their ability to detect a significant percentage of integration faults. By focusing testing efforts on high-coupling classes identified by CSTCC, developers can potentially save time and cost during integration testing. The results demonstrate that test cases developed based on CSTCC achieve high mutation scores, ranging from 98% to 100%, indicating their ability to detect a significant percentage of integration faults. Additionally, the approach results in substantial efficiency gains, with a notable reduction in the number of test cases needed, saving up to 33.3% of the testing effort in some cases. By focusing testing efforts on high-coupling classes identified by CSTCC, developers can potentially save time and cost during integration testing. The CSTCC metric provides a novel and effective approach to prioritize testing resources and improve the efficiency of integration testing in object-oriented software systems.

A Project Model to Evaluate the Feasibility of the Cognizant Flow Source

This work discussed a project being steered in Cognizant, India for the design, development and implementation of Cognizant Flowsource. Flowsource is an AI-powered, incorporated full-stack platform that accompanies in the succeeding generation of engineering. The IT solution allows quicker innovation by integrating generative AI hooked on vital phases of the software development lifecycle (SDLC), allowing developers to concentrate on rich features and incomparable user experiences (cognizant.com). Initially the researcher applied the Critical Path Method (CPM) to evaluate the feasibility of the project and this was complemented later by developing a Project Evaluation Review Technique (PERT) model. The work also presented costs calculations to determine the applicability of the project. The research reports how the Flowsource development project is being managed by the operations department of the company and suggests alternative manners of solving problems identified in the development of the IT solution.

WATERFALL MODEL OVER PCD.UCT MODEL REVIEW

Abstract. The software development life cycle (SDLC) has seen the evolution of numerous models, each tailored to meet specific project needs. Among these, the Waterfall Model has been a longstanding, traditional approach, characterized by its linear and sequential phases. In contrast, the PcD.UcT Model, a relatively newer framework, advocates for a more iterative and user-centered approach. This paper presents a comprehensive review of the Waterfall Model, evaluating its strengths and limitations in modern software development. It contrasts these findings with the PcD.UcT Model, analyzing how its principles better align with contemporary project demands, particularly in terms of flexibility, user engagement, and iterative refinement. Through this comparative analysis, the paper aims to provide insights into the applicability and effectiveness of each model, offering guidance for software development teams in choosing the appropriate methodology for their projects. Since the waterfall development methodology, the key requirements in system development strategies have shifted from processes to users. Because the process as well as the customers are both equally important, employing either a predictive or an adaptive methodology is extremely difficult. The primary goal of this work is mainly combining and then evaluating all the relevant methodologies in order to create a HydroGIS that accurately automates the complexities of the hydrology process in a HydroGIS environment while meeting all user requirements.

The Power of Words in Agile vs. Waterfall Development: Written Communication in Hybrid Software Teams

Software development is constantly evolving, adapting to emerging technologies and development paradigms while leveraging advancements in communication technologies and work modes. We conduct an exploratory case study in a large software organization to investigate how the development paradigm and the formality of communication channels affect written communication within hybrid teams. We perform statistical and content analysis of written conversations from 20 projects involving two software products that use industry adaptations of the Waterfall model and of Scrum, respectively. We found that in agile-developed projects, communication related to the execution-monitoring-control phase of the Project Management Life Cycle is more prevalent, and communication related to the initiation phase occurs more frequently in informal channels. For both project types, communication primarily pertains to the software construction phase of the Software Development Life Cycle. After annotating communication contents using speech acts, representatives are found to be prevalent in informal channels for agile-developed projects, directives are more prevalent in informal channels for waterfall-developed projects, and expressives are more frequent in informal channels for both project types. We provide empirical evidence that development paradigms and communication channel formality impact written communication, with agile-developed projects showing more collaborative interactions in informal channels compared to waterfall-developed projects.Editor’s note: Open Science material was validated by the Journal of Systems and Software Open Science Board.

Inventory Management System Using Economic Order Quantity And Reorder Point

The inventory management system for car workshops is still using Excel, which makes it inefficient and inaccurate for complex stock calculations. The solution is to design an inventory application that uses the Economic Order Quantity and Reorder Point methods. The application will provide timely stock replenishment information and optimize order quantities, increasing inventory management efficiency and accuracy. The Software Development Life Cycle used in this study is Rapid Application Development, a process emphasizing short development cycles. User Acceptance Test results show that users received the inventory management system very well, with an average satisfaction level of 98.44% for Admins and 97% for general users, indicating high satisfaction with the system's features and functionality.

ІНКРЕМЕНТНИЙ ПІДХІД ДО ПЛАНУВАННЯ РОБОТИ СТУДЕНТІВ НАД СПІЛЬНИМ ПРОГРАМНИМ ПРОЄКТОМ

As of today, well-known product and outsourcing IT companies use Agile models for the software development life cycle (SDLC), the advantages of which include rapid adaptation to changes, continuous feedback, improved product quality, increased team engagement, focus on customer value, transparency and control, as well as the reduction of internal and external risks. All Agile models are iterative, meaning the development process is divided into separate, similar iterations, which have different names in different models. Familiarization with and practical application of modern Agile models by students at the first (bachelor’s) level of higher education in the field of information technology is an important task for future IT specialists. To achieve this task, the most popular Agile model, Scrum, was chosen, which is also incremental, meaning that each iteration delivers additional functionality that is ready for use. The main roles of participants and their responsibilities, artifacts, and ceremonies of the Scrum process are reviewed. The article proposes applying the Scrum model for iterative and incremental software development that will solve a multi-criteria optimization problem using a game-theoretic approach. The formulation and general algorithm for solving the multi-criteria optimization problem using a game-theoretic approach are presented, as well as an example of formulating the Product Backlog, which contains twelve functional requirements to be implemented by the student Scrum team over twelve iterations (sprints). The recommended process for dividing students into Scrum teams and assigning roles to participants is described. An example of incremental implementation based on the Scrum model of the SDLC for solving the multi-criteria optimization problem using a game-theoretic approach is also provided.

Automated Security Vulnerability Backlog Management

In today’s fast-paced development environments, security vulnerabilities often emerge at the same rapid rate as code updates. Security teams and developers face challenges in addressing these vulnerabilities while maintaining operational efficiency. Managing a security backlog manually can be cumbersome, slow, and prone to human error. Automating the security vulnerability backlog allows organizations to track, prioritize, and mitigate security risks more efficiently and effectively, ensuring a secure software development lifecycle (SDLC) without sacrificing agility. This white paper outlines the need for an automated security backlog, the benefits it provides, and strategies for implementing it using modern DevSecOps tools. Keywords — Automated security backlog, vulnerability management, CI/CD, DevSecOps, risk- based prioritization, SAST, DAST, software composition analysis, continuous security, vulnerability tracking, security remediation, cybersecurity automation, security risk management

Shift-left approach for Vulnerability Management in SDLC

Security vulnerabilities in software development can lead to severe risks if not addressed promptly. By adopting a shift-left approach and implementing gating mechanisms in Continuous Integration/Continuous Delivery (CI/CD) pipelines, organizations can mitigate the impact of high and critical vulnerabilities early in the Software Development Life Cycle (SDLC). This paper discusses a practical methodology for integrating security gates into the CI/CD pipeline to prevent the release of software with critical security flaws. Keywords —Vulnerability Management, Shift-Left Security, CI/CD Pipeline, High Vulnerabilities, Critical Vulnerabilities, Security Gating, SDLC, GitLab, Automation.

Enhancing DevSecOps practice with Large Language Models and Security Chaos Engineering

Recently, the DevSecOps practice has improved companies’ agile production of secure software, reducing problems and improving return on investment. However, overreliance on security tools and traditional security techniques can facilitate the implementation of vulnerabilities in different stages of the software lifecycle.. Thus, this paper proposes the integration of a Large Language Model to help automate threat discovery at the design stage and Security Chaos Engineering to support the identification of security flaws that may be undetected by security tools. A specific use case is described to demonstrate how our proposal can be applied to a retail company that has the business need to produce rapidly secure software.

Peningkatan Kepatuhan Regulasi Melalui Pengembangan Sistem Informasi Keuangan Bagi Badan Usaha Milik Desa Menggunakan Teknologi Berbasis Website

This study highlights the inability of village-owned enterprises (BUMDesa) to prepare financial reports according to guidelines, indicating a lack of financial accountability. Researchers attempted to develop a web-based platform to generate BUMDesa financial reports following Ministerial Decree Number 136 of 2022. We focus on the perspective of public sector accounting and accounting information systems to respond to research questions. Furthermore, application development considers the research and development (R&D) method and design science via the software development life cycle stages. A total of six BUMDesa contributed to developing this application. The result is a web-based financial reporting application platform that meets these criteria and guidelines. We also provide a platform usage procedure to facilitate its operation. The contribution of this study is to develop a financial information management platform for BUMDesa that emphasizes reporting accuracy and compliance.

Comprehensive Analysis of Security Requirements Engineering Approaches with Assurance Perspective

Given the wide distribution of software and its current growth, security is inevitable, and software systems have become more complex. To avoid the complexity and protect valuable assets of software systems, researchers, and practitioners in the fields of security requirement engineering (SRE) and security assurance advise incorporating security requirements early in software development life cycle (SDLC). Nowadays, security requirements specification and identification are an active research area for ensuring the effectiveness of software systems. However, security requirement identification is a challenging task due to sheer numbers of threats and attacks to a software system. Previous researchers have identified different SRE techniques, each looking at the same problem from a different perspective. Therefore, a literature review conducted on SRE techniques. We compared and analyzed different SRE techniques to find the most suitable SRE techniques for researchers and practitioners. Selected SRE techniques compared based on various parameters, such as different attributes, requirement elicitation, requirement analysis, project size, and integration of standards. The literature also indicates that among SRE approaches, security quality requirements engineering (SQAURE), secure tropos, security requirements engineering process (SREP), and comprehensive lightweight application security process (CLASP) are the most used SRE approaches that focus on activities such as threats, security requirements identification, and security objectives identification. Unfortunately, several SRE approaches fail to explicitly integrate the security standard and security assurance perspective. Three questions developed for this study: Question 1 is based on comparison of existing SRE approaches, Question 2 is based on SRE with security requirements elicitation and analysis, and Question 3 highlights the incorporation of security requirements assurance by SRE approaches implicitly or explicitly. The researcher must work with the developer to easily adopt SRE approaches to elicit and ensure security requirements for the software system.

Perancangan Sistem Informasi Manajemen Klien Digital Agency PT. XYZ berbasis Website

PT XYZ operates in the service sector and is a creative agency that produces product videos for its clients. During this time PT. XYZ has not implemented a management information system to manage the resources they have and maintain relationships with clients. Ease of access via various platforms is the reason why applications are built based on websites. The stages used in the research correspond to the stages in the software development life cycle (SDLC) in the planning, analysis and design phases. Interviews and literature studies are used to explore the business processes that occur. It was found that there were three types of users, namely super admin, admin, and client. The processes handled by the system include employee registers, client registers, recording incoming orders, project monitoring, and checking employee availability. The diagrams used to explain the system plan that will be created are use case diagrams, activity diagrams, sequence diagrams, and entity relationship diagrams. Lo-fi designs are also created using the Figma application. Further research can continue to the implementation, support and security stages.