The development process can lead to modules which are no longer used subsequently in a technical workflow. Unused modules make it harder to maintain the system. Analyzing the existing structures and eradicating superfluous parts helps the people with technical responsibilities to look after their software. The implemented solution supports finding and deleting unused modules.
Supplement
In the development environment, Inubit Workbench technical workflows are created, amongst other things, comprising individual modules. By creating new workflows and moving workflows, it is possible for modules to be created which are not required subsequently. Modules that are created on an ad hoc basis for test purposes and are not subsequently removed correctly may remain unused in the system. The developed technical workflow checks the existing modules to see if they are used. The modules that are found which are not involved in a workflow and have reached a particular age are candidates for deletion. The implementation serves as an analysis possibility for the people with technical responsibilities. If a module occurs in the workflow, these occurrences are stored in a database. In the second step, the candidates for deletion can be deleted.
Subject description
The implementation of technical workflows by different developers leads to different procedures. The creation of modules which are not subsequently used cannot be entirely avoided. The modules are adapted by new requirements or are replaced. Old modules remain in the system as templates, either intentionally or unintentionally. Separating modules that are used from those that are not required is necessary for maintenance of the systems. If only the required modules are in place, they can be adapted more swiftly in case of errors or if requirements change. Support in eradication helps the people carrying out the actions.