CSC 480 Software Engineering Lecture 20 Nov 13, 2002
Apr 02, 2015
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
CSC 480 - Software Engineering 311/13/2002
The Structure of RUP
A process describes who is doing what, how. and when. Workers (who) Activities (how) Artifacts (what) Workflows (when)
CSC 480 - Software Engineering 411/13/2002
Worker, Activities, and Artifacts
CSC 480 - Software Engineering 511/13/2002
Workflow, etc
A workflow is a sequence of activities that produces a result of observable value
Additional Process ElementsGuidelinesTemplatesTool mentorsConcepts
CSC 480 - Software Engineering 611/13/2002
UI Design Activities & Artifacts
CSC 480 - Software Engineering 711/13/2002
The Requirements Workflow
CSC 480 - Software Engineering 811/13/2002
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.
CSC 480 - Software Engineering 911/13/2002
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.
CSC 480 - Software Engineering 1011/13/2002
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
CSC 480 - Software Engineering 1111/13/2002
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
CSC 480 - Software Engineering 1211/13/2002
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
CSC 480 - Software Engineering 1311/13/2002
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
CSC 480 - Software Engineering 1411/13/2002
Email Management – class diagram
CSC 480 - Software Engineering 1511/13/2002
Email Manag’t – collaboration diagram