Home|Team Rules|Personas|User Stories|Use Cases|Requirements|Interfaces|Project Plan|Contract|Design Document|Test Plan|User Manual|Contact Us

Contract

General Description

IVERT interface is a software interface that will be used by physical therapists to control a virtual environment rehabilitation treadmill. The interface will have features to allow physical therapists to store/load patient information, change virtual environment settings, adjust treadmill control settings, and log data.

Participants

  • Client: Mary Whitton
  • Consultants: Jeff Feasel, Michael Lewek
  • Developers: Enoch Chan, James Chan, Will Lahti

Requirements

The user interface requires specific functionality that is needed by physical therapists to store and assess data. The interface will be well organized to allow the user to easily adjust the system's parameters and to be able to easily visualize the changes returned from the system. Proper error handling will ensure that the user will not be able to incorrectly or accidently enter illegal values for parameters.

Primary Requirements

Please see the Requirements page.

Secondary Requirements

  • Create tutorial

Constraints

The user control interface for IVERT will be developed using Microsoft Visual Studio 2005 using the Qt add-in and C++.

Deliverables

The following will be delivered to the client: the source code for the user control interface (the code should be designed to be extensible in the future); the user control interface as an executable file; a README document that covers general use of the interface.

Resources Required

  • Microsoft Visual Studio 2005
  • Test application
  • Qt

Contractor and Client Obligations

The client will provide the necessary software and libraries, or means to acquire them. Due to the fact that the IVERT system is not readily accessible, a test application will be furnished to the team.

The team will meet with the client once a week to discuss any questions or concerns. All deliverables will be published on the project website before their respective deadlines.

Risks

None at the moment. This section may be revised in the future.

Milestones

  • October 30 - Meta Data
  • November 6 - Virtual Environment Setup
  • November 13 - Treadmill Control, Session Control
  • November 20 - Test software with actual treadmill system
  • November 27 - Logs