The user interface (UI) project is a semester long team project designing and implementing an Web Application.


You and your team will learn a design process. The design process will involve several design changes, in other word it will evolve as your team improves the design. You will implement enough of the design so that graduate students can design a usability test and assist you in the testing.

Design process steps:

  1. The project begins with forming your team and selecting potential applications (apps) to design. I will assign the apps to the teams based on your preference.
  2. After receiving your app assignment, your team will meet with the scientist. From information that you gather from the interviews with the scientist, your team will make a website and design the interaction.
  3. Your team will receive an interaction and stakeholder analysis from the graduate student. You use these design documents and your interaction design documents to make paper prototypes for your app. Your team will present the paper prototype during the walkthrough.
  4. The graduate students will send your team a heuristic evaluation after the walkthrough. Using the results of the heuristic evaluation, your team will refine the paper prototype. Your team will meet with me in the design review to present your refined design.
  5.  After beginning the implementation of the app design, your team will present to the class your final design. This is another walkthrough, which the class on the whole can delineate potential usability problems.
  6.  Finally, after helping the grad students conduct the usability tests, your team will meet with me to discuss your implementation and recommend design changes.

Team Coordination

The team size should be about 5 or 6 CS students and 2 or 3 HU students. CS and HU students work as a team to plan and design the apps. After designing the app, the CS undergraduate students will primarily be responsible for implementing the app.  STC students will do the technical writing for the app and insure that the technical content for apps are implemented. Students from both disciplines should work together to complete the app including documenting their work and conducting usability tests.

While choosing teams consider schedules, jobs, where prospective members live and work, and anything else that might impact how well the team will function. You should schedule meetings well in advance to ensure participation of all team members. During your meetings, take notes on your design decisions and how you reached your decision, so that you can use the notes in preparing your reports.

This project is a team activity. When you send e-mail to me about your project send it from your team email list and copy the list so that all team members will receive my reply and the original email.

Try to divide the project among team members so that every member of the team has experience in each phase of this process.

Team Meeting Documents

For team meetings to effective, two meeting documents should be written and posted and the team websites.

Meeting Agenda

The meeting agenda is short documented written before the meeting listing the topics that will be discussed and decided during the team meetings. This documents allows all team members to prepare for the meeting. It should emailed via the team email list before the meeting. Post the meeting agenda on the website as an historical record of the purpose of the meeting.

Meeting Minutes

Meeting minutes are written by the team. They are not individual note taking. They record who attended the meeting, what team member will do, what decisions where made, and what will be discussed in the next meeting. The outline of the meeting minutes is

  • Team Name
  • Date, time and duration of the meeting
  • Location or Media of the meeting, for example “in-person at Reki 101” or by “Google Hangouts”
  • Attendance.  List of people who attended the meeting. Indicate if a member is late or has an excused absences.
  • Action List.  This a list that specifies tasks that team members will preform in the near future. Each item in the list should be a single line specify the member name and the task that the member will preform.
  • Discussions and Decisions.  This is a list of topics that were discussed in the meeting and the decisions that where made. Each item of the list only needs to be a two sentence, one describing the discussion and the other the sentence giving the decision made.
  • Next Steps.  This is a list of topics that will be discussed in the next meeting.

The meeting minutes is the product of the meeting, so they should be posted on the team website immediately after the meeting is adjourned.

Team Directory and Website


Your team will be given a group directory for the course. All documents associated with the assignments should be kept in the directory, including notes and the website. The organization of the directory should be clear to an outsider (especially me) so that they can follow your work.

All files in the group directory will have at least group and user access. I will be a member of the group.


Your group directory will have a www subdirectory, which will contain your home page and design documents.  I expected you to maintain a website in the directory. Please do not redirect the browser to another directory or server. Place all your documents in this directory or subdirectories.

The web pages and design documents should be readable by the public. Each team is responsible for maintaining and designing their web pages.  Recall that this is a HCI course, so although I do not expect elaborate websites, I do expect clear and well organized websites.  The web site design and implementation will be part of your project grade.

Reports and Presentations

All reports and presentations are to be posted online by the time of the due dates and with links to them in your website. Your design documents should be in a format that is readable by any web browser.  Figures should be pasted in the documents; they need not need to be elaborately drawn. During the semester, Graduate students will write supporting documents for your project. The graduate students will give your team links to these documents. Your website should have links to the graduate students’ documents.

I will read the reports online and write a text file with my evaluations and email the entire team the evaluations.

Scientist/Client Meeting Notes

Your team should make notes during your meeting with scientists and post them on your team websites. These notes are different from team minutes. These meeting notes are for recording all that you learn from your meeting with the scientists. So you will try to record as much as you can during the scientists meeting. See my lectures on interviewing for more details. Karla and I plan to study the interaction between your team and scientist. We plan to use your scientists meeting minutes to learn the details of your interaction with your scientists. So, Karla and I request that your notes contain:

  • Team and Scientists Names
  • Date, time and duration of the meeting
  • Location or Media of the meeting, for example “by Zoom” or “by Phone”
  • Attendance – list of team members and scientists present at the meeting.
  • Discussion items – list of items discussed with specifics about the topics.

Scientist meeting notes should posted on the your team website immediately after the meeting


I will use the class email list to announce the order of presentation, so be sure that you are getting the class emails.

Some assignments instruct you to send me an email. When you send the email use the subject line specified in the assignment, so I will be assured to recognize your email as a course correspondence. To be sure that you receive full credit for the assignment, send your email to me early.

Team Project Assignment Pages

  1. Team and Application Selection
  2. Website and Interaction Design
  3. Paper Prototype and Walkthrough. Also see: HU4628 Team Assignment Summary, January 15-February 28.
  4. Design Changes after Walkthrough
  5. Design Review
  6. Implementation Requirements
  7. Usability Test Scheduling
  8. Final Design Presentation
  9. Meetings after Final Design Presentation
  10. Final Review with Client
  11. Implementation Review