Abstract
In the modern digital era, software systems are extensively adapted and have become an integral component of human society. Such wide use of software systems consists of large and more critical data that inevitably needs to be secured. It is imperative to make sure that these software systems not only satisfy the users’ needs or functional requirements, but it is equally important to make sure the security of these software systems. However, recent research shows that many software development methods do not explicitly include software security measures during software development as they move from demand engineering to their final losses. Integrating software security at each stage of the software development life cycle (SDLC) has become an urgent need. Tackling software security, various methods, techniques, and models have been suggested and developed, however, only a few of them provide strong evidence for building secure software applications. The main purpose of this research is to study security measures in the context of the development of secure software (SSD) during the study of systematic mapping (SMS). Based on the inclusion and exclusion criteria, 116 studies were selected. After the data extraction from the selected 116 papers, these were classified based on the quality assessment, software security method, SDLC phases, publication venue, and SWOT analysis. The results indicate that this domain is still immature and sufficient research work needs to be carried out particularly on empirically evaluated solutions.
Highlights
Over the last two decades, the software industry observed phenomenal growth, and the same is continued at a rapid pace
It is reported that the findings, in our study reported in this paper, will have an impact on the body of information by providing a tax on the Secure Software Engineering (SSE)-related research topic that may invite researchers to focus on further research in this field
This study aims to analyze the process of software development from the perspective of each software development life cycle (SDLC) phase and to attempt to define key security measures to be used to make the most secure applications in all stages of the SDLC
Summary
Over the last two decades, the software industry observed phenomenal growth, and the same is continued at a rapid pace. System designers are doing their best to find the most powerful design Developers are doing their best to improve the app in a very efficient way. Testers do their best to detect software crashes. Engineers only broaden particular requirements (overall performance necessities) and ignore safety requirements It will be more beneficial if they take the security requirements in the earlier phases and following the same in the requirement gathering phases; such as design, development, and testing. Once they incorporate the security at all stages of SDLC, the software developed by adapting the security measures will produce more secure software
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
