An exploratory study of the standard reuse practice in a medium sized software development firm

Barros-Justo, José L.; Olivieri, David N.; Pinciroli, Fernando

doi:10.1016/j.csi.2018.06.005

Cited by 11 publications

(9 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…or "influence factors", among others [12,23,35,36,37,38,39,40,41,42], [24,25,27,28,30,31,32,33]. Some of these factors were selected and used to answer SQ1.…”

Section: Resultsmentioning

confidence: 99%

“…Mistrust of reusable artifacts [50] Software developer's resistance [50] Lack of skills [50] Resistance to systematic reuse [49] Organizational Lack of quantitative measures to assess the benefits and costs [49] Lack of an autonomous reuse group [49] Lack of incentives [12,49] Lack of reuse policies to govern the creation of reusable assets [49] Lack of software quality [49] Lack of an educational and training program or a mentoring [41,49] Large size of the industry [50] Technical Lack of adoption of existing requirements reuse proposals [42] Lack of available components [36] Lack of stable standards for component technology [36] Lack of certified components [36] Lack of a technology that supports reuse [49] Lack of complete and reliable components [36,41] Lack of information on the availability of reusable assets [49] Lack of assets management [49] Incompatibility with traditional methodology [49] Difficulty to locate reusable assets [49] Lack of a well-organized and indexed software repository [41,49]…”

Section: Categories Barrier Referencesmentioning

confidence: 99%

“…The ad-hoc reuse is characterized by the lack of procedures and is opposed to systematic reuse, where software reuse is planned [7]. The effective implementation of software reuse faces technical and non-technical inhibitors [8,9] such as lack of comprehensively reuse-oriented CASE tools, lack of model-level component libraries ready for use across platforms, immaturity of methodologies that integrate multiple reuse techniques, immaturity of standard languages to support model-level reuse, immaturity of a distributed architecture for the publication of third-party components, difficulties in locating and accessing components, fierce competition from the software industry, leading to an obsession with time-to-market of next product or product release, reuse ROI (Return On Investment) is only in the long term, cost of delay almost impossible to estimate accurately, reuse requires costly software house organization re-engineering, changing team structures, productivity measures oriented to the number of lines of source code written, design for reuse and design from existing assets heavily under-taught, developers with hard-to-find reuse skills, "Not invented here" syndrome [10], hacker mentality, resistance to change habits and lack of business models for component asset suppliers [8,11,12,13,14]. This paper presents a literature review in which we adopt some elements from a Systematic Mapping Study (SMS) to determine which factors influence the success of software reuse.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Factores de éxito y barreras de adopción en la reutilización de software: Una revisión de la literatura

Gutierrez

Monsalve

Mazo

et al. 2021

Investigación e Innovación en Ingenierías

View full text Add to dashboard Cite

Objetivo: Conocer el estado del arte de la reutilización de software, centrándose en sus factores de éxito y barreras de adopción. Metodología: Para alcanzarlo realizamos una revisión de la literatura en la cual adoptamos algunos elementos de un estudio de mapeo sistemático. Esta revisión de la literatura constó de cinco etapas (i) definición de las preguntas de investigación, (ii) definición de la estrategia de búsqueda, (iii) definición de los criterios de inclusión/exclusión, (iv) realización de la búsqueda y, finalmente, (v) resolución de las preguntas. Resultados: El trabajo recopila veintiséis factores que influyen en la reutilización del software y las barreras de adopción encontradas en la literatura. Estos factores se clasificaron en cuatro perspectivas: factores organizativos, factores empresariales, factores tecnológicos y factores de proceso. Conclusiones: Los factores resultantes podrían utilizarse para introducir prácticas de reutilización de software y conocer el estado actual de la reutilización de software en las empresas. Asimismo, los factores resultantes podrían aplicarse en la industria del software para conocer su estado actual de práctica.

show abstract

“…or "influence factors", among others [12,23,35,36,37,38,39,40,41,42], [24,25,27,28,30,31,32,33]. Some of these factors were selected and used to answer SQ1.…”

Section: Resultsmentioning

confidence: 99%

Section: Categories Barrier Referencesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Factores de éxito y barreras de adopción en la reutilización de software: Una revisión de la literatura

Gutierrez

Monsalve

Mazo

et al. 2021

Investigación e Innovación en Ingenierías

View full text Add to dashboard Cite

show abstract

“…The areas of Reuse and Software Product Lines (SPL) also obtain advantages when adopting Use Cases [48].…”

Section: Resultsmentioning

confidence: 99%

“…The areas of Reuse and Software Product Lines (SPL) also obtain advantages when adopting Use Cases [48]. Use Cases are able to describe the common characteristics of all the products belonging to a product line and the variations that differentiate them [SP13 and SP38].…”

Section: 1mentioning

confidence: 99%

The impact of Use Cases in real-world software development projects: A systematic mapping study

Barros-Justo

Benitti

Tiwari

2019

Computer Standards & Interfaces

Self Cite

View full text Add to dashboard Cite

Context: There is abundant literature on the application of UML Use Cases. However, the impact that these applications have had on real projects (in industry) is not well known. It is necessary to know what the impact of the Use Cases really is, so that both, researchers and professionals can make the most pertinent decisions.Objective: To identify and classify the positive and negative impacts of using Use Cases in real-world settings. Method:We conducted a systematic mapping study. The search strategies retrieved a set of 4,431 papers out of which 47 were selected as primary studies. We defined four facets to classify these studies: 1) the positive impact (advantages), 2) the negative impact (disadvantages), 3) the industry's domain and 4) the type of research reported. Results:Our study identified eight categories of advantages related to the application of Use Cases. The most mentioned were estimation, analysis and automation. These advantages had a heterogeneous distribution along the years. On the other hand, the granularity of the scenarios described in the Use Cases, the lack of a standardized format for specifying requirements, and the lack of appropriate guidelines for analysing them were the most mentioned disadvantages. We identified a variety of industry domains, grouped into seven categories. As we can expect most of the papers report experiences in the Information Technology domain, followed by financials applications. Almost half the papers applied evaluation research, including an empirical validation. Only one third of the analysed papers reported threats to validity, the most mentioned being generalizability (38%). Conclusions:Use Cases have proven to be a useful tool in software development, particularly during the early stages. The positive effects far outweigh the few negative effects reported, although this may be due to the researchers' tendency of not reporting negative results.

