Interactive Scalable Abstraction of Reverse Engineered UML Class Diagrams

Osman, Mohd Hafeez; Chaudron, Michel R. V.; Putten, Peter van der

doi:10.1109/apsec.2014.34

Cited by 9 publications

(4 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, knowledge of role stereotypes can aid in reducing the information presented to developers through design summarisation. Initial studies into summarisation have been described by Osman et al (2014). These studies showed that additional semantic information about components in the design could be useful.…”

Section: Use In Program Comprehensionmentioning

confidence: 99%

Role stereotypes in software designs and their evolution

Ho-Quang

Nurwidyantoro

Rukmono

et al. 2022

Journal of Systems and Software

View full text Add to dashboard Cite

Section: Use In Program Comprehensionmentioning

confidence: 99%

Role stereotypes in software designs and their evolution

Ho-Quang

Nurwidyantoro

Rukmono

et al. 2022

Journal of Systems and Software

View full text Add to dashboard Cite

“…There are several academic approaches on architectural views oriented to soft-ware comprehension tasks, for example: CodeCity (Wettel et al 2011), eCity+ (Khan et al 2014), AIVA (Snajberk et al 2012;najberk et al 2013), SAABs (Osman et al 2014), Softwarenaut (Lungu et al 2014), VizDSL (Morgan et al 2018), Modigen (Gerhart and Boger 2016), EuGENia, 17 Moose, 18 and GRAPH (Bergel et al 2014).…”

Section: Software Visualizationmentioning

confidence: 99%

Metric-centered and technology-independent architectural views for software comprehension

Mendivelso¹,

Garcés²,

Casallas³

2018

J Softw Eng Res Dev

View full text Add to dashboard Cite

The maintenance of applications is a crucial activity in the software industry. The high cost of this process is due to the effort invested on software comprehension since, in most of cases, there is no up-to-date abstraction or documentation to ease this task but the source code. The goal of many commercial and academic tools is to build software architectural views from the code. The main disadvantages of such tools are: i) they are dependent on the language/technology on top of which the application is built; and ii) they offer pre-defined views that are too difficult to adapt to meet particular software comprehension needs. In this paper, we present a Technology-independent approach which is flexible enough to allow developers to define metric-centered architectural views by using annotations. These views display in a single canvas architectural elements whose look and feel maps software metrics. Our work results from joint projects with industry partners with software modernization needs in different technologies: Oracle Forms, Java EE, and Ruby on Rails. We present how our proposal was applied in these projects and compare the results with those of the previously followed process.

show abstract

“…A fast way to recover missing documentation is to rely on reverse engineering [9]. However, reverse engineered models have a tendency to become overly complex since they do not contain the abstraction mechanisms usually applied manually by architects [10]. Some of these abstractions can be achieved by methods of filtering software entities.…”

Section: B Separating Names-used and User-names In The Feature Vectormentioning

confidence: 99%