1 / 22

Team Project

Team Project. IS 485, Professor Matt Thatcher. Agenda. Review Team project project overview team feedback milestones Questions?. Review. Interactive, User-Centered Design task analysis prototyping model. Project Overview. Each team will propose an interface idea

calida
Download Presentation

Team Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Project IS 485, Professor Matt Thatcher

  2. Agenda • Review • Team project • project overview • team feedback • milestones • Questions?

  3. Review • Interactive, User-Centered Design • task analysis • prototyping model

  4. Project Overview • Each team will propose an interface idea • can be based on company sponsor • other ideas for applications to design are welcome • Team make-up • each team should have 4-5 members • Project purpose • apply several HCI methods to a single user interface

  5. Project Deliverables

  6. Final Prototype = “Real” UI design, but not necessarily a “real” application full-scale development and implementation of a production-quality software by the end of the semester is unrealistic for us The Final Prototype User User Interface Applications Software Systems Software Data base and Telecommunications Hardware

  7. TF(1)Project Proposal • Past project proposals • in-car display application • interactive briefing room (Air Force) • on-line fitness application • waiter support system (restaurants) • Blackboard (proposed redesign) • scheduling system (Tucson Medical Center) • account maintenance application (IBM) • client information system (Our Town Family Center) • etc. • The more creative the project, the better • pure inventory management applications are a little boring

  8. TF(2)Task Analysis Update

  9. M(1)Contextual Inquiry and Task Analysis • Interview at least three (3) target users (no IS485 classmates) using the contextual inquiry methodology • Answer the standard task analysis questions • who, what, where, when, and how • Develop three (3) benchmark scenarios of actual use. • Design rough sketches of important screens of your proposed user interface and clearly explain (in text and with storyboards) how a user will complete each of the three scenarios using your interface

  10. Sketching and Storyboarding (Milestone 1)

  11. Sketching and Storyboarding (Milestone 1)

  12. TF(3)Scenario Walkthrough Update

  13. M(2)Scenario Walkthroughs • Interactive design evaluation led by design team using a PowerPoint presentation

  14. M(2)Scenario Walkthroughs • Present a PowerPoint presentation of design ideas to class

  15. M(3)Low-Fi User Testing • Build a paper-based, chauffeured prototype • Perform a simple user test • Incorporate the results of the test into design changes for the next iteration of the prototype.

  16. Paper Prototypes for User Testing (Milestone 3)

  17. Paper Prototypes for User Testing (Milestone 3)

  18. Past Project Examples

  19. What Are Your Project Ideas?

  20. Keys to Team Success • Common commitment • requires a purpose in which team members can believe • Specific performance goals • comes directly from the common purpose • “increasing the scores of graduates from 40% to 95%” • helps maintain focus – start w/ something achievable • A right mix of skills • technical/functional expertise (prototyping / tools / behavioral / writing) • problem-solving & decision-making skills • interpersonal skills • Agreement • who will do particular jobs, when to meet & work, schedules

  21. design (visual/interaction) software user testing heuristic evaluation Team Action Items • Meet & get used to each other • Figure out strengths of team members • Assign each person a role • responsible for seeing work is organized & done • not responsible for doing it themselves • Roles • team manager (coordinate big picture) • documentation (writing)

  22. Questions?

More Related