Requirements in the software lifecycle

The software development process model or what is commonly called SDLC (Software Development Life Cycle) is one of the Software Engineering (RPL) course materials in the Information Engineering Education (PTI) undergraduate study program where one of the competencies is understanding and knowing the concepts of device engineering software that can be applied in the software development life cycle which is summarized in the material for the SDLC software development process model. This material is the initial material that must be mastered by students to develop quality software. The use of interactive and interesting computer assisted learning media is expected to help the stages of the student learning process properly. This requires an interactive learning multimedia application. The purpose of this research is to develop interactive learning media as an alternative to independent learning tools to assist students in mastering the Software Development Process Model (SDLC) material for students and to find out the feasibility of multimedia application products for learning the Software Development Process Model (SDLC). The research and development methodology used in this research is Research and Development (R&D) with Borg and Gall's development steps which include: (1) Research and data collection; (2) Planning; (3) Development of product drafts; (4) Initial field trials; (5) Revision of trial results (6) Field trials; (7) Product improvement; (8) Field implementation test; (9) Completion of the final product; and (10) Dissemination of implementation. This methodology covers all matters relating to development to produce quality interactive learning media software. Based on the trials, the results obtained were 90.63 percent from media experts, 98.08 percent from material experts, 85.46 percent from initial field trials, 84.56 percent from field trials, and 86.27 percent from field implementation trials. The average value obtained is 89 percent based on the results of the overall data analysis. The conclusion of this research is that the development of multimedia applications for learning the Software Development Process Model (SDLC) is feasible as an independent learning medium. The product produced in this development research is a multimedia application for learning flash-based software development process (SDLC) models.

Cybersecurity risks are increasing in frequency and complexity, but many organizations struggle to plan and implement adequate protections at all stages of the software development life cycle (SDLC). Security is frequently added at the end of development (afterthought), and making effective use of safeguard space is difficult for IT leaders. The purpose of this study is to produce an all‐encompassing framework to adopt and ensure security throughout each phase of the SDLC, from planning through maintenance. The aim is to minimize vulnerabilities and improve the resilience of software by making “security by design” a structure that not only adopts security elegantly as a living document but also is built to be part of the development process. This study adopted a mixed‐methods approach. The initial stage of inquiry involved a systematic literature review (SLR) to identify common cybersecurity issues associated with each SDLC phase. The SLR was followed by an empirical survey of 71 software professionals from a variety of organizations. The survey was designed to gather perceived threats, current practices, and challenges associated with software development for survey participants' organizations. The data collected were analyzed and reviewed statistically, through chi‐square tests and ANOVA, to profile the variance relative to the size of the organization, geographic region, and experience level of the practitioner. The results noted several high‐risk challenges across the SDLC: underfunded security controls, imprecise requirements, insecure architecture, software bugs (i.e., injection vulnerabilities), inadequate testing, misconfigured production environments, and unreliable maintenance. The proposed framework provides cybersecurity mitigation techniques for each stage of the SDLC, such as leveraging security‐oriented design patterns, secure coding policies (i.e., input validation and authentication protocols), robust testing (i.e., penetration testing and code review), and continuous monitoring after deployment. The implementation of these measures leads to a significant risk reduction in the overall organizational security posture. The framework is a formalized end‐to‐end approach to secure software development by embedding security throughout the cycle. Embedding security as a part of the process versus an afterthought at every stage of the cycle creates a risk reduction impact. This integrated approach also provides organizations with the opportunity to foresee and mitigate events earlier in the cycle, along with general compliance mandates (i.e., GDPR, HIPAA, and PCI‐DSS), to provide more resilient, trustworthy software systems.

Selection of appropriate Software Development Life Cycle(s) can increase projects success. Depending on the selected SDLC (Software Development Life Cycle), one can decrease development time/cost, minimize overhead and risk exposure, manage uncertainty, improve quality, promote client relations, and provide better project tracking and control. Despite the benefits of using suitable SDLC(s), it is generally difficult to select the most appropriate one. There is not enough information in the literature about the criteria and how to take them into account to select appropriate SDLC(s). Frequently used SDLCs and their comparative properties were elicited from literature, Internet and experts according to the criteria to select appropriate SDLC(s). A Fuzzy Logic (FL) system was developed according to the elicited knowledge about the criteria and their affect on selecting suitable SDLCs in various cases. Fuzzy input/output variables, membership functions and fuzzy rules were defined and generated according to the elicited knowledge. The FL system was tested for various inputs and improved according to the test results.

