EDA-Browser Bridge Using Design Markup Language
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Electronic design automation (EDA) systems require significant investment and specialized programming skills to extend or customize, as they use EDA-specific programming languages that are not commonly used outside the EDA context, making it difficult for developers with web development skills to interact with integrated circuit (IC) design objects.
Innovation Solution
A bi-directional EDA-browser bridge mechanism using a design markup language (DML) allows EDA systems to interact with browsers, enabling a document-based approach that leverages web development skills and third-party libraries, making it easier to generate interactive interfaces for IC design objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If EDA-specific programming languages and APIs are used for extending EDA systems, then EDA functionality and IC design object interaction are improved, but accessibility and ease of use for developers are worsened
Solution Approach 1:
The patent introduces a markup language document as an intermediary between the browser and the EDA system. This document contains references to IC design objects and enables communication without requiring developers to learn EDA-specific programming languages. The markup language serves as a mediator that translates web development concepts into EDA system interactions, resolving the contradiction between maintaining EDA functionality and improving developer accessibility.
2Reliability
If traditional API-based approaches are used for EDA system extension, then precise control and EDA object interaction are improved, but complexity and learning curve are worsened
Solution Approach 1:
The patent employs a document-based approach that copies the simplicity and structure of web markup languages into the EDA domain. Instead of requiring developers to work with complex EDA APIs, the system uses markup language documents with references to IC design objects, replicating the ease of web development while maintaining reliable EDA object interaction through the structured reference system.
3Ease of operation
If web programming languages are used for EDA applications, then accessibility and ease of development are improved, but ability to capture IC design object behavior is worsened
Solution Approach 1:
The patent applies local quality by enhancing specific elements within the markup language document. While the overall document structure remains simple and web-friendly, specific references within the document are designed to capture IC design object behavior. This allows the system to maintain web programming language accessibility while incorporating specialized capabilities for representing and interacting with IC design objects through targeted reference mechanisms.
Data Source
AI summary
A bi-directional EDA-browser bridge mechanism enables an EDA system and its related (external) tools to interact with a browser. The EDA-browser bridge uses a design markup language (DML) to communicate with the browser, using a document-based approach rather than a more traditional programming/API-based approach to extending (e.g., integrating tools) the EDA system. By using a markup language, extending the EDA system becomes more accessible to a wider community of developers (e.g., those with web development skills, as opposed to those with just EDA programming skills), and be able to leverage a wider variety of powerful third-party libraries, such as jQuery or D3. For example, developers are able to more easily generate interactive interfaces for viewing results related to the EDA system.