Validation of RP-SPF framework: a systematic method for requirements reuse in software product lines

Reuse of requirements is crucial activity in software development especially across software product line engineering (SPLE), which involves two main processes known as domain engineering and application engineering. With these two processes SPLE enables systematic reuse of requirements through proper planning and development. This paper presents methodology and result of survey of experts for validating a proposed systematic requirement reuse approach named requirements pattern for software product families (RP-SPF) framework. During the survey, 14 experts in requirements engineering (RE), SPLE and software development responded and gave their opinions on RP-SPF framework. The result of the survey shows that RP-SPF approach is suitable and can effectively improve requirements engineering activities of SPLE. © BEIESP

Code Reuse in Open Source Software Development: Quantitative Evidence, Drivers, and Impediments

The focus of existing open source software (OSS) research has been on how and why individuals and firms add to the commons of public OSS code—that is, on the “giving” side of this open innovation process. In contrast, research on the corresponding “receiving” side of the innovation process is scarce. We address this gap, studying how existing OSS code is reused and serves as an input to further OSS development. Our findings are based on a survey with 686 responses from OSS developers. As the most interesting results, our multivariate analyses of developers’ code reuse behavior point out that developers with larger personal networks within the OSS community and those who have experience in a greater number of OSS projects reuse more, presumably because both network size and a broad project experience facilitate local search for reusable artifacts. Moreover, we find that a development paradigm that calls for releasing an initial functioning version of the software early—as the “credible promise” in OSS—leads to increased reuse. Finally, we identify developers’ interest in tackling difficult technical challenges as detrimental to efficient reuse-based innovation. Beyond OSS, we discuss the relevance of our findings for companies developing software and for the receiving side of open innovation processes, in general

Requirements reuse and requirement patterns: a state of the practice survey

