The following blog entry was written by Rick Eram, Director of Field and Sales Operations at Real Intent
Designing an excellent EDA tool takes a great deal of understanding from several different viewpoints. First the tool designers must understand the actual engineering problem they are trying to solve. Second, they must understand the end-user design needs and satisfy those in the tool. Third the results have to be meaningful and consistent with the user’s existing design flow and ideally do not make it harder for designs to be signed off by engineers and their managers.
Software developers spend years refining their products to meet market demands. The first solution out of the box usually gets the need part right, but can miss on the meaningfulness of the results and presentation of information, as well as ease of use. For example, one of the RTL linting solutions in the marketplace started out as a generic checker over 10 years ago. A decade later, many hours of unnecessary debugging time is lost every day the tool is invoked because of the overhead due to checking and waiving erroneous messages. The reason for this misalignment of the customer needs lies solely on the way the tool was designed from the start.