Security considerations for the spiral development model

Ray, Loye Lynn

doi:10.1016/j.ijinfomgt.2013.03.003

Cited by 4 publications

(5 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[15] and The spiral model is consistent with an approach that includes multiple software builds and allows for an orderly transition to maintenance activities [7]. Spiral models can be implemented for IT infrastructure security [17] and security protects software products from deployment [14]. Implement the security development phase in a spiral model and propose new security [13].…”

Section: Rq1 What Research Topics Use the Spiral Method?mentioning

confidence: 99%

The Systematic Literature Review of the spiral development model: Topics, trends, and application areas

et al. 2022

View full text Add to dashboard Cite

The spiral model is one of the methods used to perform software engineering development and can also be used for development in other fields. This spiral model is the result of a modification from the combination of the waterfall model and prototyping model so that it has many advantages including in each result an evaluation will be carried out, carried out sequentially or systematically, and is more focused in carrying out risk analysis from each stage. Has a function in development to make changes, additions and developments by determining accuracy and speed based on needs. In its implementation the spiral model has been carried out in various fields, but the results of the implementation are not yet known in what scope and how many implementations each year. This study aims to identify the results of the implementation of the spiral model development with data obtained from related papers in the 2012-2022 range. The method used in this study is the Systematic Literature Review (SLR) with the aim of identifying, reviewing, evaluating, and concluding all research on each relevant paper. The results showed that the spiral model development was mostly implemented in software development with a total of 19 papers and in the education sector as many as 17 papers, while the peak of the spiral model development was mostly implemented in 2016 and then increased again in 2021

show abstract

Section: Rq1 What Research Topics Use the Spiral Method?mentioning

confidence: 99%

The Systematic Literature Review of the spiral development model: Topics, trends, and application areas

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Key words such as "security requirements", "Software development methodologies", "Software development framework", "Traditional Software Development Methods" and "Agile software Development Methods" were appropriately combined with Boolean operators of "AND", "NOT" and "OR", to identify only literatures which focused on elucidating security requirement gathering abilities in various software development methodologies. Some security requirement standards such as CC (Davoud Mougouei, Sani, & Almasi, 2013; Wäyrynen et al, 2004), SSE-CMM, SQUARE (Mead, Viswanathan, & Padmanabhan, 2008;Ray, 2013) and NIST recommendations on information security requirement considerations, were identified in the survey and explored for security requirement activities (Jones & Rastogi, 2004;Raj et al, 2014). The suitability of the software development methodologies, regarding information security requirement development in software, were then assessed by using the security requirement activities as a reference point.…”

Section: Methodsmentioning

confidence: 99%

“…In the spiral model, a partial list of the objectives, alternatives and constraints (Ray, 2013) are initially obtained. The model usually begins with this incomplete requirement but with add on functionalities as it progresses in its various stages.…”

Section: Security Requirements In Traditional Software Development Me...mentioning

confidence: 99%

Comparative Analysis of Software Development Methodologies for Security Requirement Analysis: Towards Healthcare Security Practice

Yeng

Wolthusen

Yang

2020

Proceedings of the 13 Th IADIS International Conference Information Systems 2020

View full text Add to dashboard Cite

Reducing time to market (TTM), dynamic requirement changes and increasing profit to service providers are some of the features that are most interesting to software developers, in their look-up for software development methodologies. Security requirement features in system development methodologies are often not the primary concern of developers until now. Due to the increasing rate of data breaches in healthcare, software engineers in healthcare are desiring for suitable methods which have been incorporated with security requirement activities, for effective security requirement analyses. This study surveyed on existing software development methodologies and assessed their suitability for security requirements gathering and analysis towards enhancing information security assurance in healthcare. Security requirement activities were obtained from software security engineering standards and guidelines. The security activities were then assessed in existing software development methods to determine their extend of incorporation towards secure software development in healthcare. In this review, the traditional software development methods, including the Waterfall Model, were realized to have more integration of security requirement capturing activities than the agile methods.

show abstract

“…(2) Research on managing the software development process via Capability Maturity Model CMM and CMMI [7,8]. (3) Research on software project life cycle models, such as waterfall model [9], iterative model, incremental model [10,11], and spiral model [12]. However, there are limited studies on the optimization of software project management processes using defect management.…”

Section: Introductionmentioning

confidence: 99%

Using GQIM Model and Gompertz Model to Measure, Analyze, and Optimize the Whole Process of Software Project

Zhao

Wang

et al. 2023

Mathematical Problems in Engineering

View full text Add to dashboard Cite

This paper proposes a novel concept of using defect management technology to measure, predict, and optimize the management of the entire software project cycle. It first utilizes the software defect measurement GQIM model and prediction Gompertz model to track and quantify the defects of the entire project cycle. Then, the specific optimization strategy is proposed to manage the core processes of the project management, including project scope management, project time management, project quality management, project human resource management, project communication management, and project risk management. This study solves the quantification problems that are common in the current software project management process, such as complex testing procedures, high defect repair costs, and high communication costs. Furthermore, it contributes to promote the overall level of project management in the software industry. Taking the SDLM’s electronic banking software project management as an example, the various management quality indicators before and after the optimization of the project management process strongly indicate that using software defect management technology to optimize the software project management process is feasible and effective.

show abstract

Security considerations for the spiral development model

Cited by 4 publications

References 2 publications

The Systematic Literature Review of the spiral development model: Topics, trends, and application areas

The Systematic Literature Review of the spiral development model: Topics, trends, and application areas

Comparative Analysis of Software Development Methodologies for Security Requirement Analysis: Towards Healthcare Security Practice

Using GQIM Model and Gompertz Model to Measure, Analyze, and Optimize the Whole Process of Software Project

Contact Info

Product

Resources

About