Identifying Issues and Concerns in Software Reuse in Software Product Lines

Jha, Meena; O’Brien, Liam

doi:10.1007/978-3-642-04211-9_18

Cited by 10 publications

(20 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The number of requirements for pilot project were 107 and 97 of which have been reused, showing a high proportion of 90.7%. However, as mentioned in [5], the good results as like above can be achieved because most companies develop projects for similar purposes mainly in the same field. However, different results may be obtained if this study has been applied to projects in different fields or for different purposes.…”

Section: Results Of Case Analysismentioning

confidence: 87%

Repository Construction and Reuse of Software Requirement

2019

IJEAT

View full text Add to dashboard Cite

Software reuse is not limited to reusing code used a lot but can be used in all steps and activities related to software production. In particular, the reuse of requirements has various benefits by reusing reliable requirements, and the development of requirements is an early stage of software development and may have higher efficiency than the utilization of reuse in later stages if reuse is utilized from the initial stage. However, despite its many advantages, the study on the reuse of requirements is insufficient. Therefore, to explore the possibility of the requirements reuse, we conducted a total of four stages in this paper: selection of targets and stakeholders, construction of requirements repository, reuse of requirements repository, and result analysis, and a case study of requirements repository construction and reuse was conducted. We have confirmed the fact that the reuse of requirements possible with a high proportion in practice through the application of actual case and we have also confirmed the possibility of research on the reuse of requirements. If we deal with the reliable requirements by increasing the utilization of requirements reuse, the possibility of the project's success will also be greatly increased.

show abstract

Section: Results Of Case Analysismentioning

confidence: 87%

Repository Construction and Reuse of Software Requirement

2019

IJEAT

View full text Add to dashboard Cite

show abstract

“…We identified issues and concerns for software reuse within the SPL community and we also examined if reliability of software assets/components is an issue for reuse in the SPL community. This survey was built upon our previous survey on software reuse in the CSE community [11]. This latter survey was email based and carried out in mid 2008.…”

Section: Related Approachesmentioning

confidence: 99%

A comparison of software reuse in software development communities

Jha

O’Brien

2011

2011 Malaysian Conference in Software Engineering

Self Cite

View full text Add to dashboard Cite

Software reuse has been regarded as one of the most important areas for improving software development productivity and the quality of software. Research and practice has shown that software reuse can be used for developing products from reusable assets in a routine manner, on an industrial scale. However successful application of software reuse is limited to certain domains and not widespread across the software industry. There is no clear consensus between input and, output artifacts and the requirements that an effective reuse process must have. To examine the issues and concerns in more detail we have completed surveys on software reuse in the conventional software engineering (CSE) community and in the software product line (SPL) community to compare and contrast the results for similarities and differences in software reuse philosophy. This paper outlines some of the identified differences and similarities of issues and concerns in software reuse in both communities and what one community can gain from the other to overcome the identified software reuse problems. The comparison highlights areas where the existing SPL and CSE communities provide extensive support in software reuse and those in which the SPL and CSE communities are deficient, suggesting an understanding of the factors resisting software reuse in both communities.

show abstract

“…Projects with different purposes or in different domains might produce a different result. However, most small‐sized and medium‐sized enterprises mainly develop projects with a similar purpose in the same domain actually . Creating and applying small and non‐specific assets …”

Section: Threats To Validity and Limitationmentioning

confidence: 99%

“…However, most small-sized and medium-sized enterprises mainly develop projects with a similar purpose in the same domain actually [13].…”

Section: Threats To Validity and Limitationmentioning

confidence: 99%

EURECA: End‐user requirements engineering with collaborative animation

et al. 2017

View full text Add to dashboard Cite

Summary In recent years, software development environments have changed from being driven by professional developers to being driven by technical end users. One of the key issues in end‐user‐driven software development environments is how to guarantee the quality of the software artifacts. Measuring the quality of developed software requires the correct specification of a quality range the software is expected to meet. However, technical end users are non‐professionals in engineering techniques for software requirements, and training a developer to be an expert in requirements engineering in a short period of time is difficult. This paper proposes a new software development life cycle based on reutilizing previously evaluated software requirements assets from completed projects. End‐User Requirements Engineering with Collaborative Animation, a tool that was developed to support the proposed software development life cycle, is described and demonstrated by application to three projects. The results from real cases are used as the basis for a discussion on the efficiency enhancement of requirements work, an increased rate of reusing legacy software requirements assets, and an improvement in the technical end user's individual competency level using the End‐User Requirements Engineering with Collaborative Animation. Copyright © 2017 John Wiley & Sons, Ltd.

show abstract

Identifying Issues and Concerns in Software Reuse in Software Product Lines

Cited by 10 publications

References 6 publications

Repository Construction and Reuse of Software Requirement

Repository Construction and Reuse of Software Requirement

A comparison of software reuse in software development communities

EURECA: End‐user requirements engineering with collaborative animation

Contact Info

Product

Resources

About