Apart from the different formats of software process descriptions and life cycle models as discussed in the previous chapter, there are many different types of such models. The basis for these models is formed by several fundamental life cycles, in particular sequential models such as the waterfall model or the V-shaped model, and iterative-incremental models such as the spiral model or Scrum. These fundamental life cycles can be varied in many forms, or extended by adding information leading to detailed process models such as the (Rational) Unified Process. The models can also include different sets of processes, where at one end of the spectrum, software processes support software development by structuring the different development-related activities. At the other end of the spectrum, software processes also provide a more comprehensive perspective, e.g. including operation and IT service management, or interfacing with organisational and administrative tasks. Depending on the purpose of the model, there are some very different types of process reference models available, including for example method-driven life cycle models, agile methodologies, process assessment models. In this chapter, we survey these different types of software processes and their role in the software life cycle. We provide a categorization of software processes, introduce the basic life cycle models, and present some selected reference models.

The software development life cycle (SDLC) is a structured process for delivering a high-quality product within a specified timeframe. Developing a cost-effective and efficient software product life cycle has always been a priority in software engineering, which can impact product quality. This study aims to provide an overview of the recent articles that focus on applying optimization techniques, mathematical models, and software cost estimation in the software development process and propose possible future directions. For the selected 29 studies, the development phase of the SDLC is most commonly focused on in studies. This emphasis highlights the pivotal role of optimization and mathematical modeling in enhancing software development efficiency.

The rise in software development has intensified reliance on complex applications across sectors. However, this growth is paralleled by increased cybersecurity threats, revealing critical vulnerabilities within the Software Development Life Cycle (SDLC). Agile and DevOps methodologies, while offering speed and adaptability, often overlook vital security concerns, thus heightening exposure to cyber risks. This study addresses a novel research gap by examining how discrepancies in security integration across SDLC methodologies can lead to significant gaps in cybersecurity posture. Using a combination of case study scenarios, literature-informed analysis, and focus groups with subject matter experts, this research presents a comprehensive applied approach to cybersecurity in software development. Notably, the study engages participants with advanced expertise and real-world experience, whose insights enhance understanding of secure SDLC integration’s theoretical and practical aspects. This multi-method approach provides emerging cybersecurity professionals with actionable hands-on strategies to identify and mitigate vulnerabilities, aligning with current industry standards. The study’s findings underscore the urgency of standardized security practices within the SDLC, contributing to developing industry-wide best practices prioritizing security alongside speed and flexibility. By bridging theoretical frameworks with applied research, this study offers significant advancements for cybersecurity education and industry practice, preparing future professionals to address evolving cybersecurity challenges effectively.

Introduction to Software Development Life CycleThe Software Development Life Cycle (SDLC) can be defined as a comprehensive and visual representation of the entire journey of a software product, starting from its inception and continuing until its retirement or end of usefulness.It encompasses all the necessary activities that need to be undertaken throughout the software's life cycle, depicting the order in which these activities are performed.The SDLC provides a descriptive and diagrammatic representation of the various stages involved in the development, deployment and maintenance of a software product.It serves as a roadmap, outlining the sequential execution of tasks, processes and methodologies employed to ensure the successful creation, evolution, and eventual retirement of the software.Essentially, the SDLC captures the entire spectrum of activities performed on a software product, guiding its development and management from beginning to end.The SDLC typically consists of the following stages: Requirements gatheringIn this phase, the project requirements are collected by communicating with stakeholders, users, and domain experts.The goal is to understand the needs and expectations of the software. DesignThe design phase involves creating a blueprint for the software solution.This includes designing the architecture, database structure, user interface, and other system components.The design should address the functional and non-functional requirements of the software. DevelopmentIn this phase, the actual coding of the software takes place.Developers write code based on the design specifications and programming languages.This stage may involve multiple iterations and testing to ensure the software meets the desired functionality. TestingThe developed software undergoes various testing processes to identify and fix bugs, errors, and other issues.This includes unit testing, integration testing, system testing, and user acceptance testing.The goal is to ensure that the software functions correctly and meets the specified requirements. Deployment/ImplementOnce the software has been thoroughly tested and approved, it is deployed to the production environment.This involves installing the software on the target systems and making it available to end users.Configuration and data migration may also be performed during this phase.

This history column article provides a tour of the main software development life cycle (SDLC) models. (A lifecycle covers all the stages of software from its inception with requirements definition through to fielding and maintenance.) System development lifecycle models have drawn heavily on software and so the two terms can be used interchangeably in terms of SDLC, especially since software development in this respect encompasses software systems development. Because the merits of selecting and using an SDLC vary according to the environment in which software is developed as well as its application, I discuss three broad categories for consideration when analyzing the relative merits of SDLC models. I consider the waterfall model before the other models because it has had a profound effect on software development, and has additionally influenced many SDLC models prevalent today. Thereafter, I consider some of the mainstream models and finish with a discussion of what the future could hold for SDLC models.

