Experiences with commonality control procedures to develop clinical instrument system

Kodama, Ryuichiro; Shimabukuro, Jun; Takagi, Yoshimitsu; Koizumi, Shinobu; Tano, Shun’ichi

doi:10.1145/2648511.2648540

Cited by 4 publications

(1 citation statement)

References 9 publications

(9 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The success was associated with Testo's ability to develop more complex products, and the increase in the satisfaction of the developers involved in the project. Another interesting experience, from Hitachi, is reported in [S33][64] by Kodama et al The authors describe an estimation method for the integration of heterogeneous clinical instruments in the CIIMS system (Clinical Instrument Integration Management Software). The method estimates commonality with precision, and allows the integration of new instruments into the system through an SPL process.…”

mentioning

confidence: 99%

What software reuse benefits have been transferred to the industry? A systematic mapping study

Barros-Justo

Pinciroli

Matalonga

et al. 2018

Information and Software Technology

View full text Add to dashboard Cite

Context: The term software reuse was first used in 1968 at the NATO conference. Since then, work in the scientific literature have stated that the application of software reuse offers benefits such as increase in quality and productivity. Nonetheless, in spite of many publications reporting software reuse experiences, evidence that such benefits having reached industrial settings is scarce. Objective: To identify and classify the benefits transferred to real-world settings by the application of software reuse strategies. Method: We conducted a systematic mapping study (SMS). Our search strategies retrieved a set of 2,413 papers out of which 49 were selected as primary studies. We defined five facets to classify these studies: a) the type of benefit, b) the reuse process, c) the industry's domain, d) the type of reuse and e) the type of research reported. Results: Quality increase (28 papers) and Productivity increase (25 papers) were the two most mentioned benefits. Component-Based Development (CBD) was the most reported reuse strategy (41%), followed by Software Product Lines (SPL, 30%). The selected papers mentioned fourteen industrial domains, of which four stand out: aerospace and defense, telecommunications, electronics and IT services. The application of systematic reuse was reported in 78% of the papers. Regarding the research type, 50% use evaluation research as the investigation method. Finally, 13 papers (27%) reported validity threats for the research method applied. Conclusions: The literature analyzed presents a lack of empirical data, making it difficult to evaluate the effective transfer of benefits to the industry. This work did not find any relationship between the reported benefits and the reuse strategy applied by the industry or the industry domain. Although the most reported research method was industrial case studies (25 works), half of these works (12) did not report threats to validity.

show abstract

mentioning

confidence: 99%

What software reuse benefits have been transferred to the industry? A systematic mapping study

Barros-Justo

Pinciroli

Matalonga

et al. 2018

Information and Software Technology

View full text Add to dashboard Cite

show abstract

Visualizing the customization endeavor in product-based-evolving software product lines: a case of action design research

et al. 2022

View full text Add to dashboard Cite

Software Product Lines (SPLs) aim at systematically reusing software assets, and deriving products (a.k.a., variants) out of those assets. However, it is not always possible to handle SPL evolution directly through these reusable assets. Time-to-market pressure, expedited bug fixes, or product specifics lead to the evolution to first happen at the product level, and to be later merged back into the SPL platform where the core assets reside. This is referred to as product-based evolution. In this scenario, deciding when and what should go into the next SPL release is far from trivial. Distinct questions arise. How much effort are developers spending on product customization? Which are the most customized core assets? To which extent is the core asset code being reused for a given product? We refer to this endeavor as Customization Analysis, i.e., understanding the functional increments in adjusting products from the last SPL platform release. The scale of the SPLs’ code-base calls for customization analysis to be conducted through Visual Analytics tools. This work addresses the design principles for such tools through a joint effort between academia and industry, specifically, Danfoss Drives, a company division in charge of the P400 SPL. Accordingly, we adopt an Action Design Research approach where answers are sought by interacting with the practitioners in the studied situations. We contribute by providing informed goals for customization analysis as well as an intervention in terms of a visual analytics tool. We conclude by discussing to what extent this experience can be generalized to product-based evolving SPL organizations other than Danfoss Drives.

show abstract

Understanding and evaluating software reuse costs and benefits from industrial cases—A systematic literature review

Chen,

Usman,

Badampudi

2024

Information and Software Technology

View full text Add to dashboard Cite

Experiences with commonality control procedures to develop clinical instrument system

Cited by 4 publications

References 9 publications

What software reuse benefits have been transferred to the industry? A systematic mapping study

What software reuse benefits have been transferred to the industry? A systematic mapping study

Visualizing the customization endeavor in product-based-evolving software product lines: a case of action design research

Understanding and evaluating software reuse costs and benefits from industrial cases—A systematic literature review

Contact Info

Product

Resources

About