![](bgb.png)
Acknowledgement
We would like to thank all reviewers of this paper who provided valuable feedback,
especially Stefan Seltzsam and Steffen Fries for their support.
References
1. Khaled El Emam and A. G
¨
unes Koru. A replicated survey of it software project failures.
IEEE Software, 25(5):84–90, 2008.
2. Department of Homeland Security. Requirements analysis for secure software, 2012.
3. Andy Greenberg. A tax on buggy software, 2008. http://www.forbes.com/2008/06/26/
rice-cyber-security-tech-security-cx ag 0626rice.html. Visited on January 15th, 2014.
4. Barry W. Boehm. Software engineering economics. Prentice-Hall advances in computing
science and technology series. Prentice-Hall, Englewood Cliffs and N.J, 1981.
5. G. McGraw. Testing for security during development: why we should scrap penetrate-and-
patch. Aerospace and Electronic Systems Magazine, IEEE, 13(4):13–15, 1998.
6. Golnaz, Elahi, Yu, Eric, Tong Li, Lin Liu. Security requirements engineering in the wild: A
survey of common practices. In Proceedings of the 35th Annual IEEE International Com-
puter Software and Applications Conference, Proceedings - International Computer Software
& Applications Conference, pages 314–319, Danvers, 2011. IEEE.
7. John Wilander and Jens Gustavsson. Security requirements – a field study of current practice,
2005.
8. Nancy R. Mead. Security requirements engineering, 2006. https://buildsecurityin.
us-cert.gov/bsi/articles/best-practices/requirements/243-BSI.html. Visited on January 15th,
2014.
9. Theodore Winograd, Holly Lynne McKinley, Lyndon Oh, Michael Colon, Thomas McGib-
bon, Elaine Fedchak, and Robert Vienneau. Software security assurance: A State-of-the Art
Report (SOAR). Information Assurance Technology Analysis Center, Herndon and Virginia,
2007.
10. Donald G. Firesmith. Engineering security requirements. Journal of Object Technology, vol.
2, no. 1,, pages 53–68, 2003.
11. Haralambos Mouratidis, Paolo Giorgini, and Gordon Manson. When security meets soft-
ware engineering: a case of modelling secure information systems. Information Systems,
30(8):609–629, 2005.
12. Eric Dubois and Haralambos Mouratidis. Guest editorial: security requirements engineering:
past, present and future. Requirements Engineering, 15(1):1–5, 2010.
13. Frank Swiderski and Window Snyder. Threat modeling. Microsoft Press, Redmond and
Wash, 2004.
14. PTA Technologies. Practical threat analysis for information security experts. http://
www.ptatechnologies.com/default.htm. Visited on January 15th, 2014.
15. Yue Chen. Software security economics and threat modeling based on attack path analysis;
a stakeholder value driven approach. University of Southern California. Libraries, 2007.
16. J. McDermott and C. Fox. Using abuse case models for security requirements analysis. In
Computer Security Applications Conference, 1999. (ACSAC ’99) Proceedings. 15th Annual,
pages 55–64, 1999.
17. Ian F. Alexander. Initial industrial experience of misuse cases in trade-off analysis. In
Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements
Engineering, RE ’02, pages 61–70, Washington and DC and USA, 2002. IEEE Computer
Society.
73