This paper presents two concept models to compare and contrast conventional software development life cycle(SDLC) and the development of smart applications where Artificial Intelligence/Machine Learning (AI/ML) modules are integrated into the software products. The first concept model illustrates the intersections and differences between SDLC and AI/ML-based application development; whereas, the second concept model depicts the processes/concepts involved in data preprocessing stage of AI/ML-based application development. The concept models show that while there are some similarities between SDLC and AI/ML-based application development; AI/ML-based development follows its own unique features and challenges that need development of further software engineering techniques.

Software Engineering encompasses a lot of processes of which writing of efficient codes for development of high quality and effective programs is one of them. Development of quality software is achieved through a well-articulated Software Development Life Cycle (SDLC) model. Delivery of software project within timeline and budget require thorough analysis from which these two pertinent questions must be answered such as what shall we do next and how long shall we continue to do it’? Therefore, the need for an appropriate SDLC model for a software project is of high significance. V-Model is applicable in project that requires a lot of time and are complex in nature. When the focus of the project is more of quality than fast delivery time, then V-Model is a choice of SDLC to be considered. Also, Waterfall model is desirable when quality control is of concern with short project duration. On the other hand, Spiral Model is desirable when organizational expectations are unpredictable concerning the software development process. Irrespective of the size of the project, delivery time and level of expertise involved, the organization of the project plays a significant role in the choice of SDLC model. SDLC model under consideration, must take into cognizance the level of risk, duration of the project and cost implication associated with every software project for successful completion. Comparative analysis of the three SDLC models studied was presented.

Software projects typically require effort estimation from the software development life cycle (SDLC) staff at the commencement of the software development activities. Inaccuracies in effort estimation of software projects early on in the SDLC continues to be a perennial problem. Typically, improved estimates for software projects are provided under circumstances where requirements engineering (RE) is completed. RE provides a key reference in the form of requirements for the estimation process. However, RE by itself may consume significant effort demanding the RE phase to be estimated as the first step in the SDLC. It is difficult to establish RE estimates, as RE usually has no tangible reference on which estimates can be based. This paper provides a practical estimation method for large and complex RE processes. We demonstrate using a case study snapshot in a large software organization that the method provides improved effort estimates for the RE process.

Serious mental illness (SMI) is a leading disability worldwide. Partnering with people with SMI to co-produce smartphone apps to support mental health outcomes throughout the software development lifecycle may support patient engagement with smartphone health app interventions. Partnering with this community is often challenging and requires a highly specialized community engagement training and skillset. The purpose of this study was to identify stakeholders' perspectives on partnering to inform the software development lifecycle of a smartphone health app intervention for people with SMI. We conducted thirty-five semi-structured qualitative interviews with 20 mental health patients and 15 peer support specialists. We identified six themes: (1) co-produce health app intervention content; (2) selection of app technology features; (3) integration of human factors in digital health apps; (4) consideration of personalized patient preferences in digital health apps; (5) identify unrecognized concerns early in the software development lifecycle; and (6) inclusion of real-world social, cognitive, and environmental contexts. Integration of these considerations may elucidate the partnering process to facilitate engagement among vulnerable populations that commonly disengage from mental health smartphone apps use such as people with SMI.

Patterns are a means for capturing experience in solving general problems. They give general solutions to common and recurring problems. They exist at various phases of the software development life-cycle (SDLC), namely the analysis phase, the design phase, the coding phase and the testing phase. Patterns in each phase are identified independently. It is possible for the patterns of one phase to be related to patterns in other phases. This paper proposes pattern mapping to inter-relate the patterns of various phases in SDLC to address this issue. It is advantageous to capture the related patterns of different phases as a single unit for software development. Reusable integrated components (ICs) of patterns are proposed to capture the related patterns. A software IC is a group of inter-related patterns, that gives solutions for a recurring problem at various phases of SDLC. A representation mechanism for ICs is presented using the URA (Unified Representation of an Artifact) model, which captures the software development process. Also, this paper proposes a software development process that is based on reusable ICs of patterns. The representation of a software project developed using ICs is also discussed.

The rising of technology in the 21st century grows in a way that we never thought of before. The COVID-19 pandemic shifted many organizations in different sizes, specialties, and sectors to work online, resulting in a critical need to secure their software, applications, and web-based applications. Furthermore, Organizations that do not implement security in the Software Development Life Cycle (SDLC) process often discover that their applications suffer from security flaws and security bugs, thus exposing their applications to attacks. Applying security measures to the SDLC will ensure that applications are secure from the early planning stages until release. Penetration testing is an essential security measure and is counted as one of the best security practices applied to applications because it focuses on the technical part of application security. Each kind of application the organization uses, in-house developed applications or on-the-shelf applications, has its method for penetration testing. This paper is a systematic literature review that examines the web application security measures and the penetration testing methods and tools to detect vulnerabilities on web applications. Moreover, it gives a general view of adapting penetration testing as a security approach to the SDLC.

A risk management framework for distributed agile projects