An Integrated Requirements Engineering Framework for Agile Software Product Lines

2019 ◽  
pp. 124-149
Author(s):  
Hassan Haidar ◽  
Manuel Kolp ◽  
Yves Wautelet
Keyword(s):  
Requirements Engineering ◽  
Software Product Lines ◽  
Product Lines ◽  
Software Product ◽  
Agile Software

A Security Requirements Engineering Tool for Domain Engineering in Software Product Lines

2011 ◽  
pp. 73-92
Author(s):  
Jesús Rodríguez ◽  
Eduardo Fernández-Medina ◽  
Mario Piattini ◽  
Daniel Mellado
Keyword(s):  
Requirements Engineering ◽  
Software Product Lines ◽  
Product Line ◽  
Security Requirements ◽  
Engineering Process ◽  
Product Lines ◽  
Requirements Engineering Process ◽  
Security Requirements Engineering ◽  
Software Product ◽  
Automated Support

The concepts of Service-Oriented Architectures and Software Product Lines are currently being paid a considerable amount of attention, both in research and in practice. Both disciplines promise to make the development of flexible, cost-effective software systems possible and to support high levels of reuse, and may sometimes be complementary to each other. In both paradigms, security is a critical issue, although most of the existing product line practices do not comprise all the security requirements engineering activities or provide automated support through which to perform these activities, despite the fact that it is widely accepted that the application of any requirements engineering process or methodology is much more difficult without a CARE (Computer-Aided Requirements Engineering) tool, since it must be performed manually. Therefore, this chapter shall present a tool denominated as SREPPLineTool, which provides automated support through which to facilitate the application of the security quality requirements engineering process for software product lines, SREPPLine. SREPPLineTool simplifies the management of security requirements in product lines by providing us with a guided, systematic and intuitive manner in which to deal with them from the early stages of product line development, thus simplifying the management and the visualization of artefact variability and traceability links and the integration of security standards, along with the management of the security reference model proposed by SREPPLine.

scholarly journals Secure Tropos framework for software product lines requirements engineering

2014 ◽  
Vol 36 (4) ◽  
pp. 711-722 ◽  
Author(s):  
Daniel Mellado ◽  
Haralambos Mouratidis ◽  
Eduardo Fernández-Medina
Keyword(s):  
Requirements Engineering ◽  
Software Product Lines ◽  
Product Lines ◽  
Software Product

scholarly journals Value-Oriented Requirements: Eliciting Domain Requirements from Social Network Services to Evolve Software Product Lines

2019 ◽  
Vol 9 (19) ◽  
pp. 3944 ◽  
Author(s):  
Ali ◽  
Hong
Keyword(s):  
Social Network ◽  
Software Development ◽  
Requirements Engineering ◽  
Software Product Lines ◽  
End Users ◽  
Network Services ◽  
Product Lines ◽  
Development Organizations ◽  
Software Product ◽  
Social Network Services

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.

Sign in / Sign up

Export Citation Format

Share Document