Wrapper for Legacy Verification Components in Open Frameworks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Legacy hardware verification languages are proprietary and incompatible with modern open verification methodologies, making it difficult to reuse legacy verification components in modern verification frameworks.

Innovation Solution

A wrapper is generated for the legacy verification component, along with an interface reflection, allowing the legacy component to be instantiated into a verification framework and extending its functionality to be compatible with open verification methodologies, facilitating the coexistence of multiple verification components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If legacy verification components are used in modern verification frameworks, then verification coverage is improved, but compatibility is worsened due to proprietary language limitations

Engineering Contradiction:

Improveverification coverageVSAvoidcompatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a wrapper component as an intermediary layer between legacy verification components and modern verification frameworks. This wrapper translates proprietary language constructs into open verification methodology-compatible interfaces, enabling legacy components to function within modern frameworks without modifying the original legacy code. The wrapper acts as a mediator that resolves the compatibility conflict while preserving verification coverage.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the verification system into distinct layers: the legacy verification component layer, the wrapper translation layer, and the modern framework layer. This segmentation allows each layer to operate independently with its own language and interface requirements, while the wrapper handles the translation between layers. This resolves the compatibility issue by isolating the proprietary language constraints to a specific segment.

Inventive Principle:

Principle #1Segmentation

2Productivity

If legacy verification components are integrated into modern frameworks, then code reuse is improved, but system complexity is worsened due to multiple component types

Engineering Contradiction:

Improvecode reuseVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal wrapper interface that can accommodate multiple types of legacy verification components through a standardized translation mechanism. This universal interface allows different legacy components (written in various proprietary languages) to be integrated into the modern framework using the same wrapper pattern, reducing the need for component-specific integration code and thereby managing system complexity despite the diversity of legacy components.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent generates wrapper code automatically through code generation tools that translate legacy component interfaces into modern framework-compatible interfaces. This automated copying and transformation process reduces manual integration effort and minimizes errors, allowing efficient reuse of legacy components while keeping the integration layer manageable in complexity.

Inventive Principle:

Principle #26Copying

3Reliability

If proprietary verification languages are used, then legacy component functionality is preserved, but interoperability is worsened with open verification methodologies

Engineering Contradiction:

Improvefunctionality preservationVSAvoidinteroperability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The wrapper serves as an intermediary that preserves the original proprietary language functionality of legacy components while enabling interoperability with open verification methodologies. The wrapper maintains the original component's interface and behavior unchanged, translating only the interaction protocols between the legacy component and the modern framework, thus preserving functionality while achieving interoperability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of attempting to convert legacy components to open verification languages (which would risk altering functionality), the patent inverts the approach by keeping the legacy components in their original proprietary language and translating the interface layer instead. This inversion preserves the original functionality exactly while achieving interoperability through the reversed translation direction.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS8972914B2Coexistence of multiple verification component types in a hardware verification framework

Publication Date: 2015.03.03 MENTOR GRAPHICS CORP

AI summary

Coexistence of multiple types of verification components in a single verification framework is provided. Particularly, the coexistence of proprietary e verification components in an open verification methodology framework is provided.