Abstract

Social network services allow a large population of end-users of software products to publicly share their concerns and experiences about software systems. From a software engineering perspective, such data can be collected and analyzed to help software development organizations to infer users’ emerging demands, receive their feedback, and plan the rapid evolution of software product lines. For the evolution of software product lines, organizations supplement emerging requirements in their products to meet user’s needs and also to retain their dominance in the market. Therefore, social network services, being a communication channel, have supported a number of software development activities such as requirements engineering. It has supported software development organizations to cope with numerous limitations of the traditional requirements engineering approaches by eliciting, prioritizing, and negotiating user requirements. However, these approaches do not consider eliciting requirements in terms of variability and commonality while identifying requirements. To address this issue, we have proposed a social network service-based requirement engineering process. It considers the attributes of users’ opinions to determine variability and commonality. In order to justify our proposed approach, a controlled experiment was conducted on a sample set of end-users on Facebook and Twitter. The experimental results show that the team using the proposed approach performed better in terms of efficiency and effectiveness than the team that used a traditional requirements engineering approach.

Highlights

  • The World is generic and the user demands are rapidly changing as time goes by [1,2]

  • The proposed approach identifies software product line (SPL) requirements effectively and efficiently. This hypothesis is further divided into two: Hypothesis 1a (H1a). μ (Time taken by T1) > μ (Time Taken by T2)

  • Responses products and of end-users improve to their their products products with the improve passage their of time

Read more

Summary

Introduction

The World is generic and the user demands are rapidly changing as time goes by [1,2]. The fundamental factor in the success of a software product line (SPL) is to understand what users really want [1,2]. SPL is a paradigm where applications are derived from core assets which are built in domain engineering [3]. In order to fulfil user requirements, it is necessary for SPL organizations to know the opinions on the products that they have already floated on the market. The opinion may tell about user satisfaction which measures how software product, provided service, and overall user experience.

Objectives
Methods
Findings
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.