Embed Size (px)
DESCRIPTION
http://seal.ifi.uzh.ch/msa2010/
Citation preview
Ahmed LamkanfiSerge Demeyer
Lab On ReengineeringUniversity of Antwerp
Impact Analysis of Software Maintenance using Software Traceability
Introduction
•Source code continually changes
Introduction
•Source code continually changes
•The origin of changes➡ track modifications back to their origin
➡ analyze
Introduction
•Two steps:➡ reconstruct traceability
➡ analyzing the evolution of traceability
•Source code continually changes
•The origin of changes➡ track modifications back to their origin
➡ analyze
Software Traceability
Source code unit
Requirement traceability link
Software Traceability
Source code unit
Requirement
• file
• class
• method
• use case
• test case
• bug report
traceability link
Software Traceability
Source code unit
Requirement
• file
• class
• method
• use case
• test case
• bug report
traceability link
➡ text mining
➡ static analysis
➡ dynamic analysis
Traceability Evolution
version 1
R1
R2
C1
C2
C3
Traceability Evolution
version 1
R1
R2
C1
C2
C3
version 2
R1
R2
C1
C2
C3
C4
Traceability Evolution
version 1
R1
R2
C1
C2
C3
version 2
R1
R2
C1
C2
C3
C4
. . .
version n
R1
R3
C1
C2
C3
C4R4
Traceability Evolution
•Look for Frequently Applied Changes➡ in the source code➡ in the requirements
•(How) do they relate?
version 1
R1
R2
C1
C2
C3
version 2
R1
R2
C1
C2
C3
C4
. . .
version n
R1
R3
C1
C2
C3
C4R4
Traceability Evolution
•What impact do changing requirements have on the source code?
•What impact do reported bugs have on the source code?
The past is behind, learn from it.The future is ahead, prepare for it.
Thomas S. Monson
