Systems Design Engineering

SyDe 542 - Interface Design

Grading and Assignments

University of Waterloo Logo

 


                                                                                                                                                

Home Page

Announcements

Schedule of Lectures

Grading/Assignments

Frequently Asked Questions

Topics from previous years 

Presentations

Presentation Marking Sheet

 

 

 

Jan. 7: Checkpoint 1: Project Proposal  5%

 

Write a paragraph max 200 words describing what your project might be.  Answer the following questions:

-          What is the problem you are trying to solve?

-          How do people solve it now?

-          Why would EID be a good approach?

Guide to Checkpoint Marking

Are you truly solving a problem?  /2

Does EID fit the problem?  /2

Do you know how the problem is solved now?  /1

Late 1 day   -1/day

Explanation too long  -1

 

Jan. 24: Checkpoint 2: Work Domain Analysis 5%

 

Submit a 1 page version of your WDA.  Discuss or write a paragraph that answers the following questions:

  • Where is the system boundary?  What’s in the system and what’s not?
  • What are the purposes of the system?
  • What are the principles behind the system?
Guide to Checkpoint Marking

Understanding of levels and bounding  /5

Late 1 day  -1/day

Explanation too long  -1

 

Feb 2: Checkpoint 3: Information Availability Analysis 5%

 

Submit a 1 page table of Information Requirements from your WDA.  Indicate which variables are readily available, which could be calculated or simulated, which can not be obtained.

 

Feb. 9: Checkpoint 4: Phase 2 Design Sketch  5%

 

Submit a 1 page sketch of your design to date.  The design should show major variables and elements of context. 

 

Feb. 16: Checkpoint 5: Phase 3 Design Sketch 5%

 

Submit a 1 page sketch showing 1 place in your design where you can develop a graphic that integrates several variables.

 

 

March 9 (updated): Report 1: Prototype and Description of Design 40%

 

  • Work domain analysis with information requirements and availability discussion 10/40
  • Description of the design (using course terms counts here) 5/40
  • Description of prototype (tools used, level of prototype, objectives) 5/40
  • Prototype (demonstration of design concepts, quality of the prototype as a testing tool, pizzazz) 20/40

 

 

March 30: Report 2: User Testing Results and Recommendations for Design Improvement 20%

 

  • Write up as a lab report.
  • Objectives -  describe your key areas of interest. 5/20
  • Method – describe your method, show how it attains objectives, set targets. 5/20
  • Results – frankly report your results in a quantitative manner. 5/20
  • Discussion – what is good about your design, what needs improvement, be honest. 5/20

Results: Who were your users? Report their performance on the task. Did they make any comments about your interface?  Frankly report your results in a quantitative manner

Discussion: Discuss what you have learned about the interface. What parts were good and what parts need improvement and how? Where your users appropriate to do this evaluation or should you have used different users? What were the limitations of your evaluation? If you had more time would you evaluate further?

As scheduled: Presentation 15%

 

Presentations are 15 minutes long with 5 minutes for discussion/questions.

The order each day will be the order of sign up.

Next presenters should be ready to swap equipment during the discussion period.

 

Either bring your own laptop, or burn a CD. The only applications that will be provided for presentation purposes are MS Powerpoint and Internet Explorer.

 

See the presentation marking sheet.

 

 

This page was last updated Feb 28, 2005