Context. Requirements engineering is a discipline with numerous challenges to overcome. One of these challenges is the implementation of requirements reuse approaches. Although several theoretical proposals exist, little is known about the practices that are currently adopted in industry. Objective. Our goal is to contribute to the investigation of the state of the practice in the reuse of requirements, eliciting current practices from practitioners, and their opinions whenever appropriate. Besides reuse in general, we focus on requirement patterns as a particular strategy to reuse. Method. We conducted an exploratory survey based on an online questionnaire. We received 71 responses from requirements engineers with industrial experience in the field, which were analyzed in order to derive observations. Results. Although we found that a high majority of respondents declared some level of reuse in their projects (in particular, non-functional requirements were identified as the most similar and recurrent among projects), it is true that only a minority of them declared such reuse as a regular practice. Larger IT organizations and IT organizations with well-established software processes and methods present higher levels of reuse. Ignorance of reuse techniques and processes is the main reason preventing wider adoption. From the different existing reuse techniques, the simplest ones based on textual copy and subsequent tailoring of former requirements are the most adopted techniques. However, participants who apply reuse more often tend to use more elaborate techniques. Opinions of respondents about the use of requirement patterns show that they can be expected to mitigate problems related to the quality of the resulting requirements, such as lack of uniformity, inconsistency, or ambiguity. The main reasons behind the lack of adoption of requirement patterns by practitioners (in spite of the increasing research approaches proposed in the community) are related to the lack of a well-defined reuse method and involvement of requirement engineers.Peer ReviewedPostprint (author's final draft

End-user acceptability of personal protective equipment disinfection for potential reuse: a survey of health-care workers in Aotearoa New Zealand

Background The COVID-19 pandemic has highlighted personal protective equipment (PPE) supply, distribution, and disposal issues worldwide. Calls to conserve PPE stocks and increase supply resulted in the rapid development of potential disinfection methods, with the possibility of improvements in medical waste reduction. However, how receptive health-care workers are to PPE reuse remains unknown. We aimed to examine the views of health-care workers who used PPE during the first COVID-19 wave in Aotearoa New Zealand, in relation to acceptability of PPE disinfection and reuse. Methods In this multi-methods survey, health-care workers in New Zealand, were invited via a multimodal recruitment strategy to complete a survey regarding use of PPE during the first COVID-19 wave. Gender question options were male, female, gender diverse, or prefer not to say. Demographic differences in self-reported PPE reuse and acceptability were examined. The survey included closed (single-response, multi-response, ranking, and Likert-scale questions) and open-text questions. Any open-text comments were analysed with thematic analysis. The survey was built and deployed using Qualtrics software. Findings 1411 health-care workers completed the survey between Oct 7 and Nov 30, 2020. 1397 participants had gender data available (1140 [82%] female and 257 [18%] male) and 995 (74%) of 1347 were of New Zealand European ethnicity. PPE reuse was common and reported by 628 (45%) of the 1411 participants, with 396 (63%) of the 628 reporting reusing PPE multiple times in 1 day. Acceptability of the concept of PPE disinfection for potential reuse was high overall (1196 [85%] of 1411) but varied depending on the type of PPE. Thematic analysis confirmed that PPE reuse was already occurring and respondents recognised the potential benefits of reduced medical wastage and increased PPE supply. Important caveats for consideration included the availability of scientific evidence, level of negotiated risk, and trust in the organisation undertaking PPE disinfection, with clear communication about decontamination processes being crucial to acceptability. Interpretation PPE reuse occurred frequently during the first wave of COVID-19 in New Zealand. Although support for the disinfection of PPE for reuse was high, the success of any future programmes to reuse PPE will require meaningful engagement and clear communication with health-care workers. Further research into PPE disinfection safety and logistics is warranted, alongside the development of standard operating procedures and clearly communicated policies for the end user, should this more sustainable health-care practice be planned for adoption in certain settings. Funding New Zealand Ministry of Business, Innovation and Employment (COVID-19 Innovation Acceleration Fund) and the Medical Assurance Society Foundation

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version

A concept of water usage efficiency to support water reduction in manufacturing industry

Increasing pressures on freshwater supplies, continuity of supply uncertainties, and costs linked to legislative compliance, such as for wastewater treatment, are driving water use reduction up the agenda of manufacturing businesses. A survey is presented of current analysis methods and tools generally available to industry to analyze environmental impact of, and to manage, water use. These include life cycle analysis, water footprinting, strategic planning, water auditing, and process integration. It is identified that the methods surveyed do not provide insight into the operational requirements from individual process steps for water, instead taking such requirements as a given. We argue that such understanding is required for a proactive approach to long-term water usage reduction, in which sustainability is taken into account at the design stage for both process and product. As a first step to achieving this, we propose a concept of water usage efficiency which can be used to evaluate current and proposed processes and products. Three measures of efficiency are defined, supported by a framework of a detailed categorization and representation of water flows within a production system. The calculation of the efficiency measures is illustrated using the example of a tomato sauce production line. Finally, the elements required to create a useable tool based on the efficiency measures are discussed

ICOPER Project - Deliverable 4.3 ISURE: Recommendations for extending effective reuse, embodied in the ICOPER CD&R

The purpose of this document is to capture the ideas and recommendations, within and beyond the ICOPER community, concerning the reuse of learning content, including appropriate methodologies as well as established strategies for remixing and repurposing reusable resources. The overall remit of this work focuses on describing the key issues that are related to extending effective reuse embodied in such materials. The objective of this investigation, is to support the reuse of learning content whilst considering how it could be originally created and then adapted with that ‘reuse’ in mind. In these circumstances a survey on effective reuse best practices can often provide an insight into the main challenges and benefits involved in the process of creating, remixing and repurposing what we are now designating as Reusable Learning Content (RLC). Several key issues are analysed in this report: Recommendations for extending effective reuse, building upon those described in the previous related deliverables 4.1 Content Development Methodologies and 4.2 Quality Control and Web 2.0 technologies. The findings of this current survey, however, provide further recommendations and strategies for using and developing this reusable learning content. In the spirit of ‘reuse’, this work also aims to serve as a foundation for the many different stakeholders and users within, and beyond, the ICOPER community who are interested in reusing learning resources. This report analyses a variety of information. Evidence has been gathered from a qualitative survey that has focused on the technical and pedagogical recommendations suggested by a Special Interest Group (SIG) on the most innovative practices with respect to new media content authors (for content authoring or modification) and course designers (for unit creation). This extended community includes a wider collection of OER specialists. This collected evidence, in the form of video and audio interviews, has also been represented as multimedia assets potentially helpful for learning and useful as learning content in the New Media Space (See section 4 for further details). Section 2 of this report introduces the concept of reusable learning content and reusability. Section 3 discusses an application created by the ICOPER community to enhance the opportunities for developing reusable content. Section 4 of this report provides an overview of the methodology used for the qualitative survey. Section 5 presents a summary of thematic findings. Section 6 highlights a list of recommendations for effective reuse of educational content, which were derived from thematic analysis described in Appendix A. Finally, section 7 summarises the key outcomes of this work

Reusability in software engineering

This paper surveys recent work concerning reusability in software engineering. The current directions in software reusability are discussed, and the two major approaches of reusable building blocks and reusable patterns studied. An extensive bibliography, parts of which are annotated, is included

Selection of third party software in Off-The-Shelf-based software development: an interview study with industrial practitioners

The success of software development using third party components highly depends on the ability to select a suitable component for the intended application. The evidence shows that there is limited knowledge about current industrial OTS selection practices. As a result, there is often a gap between theory and practice, and the proposed methods for supporting selection are rarely adopted in the industrial practice. This paper's goal is to investigate the actual industrial practice of component selection in order to provide an initial empirical basis that allows the reconciliation of research and industrial endeavors. The study consisted of semi-structured interviews with 23 employees from 20 different software-intensive companies that mostly develop web information system applications. It provides qualitative information that help to further understand these practices, and emphasize some aspects that have been overlooked by researchers. For instance, although the literature claims that component repositories are important for locating reusable components; these are hardly used in industrial practice. Instead, other resources that have not received considerable attention are used with this aim. Practices and potential market niches for software-intensive companies have been also identified. The results are valuable from both the research and the industrial perspectives as they provide a basis for formulating well-substantiated hypotheses and more effective improvement strategies.Peer ReviewedPostprint (author's final draft