Tracking Objects to Detect Feature Dependencies

Lienhard, Adrian; Greevy, Orla; Nierstrasz, Oscar

doi:10.1109/icpc.2007.38

Cited by 29 publications

(19 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To illustrate the flexibility of our setup, we present the research development of our Feature Dependency Browser tool, which we developed to analyze runtime dependencies between features [4].…”

Section: Introductionmentioning

confidence: 99%

Rapid Prototyping of Visualizations using Mondrian

Lienhard

Kuhn

Greevy

2007

2007 4th IEEE International Workshop on Visualizing Software for Understanding and Analysis

Self Cite

View full text Add to dashboard Cite

Science requires tools, and computer science is no different. In a typical research context however, it is not known upfront how a tool should work. Researching the tool's design is part of the investigation process. Various designs have to be prototyped and experimented with. This paper focuses on the research process of interactive visualization tools. We present how to improve development, so that a novel tool can be tested and modified at (almost) the same time. We present the Mondrian framework, which supports on-the-fly prototyping of interactive visualizations. As an example, we present the research process of the Feature Dependency Browser, a visualization tool which we developed to allow software engineers inspect runtime dependencies between features.

show abstract

Section: Introductionmentioning

confidence: 99%

Rapid Prototyping of Visualizations using Mondrian

Lienhard

Kuhn

Greevy

2007

2007 4th IEEE International Workshop on Visualizing Software for Understanding and Analysis

Self Cite

View full text Add to dashboard Cite

show abstract

“…(see Table 1). Our answer to this question is an overview of a set Feature location and analysis Lienhard et al 2007) of activities that dependency analysis solutions in the literature claim to support or address. Our motivation to present this answer under these terms is motivated by what we observed in practice.…”

Section: Application Areas Of Dependency Analysismentioning

confidence: 99%

“…Most techniques and tools for execution trace analysis are presented for specific paradigms and even specific programming languages (Hamou-Lhadj and Lethbridge 2004). In the cases of dependency analysis, most solutions are to analyze object oriented implementations exploring relationships such as inheritance, polymorphism, and dynamic binding of languages such as Java and C++ (Egyed 2003;Lienhard et al 2007). The dynamic analysis techniques used among dependency analysis solutions include, footprint graph analysis (Egyed 2003), clustering (Xiao and Tzerpos 2005), whole path profiling (Law and Rothermel 2003a, b), object flow analysis (Lienhard et al 2007), redundant coupling detection (Alzamil 2007), online detection (Xin and Zhang 2007), execute after/before analysis (Jász et al 2008), compression and traversing of traces (Tallam and Gupta 2007), and formal concept analysis (Pfaltz 2006).…”

Section: Dynamic Analysismentioning

confidence: 99%

“…This information is in general not obvious or outdated, which causes that understanding the system becomes harder every time a feature is changed. Thus dependency analysis solutions provide support for the identification and analysis of system features mainly by conducting scenario-based analysis Eisenbarth et al 2001Eisenbarth et al , 2003Lienhard et al 2007). …”

Section: Traceability and Feature Analysismentioning

confidence: 99%

See 1 more Smart Citation

A practice-driven systematic review of dependency analysis solutions

2011

View full text Add to dashboard Cite

When following architecture-driven strategies to develop large softwareintensive systems, the analysis of the dependencies is not an easy task. In this paper, we report a systematic literature review on dependency analysis solutions. Dependency analysis concerns making dependencies due to interconnections between programs or system components explicit. The review is practice-driven because its research questions, execution, and reporting were influenced by the practice of a group of software architects at Philips Healthcare MRI. The review results in an overview and assessment of the state-of-the-art and applicability of dependency analysis. The overview provides insights about definitions related to dependency analysis, the sort of development activities that need dependency analysis, and the classification and description of a number of dependency analysis solutions. The contribution of this paper is for both practitioners and researchers. They can take it as a reference to learn about dependency analysis, match their own practice to the presented results, and to build similar overviews of other techniques and methods for other domains or types of systems.

show abstract

“…While study of runtime code based, we found that several approaches is related with this work. The used runtime program to detect feature dependency is proposed in [7], by tracking the object created at the runtime. It's focused on feature of the software, using dynamic analysis, and visualizes the object oriented software behavior.…”

Section: Software Comprehension and Toolmentioning

confidence: 99%

R3ST for Requirements Recovery of Legacy Runtime Code

Budiardjo¹,

Zamzami²,

Wahyudianto³

2015

LNSE

View full text Add to dashboard Cite

Abstract-In reality, we often find that proven and workable software, exist without source code. Identifying end-to-end interaction within existing legacy runtime code is a promising way for requirements recovery. Those identified interaction forms a set of use cases. Based on use case modeling concept, ontology is created for each finding interaction in order to check for completeness and consistency. OWL serves as platform for ontology development. That ontology reflects the recovered requirements. The procedures to identify the end-to-end interaction has been formulated and tested for university information systems. R3ST, tighly couple to Proté gé , has been developed with the objective to assist and automate those procedures.Index Terms-End-to-end interaction, use case, ontology, requirements recovery, software comprehension, software maintenance.

show abstract

Tracking Objects to Detect Feature Dependencies

Cited by 29 publications

References 14 publications

Rapid Prototyping of Visualizations using Mondrian

Rapid Prototyping of Visualizations using Mondrian

A practice-driven systematic review of dependency analysis solutions

R3ST for Requirements Recovery of Legacy Runtime Code

Contact Info

Product

Resources

About