A Specification Driven Slicing Process for Identifying Reusable Functions

CIMITILE, ANIELLO; LUCIA, ANDREA DE; Munro, Malcolm

doi:10.1002/(sici)1096-908x(199605)8:3<145::aid-smr127>3.0.co;2-9

Cited by 52 publications

(24 citation statements)

References 45 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The simplification offered by program slicing has led to its application in a number of software engineering tasks, for example, debugging [2,73,95,124], restructuring [30], reuse [10,34,89] and program comprehension [36]. One drawback common to all slicing techniques is the low level at which a slicing criterion is specified.…”

Section: Aims and Objectives Of This Thesismentioning

confidence: 99%

Identifying high-level dependence structures using slice-based dependence analysis

2009

2009 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

This thesis addresses dependence based concept assignment using slicing based dependence analysis on concept assignment.Concepts are domain level entities concerned with the real world. Although concepts are defined at the domain level, the source code of a program must, nonetheless, express these concepts in program code denotations. Traditional concept assignment maps the low level of source code to the high level of the domain through the medium of associations. These associations typically take the form of comments and identifiers.Previous work on the combination of dependence analysis with concept assignment gave the definition of either extending concepts to concept slices or abbreviating concepts to key statements. However, there are no empirical studies to show the feasibility of these two approaches.In this thesis, we propose an improved key statement analysis algorithm and empirically study executable concept slicing and key statement analysis using ten subject programs with more than 600 concept bindings identified. We define dependence based metrics to evaluate both approaches and to provide evidence of both advantages and disadvantages. Based on these foundations, we propose a new combination technique -concept refinement, which adopts the advantages and overcome the disadvantages of previous two approaches.The results for the same programs with the same concept bindings showed that concept refinement can produce dependence based concept bindings. The refined concept binding is smaller, but with similar impact and higher cohesion than the original HB-CA concept binding. Therefore, it becomes more precise after refinement; the refined concept binding is much smaller than the executable concept slice with respect to the original HB-CA concept binding. These findings suggest that the refined concept binding is more reasonable in size for program comprehension.Furthermore, the refined concept binding can be extracted from most of the original HB-CA concept bindings, thus concept refinement is more appropriate than the key statement analysis. DeclarationThe work presented in this thesis is original work undertaken between September

show abstract

Section: Aims and Objectives Of This Thesismentioning

confidence: 99%

Identifying high-level dependence structures using slice-based dependence analysis

2009

2009 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

show abstract

“…Through control and data dependency analysis, it is easy to verify that node 8 is the validation node of node 4, and node 10 is the validation node of node 5. In addition, (2,8) is the validation chain at node 8, and (2,8,10) is the validation chain at node 10.…”

Section: Analysis Modelmentioning

confidence: 99%

“…From Property 2, we infer that the validation chain (2,8) at node 8 implements a decision to such that if a user is logged in but the product ID is not available in the database, then the input is rejected. The validation chain (2,8,10) at node 10 implements a decision such that if the user is logged in, product ID is valid, and product count is greater than 0, then the input is accepted and processed accordingly; otherwise, it is rejected. An investigation of the AddtoCart program shows that there are two decisions in the program to accept or reject input read at node 4 and 5.…”

Section: Empirical Propertiesmentioning

confidence: 99%

An approach for the maintenance of input validation

Liu

Tan

2008

Information and Software Technology

View full text Add to dashboard Cite

“…The field of program slicing is concerned with computing a quotient of a program which preserves part of the behaviour of the original program. Program slicing is used in program comprehension [2,3], software maintenance [4,5,6,7], and debugging [8,9,10,11].…”

Section: Introductionmentioning

confidence: 99%

On the computational complexity of dynamic slicing problems for program schemas

Danicic

Hierons

Laurence

2011

Math. Struct. Comp. Sci.

View full text Add to dashboard Cite

Given a program, a quotient can be obtained from it by deleting zero or more statements. The field of program slicing is concerned with computing a quotient of a program which preserves part of the behaviour of the original program. All program slicing algorithms take account of the structural properties of a program such as control dependence and data dependence rather than the semantics of its functions and predicates, and thus work, in effect, with program schemas. The dynamic slicing criterion of Korel and Laski requires only that program behaviour is preserved in cases where the original program follows a particular path, and that the slice/quotient follows this path. In this paper we formalise Korel and Laski's definition of a dynamic slice as applied to linear schemas, and also formulate a less restrictive definition in which the path through the original program need not be preserved by the slice. The less restrictive definition has the benefit of leading to smaller slices. For both definitions, we compute complexity bounds for the problems of establishing whether a given slice of a linear schema is a dynamic slice and whether a linear schema has a non-trivial dynamic slice and prove that the latter problem is NP-hard in both cases. We also give an example to prove that minimal dynamic slices (whether or not they preserve the original path) need not be unique.

show abstract

A Specification Driven Slicing Process for Identifying Reusable Functions

Cited by 52 publications

References 45 publications

Identifying high-level dependence structures using slice-based dependence analysis

Identifying high-level dependence structures using slice-based dependence analysis

An approach for the maintenance of input validation

On the computational complexity of dynamic slicing problems for program schemas

Contact Info

Product

Resources

About