The relevance of the results is as- sessed on the basis of deployment problems that would have historically occurred within a set of industrial systems.Īpplication Programming Interfaces (API) provide reusable functionality to aid developers in the development process. The approach is evaluated for its ability to drastically lter irrelevant details, while being unlikely to lter important ones. This paper presents a recommendation approach for lter- ing the ood of change events on deployment dependencies to those that are most likely to cause problems for the indi- vidual developer.
As a result, errors may arise at deployment time that the developer does not immediately detect. To proactively respond to such situations, developers must constantly monitor a ood of information involving changes to the deployment environ- ments unfortunately, the vast majority of this information is irrelevant to the individual developer, and its sheer volume makes it likely that infrequent change events of relevance are overlooked.
Rssowl broken code#
It is often assumed that developers' view of their system and its environment is always consistent with everyone else's in practice, this assumption can be false, as the developer has little practical control over changes to the environments in which their code will be deployed.
0 kommentar(er)
