Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ezfit:dev:software_meeting_2010-08-09 [2010/08/16 13:51]
smayr
ezfit:dev:software_meeting_2010-08-09 [2011/05/10 12:22] (current)
smayr
Line 1: Line 1:
 == Software Development Meeting 2010-Aug-09 == == Software Development Meeting 2010-Aug-09 ==
  
-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: Attendees:
Line 31: Line 31:
   * Add a note in marketing material and software that BTEs from Intuition family cannot use NOAHlink with standard cables (Diana/AJ).   * Add a note in marketing material and software that BTEs from Intuition family cannot use NOAHlink with standard cables (Diana/AJ).
   * Review how many customers are ordering Intuition BTEs, to know the impact of this decision (Paul).   * Review how many customers are ordering Intuition BTEs, to know the impact of this decision (Paul).
-== Custom Branding (Updated 2010-08-12) ==+== Custom Branding (Updated 2010-08-13) ==
 === Plan A: Global ManID === === Plan A: Global ManID ===
 Implement a Global ManID (14). Implement a Global ManID (14).
Line 39: Line 39:
   * Straight forward to implement and support.   * Straight forward to implement and support.
 === Plan B:  Unique ManID for All Custom Brands === === Plan B:  Unique ManID for All Custom Brands ===
-Implement a unique ManID for <del>each</del> all custom brands (a single ManID shared with all custom brands).+Implement a single and unique ManID for <del>each</del> all custom brands (i.e. a single ManID shared with all custom brands).
  
   * Avoids cross reading any product with any software (if not a module account).   * Avoids cross reading any product with any software (if not a module account).
Line 47: Line 47:
   * Requires building branding software to set ManID (especially for Ethos circuit based products).   * Requires building branding software to set ManID (especially for Ethos circuit based products).
   * Requires requesting ManID from circuit supplier, or assign one internally (but then each custom brand must be calibrated, including BTEs, OTEs, and other stock products).   * Requires requesting ManID from circuit supplier, or assign one internally (but then each custom brand must be calibrated, including BTEs, OTEs, and other stock products).
 +
 === Plan C: Hybrid Approach === === Plan C: Hybrid Approach ===
 Implement Plan A (Global MainID) for future products (including Intellio). Implement Plan A (Global MainID) for future products (including Intellio).
-Implement Plan B (Unique ManID for <del>each</del> all custom brands) for current products being manufactured (Intuition, Sparo, Flx, BTE 478P, etc.). +Implement Plan B (Single and Unique ManID for <del>each</del> all custom brands) for current products being manufactured (Intuition, Sparo, Flx, BTE 478P, etc.). 
   * Stops cross reading for current products being shipped out of the factory.   * Stops cross reading for current products being shipped out of the factory.
   * Simplifies implementation of future products, especially it avoids the issue of multiple DLLs unable to coexist in the same machine.   * Simplifies implementation of future products, especially it avoids the issue of multiple DLLs unable to coexist in the same machine.