Exploring the role of generative AI in enhancing cybersecurity in software development life cycle

This research is motivated by the management of the Jami Al-Kautsar Mosque in Depok which has not been properly recorded and the data storage is scattered. These constraints have the potential for data loss and inaccurate information and a process taking a long time to produce such information. In this study, the data collection techniques used are observation, interviews and literature study. The information system built uses the waterfall method as a software development or Software Development Life Cycle (SDLC) using object-oriented design of the Unified Modeling Language (UML) and testing using Black Box. The process in this study includes the process of managing activities, managing the mosque, inventory, finances and goods (income and expenditure). The results of research implemented by the author on the Management Information System of the Jami Al-Kautsar Mosque is a system that can provide information on the management of activities, mosque administrators (human resources), inventory, finances and goods (income and expenditure) as well as communicative and informative reports so that they can make evaluation materials and transparent accountability reports from the management to all congregations of the Jami Al-Kautsar Mosque. User satisfaction with the evaluation information system uses the five-category Black Box test and produces a good information system. Three categories of Black Box testing are no errors in functions, database access and structure and system performance above 60%.

Software security is an essential requirement for software systems. However, recent investigation indicates that many software development methodologies do not explicitly include methods for incorporating information security into the software development life cycles (SDLC). This research investigates, using case study, the methodologies being used in software development in Saudi Arabia and describes a model for integrating security into the SDLC. The aim is to identify the appropriate means of introducing security measures much earlier in the SDLC. This model is designed to be an extension to the existing SDLC. For achieving the research objectives and answering the research questions, the research followed a case study research design in an information‐based organization. The research identified various important elements as security standards, policies, processes being practiced, and tools used within SDLC projects. In this regard, recommendations and verification were gathered to elicit the actual activities that are appropriate to be conducted at each phase of SDLC. The non‐functional security requirements were also found, to the use of fortify and hp alm for source code review and web application testing. Copyright © 2016 John Wiley & Sons, Ltd.

Software Development Life Cycle (SDLC) is an important concept used in software engineering to describe a procedure for planning, creating, coding, testing and implementation of user requirement specification. Software development life cycle applies to a range of hardware and software configurations. SDLC is step by step process for creating quality software for users. It involves different phases that are followed one after one, that are essential for software engineers such as planning, analysis, design, coding, testing and implementation. In the early years, hardware was costly and software relatively cheap. In digital era, hardware is cheap and software is expensive. So the costs of hardware and software have been reversed due to increased demand of well engineered software products. This paper includes different phases of SDLC, software quality, qualities of well engineered software and factors affecting software quality. Key words: SDLC, Phases, Software Quality, Factors

Among the many pressing concerns in the realm of computers, software project development is among the highest. System development life cycle is a part of this (SDLC). A key goal of the software development life cycle (SDLC) is to reduce the likelihood of errors while improving the quality of the final result. Without a well-defined set of steps, the software development process is a pretty complicated affair. Method established to standardize and streamline software development. The introduction of the SDLC (Software Development Life Cycle) existence. What we have here is a methodical and organized approach to the process of creating software. Using the SDLC as a guide, entails a wide variety of steps and processes that must be completed before the final programmer is released. Software comes in many forms. Types of software development life cycles, each with their own benefits and drawbacks, are commonly employed in the software development process. Disadvantages Five of these software development life cycle (SDLC) models, including the waterfall model, the v-shaped model, and the prototype model, are presented in this study. Existing models are compared using a spiral and an iterative structure.

Security is critical to the success of software, particularly in today's fast-paced, technology-driven environment. It ensures that data, code, and services maintain their CIA (Confidentiality, Integrity, and Availability). This is only possible if security is taken into account at all stages of the SDLC (Software Development Life Cycle). Various approaches to software quality have been developed, such as CMMI (Capability maturity model integration). However, there exists no explicit solution for incorporating security into all phases of SDLC. One of the major causes of pervasive vulnerabilities is a failure to prioritize security. Even the most proactive companies use the “patch and penetrate” strategy, in which security is accessed once the job is completed. Increased cost, time overrun, not integrating testing and input in SDLC, usage of third-party tools and components, and lack of knowledge are all reasons for not paying attention to the security angle during the SDLC, despite the fact that secure software development is essential for business continuity and survival in today's ICT world. There is a need to implement best practices in SDLC to address security at all levels. To fill this gap, we have provided a detailed overview of secure software development practices while taking care of project costs and deadlines. We proposed a secure SDLC framework based on the identified practices, which integrates the best security practices in various SDLC phases. A mathematical model is used to validate the proposed framework. A case study and findings show that the proposed system aids in the integration of security best practices into the overall SDLC, resulting in more secure applications.

