Verification Academy

Search form

My Account Menu

  • Register
  • Log In
  • Topics
  • Courses
  • Forums
  • Patterns Library
  • Cookbooks
  • Events
  • More
  • All Topics
    The Verification Academy offers users multiple entry points to find the information they need. One of these entry points is through Topic collections. These topics are industry standards that all design and verification engineers should recognize. While we continue to add new topics, users are encourage to further refine collection information to meet their specific interests.
    • Languages & Standards

      • Portable Test and Stimulus
      • Functional Safety
      • Design & Verification Languages
    • Methodologies

      • UVM - Universal Verification Methodology
      • UVM Framework
      • UVM Connect
      • FPGA Verification
      • Coverage
    • Techniques & Tools

      • Verification IQ
      • Verification IP
      • Static-Based Techniques
      • Simulation-Based Techniques
      • Planning, Measurement, and Analysis
      • Formal-Based Techniques
      • Debug
      • Acceleration
  • All Courses
    The Verification Academy is organized into a collection of free online courses, focusing on various key aspects of advanced functional verification. Each course consists of multiple sessions—allowing the participant to pick and choose specific topics of interest, as well as revisit any specific topics for future reference. After completing a specific course, the participant should be armed with enough knowledge to then understand the necessary steps required for maturing their own organization’s skills and infrastructure on the specific topic of interest. The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization’s processes so that you can then reap the benefits that advanced functional verification offers.
    • Universal Verification Methodology (UVM)

      • Introduction to UVM
      • UVM Basics
      • Advanced UVM
      • UVM Connect
      • UVM Debug
      • UVMF - One Bite at a Time
    • Featured Courses

      • Introduction to ISO 26262
      • Introduction to DO-254
      • Clock-Domain Crossing Verification
      • Portable Stimulus Basics
      • Power Aware CDC Verification
      • Power Aware Verification
      • SystemVerilog OOP for UVM Verification
    • Additional Courses

      • Assertion-Based Verification
      • An Introduction to Unit Testing with SVUnit
      • Evolving FPGA Verification Capabilities
      • Metrics in SoC Verification
      • SystemVerilog Testbench Acceleration
      • Testbench Co-Emulation: SystemC & TLM-2.0
      • Verification Planning and Management
      • VHDL-2008 Why It Matters
    • Formal-Based Techniques

      • Formal Assertion-Based Verification
      • Formal-Based Technology: Automatic Formal Solutions
      • Formal Coverage
      • Getting Started with Formal-Based Technology
      • Handling Inconclusive Assertions in Formal Verification
      • Sequential Logic Equivalence Checking
    • Analog/Mixed Signal

      • AMS Design Configuration Schemes
      • Improve AMS Verification Performance
      • Improve AMS Verification Quality
  • All Forum Topics
    The Verification Community is eager to answer your UVM, SystemVerilog and Coverage related questions. We encourage you to take an active role in the Forums by answering and commenting to any questions that you are able to.
    • UVM Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • UVM Forum
    • SystemVerilog Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • SystemVerilog Forum
    • Coverage Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • Coverage Forum
    • Additional Forums

      • Announcements
      • Downloads
      • OVM Forum
  • Patterns Library
    The Verification Academy Patterns Library contains a collection of solutions to many of today's verification problems. The patterns contained in the library span across the entire domain of verification (i.e., from specification to methodology to implementation—and across multiple verification engines such as formal, simulation, and emulation).
    • Implementation Patterns

      • Environment Patterns
      • Stimulus Patterns
      • Analysis Patterns
      • All Implementation Patterns
    • Specification Patterns

      • Occurrence Property Patterns
      • Order Property Patterns
      • All Specification Patterns
    • Pattern Resources

      • Start Here - Patterns Library Overview
      • Whitepaper - Taking Reuse to the Next Level
      • Verification Horizons - The Verification Academy Patterns Library
      • Contribute a Pattern to the Library
  • All Cookbooks
    Find all the methodology you need in this comprehensive and vast collection. The UVM and Coverage Cookbooks contain dozens of informative, executable articles covering all aspects of UVM and Coverage.
    • UVM Cookbook

      • UVM Basics
      • Testbench Architecture
      • DUT-Testbench Connections
      • Configuring a Test Environment
      • Analysis Components & Techniques
      • End Of Test Mechanisms
      • Sequences
      • The UVM Messaging System
      • Other Stimulus Techniques
      • Register Abstraction Layer
      • Testbench Acceleration through Co-Emulation
      • Debug of SV and UVM
      • UVM Connect - SV-SystemC interoperability
      • UVM Versions and Compatibility
      • UVM Cookbook
    • Coding Guidelines & Deployment

      • Code Examples
      • UVM Verification Component
      • Package/Organization
      • Questa/Compiling UVM
      • SystemVerilog Guidelines
      • SystemVerilog Performance Guidelines
      • UVM Guidelines
      • UVM Performance Guidelines
    • Coverage Cookbook

      • Introduction
      • What is Coverage?
      • Kinds of Coverage
      • Specification to Testplan
      • Testplan to Functional Coverage
      • Bus Protocol Coverage
      • Block Level Coverage
      • Datapath Coverage
      • SoC Coverage Example
      • Requirements Writing Guidelines
      • Coverage Cookbook
  • All Events
    No one argues that the challenges of verification are growing exponentially. What is needed to meet these challenges are tools, methodologies and processes that can help you transform your verification environment. These recorded seminars from Verification Academy trainers and users provide examples for adoption of new technologies and how to evolve your verification process.
    • Featured & On-Demand

      • Continuous Integration - March 28th
      • Questa Verification IQ - April 11th
      • SystemVerilog Assertions
      • SoC Design & Functional Safety Flow
      • 2022 Functional Verification Study
      • Design Solutions as a Sleep Aid
      • CDC and RDC Assist
      • Formal and the Next Normal
      • Protocol and Memory Interface Verification
      • Webinar Calendar
    • On-Demand Library

      • Practical Flows for Continuous Integration
      • Lint vs Formal AutoCheck
      • The Three Pillars of Intent-Focused Insight
      • Formal Verification Made Easy
      • Fix FPGA Failures Faster
      • HPC Protocols & Memories
      • FPGA Design Challenges
      • High Defect Coverage
      • The Dog ate my RTL
      • Questa Lint & CDC
      • Complex Safety Architectures
      • Data Independence and Non-Determinism
      • Hierarchical CDC+RDC
      • All On-Demand Recordings
    • Recording Archive

      • Aerospace & Defense Tech Day
      • Exhaustive Scoreboarding
      • Improving Initial RTL Quality
      • CDC Philosophy
      • Hardware Emulation Productivity
      • Visualizer Debug Environment
      • Preparing for PCIe 6.0: Parts I & II
      • Automotive Functional Safety Forum
      • Siemens EDA Functional Verification
      • Improving Your SystemVerilog & UVM Skills
      • All Webinar Topics
    • Conferences & WRG

      • Industry Data & Surveys
      • DVCon 2023
      • DVCon 2022
      • DVCon 2021
      • Osmosis 2022
      • All Conferences
    • Siemens EDA Learning Center

      • SystemVerilog Fundamentals
      • SystemVerilog UVM
      • EDA Xcelerator Academy(Learning Services) Verification Training, Badging and Certification
      • View all Learning Paths
  • About Verification Academy
    The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization's processes so that you can then reap the benefits that advanced functional verification offers.
    • Blog & News

      • Verification IQ
      • Verification Horizons Blog
      • Technical Resources
    • Verification Horizons Publication

      • Verification Horizons - March 2023
      • Verification Horizons - December 2022
      • Verification Horizons - July 2022
      • Issue Archive
    • About Us

      • Verification Academy Overview
      • Subject Matter Experts
      • Academy News
      • Contact Us
    • Training

      • Learning @OneGlance (PDF)
      • SystemVerilog & UVM Classes
      • Siemens EDA Classes
