Organizations such as the DTC and SI2, and EDA vendors are determining more specifically what the API should look and act like. An extensive list of attributes for the ideal API illuminates the challenge ahead for those seeking to make the interface a reality. Of primary importance is in-memory operation to allow tools to operate on the same design data and incrementally modify and improve design results efficiently. Such capability eliminates iterative loops among tools, particularly synthesis and verification tools. Designers since the advent of the deep submicron era have tolerated such loops.
Flexibility is essential.
The interface must extend to a multitude of design tools and tasks to accommodate future data requirements. A standard API and data model must not compromise tool performance. All of this is tempered by practical constraints such as having a clearly defined scope and being available as soon as possible. Almost as important as defining what the API should be is how it will be disseminated. The DTC recommends placing source code in the public domain.