Targets of a comprehensive Software Conflict Management
For Raynet, conflict management is an essential building block in providing quality assured software packages. Terms like “Conflict Elimination”, “Conflict Validation” and “Conflict Solution” are differently interpreted within the context of software packaging. Some tools define violations of rules within the software package and encapsulated “design variances” as conflicts (ICE conflicts). Others talk about software conflicts once a file used in a software package is installed jointly with a same-name-file of another package in the same environment.
There are certainly further occurrences of software conflicts in software packages. All of them share the fact, that they get manifested to a problem in later phases, when different software products are being installed in the same environment or have to interact with the operating system as well as prior or after a change in the installation status (installation, de-installation, etc.).
The only weapon to avoid disturbances and work pro-actively against conflicts is an exact knowledge about the consequences of installing or de-installing an application on a certain client.
By adjusting and matching software towards the target system it should run on, losses in work time and disturbances on the clients can be avoided or reduced. This means a lesser volume on helpdesk calls, less incidents and significant increase in the quality of the software provision process. This underlines the importance of a conflict management system.
Conflict Management allows the discovery of possible conflicts between applications already during the provision process. Even better, it is possible to already eliminate those conflicts before providing the packaged application to the customer. Conflict management is done continuously during the overall process and by the individuals assigned to the various tasks.
Steps of a Software-Conflict-Management
Within RaySuite, Raynet uses RayQC as an automation tool to detect possible conflicts in applications and lists them for either an automatic correction or later examination. Raynet consultants elaborate your individual environment and consider principles and recommendations when implementing a conflict management, such as:
- Setup of a central Conflict Management database
- Building „Application-Sets“ guaranteed free of conflicts. New applications will be tested against the set it is supposed to join. Alternatively, the conflict check will be done against the largest possible base released.
- Handling of software packages of just one type (e.g. native MSI, virtual package, etc.)
- Setting test criteria for the Conflict Management
- Setting up a release management to administer applications, application gorups and the tested base.