In reply to Malai_21:
Portable Stimulus is most definitely NOT a replacement for UVM.
PSS is a declarative language that lets you define stimulus scenarios at an abstract level, including rules for scheduling behaviors (called ‘actions’ in PSS), data flow between actions, and resource utilization. From these abstract models, a tool can automatically generate tests for your target platform, whether that is C code running on a processor, or UVM code to run in simulation. The PSS language uses both OOP and AOP concepts.
For each behavior in the abstract model, you specify an implementation for the target platform, and the tool generates the target implementation to stitch together the behaviors according to the schedule of your abstract model. This “realization layer” includes the ability to specify templates for target code, import methods, or, in 2.0, the ability to specify abstract procedural code that can then be targeted to your platform.
Note that in the UVM case, the PSS model generates an implementation usually in the form of UVM sequences and virtual sequences. It would be up to you to define the UVM environment (including agents, etc) and the test(s) that would call these PSS-generated sequences.
So, PSS is not a replacement for UVM. Rather, UVM is expected to be one of the more prominent targets for tests generated by a PSS tool. For more information, please see our Portable Stimulus Basics video course.