CSC 480 Software Engineering Lecture 20 Nov 13, 2002

CSC 480Software Engineering

Lecture 20Nov 13, 2002

CSC 480 - Software Engineering 211/13/2002

UI Design in RUP

Major concepts in RU Analysis by use case storyboarding Interaction modeling using boundary

classes UI prototyping


The Structure of RUP

A process describes who is doing what, how. and when. Workers (who) Activities (how) Artifacts (what) Workflows (when)


Worker, Activities, and Artifacts


Workflow, etc

A workflow is a sequence of activities that produces a result of observable value

Additional Process ElementsGuidelinesTemplatesTool mentorsConcepts


UI Design Activities & Artifacts


The Requirements Workflow


UI Designer’s Responsibilities

Flow of events-storyboard and associated diagrams are readable and suits its purpose.

Usability requirements are readable and suit their purpose, and correctly capture the usability requirements of the corresponding use case in the use case model.

Trace dependency to the corresponding use case in the use case model is correct.

Relationships of the corresponding use case are handled correctly within the use case storyboard.


UI Modeling Activities

Describe the characteristics of related actors. Create a use case storyboard. Describe the flow of events-storyboard. Capture usability requirements on the use case

storyboard. Find boundary classes needed by the use case

storyboard. Describe interactions between boundary objects and

actors. Complement the diagrams of the use case storyboard.


UI Modeling Activities – continued

Refer to the user interface prototype from the use case storyboard. For the identified boundary classes, follow these steps: Describe the responsibilities of boundary classes. Describe the attributes of boundary classes. Describe the relationships between boundary classes. Describe the usability requirements on the boundary classes Present the boundary classes in global class diagrams

Evaluate results


UI Prototype

A UI prototype is a rough initial model of the UI Paper sketches Bitmaps from a draw tool An interactive executable prototype

Purpose Understand the UI for a use case Understand the impact on the system – what it

requires from the “inside” of the system Plan testing activities


UI Prototyping Activities

For each use case storyboard to be prototyped Design the UI prototype Implement the UI prototype Obtain feedback on the UI prototype

Design Identify and design primary windows

Visualization Operations


Use Case Storyboarding

A use case storyboard is a logical and conceptual description of how a use case is provided by the UI. It is described in terms of Boundary classes

Properties Relationships – aggregations, associations Interactions


Email Management – class diagram


Email Manag’t – collaboration diagram

Documents

CSC 480 Software Engineering Lecture 20 Nov 13, 2002