This is an old revision of the document!


Software Development Meeting 2010-Jun-07

Notes relevant to ezFIT 5.0 Milestones.

Attendees:

  • Marc
  • Frank
  • Paul
  • Barbara
  • Joel
  • AJ
  • Steve
  • Siegwart
Software Review
  • No log support, switching to diff components
  • Now there is audiogram support
  • Walk through of sw aw it is at this time
  • Paul likes the color change as mouse over
  • Fitting screen eliminated the buttons and provided fast info.
Suggested Actions
  • Filter by tabs for different styles
  • Filter by technology/environment
  • Extra tab with all the check boxes so that you can choose multiple styles and technology for filtering. On this tab would be fitting ranges overlayed with the audiogram to help with
  • Fitting:
    • Quick Adjustments. These need to be fine tailored:
  • Super controls
    • Adaptation manager
    • Occlusion manager
  • Gain under fine adjustments: come up with a way to demo both right and left. These are not standard controls so they would probably have to be coded
  • Components: Wpf studio (get graphical interface going and then can craft it) Marketing did the images and then these were put on for controls.
  • Obtain screen shots from other manufacturers:
    • Sebotek (Steve action).
    • Mark was going to see about getting screen shots to show an example.
  • User Interface:
    • Use of icons for representing buttons. Need coordination with marketing for overall look and feel (colors, etc).
    • Scale back/remove pink change background to pink
  • Fitting:
  • Languages
    • Localization not for April 2011 release.
    • It is a fairly complex process.
    • Tools will be built for the translation portion to be handled.
    • If localization is a top priority requirement, then we would need to address this issue.
    • How quickly would it be to implement it after that?
  • Skins
    • Priority is set not for the April release.
  • Goal = functionality and getting the first set of instruments on the release, but the in the design process these are being kept in mind.
  • Link for memories need a new term for same side memory link. Perhaps highlight the memories that you want to link
  • Curves:
    • Rigt ear or left ear for fitting. That is a fitting selection versus a display selection.
    • Want to have a way to simultaneously display 2 different curves for the same ear.
  • Get formulates for puretone threshold average 2 and 3 freq to Sieg (Barbara action).
  • Clarujust summary data is complete.
  • Impedance: B get graphs
  • Rename Autofit to First Fit?
  • Need to figure out the best implementation of acclimatization
  • Where do you put the hearing aid configuration and pt information factors that impact the fitting such as dome type, tubing style, etc.

Put on pt information section access to acclim level, pre fitting information If no information is in there when the provider goes to do an autofit, a box pops up to gather that information (which will populate back to that pre fitting info).

Solultion: pt information acclimatization

Do a dump of datapoints from the graphs to compare with verifit ( for our purposes)

Directional support: how are we going to display polar plots, etc. thoughts: put it so that it displays over current chart.

Look at options for ways to handle all the compression data.

Two things found for drag and drop.

Clarujust access still in debate

AJ ACTION: work with graph splines what is built in and does it have what we need for displaying the graphs for the various product and components.

Graphing component and the wish list regarding scaling and scrolling. This is a steve consideration with regards to ANSI standards.

Steve: ACTION: make data sets for graphing purposes.

Next meeting to be June 21 2010.

GOALS:

Chart graphing = priority

Naming

Functionality 
Workflow
	Ex. Read instrument button…
	Search database by pt name, serial number etc. 
Priority list
	Ex. Language localization
		Need to rethink on how to do this and be able to edit in an easy manner  is 
		there a better way than multilizer
web people and marketing design input
Completed Actions
Conclusion
  • Next meeting: Jun 21, 2010, 2pm