eAnalyzer
Static Analysis and Verification Methodology Compliance System |
|
|
eAnalyzer
Benefits
|
 |
- Easy to use
- Ramps up new environments and new users faster
- Increases verification performance
- Sets coding style standards
- Promotes reuse with eRM
compliance
- Optimizes coverage goals
- Ensures compliance with future IEEE P1647
|
|
|
How reliable is my verification environment? Is my code clean and
ready to integrate? Is it structured for maximum reusability? How
can I optimize generation and coverage performance? Designers need
tools to analyze and debug their verification environment before integrating
with the rest of the project.
Verisitys eAnalyzer makes it easy
to develop high-quality, consistent verification environments. eAnalyzer
is an intuitive static analysis and methodology tool that simplifies
verification environment development with a unique combination of
rules and methodology checks; including Verisitys e
Reuse Methodology (eRM) compliance
reporting and Coverage-Driven Verification (CDV) guidance. Furthermore,
eAnalyzer ensures that your code complies
with the future IEEE P1647 standard.

eAnalyzer runs from both the command line
and the graphical user interface (GUI). The GUI provides an interactive
results display, allowing users to click on specific messages and
highlight the source code that caused the message.
As verification complexity grows with ever increasing design sizes,
the verification challenge becomes extremely difficult to manage.
Projects require powerful methodology that scales from the module
to the system level, optimizes code creation, and improves engineers
performance.
Verisitys eAnalyzer addresses this
challenge by directly supporting both the Coverage-Driven Verification
(CDV) and e Reuse Methodologies (eRM);
thus helping verification teams accelerate the development process.
And with over 200 rule checks in eight separate categories, eAnalyzer
supports a wide range of verification engineers from first-time
users to those more experienced in functional verification.
But Our Environment Is Already Clean ...
eAnalyzers unique combination of static
analysis and its direct support of Verification Process Automation
set it apart from traditional lint checkers. For example, eAnalyzers
eRM checker generates a complete eRM
compliance report. Having the ability to check methodology
combined with features such as performance profilers, generation
and coverage analysis, and style checking enables new users to quickly
come up to speed, and increases the efficiency of experienced engineers.
Rules Checking
eAnalyzer includes over 200 built-in
checks covering eight classes of rules. These checks help you reduce
downstream simulation and DUT errors, and provide consistency for
diverse design teams.

Use eAnalyzer to generate an eRM
compliance report to certify that your verification components are
ready for delivery.
eAnalyzers eight types of rules checkssyntax,
semantic, standard lint, coding style, generation, performance,
Coverage-Driven Verification, and e Reuse
Methodology (eRM) complianceallow you
to find questionable code and coding styles, identify reuse and
porting issues, and generally accelerate the setup, debug, and integration
of the verification environment.
Improve Code and Team Performance
eAnalyzers intuitive interface combined
with its code and methodology analysis features increases the verification
engineers productivity, ultimately allowing you to find DUT
bugs faster.
Verification Process Automation
eAnalyzer fits easily into existing design
flows, and is applicable at any stage of the design cycle.
| Verification
Phase |
eAnalyzer
Application |
Environment Setup
& Construction
|
| > |
Initial environment setup, including desired
eRM infrastructure |
| > |
Quickly bring new engineers up to speed |
| > |
Interface checking and integration of multiple eVCs |
| > |
Guard code check-ins to central code library |
|
|
Verification Closure
|
| > |
Generation constraint development |
| > |
Help expand coverage items to reach 100% coverage |
| > |
Performance tuning |
| > |
Develop code "off-line" while Specman Elite
works on regressions |
|
|
eVC Packaging
|
| > |
Test for eRM compliance before
delivery |
| > |
Use eRM compliance report as
sign-off mechanism |
| > |
With message filtering, promote and enforce company-wide
coding practices |
|
Message Filtering and Coding Style Enforcement
eAnalyzers various filtering mechanisms
allow you to view only what is important to you. You can filter
and sort messages before generating reports, assign severity levels
to each message type and use filter files from the GUI when generating
a textual report. In addition, multiple filter files can be loaded
simultaneously, supporting local debugging efforts as well as group
and company level screening criteria.
Contact Us
|