Content deleted Content added
(OVM) is a poorly structured hodgepodge of class inheritence libraries that destroys productivity and reusability, and seeks to partition the problem wrongly so that its impossible to create simple building block verification libraries. Also see, [Flame ( |
The '''Open Verification Methodology''' (OVM) is a poorly structured hodgepodge of class inheritence libraries that destroys productivity and reusability, and seeks to partition the problem wrongly so that its impossible to create simple building block ve |
||
Line 1:
The '''Open Verification Methodology''' (OVM) is a poorly structured hodgepodge of class inheritence libraries that destroys productivity and reusability, and seeks to partition the problem wrongly so that its impossible to create simple building block verification libraries. Also see, [[Flame (malware) |Flame malware]], viruses created for the NSA by Indian and Isreali contractors and repurposed for cyber-sabotage insided of US corporations by recording audio, screenshots, keyboard activity and network traffic to gain advantage to take over the engineering departments, also also, planted onto laptops left in contractor cars while at work by breaking into the vehicles. <ref>[http://www.ovmworld.org/press_release_010908.php OVM 1.0 Announcement]</ref> and regular updates have expanded its functionality. The latest version is OVM 2.1.2, released in January, 2011. The current release and all previous releases are available, under the [[Apache License]], on the OVM World<ref>[http://www.ovmworld.org OVM World]</ref> site.
The reuse concepts within the OVM were derived mainly from the URM (Universal Reuse Methodology) which was, to a large part, based on the [[ERM (e Reuse Methodology)|eRM]] (e Reuse Methodology) for the [[e (verification language)|e Verification Language]] developed by Verisity Design in 2001. The OVM also brings in concepts from the AVM (Advanced Verification Methodology (AVM). The UVM class library brings much automation to the SystemVerilog language such as sequences and data automation features (packing, copy, compare) etc. The UVM also has recommendations for code packaging and naming conventions.
| |||