DescriptionThe Universal Verification Methodology (UVM) is now 10 years old. In the past decade, the UVM ecosystem has grown to dominance of our industry, but what about the next 10 years? Verification looks very different today than it did 10 years ago. We are now facing a substantial amount of software content as an integral piece of the overall SoC functionality, and SoC size and complexity is outstripping simulators' ability to randomly generate the right stimulus sequences to cover all of the corner cases where bugs lie. There is also the need to be able to staff verification teams to take advantage of UVM as the next generation of verification engineers comes of age. How do we keep UVM relevant and build on its success such that we can continue to rely on the great work done so far as verification itself progresses along with ever-growing SoC complexitly?