Conversely, if you don't ship any products, no payments arrive from customers, and you lose. The embedded software realm is quite different from other engineering disciplines when it comes to what's good enough to ship. In the mechanical world, people can touch and feel an engineer's product. Rigid rules exist for what will and won't work. For example, a finger hole to open a cabinet must be at least a certain size, or the force to turn a knob must be less than a certain value.
Designers can fall back on commonly accepted criteria during product design.
In the embedded world, though, you won't find accepted norms for what is and isn't acceptable. Obviously, someone must answer these questions before finishing an embedded design. Further, you can probably see that some of these issues concern software, while others relate to hardware. Unfortunately clear-cut answers don't exist. If the problem causes an impact on sales, you must estimate the cost of the problem and the solution-and don't forget the possible expense associated with delayed market entry, disappointed customers and bashing by the competition.