Benefits of Intersecting UPT-IRM Merge
It is useful to compare the UPT .csv with the IRM .csv files so as to focus testing only on objects that are in use by the customer as well as modified by IRM and not on all modified objects. If you choose to compare the two sets of .csv files, the intersection will yield a list of repository objects that are used and modified. These objects are the ones most used by end users and, therefore, require more testing.
When you intersect UPT data with IRM data, you obtain an accurate view of the actual product components used by a customer and the repository artifacts that IRM touches during the upgrade cycle. This targeted testing will help customers:
Obtain data-backed targeted and specific investments so as to get predictable results.
Reduce the cost of upgrades and cost of ownership through focused functional, integration, and performance testing post upgrade.
For example, UPT events may indicate that 10 applets across five views in two screens are the only objects used by a customer. IRM delta changes may be across 15 applets, 10 views, and 12 screens. The resultant intersection of UPT and IRM could be 6 applets, 3 views, and 1 screen. This would be generated as a report and be an output of the IRM Upgrade cycle. This will help the customer focus on testing the entities obtained solely from the intersection. The resultant saving will be on resources, time, and money.