Using UPK for an evolving system

UPK is a handy tool to create documentation for the various phases in a (big) project. Often, projects are unfortunately not quite in the outlined phases. What about the project while the system is still in developing?

(source: Oracle)

UPK provides really good support in large complex projects where (a) the system development is not according to the planning  and (b) there is also lack of functional specifications of the system. 

The first recording of the functionalities used to provide a picture of how the emerging system will support existing business processes. These recordings are also used by the tester for help understanding the functionality of the system but also to know the relationship between the functionalities concerning what the has to test.

The recording were also use to tell the developers how the system should be build to support the business processes and the help to understand the various process links that the system should support.

Last but not least was the recording also use to communicate with the client the expectation of the system that is been build for the client. 

Re-recording

The changes in the functionalities of the system were readmitted when they occur. There for is the ‘Re-recording Topic’ function in UPK an great tool. This way is easy to determine exactly what the changes in the functionalities are compare to the way they were before. 

This way of working using UPK was ideal and positive experienced by the client. They enjoy regularly to see how the system was evolving and how it work. Afterwards was the system not unknown anymore and is the level of acceptance much higher because they know what they finally will get.

 Viewed 4314 times by 1323 visitors

Posted by: Sjahaira Eisden (1 post(s)).

Oracle consultant experienced in process improvement and information management. Knowledge of UPK, PeopleSoft and E-Business Suite.