Ask a Question
SystemVerilog
  • Home
  • Forums
  • SystemVerilog
  • Why doesn't Systemverilog need a 'main' function like Java?

Why doesn't Systemverilog need a 'main' function like Java?

SystemVerilog 6318
Shawn Zhang
Shawn Zhang
Full Access
4 posts
January 31, 2023 at 11:41 pm

I know SV has an 'initial' keyword to mark the 0 time of the simulation time of the program.
I know UVM is designed by using SV and the entry of a UVM test case is the 'run_test()'.
I also heard that SV language is designed by using Java as a prototype.

Then, come this curiosity,

  • Why doesn't Systemverilog needSystemverilogction like Java?
  • What's the difference between the 'simulation time' of SV with the 'runtime' of Java?

Regards
Shawn

Replies

Log In to Reply

Solution

Solution

dave_59
dave_59
Forum Moderator
10661 posts
February 01, 2023 at 8:54 pm

In reply to Shawn Zhang:

SystemVerilog is foremost a Hardware Description Language (HDL). "Hardware" in this case is a discrete digital abstraction of continuous analog voltages, currents, and billions of devices operating concurrently. Everything is executing in parallel, there is no single "main" entry point like there is in software.

Simulation of hardware is using software to model hardware. An HDL gets compiled onto a host hardware platform for simulation, and that host hardware has nothing to do with the hardware being modeled. The host hardware platform may take hours to simulate what occurs in seconds on the hardware being modeled. The "simulation time" represents the time in the hardware model. It is different abstraction from the time it takes host hardware to execute the model.

