loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Problem Statement is the Problem
March/April 2005 (vol. 3 no. 2)
pp. 80
ASCII Text
x 
 
Daniel Geer Jr., "The Problem Statement is the Problem," IEEE Security and Privacy, vol. 3, no. 2, pp. 80, March/April, 2005.
 
 
BibTex
x
 
@article{ 10.1109/MSP.2005.53,
author = {Daniel Geer Jr.},
title = {The Problem Statement is the Problem},
journal ={IEEE Security and Privacy},
volume = {3},
number = {2},
issn = {1540-7993},
year = {2005},
pages = {80},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2005.53},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - The Problem Statement is the Problem
IS - 2
SN - 1540-7993
SP
EP
EPD - 80
A1 - Daniel Geer Jr.,
PY - 2005
VL - 3
JA - IEEE Security and Privacy
ER -
 
Daniel Geer Jr., Verdasys
A problem statement encouraging elegance is spare, unadorned, clean, and leaves the designer as much room as can be left. This is the hardest part of any design process. A good problem statement is a mentor and a supervisor. It asks the right question. A good problem statement extends its writer's skill and wisdom so that, if those are in short supply, the problem statement can make up for some of that itself.
Citation:
Daniel Geer Jr., "The Problem Statement is the Problem," IEEE Security and Privacy, vol. 3, no. 2, pp. 80, Mar./Apr. 2005, doi:10.1109/MSP.2005.53
Usage of this product signifies your acceptance of the Terms of Use.