Experiences from identifying software reuse opportunities by domain analysis

Koziolek, Heiko; Goldschmidt, Thomas; Gooijer, Thijmen de; Domis, Dominik; Sehestedt, Stephan

doi:10.1145/2491627.2491641

Cited by 10 publications

(6 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Previous work investigate the identification of reuse opportunities from software systems [Inoue et al 2005, Koziolek et al 2013, Li et al 2005, Mende et al 2009, Michail and Notkin 1999, Oliveira et al 2007, Ye and Fischer 2005. As an example, Inoue et al (2005) propose a graph-based technique to support the extraction of frequently used components in a given software component repository.…”

Section: Identification Of Reuse Opportunitiesmentioning

confidence: 99%

See 1 more Smart Citation

A Method Based on Naming Similarity to Identify Reuse Opportunities

Oliveira

Fernandes²,

Souza³

et al. 2017

iSys

View full text Add to dashboard Cite

Software reuse is a development strategy in which existing software components are used to implement new software systems. There are many advantages of applying software reuse, such as minimization of development efforts and improvement of software quality. Few methods have been proposed in the literature for recommendation of reuse opportunities. In this paper, we propose a method for identification and recommendation of reuse opportunities based on the similarity of the names of classes. Our method, called JReuse, computes a similarity function to identify similarly named classes from a set of software systems from a specific domain. The identified classes compose a repository with reuse opportunities. We also present a prototype tool to support the proposed method. We applied our method, through the tool, to 72 software systems mined from GitHub, in 4 different domains: accounting, restaurant, hospital, and e-commerce. In total, these systems have 1,567,337 lines of code, 57,017 methods, and 12,598 classes. As a result, we observe that JReuse is able to identify the main classes that are frequent in each selected domain.

show abstract

Section: Identification Of Reuse Opportunitiesmentioning

confidence: 99%

“…In turn, Koziolek et al (2013) present a technique for identification of reuse opportunities based on domain analysis. The proposed technique aims to support the assessment of potential Software Product Line implementation by organizations.…”

Section: Identification Of Reuse Opportunitiesmentioning

confidence: 99%

A Method Based on Naming Similarity to Identify Reuse Opportunities

Oliveira

Fernandes²,

Souza³

et al. 2017

iSys

View full text Add to dashboard Cite

show abstract

“…Another case study describes the development of a PLA for ABB Robotics software [16]. A more recent industrial case study on software product lines in the industrial automation domain has been conducted [17]. From a methodological view, this is complementing our runtime analysis part.…”

Section: Related Workmentioning

confidence: 99%

Analysis of Software Binaries for Reengineering-Driven Product Line Architecture—An Industrial Case Study

Peake

Blech

Fernando

et al. 2015

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

This paper describes a method for the recovering of software architectures from a set of similar (but unrelated) software products in binary form. One intention is to drive refactoring into software product lines and combine architecture recovery with run time binary analysis and existing clustering methods. Using our runtime binary analysis, we create graphs that capture the dependencies between different software parts. These are clustered into smaller component graphs, that group software parts with high interactions into larger entities. The component graphs serve as a basis for further software product line work. In this paper, we concentrate on the analysis part of the method and the graph clustering. We apply the graph clustering method to a real application in the context of automation / robot configuration software tools.

show abstract

“…Although architectural elements were examined, further grain size was not analyzed. Koziolek et al [16] reported examining re-availability from both the architecture and the domain. They described a highly abstract architecture drawn from interviews with architects and used the architecture for rebuilding.…”

Section: Stoermer and O'brienmentioning

confidence: 99%

Experiences with commonality control procedures to develop clinical instrument system

Kodama

Shimabukuro

Takagi

et al. 2014

Proceedings of the 18th International Software Product Line Conference - Volume 1

View full text Add to dashboard Cite

This paper reports our experience with software development based on the Software Product Line (SPL) approach employed for Clinical Instrument Integration Management Software (CIIMS). CIIMS is the system software which systemizes heterogeneous clinical instruments. These instruments require their particular management so that various parts of CIIMS are forced to be changed. This makes it difficult to create development plans to connect new instruments to CIIMS. In this paper we summarize a new estimate method called the Architecture Domain Matrix (ADM) method which effectively solved this problem in our experience. In ADM each architectural element is further decomposed into clinical operation flow elements and core assets of software are extracted from these elements. This method estimates the CIIMS commonality with precision and finally enables to successfully connect new instruments. In addition this method provides a Work Breakdown Structure (WBS) and supports development team building. WBS is generated by collecting all the changes for each operational flow element. A development team suitable for change is organized by taking into consideration all the changes for each architecture element. We integrated three different instruments into CIIMS in 18 months after applying this method to a real project and achieved 2.5 times greater productivity with the embedded software than that with our previous non-SPL process.

show abstract

Experiences from identifying software reuse opportunities by domain analysis

Cited by 10 publications

References 13 publications

A Method Based on Naming Similarity to Identify Reuse Opportunities

A Method Based on Naming Similarity to Identify Reuse Opportunities

Analysis of Software Binaries for Reengineering-Driven Product Line Architecture—An Industrial Case Study

Experiences with commonality control procedures to develop clinical instrument system

Contact Info

Product

Resources

About