Project #1 – Design, Create, and Evaluate a system for helping two people that speak two different languages communicate about getting directions on campus.

 

Assigned: Wednesday, January 7th, 2015

Webpage due: Monday, January 26th, 2015 (before class)

Complete other studentsÕ systems due: Wednesday, January 28th, 2015 (in class)

Final report due: Monday, February 2nd, 2015 (before class)

 

Objectives:

1.   Determine requirements for your system

2.   Design an interface

3.   Create an interface

4.   Evaluate the interface

 

 

Undergraduate students:

Determine requirements and Design (Estimated time: 2 hours)

1.   Interview a potential user to come up with at least two use cases (not a feature list).  From [Cockburn 2001]

a.   Use case: include actors, goals, scope, environment, satisfaction, equipment

2.   Sketch two potential designs using inVision (https://projects.invisionapp.com/) and list the features and functions supported

3.   Share your inVision project with your potential user and have them comment on your designs.  You can choose the final design, but consider your userÕs input.

 

Interface (Estimated time: <8 hours)

1.   Implement a system that allows two people who primarily speak two different languages use one application to communicate about getting directions on campus.  This application must include:

1.   Use Google Translate API to do the language selection and translation (example code will be provided)

2.   Have a Òcomplete interactionÓ button that, when clicked, moves the user to a page in Qualtrics where they will answer at least five survey questions.  Once the questions are answered, the user should click a Òcomplete surveyÓ

 

Evaluation (Estimated time: 1 hours)

1. On the class on Wednesday, January 28th, you will pair up with another person whose primary language is not the same as yours. Your team will be given eight websites to visit and go through a scenario. We will provide the scenarios.  They will be similar to Òask your partner for directions to a nice place to eat dinnerÓ

á      Survey:

á      (1-10, 10 being the highest) Would you recommend our product (website) to a friend? [use this question twice, once for each person in the pair using your system, the rest of the questions can be answered as a group]

á      What did you like least about our website?

á      How easy is our website to use?

á      What features of our website are most important to you?

á      What features of our website are least important to you?

á      You can add more questions if you so choose.

 

 

Graduate students:

Determine requirements and Design (Estimated time: 2 hours)

1.   Interview a potential user to come up with at least two use cases (not a feature list).  From [Cockburn 2001]

a.   Use case: include actors, goals, scope, environment, satisfaction, equipment

2.   Sketch four potential designs using inVision (https://projects.invisionapp.com/) and list the features and functions supported

3.   Share your inVision project with your potential user and have them comment on your designs.  You can choose the final design, but consider your userÕs input.

 

Interface (Estimated time: <8 hours)

1.   Implement a system that allows two people who primarily speak two different languages use one application to communicate about getting directions on campus.  This application must include:

1.   Use Google Translate API to do the language selection and translation (example code will be provided)

2.   Provide an ÒerrorÓ button for the person receiving the translated text to click if they feel the translated text is not understandable.

3.   Have a Òcomplete interactionÓ button that, when clicked, moves the user to a page in Qualtrics where they will answer at least five survey questions.  Once the questions are answered, the user should click a Òcomplete surveyÓ

 

Evaluation (Estimated time: 1 hours)

1. On the class on Wednesday, January 28th, 2015, you will pair up with another person whose primary language is not the same as yours. Your team will be given eight websites to visit and go through a scenario. We will provide the scenarios.  They will be similar to Òask your partner for directions to a nice place to eat dinnerÓ

á      Survey:

á      (1-10, 10 being the highest) Would you recommend our product (website) to a friend? [use this question twice, once for each person in the pair using your system, the rest of the questions can be answered as a group]

á      What did you like least about our website?

á      How easy is our website to use?

á      What features of our website are most important to you?

á      What features of our website are least important to you?

á      You can add more questions if you so choose.

2.   You will then compare the 8 scores you received for your interface scores against your partnerÕs scores.

 

 

Project notes:

á      You do not have to use NetBeans IDE.

á      By Monday, January 26th, 2015 (before class), email the TA (only) the link to your program, and include the languages you speak fluently. 

á      By Monday, February 2nd, 2015 submit your report via the online class management system.

 

Grading

20 points – Design (grading done in evaluation report)

1.   Use cases defined – 5 points

2.   Two designs (include in report) – 10 points

3.   User comments on designs – 5 points

 

40 points - Interface

á      Supporting translation – 30 points (graduate students), 40 points (undergraduate students)

á      Track errors (graduate students only) – 10 points

 

40 points – Evaluation Report - single space, Times New Roman/Arial, 12 pt font, 1 inch margins.  (not adhering = -10 points)

á      Page 1 – System Design (20 points, from above)

1.   InVision screenshots

2.   Use Cases

3.   Discussion about design decisions made based on user comments

á      Page 2 - Study Design – 10 points

1.   Hypothesis and NULL hypothesis – 3 points

2.   Metrics – 2 points

3.   Procedure – 5 points

á      Page 3 - Data analysis – 20 points (12 for grad)

1.   For the hypothesis:

1.   Report means, standard deviations, t-values, p-values

2.   Reject/accept null hypothesis and hypothesis

3.   Explain what the statistical results mean

2.   (grad only) for the error tracking, present the means and identify if there is a correlation between errors and user recommendation – 8 points

á      Page 4 - Conclusions – 10 points

1.   Bias/confounds – 5 points

2.   Design lessons learned – 5 points

 

Extra Credit

Interface with the highest recommendation score - +10 points

 

[Cockburn 2001] http://alistair.cockburn.us/get/2465