Differences

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

--- ezfit:dev:software_meeting_2011-06-07 [2011/06/08 09:12]
smayr created
+++ ezfit:dev:software_meeting_2011-06-07 [2011/06/16 08:46] (current)
smayr [Software Review]
@@ Line 12: / Line 12: @@
 == Software Review ==
   * Setup Automatic Testing (Unit Testing)
-  * Setup Ad Hoc Testing (Barbara writing test procedures).
+  * Review Ad Hoc Testing (Barbara wrote test procedures).
     * Testers: Paul, Barbara, Glenn, and Chris
-  *
+  * Discussed the issues of making instruments backwards compatible, especially for storing new audiograms (supporting -10dB to 120dB) into the scratch memory. Issues:
+    * The Intuition 2 / Clari-D circuits cannot support changes to the scratch memory map.
+      * Suggested to drop support for Intuition 2 products, and add a new one called Intuition 2+ based on the spin or spinNR circuits, removing advanced features found in the Intuition 2FC/2ER products, so that the product can totally replace the Intuition 2 market share.
+    * It is possible to rewriting the memory maps for newly programmed instruments, however this might render them unreadable on older software (in a scenario, for example, where the patient moves to a different provider and requests adjustments, which might be done with older software).
+    * Suggested to add required additional bits in a different area in map, keeping the original audiogram field intact for backwards compatibility.
+  * Paul expressed concern over the software development timeline for product delivery (all supported products: Ethos, InTune, Spin, SpinNR circuits).  He feels uncomfortable with shipping software with only ethos-based products (Flx, Intuition 12, Sparo 12, Cue) for the first release.  He would like to add the spin-based and intune-based products as well for the first release.  According to the timeline, the earliest possible date for that would be Apr 2012. Some concerns about this move:
+    * Software would not bee market-tested well enough waiting for a final release.  Development team supports doing incremental releases (starting with a base release) limited to certain customers, so they can provide feedback.  Therefore, any issues could be worked out before adding new features and products.
 == Completed Actions ==