ACM SIGSOFT Software Engineering Notes · 2005 · 320 citations · 11 references
EngineeringProject ManagementQuality EngineeringRequirements EngineeringSecure Software DevelopmentQuality RequirementsRequirements AnalysisRequirements ManagementRequirements ModelingSecure Requirements EngineeringSecurity RequirementsFunctional Requirements AnalysisFunctional Requirements ModelingRequirements Engineering For Secure SystemsSecurity EngineeringSecurity Requirements AnalysisSecurity Requirements ElicitationSecurity Requirements ModelingSecurity Requirements Specification
Requirements engineering, a vital component in successful project development, often neglects sufficient attention to security concerns. Further, industry lacks a useful model for incorporating security requirements into project development. Studies show that upfront attention to security saves the economy billions of dollars. Industry is thus in need of a model to examine security and quality requirements in the development stages of the production lifecycle.In this paper, we examine a methodology for both eliciting and prioritizing security requirements on a development project within an organization. We present a model developed by the Software Engineering Institute's Networked Systems Survivability (NSS) Program, and then examine two case studies where the model was applied to a client system. The NSS Program continues to develop this useful model, which has proven effective in helping an organization understand its security posture.
11
A cost-value approach for prioritizing requirements
Jenny Karlsson, Kevin Ryan · IEEE Software · 1997 · 728 citations