DesignWIKI

Fil Salustri's Design Site

Site Tools


design:situated_use_case

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
design:situated_use_case [2021.05.03 17:44]
Fil Salustri [What is a situated use case?]
design:situated_use_case [2021.10.01 10:28]
Fil Salustri [How are situated use cases specified?]
Line 39: Line 39:
   * a unique ID (so it's easier to refer to in later stages of designing),   * a unique ID (so it's easier to refer to in later stages of designing),
   * a brief descriptive title,   * a brief descriptive title,
-  * the identify of the team member responsible for that SUC, and+  * the name of the team member responsible for that SUC, and
   * a description of the situation.   * a description of the situation.
 +
 +**When developing an SUC, you ought to depend on your [[situation scan]]**. Every aspect of the sitscan will bear on the development of every SUC. SUCs that are not consistent with the sitscan are simply wrong.
  
 Below is an example SUC for a system to move people between floors of a building((Yes, we might call that an "elevator", but we always prefer to talk about function and not structure when we're just starting a new design project.)). Below is an example SUC for a system to move people between floors of a building((Yes, we might call that an "elevator", but we always prefer to talk about function and not structure when we're just starting a new design project.)).
design/situated_use_case.txt · Last modified: 2021.10.01 10:28 by Fil Salustri