Requirements of the user interface: Use-case story board (1) The use-case storyboard –Complements use-cases by user-interface issues –Takes the use-cases‘ flow of events in order to complement it (verbally or with sketches) with user-interface issues and usability aspects –Is used to understand requirements of the user interface, including usability requirements –Is intended to support the communication between the use-case designer and the user- interface designer

Requirements of the user interface: Use-case story board (2) The use-case storyboard (continued) –Is used to describe and reason about multiple version of the user interface before it is prototyped. –Is further described in terms of boundary classes, their prefered features, and their static and dynamic relationships. Each boundary class is itself a high-level representation of a window or similar construct in the user interface.

Use-case story board – features and steps Start at the flow of events description of a use case and complement it in a stepwise fashion Complements are: –What shall be displayed where –Desired guidance –Average attribute values and volumes of objects –Average action usage

Use-case story board – example The following is an example of the final flow of events - storyboard of a storyboard for the use case Manage Incoming Mail Messages, augmented with the various usability aspects. a) The use case starts when the mail user requests to manage mail messages, and the system displays the messages. [The user should be able to differentiate between new, read, and unread messages; the user should also see the sender, subject, and priority of each message.] {An average of 100 unread mail messages are shown simultaneously; and in 90% of the cases, the subject line of a message is less than 40 characters.} b) The mail user may then follow one or more of these steps: c) Arrange mail messages according to sender or subject. (Done in more than 60% of the cases.)

Use-case story board – example d) Read the text of a mail message. {The message text contains 100 characters on average.} (Done in more than 75% of the cases.) e) Save a mail message as a file. (Done in less than 5% of the cases.) f) Save a mail-message attachment as a file. [The user should be able to see the file types of the attachments.] {In 95% of the cases, there are less than two attachments.} g) The use case terminates when the mail user requests to quit managing incoming mail messages.

Use-case story board – example Class diagram

Use-case story board – example Collaboration diagram