Welcome to the InfoSci Platform
Reference Hub3
Security Requirements Engineering for Evolving Software Systems: A Survey

Security Requirements Engineering for Evolving Software Systems: A Survey

Armstrong Nhlabatsi, Bashar Nuseibeh, Yijun Yu
Copyright: © 2012 |Pages: 21
ISBN13: 9781466615809|ISBN10: 146661580X|EISBN13: 9781466615816
DOI: 10.4018/978-1-4666-1580-9.ch007
Cite Chapter Cite Chapter

MLA

Nhlabatsi, Armstrong, et al. "Security Requirements Engineering for Evolving Software Systems: A Survey." Security-Aware Systems Applications and Software Development Methods, edited by Khaled M. Khan, IGI Global, 2012, pp. 108-128. https://doi.org/10.4018/978-1-4666-1580-9.ch007

APA

Nhlabatsi, A., Nuseibeh, B., & Yu, Y. (2012). Security Requirements Engineering for Evolving Software Systems: A Survey. In K. Khan (Ed.), Security-Aware Systems Applications and Software Development Methods (pp. 108-128). IGI Global. https://doi.org/10.4018/978-1-4666-1580-9.ch007

Chicago

Nhlabatsi, Armstrong, Bashar Nuseibeh, and Yijun Yu. "Security Requirements Engineering for Evolving Software Systems: A Survey." In Security-Aware Systems Applications and Software Development Methods, edited by Khaled M. Khan, 108-128. Hershey, PA: IGI Global, 2012. https://doi.org/10.4018/978-1-4666-1580-9.ch007

Export Reference

Mendeley
Favorite

Abstract

Long-lived software systems often undergo evolution over an extended period. Evolution of these systems is inevitable as they need to continue to satisfy changing business needs, new regulations and standards, and introduction of novel technologies. Such evolution may involve changes that add, remove, or modify features; or that migrate the system from one operating platform to another. These changes may result in requirements that were satisfied in a previous release of a system not being satisfied in subsequent versions. When evolutionary changes violate security requirements, a system may be left vulnerable to attacks. In this paper we review current approaches to security requirements engineering and conclude that they lack explicit support for managing the effects of software evolution. We then suggest that a cross fertilisation of the areas of software evolution and security engineering would address the problem of maintaining compliance to security requirements of software systems as they evolve.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.