Editing Use case (section)

==== Design scopes ====

Cockburn suggests annotating each use case with a symbol to show the "Design Scope", which may be black-box (internal detail is hidden) or white box (internal detail is shown). Five symbols are available:<ref>Cockburn, 2001. Inside front cover. Icons "Design Scope".</ref>

{| class="wikitable"
|-
! Scope !! Icon|| 
|-
| Organization (black-box) || Filled House || [[File:Scope-icons-filled-house.png|Scope-icons-filled-house]]

|-
| Organization (white-box) || Unfilled House || [[File:Scope-icons-unfilled-house.png|center|Scope-icons-unfilled-house]]
|-
| System (black-box) || Filled Box || [[File:Scope-icons-filled-box.png|center|Scope-icons-filled-box]]
|-
| System (white-box) || Unfilled Box || [[File:Scope-icons-unfilled-box.png|center|Scope-icons-unfilled-box]]
|-
| Component || Screw or Bolt || [[File:Scope-icons-screw-bolt.png|center|Scope-icons-screw-bolt]]
|}

{{clear}}

Other authors sometimes call use cases at the Organization level "Business use cases".<ref>Suzanne Robertson. ''Scenarios in Requirements Discovery''. Chapter 3 in Alexander and Maiden, 2004. Pages 39-59.</ref>