Security in the Software Development Life Cycle (SDLC) has become imperative due to the variety of threats posed during and after system design. In this paper we have studied the security in system design in general and software development in particular, and have proposed strategies for integration of security in the SDLC. The paper highlights the needs of embedding security right from the earlier processes in the SDLC because patches and controls after the software delivery are more expensive to fix. We propose Source Code EMbedded (SCEM) security framework to improve the design of security policies and standards for the software development process to ensure the security and reliability in government departments such as taxation, auditing, national security, social security, and immigration. It is also envisaged that the implementation of SCEM security framework will ensure commercial and public trust in the software development process within Australia and worldwide, saving enormous redevelopment costs.

Medical device standards' requirements for traceability during the software development lifecycle and implementation of a traceability assessment model

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.

The software development life cycle process is a crucial methodology that software developers use to create high-quality software products. In the requirements-gathering phase, the software development team works with stakeholders to define the project's objectives, scope, and requirements. The design phase involves creating the software architecture, which outlines the software's structure, components, and interactions. In the testing phase, the software is tested to ensure that it meets the requirements and functions correctly. The SDLC process plays a critical role in creating software that meets user requirements, is of high quality, and can be maintained and updated over time. By following a systematic approach, software development teams can ensure that the software they create is reliable, secure, and efficient. Overall, the SDLC process is a comprehensive methodology that software developers use to create high-quality software products. Software Development Life Cycle plays a major role in the life of a software engineer. Design thinking can be used to make the software development life cycle more powerful. This paper involves a discussion on how software development life cycle can be made powerful and used to satisfy the client's requirements.

Software development life cycle (SDLC) is developed much prior to evolution of unified modeling language (UML) (design diagrams). The stages of SDLC are syllogized when design stage comprises single level design diagrams and is accepted by the software developers as de-facto standard life cycle. UML is a multilevel state-of-the-art design language comprises number of design diagrams to represent different perceptive views of the System. UML helps to design stratification grammar. Now the introduction of UML diagrams creates commotion across and within SDLC stages. Since both are de-facto standards and both are essential for au-courant software development process. Neither can be jettisoned at the cost of the other. Thus there is a need either resurrect the syllogism definition or to resuscitate UML to reestablish constellation within and across UML. This paper attempts to resuscitate the constellation within UML as it is a sub part of SDLC. The class diagram represents class name, attributes, object methods along with their visibility, signature and interrelationships. The object diagrams which also containing similar information except the additional object and state information. In the middle level the usecase diagram defines real world of an actor in terms of its needy usecases. This cannot constellate the class diagram as the cluster of syntactics and semantics of class diagram cannot represent pragmatics of usecase. Analogical to the data flow diagram at higher level and usecase diagram at the middle level justifies its existence. Since it cannot constellates higher level class diagram there is a need to develop a stereotype of use case diagram that constellates a class diagram. This paper desiderates this need by pulling down object diagram with mutatis-mutandis to suite the stereotype of usecase diagram and constellates the class diagram.

The security risk assessment is a daunting process that usually requires an in-depth knowledge of the pertinent attack scenarios and the technical understanding of all the security measures implemented in the organization. Small and medium-sized businesses are especially challenged as they can often not operate a full information security department. Sometimes the shortage of security skills and security data for the reason of limited IT resources. Software threats are progressively being used in internet-based, web-data servers, web services, and GUI-based applications. The type of threat modeling is intended for each phase before the accomplishment of the software product. Finding software and hardware threat is the most critical task in the software development life cycle (SDLC). The threat modeling process is included in SDLC at the beginning stage for minimizing the risks. This paper investigates threat attacks in the software development life cycle (SDLC) using threat categorization of risk-based approaches for security threats in the early phase. The intrusion detection attack has been identified for a web application of the healthcare management system. It is classified based on the severity of stages in the Life cycle. The proposed method findings are compared with the Microsoft stride to identify the boundaries of components, ranking of the attacks, and better understand software development and operation threats in software development process.

