1 / 6

Verry Nice! High-Five!

Verry Nice! High-Five!. Yoojin Kwak Michael Preysman Ruben Quintero Russell Savage. Test Cases. Concept Portable communication device for use within industrial, collaborative work environment Status Back end mostly finished, GUI in the works. Gumstix—problems with ALSA and GNU Classpath

judah
Download Presentation

Verry Nice! High-Five!

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. Verry Nice! High-Five! Yoojin Kwak Michael Preysman Ruben Quintero Russell Savage

  2. Test Cases • Concept • Portable communication device for use within industrial, collaborative work environment • Status • Back end mostly finished, GUI in the works. • Gumstix—problems with ALSA and GNU Classpath • Test Cases: • Boot Gumstix, connect on boot. Connect multiple Gumstix to the server. • Send/receive audio from the base station to the Gumstix. • Server acceps multiple users and can move them between groups. • Server talks only to specific groups and/or users.

  3. Performance Tests • Latency (primary) • Why: Ability to have a normal conversation. • How: Stopwatch/Basic Usability. Test Latency vs. Traffic. • Network Traffic • Why: How many users can we support? • How: Increase number of users speaking and connected • Packet Loss • Why: Don’t want clipped, unrecognizable speech. • How: JSpeex handles packet loss. • Seamlessness • Why: Users should be able to move between nodes (mobility). • How: Piggy backing on existing networks.

  4. Testing Process • Network Traffic • Brute force – increase users until system fails. • Automated – increase packets sent (not voice, just random info). • Latency • Ping from the Gumstix. • Stopwatch/General Usability. • Also increase users, see how latencyis affected.

  5. Difficulties • Latency will be most difficult because it is affected by a variety of things (traffic, processing, packet transfer, etc). • Pinging does not time from input at the microphone to output from the speakers (compression, processing, human reaction time). • Difficult to find the source of certain errors (for instance, sound: Classpath, JamVM, ALSA, OSS, etc.) • Gumstix have been relatively difficult to work with.

  6. Question Time!

More Related