cristian_amiq

It is organized using the simple and practical Javadoc style. It embeds the
natural docs annotations. It is lightweight and easily browsable.
You can also browse it online: www.dvteclipse.com/uvm-1.1-HTML_API/index.html
If you use an IDE (like DVT - www.dvteclipse.com), the API specification
embedded in comments is presented in-line with the code. You don't have to
switch to the API docs while editing.
You can extract a similar documentation from your code using DVT.

This is the UVM 1.0 API specification in HTML format.
It is organized using the simple and practical Javadoc style. It embeds the natural docs annotations. It is lightweight and easily browsable.
If you use an IDE (like DVT - www.dvteclipse.com), the API specification embedded in comments is presented in-line with the code. You don't have to switch to the API docs while editing.
You can extract a similar documentation from your code using DVT.

In 90%+ of the cases the simple search/replace ovm* with uvm* will work to get you from OVM to UVM.
Heavy OVM users (callbacks) or legacy ones (avm*, urm*) could use a more precise migration which will indicate deprecated types, deprecated macros, method signature changes etc.
The attached refactoring script contains all the differences between OVM2.1.1 and UVM1.0EA. The last few lines are text "ovm*" to "uvm*", the rest are:

removed macros removed classes removed fields removed methods renamed macros renamed classes renamed methods method signature changes (more/less arguments) macro signature changes (more/less arguments) DVT helps the OVM2UVM migration, including the capability to apply this or any other refactoring script. For more details: www.dvteclipse.com/documentation/sv/OVM_to_UVM_Migration.html and www.dvteclipse.com/documentation/sv/Refactoring_Scripts.html

The Javadoc format for documenting API is well established in the software world, so why not use it for SystemVerilog? It is a pretty simple format and it allows quick access to the API spec, especially when you need something fast.
   It doesn't supplement user guides, but it is lightweight and easily browsable. It starts from the assumption the underlying code is well commented. Which seems to be true for the UVM lib.
  Needless to say, if you use an IDE (like DVT - www.dvteclipse.com), the API spec is presented inline with the code, so you don't have to open/switch to the API docs while editing.
   Still, it is good to have the API at hand, so here it is.