A history-based matching approach to identification of framework evolution

Meng,; Wang, Xiaoyin; Zhang, Bo; Мэй,

doi:10.1109/icse.2012.6227179

Cited by 60 publications

(57 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Previous work has described how to match program elements across program versions [5,9,21,29,33]. We were not able to use an existing tool since the tool implementation is either unavailable [33] or does not support the latest Java version [5], or the technique itself focuses on identifying changes by a small set of refactorings [9,21] rather than finding the counterpart of an arbitrary program element.…”

Section: Matching Methods Across Versionsmentioning

confidence: 99%

See 1 more Smart Citation

Automatically repairing broken workflows for evolving GUI applications

Zhang

Lü

Ernst

2013

Proceedings of the 2013 International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

A workflow is a sequence of UI actions to complete a specific task. In the course of a GUI application's evolution, changes ranging from a simple GUI refactoring to a complete rearchitecture can break an end-user's well-established workflow. It can be challenging to find a replacement workflow. To address this problem, we present a technique (and its tool implementation, called FlowFixer) that repairs a broken workflow. FlowFixer uses dynamic profiling, static analysis, and random testing to suggest a replacement UI action that fixes a broken workflow.We evaluated FlowFixer on 16 broken workflows from 5 realworld GUI applications written in Java. In 13 workflows, the correct replacement action was FlowFixer's first suggestion. In 2 workflows, the correct replacement action was FlowFixer's second suggestion. The remaining workflow was un-repairable. Overall, FlowFixer produced significantly better results than two alternative approaches.

show abstract

Section: Matching Methods Across Versionsmentioning

confidence: 99%

“…It uses the observation that underlying code implementing the same functionality often stays the same between versions. Investigating the benefits of more sophisticated matching techniques [5,29] is future work.…”

Section: Supporting Software Evolutionmentioning

confidence: 99%

Automatically repairing broken workflows for evolving GUI applications

Zhang

Lü

Ernst

2013

Proceedings of the 2013 International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

show abstract

“…Information technology project performance evaluation generally refers to assessment by other organizations or individuals. On the one hand, the performance data collected fro m various controlling processes, analyzed in context and integrated based on relationships across areas, on the other hand, the physical or electronic representation of wo rk perfo rmance informat ion co mpiled in p roject documents, intended to generate decisions or raise issues, actions, or awareness [10].…”

Section: Design Of Information System Project Management Modelmentioning

confidence: 99%

The Method and Its Application of Project Management Modeling in Whole Life Cycle

Huan¹,

Chen²

2015

Proceedings of the International Conference on Logistics, Engineering, Management and Computer Science

View full text Add to dashboard Cite

Abstract-Project management is the application of knowledge, skills, tools and techniques to project activities, in order to meet the project requirements. As long as the project requirements become more complex and volatile in the university, the ability to optimize and integrate costs, schedule, effort and benefits become the most important. Therefore, how to control the project's whole life cycle in efficient and effective ways has become a critical issue for information engineers in universities. To resolve this problem, this paper extends an information system management model to the whole life cycle of project, which can manage whole procedure from feasibility analysis to performance review, and make sure implementation of information system project in universities.

show abstract

“…There are a lot of approaches [5][6][7][8][9][10][11][12] to automating migration of clients for API evolution, and all we know are designed for local APIs. Although in principle these approaches should also work on web APIs, it is still an open question whether any new problems will emerge if they are actually applied.…”

Section: Change Upper Bound Of Parametermentioning

confidence: 99%

“…Given the importance of migrating client programs, a lot of research has been devoted into this area and different approaches [5][6][7][8][9][10][11] have been proposed to automate the migration process. However, in practice, we seldom observe these approaches be adopted in the migration of web API clients.…”

Section: Introductionmentioning

confidence: 99%

How Does Web Service API Evolution Affect Clients?

Xiong

Liu

et al. 2013

2013 IEEE 20th International Conference on Web Services

Self Cite

View full text Add to dashboard Cite

Abstract-Like traditional local APIs, web service APIs (web APIs for short) evolve, bringing new and improved functionality as well as incompatibilities. Client programs have to be modified according to these changes in order to use the new APIs. Unlike client programs of a local API, which could continue to use the old API, clients of a web API often do not have the option not to upgrade, since the old version of the API may not be provided as a service anymore. Therefore, migrating clients of web APIs is a more critical task. Research has been done in the evolution of local APIs and different approaches have been proposed to support the migration of client applications. However, in practice, we seldom observe that web API providers release automated tools or services to assist the migration of client applications.In this paper, we report an empirical study on web API evolution to address this issue. We analyzed the evolution of five popular web APIs, in total 256 changed API elements, and carefully compared our results with existing empirical study on API evolution. Our findings are threefold: 1) We summarize the API changes into 16 change patterns, which provide grounded supports for future research; 2) We identify 6 completely new challenges in migrating web API clients, which do not exist in the migration of local API clients; 3) We also identify several unique characteristics in web API evolution.

show abstract

A history-based matching approach to identification of framework evolution

Cited by 60 publications

References 28 publications

Automatically repairing broken workflows for evolving GUI applications

Automatically repairing broken workflows for evolving GUI applications

The Method and Its Application of Project Management Modeling in Whole Life Cycle

How Does Web Service API Evolution Affect Clients?

Contact Info

Product

Resources

About