loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Risk Analysis in Software Design
July-August 2004 (vol. 2 no. 4)
pp. 79-84
ASCII Text
x 
 
Denis Verdon, Gary McGraw, "Risk Analysis in Software Design," IEEE Security and Privacy, vol. 2, no. 4, pp. 79-84, July-August, 2004.
 
 
BibTex
x
 
@article{ 10.1109/MSP.2004.55,
author = {Denis Verdon and Gary McGraw},
title = {Risk Analysis in Software Design},
journal ={IEEE Security and Privacy},
volume = {2},
number = {4},
issn = {1540-7993},
year = {2004},
pages = {79-84},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2004.55},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - Risk Analysis in Software Design
IS - 4
SN - 1540-7993
SP79
EP84
EPD - 79-84
A1 - Denis Verdon,
A1 - Gary McGraw,
PY - 2004
KW - software development
KW - software design
KW - misuse cases
KW - abuse cases
VL - 2
JA - IEEE Security and Privacy
ER -
 
Denis Verdon, Fidelity National Financial
Gary McGraw, Cigital
Software development is all about making software do something: when software vendors sell their products, they talk about what the particular products do to make customer's lives easier, such as improving business processes or something similarly positive. Following this trend, most systems for designing software also tend to describe positive features.
Index Terms:
software development, software design, misuse cases, abuse cases
Citation:
Denis Verdon, Gary McGraw, "Risk Analysis in Software Design," IEEE Security and Privacy, vol. 2, no. 4, pp. 79-84, July 2004, doi:10.1109/MSP.2004.55
Usage of this product signifies your acceptance of the Terms of Use.