Research Article

A Cost Effective and Preventive Approach to Avoid Integration Faults Caused by Mistakes in Distribution of Software Components

Table 1

Objectives × case study.

ObjectivesResults are obtained in the case study.

PreventionThe integration fault alert is displayed even before the faults occur. In addition, the effort to fix the configuration is minimized because the inconsistencies are identified in the log.

Be simple and cost effectiveThe development of the component for generating the inventory and prerun monitoring included around 1,200 lines of code in C# and required approximately 180 hours of work in construction and testing. The approach does not rely on information from log files or operating systems.

Cause minimal intrusionThe solution requires only the monitoring message at the startup of the application and the display of the alert in the visual interface, which implies adding less than 20 lines of source code to the application.

Provide reuseBecause the component version is an independent component, it can be coupled to other applications.