The UMT features automate and minimize the effort involved in various business scenarios where managing universe is a regular or intensive activity.
OEM Users: Consider business scenario where in the OEM users need to maintain huge universes (having 300+ Objects) and multiple versioning due product enhancements and customers business needs.
Vendor: Is software company who OEM’s Business Objects as the reporting solution with their product, including a pre-built universe and a set of reports to go with it.
Customer: Customer to the software company who buys the product along with the reporting solution, including the business objects software, the universe and reports.
Universe V1.0: Vendor Original (VO) universe which is the out-of-the box universe that was released to the customer.
Universe V1.5: Customer Modified (CM), customer makes changes/customizations to the VO universe to suit his specific requirements in terms of the data and also the functionality.
Universe V2.0: Vendor Modified (VM) which is the next version of the out-of-the box universe from the vendor which might include additional functionality, modifications and bug fixes.
Universe V2.5: Customer Final (CF) universe is the customer desired universe which contains all the changes that both Vendor and the Customer has done to the previous version of their universes.
The sequence of steps:
- The vendor develops the universe and gives it to the customer as part of the current release of the software (VO)
- The Customer customizes the universe according to the functional and the end user requirements (CM)
- Vendor release has a new version of the universe with additional functionality and bug fixes which he supplies to the customer (VM)
Customer now has three versions of the universe VO, CM and VM which need to be merged to come up with a final version of the universe that can has the new functionality and also the user customizations.
Enterprise Users: Consider business scenario where in the Enterprise users need to maintain multiple versions due to various production environment.
Scenario 1:-
Fig: Example depicting the scenario for comparing two universes.
Step 0: The customer is using a current version of the universe in production
Step 1: Over a period of time changes are made to the development environment and the Universe needs to be moved to production
Scenario 1:-
Fig: Example depicting the scenario for comparing three universes
Step 0: There is a current version of the Production Universe
Step 1: One of the developers is working on a set of classes and the objects in the universe that belong to one functional area
Step 2: A second developer is working on a set of classes and the objects in the universe that belong to a different functional area.
The sequence of steps:
User has three different versions of universe to compare and consolidate - the Dev Universe1, Dev Univrese2 and Production universe.
The features explain how UMT helps in the above scenarios |
