 | It is another hook for users to hang their ideas on when trying to explain what they want
|
|
|
| It provides a structural aspect to the procedural aspect of the use case text.
|
| It provides a place to attach detailed data format and constraint information that doesn't belong in the use case text.
|
| The prototype screen should be consistent with the use case text
|
| It doesn't have to be created in the target technology. This one was done using basic shapes in word
|
| The amount of detail in the design of the screen at this point should be proportional to its importance to the users. In other words it should contain only that which is a user requirement not detailed design decisions that are unimportant to the users
|
