TEAM 11: Chiron
Spring 2009


MEMBERS

PROJECT CONCEPT

We want to develop the "Basketball Training Glove" in order to adjust or train the shooter's performance. This project will embedded sensors to the glove to measure the shooting angle and shooting force; then, transmit the data for the analysis.

MOTIVATION

The current automatic coaching system is costly. The system that we build will try to reduce the cost for basketball training.

COMPETITIVE ANALYSIS

NOAH basketball coach training system:

TECHNICAL SPECIFICATIONS

The glove embedded with sensors and accelerometer to detect the shooter's angle and force when shooting, and send those data to computer via bluetooth. Hardware: Software: Protocols:

REQUIREMENTS

ARCHITECTURE

USE CASES (INTERACTION DIAGRAMS)

  • A pdf file containing use cases can be downloaded here
  • User start up the system: gumstix and accelerator board boot up. Once both are up, it will send the data to LEDs prompting for user input via button.
  • User is pushing a "position" button: gumstix determine user current position based on the corresponding button. Gumstix records any acceleration. Gumstix is on an active state.
  • User release the contact from the ball (detected via buttons) during the active state: Gumstix calculate whether it is a dribbling or a shot. If it is a dribbing, stays in the active state. If it is a shot, gumstix calculate the angle/acceleration/position of elbow and hands. Then give the feedback.
  • User in pushing a "send" button: gumstix transfer all the data to outside sources via bluetooth.
  • User power the system off: gumstix and accelerator halted.
  • Exception in the system: halted the system or report to user if we have memory exception.

    SYSTEM STATES & TRANSITIONS

    RISKS & MITIGATION STRATEGIES

  • Fundamental Risks:

  • Ancillary Risks:

    ERROR HANDLING

  • Hardware Failure:

  • Software Failure:

    IMPLEMENTATION DETAILS

  • Robostix side:
  • Gumstix side:

    TEST CASES

  • location tracker - This test will test the accuracy of the program and accelerator. It will find the location of the player given the initial position and set of input from the accelerometer. This test will test how accurate the system is.
  • Normal shot tracker - Test the normal functionality of the system and check that it gives the feedback that make sense.
  • Power up/down - This will test whether it can handle power outage and reset it to the initial state or not.
  • I/O connection failure - This will test how the system handle the I/O communication failure, including how it output the failure through the LED.
  • Stress test for the software part - This test will test the functionality of the software, including how it handles shared variable.

    EXPERIMENTAL EVALUATION

    To be completed.

    LESSONS LEARNED

    To be completed.

    FUN STUFF

    To be completed.

    REFERENCES


    Back to the top of this page
    18-549 course home page