Reusing Requirements in Global Software Engineering

Gea, Juan Manuel Carrillo de; Nicolás, Joaquín; Alemán, José Luis Fernández; Toval, Ambrosio; Vizcaíno, Aurora; Ebert, Christof

doi:10.1007/978-3-642-34419-0_8

Cited by 19 publications

(6 citation statements)

References 66 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• Process of reuse. Several proposals describe the process for applying requirements reuse, for instance those by Pacheco et al (2015), Carrillo- de-Gea et al (2013), and Renault et al (2009).…”

Section: Background On Requirements Reuse and Patternsmentioning

confidence: 99%

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

2016

View full text Add to dashboard Cite

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. 2 Conclusion. The results of our paper are interesting for practitioners since we highlight relevant observations from the survey participants' experiences when deciding to implement requirements reuse practices. We also suggest future lines of research based on the needs pointed out in the results.

show abstract

Section: Background On Requirements Reuse and Patternsmentioning

confidence: 99%

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

2016

View full text Add to dashboard Cite

show abstract

“…Requirements re-usability is considered as an important technology [ 28 ], speeds up and aids in software development and maintenance processes. Other benefits of reusing requirements are increasing quality, reliability, efficiency, performance and productivity (faster, better, cheaper), minimizing developments and maintenance costs and time, reducing risk of project failures, reducing stress on technical people, and satisfying customers’ needs [ 5 , 9 , 15 , 17 , 32 , 62 ] [ 14 , 44 , 60 , 64 ]. In a study, we have found that, one third errors of software occur from design and code, whereas, 40 to 60% of software errors occur from requirements errors [ 7 ].…”

Section: Discussionmentioning

confidence: 99%

Requirements Re-usability in Global Software Development: A Systematic Mapping Study

Hossain

Arafat

Amin³

et al. 2020

Computational Science and Its Applications – ICCSA 2020

View full text Add to dashboard Cite

In global software development, requirements re-usability is a common practice which ultimately helps to maintain project quality and reduce both development time and cost. However, when a large-scale project is distributed, there are some critical factors needed to be maintained and managed for reusing requirements and it is considered a challenging job to interrelate the requirements between two identical projects. In this study, we have pointed out 48 challenges faced and 43 mitigation techniques used when implementing requirements re-usability in global software development projects among distributed teams. The challenges distributed teams frequently encounter can be divided into three considering issues as Communication, Coordination and Control of distributed teams in global software development. The results from this study can be used to plan development strategies while reusing requirements in distributed manners.

show abstract

“…In another study [ 36 ], knowledge transfer and reuse in the global RE perspective are also examined. Distance between partners and cultural differences have an impact on knowledge exchange.…”

Section: Related Workmentioning

confidence: 99%

Towards dealing with commonly occurring requirements engineering process issues during software development outsourcing

et al. 2022

View full text Add to dashboard Cite

Due to specific advantages, the volume of Software Development Outsourcing (SDO) is rapidly increasing. Because of challenges arising from the Requirements Engineering (RE) process, the anticipated benefits of SDO are not achieved in case of several projects. The objective of this research work is to recommend RE practices for addressing the commonly arising RE process issues in the case of SDO. For this reason, a thorough literature review has been undertaken, as well as two questionnaire surveys have been performed with skilled SDO industry practitioners. The surveys have been done by utilizing semi-supervised style and employing Convenience Sampling method. The 50 percent rule and a four-point Likert Scale have also been used to determine the advantages of RE practices for dealing with the issues. A comprehensive list of 147 RE practices has been extracted by conducting a Focus Group session. Furthermore, the 147 RE practices have been ranked by applying Numerical Assignment and Hundred Dollar Techniques during two Focus Group sessions. The detection and adaptation of RE practices aids in enhancing the SDO RE process, evading SDO failures, and achieving the associated SDO advantages.

show abstract

Reusing Requirements in Global Software Engineering

Cited by 19 publications

References 66 publications

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

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

Requirements Re-usability in Global Software Development: A Systematic Mapping Study

Towards dealing with commonly occurring requirements engineering process issues during software development outsourcing

Contact Info

Product

Resources

About