Some strategies of reuse in an object-oriented programming environment

Lange, B. M.; Moher, Tom

doi:10.1145/67449.67465

Cited by 48 publications

(25 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This modification request 5 described a need, when hovering over a breakpoint in an editor for Java source code, 6 to display the breakpoint's properties, such as the associated line number, in a pop-up window. The request asked for a few basic properties, such as the breakpoint's line number.…”

Section: Designmentioning

confidence: 99%

“…The request asked for a more intelligent handling of this case, similar to the way it is done through the "synchronization view", where new files can be automatically versioned when they are committed. 5 Request 6660 in the Eclipse problem report database 6 A breakpoint is a debugging facility that suspends the execution of the program at a certain location in the code, enabling the developer to investigate the program's internal state. 7 Request 20982 in the Eclipse problem report database Characterization of the two tasks.…”

Section: Designmentioning

confidence: 99%

“…Often, the advice obtained is a pointer to an example (a section of code, for instance) showing how to deal with a particular problem. Studying from examples and abstracting them for application in a new context is a common way of learning in programming that has been observed extensively in both new [9] and experienced [6] programmers.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Learning from project history

Čubranić

Murphy

Singer

et al. 2004

Proceedings of the 2004 ACM Conference on Computer Supported Cooperative Work

View full text Add to dashboard Cite

The lack of lightweight communication channels and other technical and sociological difficulties make it hard for new members of a non-collocated software development team to learn effectively from their more experienced colleagues while they are coming upto-speed on a project. To address this situation, we have developed a tool, named Hipikat, that provides developers with efficient and effective access to the group memory for a software development project that is implicitly formed by all of the artifacts produced during the development. This project memory is built automatically with little or no change to existing work practices. We report an exploratory case study evaluating whether software developers who are new to a project can benefit from the artifacts that Hipikat recommends from the project memory. To assess the appropriateness of the recommendations, we investigated when and how developers queried the project memory, how they evaluated the recommended artifacts, and the process by which they utilized the artifacts. We found that newcomers did use the recommendations and their final solutions exploited the recommended artifacts, although most of the Hipikat queries came in the early stages of a change task. We describe the case study, present qualitative observations, and suggest implications of using project memory as a learning aid for project newcomers.

show abstract

Section: Designmentioning

confidence: 99%

Section: Designmentioning

confidence: 99%

See 1 more Smart Citation

Learning from project history

Čubranić

Murphy

Singer

et al. 2004

Proceedings of the 2004 ACM Conference on Computer Supported Cooperative Work

View full text Add to dashboard Cite

show abstract

“…In view of the amendments performed on existing screens, UI codes scavenging are inevitable. It is parallel to the literal form of code reuse in the programming environment employing code copying and editing strategies as noted in [4] and [5]. This consecutively resulted in the production of massive replicas of UI screen designs with modest deviations from one another.…”

Section: Introductionmentioning

confidence: 99%

Using change tracking component to manage OO driven user interface layout management system

Lim

2010

2010 International Symposium on Information Technology

View full text Add to dashboard Cite

User Interfaces (UI) layout design is one of the most important part of any software requirement activities. User interfaces (UI) emerged as an essential accomplice in fulfilling the potential of an application. Layout design of UI screens has always been very expensive and time consuming activities. However, owing to the ad-hoc nature of UI design process coupled with user involvement throughout the process have inevitably surfaced in the UI construction and management phases. This includes the amount of effort involved in fulfilling multiple user requirements which in turn lead to the generation of a large number of screen layout designs with numerous similarities among them. Taking into considerations on the amount of effort required in maintaining masses of UI layouts with plentifol commonalities, this paper focuses on the integration of an object-oriented approach towards UI layout design along with an evolution tracking system to address the issues projected Cases were used at the end of this paper to evaluate the effectiveness and accomplishments of the proposed approach so that future research work could be planned

show abstract

“…Several reasons have been suggested for the prevalence of code clones in software systems, including the difficulty of factoring out functionality using programming language constructs, and the practice of writing code by example [9].…”

Section: Introductionmentioning

confidence: 99%

Clonetracker

Duala-Ekoko

Robillard

2008

Proceedings of the 13th International Conference on Software Engineering - ICSE '08

View full text Add to dashboard Cite

Code clones are generally considered to be an obstacle to software maintenance. Research has provided evidence that it may not always be practical, feasible, or cost-effective to eliminate certain clone groups through refactoring. This paper describes CloneTracker, an Eclipse plug-in that provides support for tracking code clones in evolving software. With CloneTracker, developers can specify clone groups they wish to track, and the tool will automatically generate a clone model that is robust to changes to the source code, and can be shared with other collaborators of the project. When future modifications intersect with tracked clones, Clone-Tracker will notify the developer, provide support to consistently apply changes to a corresponding clone region, and provide support for updating the clone model. CloneTracker complements existing techniques by providing support for reusing knowledge about the location of clones in source code, and support for keeping track of clones when refactoring is not desirable.

show abstract

Some strategies of reuse in an object-oriented programming environment

Cited by 48 publications

References 7 publications

Learning from project history

Learning from project history

Using change tracking component to manage OO driven user interface layout management system

Clonetracker

Contact Info

Product

Resources

About