|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Grady Booch, "Unintentional and Unbalanced Transparency," IEEE Software, vol. 28, no. 5, pp. 12-13, September/October, 2011. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2011.112, author = {Grady Booch}, title = {Unintentional and Unbalanced Transparency}, journal ={IEEE Software}, volume = {28}, number = {5}, issn = {0740-7459}, year = {2011}, pages = {12-13}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2011.112}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Unintentional and Unbalanced Transparency IS - 5 SN - 0740-7459 SP12 EP13 EPD - 12-13 A1 - Grady Booch, PY - 2011 KW - architecture KW - software-intensive system KW - security KW - privacy KW - software engineering KW - standards and best practices VL - 28 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2011.112
Security and privacy are interdependent concepts. Each impacts the other, but to say that they are alternatives is a false dichotomy. Both are issues of human concern; their policies and their risks may be made manifest in software-intensive systems. Architecting a system that attends to the needs of security and privacy is possible and desirable, yet there are often unintended and unexpected consequences in so doing.
Index Terms:
architecture, software-intensive system, security, privacy, software engineering, standards and best practices
Citation:
Grady Booch, "Unintentional and Unbalanced Transparency," IEEE Software, vol. 28, no. 5, pp. 12-13, Sept.-Oct. 2011, doi:10.1109/MS.2011.112
Usage of this product signifies your acceptance of the Terms of Use.