A "test" can be considered software; it has a main entry point. In the UVM, that entry point is called by the task run_test().

Only one piece of SystemVerilog, its Object Oriented class system, comes from Java. Actually it comes indirectly from another language "Vera" whose class system came from Java. Both Java and Vera were developed at Sun Microsystems, hence the connection.

— Dave Rich, Verification Architect, Siemens EDA

Shawn Zhang
Shawn Zhang
Full Access
4 posts
February 01, 2023 at 11:07 pm

In reply to dave_59:

Hi Dave,
Exactly what I am looking for! Your reply enlighten me as always!
Regards
Shawn

Shawn Zhang
Shawn Zhang
Full Access
4 posts
February 02, 2023 at 7:28 pm

In reply to dave_59:

Hi Dave,

A further query about the difference of interface between java with SV.

I know that 'interface' along with 'implements' is one of the key concepts of OOP in Java.
It helps to achieve the abstraction and encapsulation of OOP.

However, it looks like 'interface' in SV is commonly used to declare the ports of a hardware.
I think the 'interface class' in SV is the one equal to 'interface' in Java. However, it seems to be not much used (as far as I know).

Above are just my immature thoughts.

  • Could you explain that in your vision?
  • Should we use more more OOP, more design pattern just like software in our tb design to achieve the performance goals such as abstraction, encapsulation reusability, extensibility etc?
  • I know UVM is leveraging many design patterns which makes UVM itself more OOP. However, even we used UVM to build up the project testbench, when there is a new project, copy/paste and modify the 'class' directly is more common than leverage OOP features such as override, inheritance, polymorphism.

Regards
Shawn

dave_59
dave_59
Forum Moderator
10661 posts
February 03, 2023 at 8:36 am

In reply to Shawn Zhang:

A predicament SystemVerilog has is it tries to avoid adding new keywords to keep code backward compatible. The keyword interface was a design construct for port connections long before interface class was added to the language in 1800-2012. You do not see much use of interface classes because it is relatively new and much of the UVM was already implemented before its introduction. But there are a growing number of examples and papers using it.

Regarding OOP versus copy/paste, that remains an educational concern. The majority of hardware design and verification engineers do not have a strong software programming background with OOP and this seems difficult to pick up once you have already started your career.

— Dave Rich, Verification Architect, Siemens EDA

Shawn Zhang
Shawn Zhang
Full Access
4 posts
February 05, 2023 at 4:52 pm

In reply to dave_59:

Make sense. Thanks!
Regards
Shawn

Siemens Digital Industries Software

Siemens Digital Industries Software

#TodayMeetsTomorrow

Portfolio

  • Cloud
  • Mendix
  • Electronic Design Automation
  • MindSphere
  • Design, Manufacturing and PLM Software
  • View all Portfolio

Explore

  • Community
  • Blog
  • Online Store

Siemens

  • About Us
  • Careers
  • Events
  • News and Press
  • Customer Stories
  • Partners
  • Trust Center

Contact

  • VA - Contact Us
  • PLM - Contact Us
  • EDA - Contact Us
  • Worldwide Offices
  • Support Center
  • Give us Feedback
© Siemens 2023
Terms of Use Privacy Statement Cookie Statement DMCA