|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Ian Alexander, "Misuse Cases: Use Cases with Hostile Intent," IEEE Software, vol. 20, no. 1, pp. 58-66, January/February, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2003.1159030, author = {Ian Alexander}, title = {Misuse Cases: Use Cases with Hostile Intent}, journal ={IEEE Software}, volume = {20}, number = {1}, issn = {0740-7459}, year = {2003}, pages = {58-66}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1159030}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Misuse Cases: Use Cases with Hostile Intent IS - 1 SN - 0740-7459 SP58 EP66 EPD - 58-66 A1 - Ian Alexander, PY - 2003 VL - 20 JA - IEEE Software ER - | |||
A misuse case is the negative form of a use case; it documents a negative scenario. Its actor is an agent with hostile intent toward the system under design. The relationships between use and misuse cases document threats and their mitigations. Use- and misuse-case diagrams (shown in the article) are valuable in threat and hazard analysis, system design, eliciting requirements, and generating test cases.
Citation:
Ian Alexander, "Misuse Cases: Use Cases with Hostile Intent," IEEE Software, vol. 20, no. 1, pp. 58-66, Jan.-Feb. 2003, doi:10.1109/MS.2003.1159030
Usage of this product signifies your acceptance of the Terms of Use.

