
Program slicing is a useful analysis for aiding differentsoftware engineering activities. In the past decades, various notionsof program slices have been evolved as well as a number of methods tocompute them. By now program slicing has numerous applications insoftware maintenance, program comprehension, reverse engineering,program integration, and software testing. Usability of program slicingfor real world programs depends on many factors such as precision,speed, and scalability, which have already been addressed in theliterature. However, only a little attention has been brought to thepractical demand: when the slices are large or difficult to understand,which often occur in the case of larger programs, how to give anexplanation for the user why a particular element has been includedin the resulting slice. This paper describes a reasoning method aboutelements of static program slices.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
