Differences

This shows you the differences between two versions of the page.

--- ezfit:dev:software_meeting_2010-06-07 [2010/06/09 10:23]
smayr
+++ ezfit:dev:software_meeting_2010-06-07 [2011/05/10 12:21] (current)
smayr [Software Development Meeting 2010-Jun-07]
@@ Line 1: / Line 1: @@
 == Software Development Meeting 2010-Jun-07 ==
-Notes relevant to [[ezfit:5.0 Milestones|ezFIT 5.0 Milestones]].
+[[ezfit:software_meeting_notes|Software Meeting Notes]] relevant to [[ezfit:5.0 Milestones|ezFIT 5.0 Milestones]].
 Attendees:
@@ Line 8: / Line 8: @@
   * Paul
   * Barbara
+  * Steve
   * Joel
   * AJ
-  * Steve
   * Siegwart
+== Software Review ==
+  * No datalog support.
+  * Switching to different components (moving from Telerik to ComponeOne).
+  * Now there is audiogram support.
+  * Walkthrough of software 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 ==
-No log support, switching to diff components
+  * Products:
-Now there is audiogram support
+    * Filter by tabs for different styles.
-Walk through of sw aw it is at this time
+    * Filter by technology/environment.
+    * Extra tab with all the check boxes so that you can choose multiple styles and technology for filtering.
+      * Product specs.
+      * Product image.
+      * Fitting ranges overlayed with the patient audiogram.
-Paul likes the color change as mouse over
+  * Fitting:
+    * Quick Adjustments. These need to be fine tailored:
+      * Super controls.
+      * Adaptation manager.
+      * Occlusion manager.
+    * Gain/Equalizers: Come up with a way to demo both right and left.  These are not standard controls, so they would probably have to be coded.
+    * Link for memories needs a new term for same side memory link. Perhaps highlight the memories that you want to link.
+    * Curves:
+      * Right ear or left ear for fitting.  That is a fitting selection versus a display selection.
+      * Simultaneously display 2 different curves for the same ear.
+    * Get formulas for pure tone threshold average 2 and 3 freq to Sieg (Barbara action).
+    * Allow dumping of chart datapoints to compare with Verifit (for our purposes).
-Combo box
+  * User Interface:
+    * Design graphical interface, then add functionality to it.  It is possible for Marketing to create images, colors, and theme, then these can be added to the controls.
+      * Obtain screen shots from other manufacturers:
+        * Sebotek (Steve & Marc action).
+        * Other manufacturers (Barbara & Paul action).
+    * Use of icons for representing buttons.  Need coordination with marketing for overall look and feel (colors, etc).
-Filter by tabs for different styles
+  * To discuss:
-Filter by technology/environment
+    * Directional support:  how are we going to display polar plots, etc.  Thoughts:  put it so that it displays over current chart.
-Extra tab with all the check boxes so that you can choose multiple styles and technology for filtering.
+    * Review options to handle all the compression data.
-On this tab would be fitting ranges overlayed with the audiogram to help with
+    * Clarujust access still in debate.
+    * Solutions:  patient information acclimatization
+      * Need to figure out the best implementation of acclimatization
+    * Review where to place factors that impact the fitting such as:
+      * Hearing aid configuration
+        * Dome type
+        * Tubing style
+      * Patient information
+        * Acclimatization level
+        * Pre-fitting information
-Fitting screen eliminated the buttons and provided fast info.
+  * Graphing component:
-Quick Adjustments:
+    * Make data sets for graphing purposes. (Steve action)
-	Super controls and items such as adaptation, occlusion mgr, etc.  These need to be fine tailored.
+    * Review graph splines support: (AJ action)
+      * Does it have what we need for displaying the graphs for the various product and components?
-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
+== Completed Actions ==
-Wpf studio (get graphical interface going and then can craft it)  Marketing did the images and then these were put on for controls.
+  * Fitting:
+    * Rename Autofit to First Fit?  --- //[[smayr@audina.net|Siegwart Mayr]] 2010/06/18 17:10//
+    * 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).  --- //[[smayr@audina.net|Siegwart Mayr]] 2010/06/18 17:10//
-Sebotek screen shots-Steve action.
+  * Graphing component:
-Mark was going to see about getting screen shots to show an example.
+    * Scaling.  Steve proposes to follow [[ezfit:ANSI:ANSI S3.22 Hearing Aid Test Standard]] (Section 6.1).
-Use of icons for representing buttons.  Need coordination with marketing for overall look and feel (colors, etc)
+  * User Interface:
+    * Scale back/remove pink change background to pink.  --- //[[smayr@audina.net|Siegwart Mayr]] 2010/06/18 17:10//
-Scale back/remove pink change background to pink
+  * Primary Priorities:
+    * Basic functionality for instrument fitting.
+    * Support for a subset of instruments:
+      * Flx
+      * Intellio
+      * Intuition 12
+      * Sparo 12
+  * Secondary Priorities:
+    * Support for additional products (need to review product list required).
+    * Support for Languages:
+      * Localization not for April 2011 release.  Scheduled for Dec 2011.
+      * 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?
+    * Support for Skins/Themes:
+      * Priority is set for the Dec 2011 release.
-Fitting screen-
-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 a requirement, then we would need to address this issue.  How quicly would it be to implement it after that?
+== Conclusion ==
-Skins-priority is set not for the April release.
+  * Next meeting: Jun 21, 2010, 2pm
+  * Chart graphing = priority
-Goal = functionality and getting the first set of instruments on the release, but the in the design process these are being kept in mind.
+  * Naming:
+    * Functionality
-Link for memories need a new  term for same side memory link
+    * Workflow
-Perhaps highlight the memories that you want to link
+      * Ex. Read instrument button
+      * Search database by patient name, serial number etc.
-Curves
+    * Priority list
-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.
+      * 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 for localization?
-ACTIONS from last meeting
+  * web people and marketing design input
-Barbara (puretone threshold average)  get the formulas for 2 and 3 freq to Sieg.
-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