Cross references are features

Schwanke, Robert W.; Platoff, M. A.

doi:10.1007/3-540-56483-7_26

Cited by 10 publications

(15 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Schwanke and Platoff's paper gives no motivation for why both feature kinds should be including, nor why they should be distinguished between [1]. We will in the following section try to provide motivation for doing so.…”

Section: Motivationmentioning

confidence: 99%

See 1 more Smart Citation

On the significance of relationship directions in clustering algorithms for reverse engineering

Jensen

Lundkvist

Hammouda

2017

Proceedings of the Symposium on Applied Computing

View full text Add to dashboard Cite

Section: Motivationmentioning

confidence: 99%

“…This idea originates from Schwanke and Platoff's paper "Cross references are features" [1]. Schwanke and Platoff also propose distinguishing between user-names (features representing other entities that use the entity) from names-used (features representing what the entity is using).…”

Section: Introductionmentioning

confidence: 99%

On the significance of relationship directions in clustering algorithms for reverse engineering

Jensen

Lundkvist

Hammouda

2017

Proceedings of the Symposium on Applied Computing

View full text Add to dashboard Cite

“…Re-engineering often deals primarily with module views [63] and aims to improve the static system structure. In our approach, we used mainly instancelevel runtime architectural views to visualize and reason about the subject system (Figures 11 and 15), although we did consider static module view ( Figure 6) to take into account ArchJava and AliasJava's rules concerning inheritance.…”

Section: Related Workmentioning

confidence: 99%

A case study in re-engineering to enforce architectural control flow and data sharing

Abi-Antoun

Aldrich

Coelho

2007

Journal of Systems and Software

View full text Add to dashboard Cite

Without rigorous software development and maintenance, software tends to lose its original architectural structure and become difficult to understand and modify. ArchJava, a recently proposed programming language which embeds a componentand-connector architectural specification within Java implementation code, offers the promise of preventing the loss of architectural structure. AliasJava, which can be used in conjunction with ArchJava, is an annotation system that extends Java to express how data is confined within, passed among, or shared between components and objects in a software system.We describe a case study in which we incrementally re-engineer an existing Java implementation to obtain an implementation which enforces the architectural control flow and data sharing. Building on results from similar case studies, we chose an application consisting of over 16,000 source lines of Java code and over 90 classes. We describe our process, the detailed steps involved (some of which can be automated), as well as some lessons learned and perceived limitations with the languages, techniques and tools we used.

show abstract

“…In reverse engineering field, there has been research on measuring similarity of components and restructuring modules in a software system, to improve its maintainability and understandability [36][37][38]. Such similarity measures are based on several metric values such as shared identifier names and function invocation relations.…”

Section: Related Workmentioning

confidence: 99%

Measuring Similarity of Large Software Systems Based on Source Code Correspondence

Yamamoto

Matsushita

Kobayashi

et al. 2005

Product Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. It is an important and intriguing issue to know the quantitative similarity of large software systems. In this paper, a similarity metric between two sets of source code files based on the correspondence of overall source code lines is proposed. A Software similarity MeAsurement Tool SMAT was developed and applied to various versions of an operating system(BSD UNIX). The resulting similarity valuations clearly revealed the evolutionary history characteristics of the BSD UNIX Operating System.

show abstract

Cross references are features

Cited by 10 publications

References 7 publications

On the significance of relationship directions in clustering algorithms for reverse engineering

On the significance of relationship directions in clustering algorithms for reverse engineering

A case study in re-engineering to enforce architectural control flow and data sharing

Measuring Similarity of Large Software Systems Based on Source Code Correspondence

Contact Info

Product

Resources

About