To Get any Project for CSE, IT ECE, EEE Contact Me @ 09666155510, 09849539085 or mail us - ieeefinalsemprojects@gmail.com-Visit Our Website: www.finalyearprojects.org

1. GLOBALSOFT TECHNOLOGIES
REPENT: Analyzing the Nature of Identifier Renamings
Abstract
Source code lexicon plays a paramount role in software quality: poor lexicon can lead to poor
comprehensibility and even increase software fault-proneness. For this reason, renaming a program
entity, i.e., altering the entity identifier, is an important activity during software evolution. Developers
rename when they feel that the name of an entity is not (anymore) consistent with its functionality, or
when such a name may be misleading. A survey that we performed with 71 developers suggests that 39
percent perform renaming from a few times per week to almost every day and that 92 percent of the
participants consider that renaming is not straightforward. However, despite the cost that is associated
with renaming, renamings are seldom if ever documented-for example, less than 1 percent of the
renamings in the five programs that we studied. This explains why participants largely agree on the
usefulness of automatically documenting renamings. In this paper we propose REanaming Program
ENTities (REPENT), an approach to automatically document-detect and classify-identifier renamings in
source code. REPENT detects renamings based on a combination of source code differencing and data
flow analyses. Using a set of natural language tools, REPENT classifies renamings into the different
dimensions of a taxonomy that we defined. Using the documented renamings, developers will be able
to, for example, look up methods that are part of the public API (as they impact client applications), or
look for inconsistencies between the name and the implementation of an entity that underwent a high
risk renaming (e.g., towards the opposite meaning). We evaluate the accuracy and completeness of
REPENT on the evolution history of five open-source Java programs. The study indicates a precision of 88
percent and a recall of 92 percent. In addition, we report an exploratory study investigating and
discussing how identifiers are renamed in the five programs, according to our taxonomy.
Existing system
IEEE PROJECTS & SOFTWARE DEVELOPMENTS
IEEE FINAL YEAR PROJECTS|IEEE ENGINEERING PROJECTS|IEEE STUDENTS PROJECTS|IEEE
BULK PROJECTS|BE/BTECH/ME/MTECH/MS/MCA PROJECTS|CSE/IT/ECE/EEE PROJECTS
CELL: +91 98495 39085, +91 99662 35788, +91 98495 57908, +91 97014 40401
Visit: www.finalyearprojects.org Mail to:ieeefinalsemprojects@gmail.com

2. Source code lexicon plays a paramount role in software quality: poor lexicon can lead to poor
comprehensibility and even increase software fault-proneness. For this reason, renaming a program
entity, i.e., altering the entity identifier, is an important activity during software evolution. Developer s
rename when they feel that the name of an entity is not (anymore) consistent with its functionality, or
when such a name may be misleading. A survey that we performed with 71 developers suggests that 39
percent perform renaming from a few times per week to almost every day and that 92 percent of the
participants consider that renaming is not straightforward. However, despite the cost that is associated
with renaming, renamings are seldom if ever documented-for example, less than 1 percent of the
renamings in the five programs that we studied. This explains why participants largely agree on the
usefulness of automatically documenting renamings.
Proposed system
we propose REanaming Program ENTities (REPENT), an approach to automatically document -detect and
classify-identifier renamings in source code. REPENT detects renamings based on a combination of
source code differencing and data flow analyses. Using a set of natural language tools, REPENT classifies
renamings into the different dimensions of a taxonomy that we defined. Using the documented
renamings, developers will be able to, for example, look up methods that are part of the public API (as
they impact client applications), or look for inconsistencies between the name and the implementation
of an entity that underwent a high risk renaming (e.g., towards the opposite meaning). We evaluate the
accuracy and completeness of REPENT on the evolution history of five open-source Java programs. The
study indicates a precision of 88 percent and a recall of 92 percent. In addition, we report an exploratory
study investigating and discussing how identifiers are renamed in the five programs, according to our
taxonomy.
SYSTEM CONFIGURATION:-
HARDWARE CONFIGURATION:-
 Processor - Pentium –IV
 Speed - 1.1 Ghz
 RAM - 256 MB(min)
 Hard Disk - 20 GB
 Key Board - Standard Windows Keyboard
 Mouse - Two or Three Button Mouse
 Monitor - SVGA

3. SOFTWARE CONFIGURATION:-
 Operating System : Windows XP
 Programming Language : JAVA
 Java Version : JDK 1.6 & above.