1 / 15

Capstone Design A Pedagogical Tool for Usability Science

This capstone design project aims to develop a pedagogical tool for usability science by creating a system that simulates control panels, records test data, and allows for easy customization and modification of input/output devices.

renfroe
Download Presentation

Capstone Design A Pedagogical Tool for Usability Science

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. Capstone DesignA Pedagogical Toolfor Usability Science • Susan Beckhardt • Advisors: Chris Fernandes • Aaron Cass • James Hedrick

  2. Outline • • Introduction to Usability Science • • Project requirements • • Design • • Future work • • Questions

  3. IntroductionWhat is Usability Science?

  4. The Project • • A system to simulate control panels and record test data

  5. Requirements • • Simulate the layout of a control panel • • repositionable • Programmable • connect inputs to desired outputs • Log events

  6. Additional Requirements • • Repositionable I/O devices (widgets) • • Ease of physical setup • • Easy to update/modify • • Easy to create new widgets

  7. Additional Desired Features(“wish list”) • • Easy to program (with little computer experience) • • Aesthetics

  8. Design • • I/O Widgets: Simple input or output devices (switches, lights, etc.) • • Controller • • Event Logger • Controller-widget communication via ethernet

  9. Widget

  10. Controller • • State Machine • • User program defines state machine • • Controller loop: • • Wait for an input signal • • Change outputs based on input and state • • Change state • • Send input/output/state change data to event logger

  11. Event Logger • • Receives/records messages from controller: • • input received • • output changed • • new state • • add time stamp

  12. TINI Networked Microcontroller • • controls each widget • • runs Java • • built-in Ethernet capability

  13. Results • • Working with two TINI Networked Microcontrollers • • Fully implemented widget

  14. Future Work • • Implement full controller and event logger • • Create more widgets!

  15. Questions?

More Related