The Impact of View Histories on Edit
Recommendations
ABSTRACT:

Recommendation systems are intended to increase developer productivity
by recommending files to edit. These systems mine association rules in
software revision histories. However, mining coarse-grained rules using
only edit histories produces recommendations with low accuracy, and can
only produce recommendations after a developer edits a file.

In this work, we explore the use of finer-grained association rules, based on
the insight that view histories help characterize the contexts of files to edit.
To leverage this additional context and fine-grained association rules, we
have developed MI, a recommendation system extending ROSE, an
existing edit-based recommendation system.

We then conducted a comparative simulation of ROSE and MI using the
interaction histories stored in the Eclipse Bugzilla system. The simulation
demonstrates that MI predicts the files to edit with significantly higher
recommendation accuracy than ROSE (about 63% over 35%), and makes
recommendations earlier, often before developers begin editing.

Our results clearly demonstrate the value of considering both views and
edits in systems to recommend files to edit, and results in more accurate,
earlier, and more flexible recommendations.
Existing System
Existing System
Programmer interactions histories contain the records of files viewed by
programmers as well as those edited, and, are thus a more informative source
than software revision histories. We believe this can significantly improve
recommendations for editing, as the records of viewed files establish a more
accurate programmer context to recommend relevant files to edit.
Let us explain this idea with the example in which shows a situation in
which programmers have performed tasks and a programmer is now performing
task. The lower-case letters in represent the files that are viewed or edited by
programmers. While performing, this programmer views files. Given these
interaction events, the following question arises.
Previous approaches that mine edit histories cannot make
recommendations at this point because the programmer has not yet edited a file.
If the programmer edits a file, the files as a context to find other files to edit
together.
Existing System Architecture
PROPOSED SYSTEM
Proposed System
The propose, MI (Mining programmer Interaction histories), recommends
files to edit using the context provided by both the viewed files and the edited
files. The records of viewed files are used to identify the interaction history
events that are most similar. As the programmer’s current navigation activities
for the most similar task, the files edited in Task are most likely to be edited in
Task. When the programmer views uses the viewed files to find files to edit. As
the files were also viewed in Task, MI recommends the files that were edited in
Task. Once a programmer edits, MI adds this interaction to create the context of
viewed files. MI again associates this context with Task and recommends file to
edit.
Using a context that includes viewed files can improve the accuracy of
recommending files to edit. To recommend files to edit by utilizing the records of
viewed files, MI mines interaction histories.
MI mines interaction traces, finds association rules using the current
context, and generates recommendations of files to edit. The essential part of the
recommendation system is the context. The context characterizes the situation of
the programmer viewed files, and is used as a query at the time of
recommendation. We first explain the detailed procedure of MI and propose the
outline for context formation in MI.
MODULE DESCRIPTION
Modules:
The system consists of modules and threat modules.
 Public Key
 File Store
 Message Edit and File Edit
 View Project Edit Histories and File Edit Histories
 Recommendation for Project Edit and File Edit.
Module Explanations:
Public Key:
In this Module public key is generated for authentication for the user to
provide the user specification of the task.
File Storage
The File Storage module the file stored for the further usage of the
consumer for the and the file is provided the option to edit file provided
recommendation by the administrator.
Message Edit and File Edit
The message send to the user to perform the task of project operation after
completion the task according to the message received
View Project Edit History and File Edit History
This module provides the histories or logs the tasks who has did at what
time and what task he performed on the file or messages.
Recommendation for Project Edit and File Edit.
In this module the recommendation is approved to edit the file so that it should
be the action which has to be carried to the proficiency.
SYSTEM CONFIGURATION
SOFTWARE REQUIREMENTS:
 Operating System
:
Windows 7
 Technology
:
Java and J2EE
 Web Technologies
:
Html, JavaScript, CSS
 IDE
:
Eclipse Juno
 Web Server
:
Tomcat
 Database
:
My SQL
 Java Version
:
J2SDK1.5
 Hardware
:
Pentium Dual Core
 Speed
:
2.80 GHz
 RAM
:
1GB
 Hard Disk
:
20 GB
 Floppy Drive
:
1.44 MB
 Key Board
:
Standard Windows Keyboard
 Mouse
:
Two or Three Button Mouse
 Monitor
:
SVGA
HARDWARE REQUIREMENTS: