GuardIEn at Pohjola (now OP Keskus)

Pohjola - Company Profile

The Pohjola Group is an insurance company based in Finland covering the entire spectrum of insurance services.

The Pohjola Group use Gen as the development environment for a very large and integrated Insurance Services Application. This client/server application is deployed to many hundreds of desktops and notebooks around the country. The basic principles of the development architecture are reusability of common services, protection of the application from the database structure and integration of components delivered by multiple project teams. We have taken an approach which maximises the ability to use the repository for impact analysis and for that reason have only implemented some of the principles of object orientation.

The core of common service action blocks is very large. Their number and degree of integration has meant that a single development model architecture has been necessary. Within this model there are 12 projects (70 developers) providing services to one another in about 3000 common action blocks. Some of the procedure steps call in excess of 200 action blocks and in a situation where these action blocks are delivered by many different teams it is essential to have strict version control and release management policies. In addition it has been essential too to develop in-house utilities (like publishing cabs to dlls) to limit the necessity of downloading huge subsets and also allow cab changes in the model while a stable compiled version still exists for other projects to test off.

It’s for this reason that GuardIEn was purchased and implemented as the change control environment. Initially migration to System Test and other environments was centrally managed with the teams only taking responsibility for updating Owner, Release, Version and Status information. The cross-referencing and checking facilities offered by GuardIEn were essential to scoping accurate migrations where the functioning of a procedure step in system test might only be achieved by the accurate migration of 200 or more supporting cabs.

GuardIEn has also allowed the process of migration to be delegated to project teams. This is achieved through the concept of ownership which allows developers to control their own objects without affecting those of other projects. In addition GuardIEn does checks for dependent objects and verifies that the migration is complete. The GuardIEn interface to generate migration JCL is very simple to use and more effective than aggregate sets. It was therefore possible to pass this responsibility on without undue risk. Migrations after System test are still centrally managed however.

We rely heavily on it’s facilities for version, change and release management.

Terho Veijalainen
CE Administrator
The Pohjola Group