Updated readme

Author: jgebal

README.md

@@ -3,29 +3,31 @@
 
 # utPLSQL v2 to v3 migration utility
 
-This project provides a migration utility to enrich utPLSQL v2 package specification with [utPLSQL v3 annotations](https://utplsql.github.io/utPLSQL/v3.0.0/userguide/annotations.html).
-
-## Content
-
-This utility contains the following components:
-
-- Package `ut_v2_migration`
-- Modified version of `utassert` package from utPLSQL version 2.3.1
-- Modified version of `utassert2` package from utPLSQL version 2.3.1
+This project provides a migration utility to enrich utPLSQL v2 package specification with [utPLSQL v3](https://github.com/utPLSQL/utPLSQL) [annotations](https://utplsql.github.io/utPLSQL/v3.0.0/userguide/annotations.html)
 
 ## Download
 
-Download latest release from (TODO) 
+Download latest release from this location:
+https://github.com/utPLSQL/utPLSQL/releases/latest
+
 
 ## Requirements
 
 - utPLSQL v2 needs to be installed
 - utPLSQL v3 needs to be installed
-- user executing the installation needs to have following privileges:
-   - `create any procedure`
-   - `create public synonym`
-   - `grant any object privilege`
+- Installation needs to be done from a `SYS` account or as `SYSDBA` as utPLSQL v3 user needs to be granted execute privilege on `UTL_FILE`.
+This is required for installing utPLSQL v2 compatibility within utPLSQL v3.
+
+
+## Content
 
+Migration utility contains the following components:
+
+- Package `ut_v2_migration`
+- Modified version of `utassert` package from utPLSQL version 2.3.1
+- Modified version of `utassert2` package from utPLSQL version 2.3.1
+
+All of above components are installed into utPLSQL v3 schema, have public synonyms created and are granted to public. 
 
 ## Installation
 
@@ -44,5 +46,26 @@ The install script does the following:
 - Creates public synonyms for `utassert` and `utassert2` in utPLSQL v3 schema  
 - Grants execute on packages: `ut_v2_migration`, `utassert`, `utassert2` to PUBLIC
 
+
+# Migration process
+
+## Requirements
+
+The migration process scans utPLSQL v2 meta-data tables: 
+- ut_package
+- ut_suite
+- ut_config
+
+In order to be considered by migration process, Unit Test package needs to:
+- be registered in `ut_package` table - this can be done either by manually registering a package or by executing test package using utPLSQL v2 framework
+- be existing in the database
+- be valid
+
+User executing the migration needs to:
+- be the owner of migrated packages
+- have `create any procedure` system privilege 
+
 ## Executing migration
 
+
+