The software development process needs specific and studied steps within a reliable plan to achieve the requirements for the success of any project. Software development life cycle (SDLC) methodologies have provided several models that meet the needs of the various proposed projects. These methodologies present various scenarios that can be applied in the process of developing systems to make them more efficient and predictive. The paper aims to illuminate the paramount Software Development Life Cycle (SDLC) methodologies by conducting a comprehensive review of the pros and cons of the various models widely used for software design. Furthermore, the paper discusses fundamental trajectories that are shaping the future landscape of SDLC methodologies. This review included two main types of software development life cycle approaches such as traditional SDLC (heavy-weight) and agile SDLC (light-weight) approaches. The traditional approach included several models such as the Waterfall model, Iterative model, Spiral model, V-Model, and Big Bang Model. Whereas, the agile approach included various models such as the eXtreme Programming (XP) Model, scrum Model, Feature Driven Development (FDD) Model, and Kanban Model. A comprehensive analytical study of all software development life cycle models was achieved and highlighted their most prominent strengths and weaknesses of them. SDLC methodologies wield substantial ramifications across a multitude of sectors, contingent upon several models tailored to individual developmental and research contexts. In culmination, the paper furnishes an all-encompassing perspective on paramount SDLC models, encompassing two principal paradigms: the traditional and the agile approaches. These encompass fundamental sub-models that encapsulate pioneering models poised for application in system development, thus facilitating their refinement more efficiently and predictably.

The selection of a software development life cycle (SDLC) model for a software project is highly dependent upon the characteristics of the software product to be developed. We classified software products according to characteristics that matter for SDLC selection. We surveyed literature to elicit recommendations for SDLC selection. We formalized our findings to present a rule based recommendation system that can be helpful to software developers in selecting the most appropriate SDLC model to be used for the development of a software product. We conducted an initial evaluation of our system. We believe our SDLC recommendation system provides useful hints for selecting an SDLC, and provides a base for validating and refining SDLC recommendation rules.

Risk management in the software development lifecycle (SDLC) is a continuous process that addresses risks throughout a system's lifecycle, including acquisition, development, maintenance, or operation. Despite its importance, ineffective risk management practices can lead to project failures, impacting organizations financially and reputationally. Therefore, there is a need for a systematic understanding of risk management practices in SDLC. This study conducts a Systematic Literature Review (SLR) related to risk management activities performed by previous research during the SDLC. The SLR method combines Kitchenham with the toll-gate method to select literature for use. This SLR aims to investigate activities in traditional waterfall and agile development processes, which will be mapped into risk management activities in SDLC according to ISO 16085:202. Additionally, the review highlights the challenges encountered in implementing risk management in the SDLC process, including project complexity, adherence to policies and standards, lack of communication, lack of resources, and organizational culture.

Summary form only given as follows. This paper discusses an innovation in teaching the Systems and Software Development Life Cycle (SDLC) in the Graduate School of Management and Technology at University of Maryland University College. The innovation is a Meta-Project that takes the form of a series of linked projects across the four classes that cover the SDLC. The benefits that the Meta-Project provides the student with, are a better understanding of the interaction between the phases in the SDLC, and a better ability to cope with the vagueness of the real world. The students thus experience the entire SDLC of a system in four semesters. They learn by completing their assignments in the phase of the SDLC covered by the class. They do this handicapped by the consequences of poor performance up-schedule in a previous phase. Consequently, they develop an awareness of the effect of poor performance in any phase of the SDLC on its later phases. As iterations of the courses in SDM track continue and issues are uncovered, the Meta-Project will adjust and improve itself. This will help to provide UMUC with an educational program that is geared toward preparing the students to cope with the projects that they will be expected to complete in the real world. As with any new project, the initial reception has been mixed. The Meta-Project links a series of projects in each of four classes by using products and skills developed in one class in others.