Typical Current Situation

The whole process and method for the creation and modification of software systems and their related documents is not often automatically managed. The transfer of any related task descriptions (both forward and backward) is not properly understood, the completeness and the consistency of all affected documents cannot be guaranteed.

Modifications without a task description (say hot fixes), often get round existing management controls for quality checks and security within the IT department. There is no early warning of any conflicts.

Tasks, in particular those overall system related guidelines, are not documented together with the relevant software objects as part of the change management system. The inability to be able to rebuild these task descriptions, complicates the proper understanding of why changes are being made to the software in the first place.


Solution using SET-LIBER Task Management

The SET-LIBER Task Management concept is to store all tasks as description files, this makes all of their relationships obvious at an early stage. The task descriptions are normally used to make the related software objects available for the developer (groups).

SET-LIBER Task-Management manages and provides version control for the task descriptions in the same way as for the other software objects. The task descriptions are also used for the control of processes like compile, catal. and the transfer into production. All related documents are checked for completeness, at transfer time.

SET-LIBER Conflict-Management will show clearly whether any other objects, documents or load modules for example, are in conflict with the status of other change or production objects. All objects are taken into account, upwards and downwards, as well as possible cross platform relationships.

SET-LIBER provides for the possibility of getting Hot Fix changes into production quickly, but not at the expense of proper controls, all the reasons for the changes and the authorizations are fully documented