show abstract

Large scale reuse of microservices using CI/CD and InnerSource practices - a case study

Badampudi,

Usman,

Chen

2024

Empir Software Eng

View full text Add to dashboard Cite

Contemporary practices such as InnerSource (adopting open source practices within an organization), continuous integration and delivery (CI/CD), and the use of microservices promote software reuse. Although the benefits of individual contemporary practices on reuse may be known, the implications of collective contemporary practices, mainly challenges and improvements to mitigate the challenges, are to a large extent unknown. In this study, we investigate the additional effort (cost factors), benefits, challenges, and potential improvements in contemporary reuse at Ericsson. We performed the study in two phases: a) the initial data collection based on a combination of data collection methods (e.g., interviews, discussions, company portals), and b) a follow-up group discussion after a year to understand the status of the challenges and improvements identified in the first phase. Our results indicate that developing reusable assets resulted in upfront cost factors, such as additional effort in ensuring compliance. Furthermore, development with reuse also resulted in cost factors, for example, additional effort in integrating and understanding reusable assets. Ericsson perceived the cost factors as an investment resulting in long-term benefits such as improved quality, productivity, customer experience, and way of working. The main challenge faced by Ericsson was the pressure on the producers of reusable assets. Our study shows how InnerSource can lead to an increase in contributions to reusable assets. Furthermore, Ericsson implemented measures like automating compliance checks that improved the maturity of reusable assets, resulting in an increase in their reuse. In summary, effective use of contemporary practices such as InnerSource and CI/CD, along with the use of microservices, can facilitate large scale reuse.

show abstract

An exploratory study of the standard reuse practice in a medium sized software development firm

Cited by 11 publications

References 8 publications

Factores de éxito y barreras de adopción en la reutilización de software: Una revisión de la literatura

Factores de éxito y barreras de adopción en la reutilización de software: Una revisión de la literatura

The impact of Use Cases in real-world software development projects: A systematic mapping study

Large scale reuse of microservices using CI/CD and InnerSource practices - a case study

Contact Info

Product

Resources

About