Research of the Software Aging Regeneration Strategy Based on Components

2DCBS: A Model for Developing Dependable Component-Based Software

“…Moreover, common parts may be written once and then reused many times rather than be written over and over again [1]. At the same time, CBSD offers a range of benefits, from enhancing an individual programmer's productivity to analyzing the costs of the developed software effectively [2][3][4][5]. The widespread and systematic reuse of software can meet the demands for accelerated delivery, reduced software production and maintenance costs, and improved quality.…”

2DCBS: A Model for Developing Dependable Component-Based Software

“…Moreover, common parts may be written once and then reused many times rather than be written over and over again [1]. At the same time, CBSD offers a range of benefits, from enhancing an individual programmer's productivity to analyzing the costs of the developed software effectively [2][3][4][5]. The widespread and systematic reuse of software can meet the demands for accelerated delivery, reduced software production and maintenance costs, and improved quality.…”

Awareness of Embedding Security Features Into Component-Based Software Development Model: A Survey

“…The idea is to assemble software applications from reusable software codes, thereby simplifying software development in terms of time and budget constraints. CBSD offers a range of benefits, such as managing increasing complexity (Chen et al, 2011;Kumari and Bhasin, 2011;Sozer et al, 2011), improving the capability to reuse components (Lin, 2007;Fredriksson, 2008;Carvalho et al, 2009;Li et al, 2011), improving efficiency (Salmi and Ioualalen, 2012;Yang et al, 2012;Chen et al, 2012), decreasing the time and effort needed to develop software (Alhazbi and Jantan, 2007;Kaur et al, 2007;Ahmed et al, 2012), improving the quality of the system (Capretz, 2005;Mohanty et al, 2011), reducing production costs through software reuse (Chen et al, 2012;Barnawi et al, 2012), reducing maintenance costs (Li et al, 2011;Sommerville, 2011), increasing development productivity (Barnawi et al, 2012;Aris and Salim, 2007;Shang et al, 2011), ensuring a greater degree of consistency (Crnkovic, 2003;Ganguly and Bhattacharyya, 2011;Brada, 2011), providing a wider range of usability (Selvi et al, 2008;Jun et al, 2012) and supporting the effective use of specialists (Sommerville, 2011;Cann et al, 2004;Kaur and Mann, 2010). However, despite the wide adoption of CBSD in the software industry and the tremendous number of publications about it in academic research, CBSD still lacks essential formal foundations for the specification, composition and verification of security requirements.…”

2DCBS: A Model for Developing Dependable Component-Based Software

“…Moreover, common parts may be written once and then reused many times rather than be written over and over again [1]. At the same time, CBSD offers a range of benefits, from enhancing an individual programmer's productivity to analyzing the costs of the developed software effectively [2][3][4][5]. The widespread and systematic reuse of software can meet the demands for accelerated delivery, reduced software production and maintenance costs, and improved quality.…”

Awareness of Embedding Security Features Into Component-Based Software Development Model: A Survey

“…The idea is to assemble software applications from reusable software codes, thereby simplifying software development in terms of time and budget constraints. CBSD offers a range of benefits, such as managing increasing complexity (Chen et al, 2011;Kumari and Bhasin, 2011;Sozer et al, 2011), improving the capability to reuse components (Lin, 2007;Fredriksson, 2008;Carvalho et al, 2009;Li et al, 2011), improving efficiency (Salmi and Ioualalen, 2012;Yang et al, 2012;Chen et al, 2012), decreasing the time and effort needed to develop software (Alhazbi and Jantan, 2007;Kaur et al, 2007;Ahmed et al, 2012), improving the quality of the system (Capretz, 2005;Mohanty et al, 2011), reducing production costs through software reuse (Chen et al, 2012;Barnawi et al, 2012), reducing maintenance costs (Li et al, 2011;Sommerville, 2011), increasing development productivity (Barnawi et al, 2012;Aris and Salim, 2007;Shang et al, 2011), ensuring a greater degree of consistency (Crnkovic, 2003;Ganguly and Bhattacharyya, 2011;Brada, 2011), providing a wider range of usability (Selvi et al, 2008;Jun et al, 2012) and supporting the effective use of specialists (Sommerville, 2011;Cann et al, 2004;Kaur and Mann, 2010). However, despite the wide adoption of CBSD in the software industry and the tremendous number of publications about it in academic research, CBSD still lacks essential formal foundations for the specification, composition and verification of security requirements.…”

2DCBS: A Model for Developing Dependable Component-Based Software

“…Moreover, common parts may be written once and then reused many times rather than be written over and over again [1]. At the same time, CBSD offers a range of benefits, from enhancing an individual programmer's productivity to analyzing the costs of the developed software effectively [2][3][4][5]. The widespread and systematic reuse of software can meet the demands for accelerated delivery, reduced software production and maintenance costs, and improved quality.…”

Awareness of Embedding Security Features Into Component-Based Software Development Model: A Survey

“…The idea is to assemble software applications from reusable software codes, thereby simplifying software development in terms of time and budget constraints. CBSD offers a range of benefits, such as managing increasing complexity (Chen et al, 2011;Kumari and Bhasin, 2011;Sozer et al, 2011), improving the capability to reuse components (Lin, 2007;Fredriksson, 2008;Carvalho et al, 2009;Li et al, 2011), improving efficiency (Salmi and Ioualalen, 2012;Yang et al, 2012;Chen et al, 2012), decreasing the time and effort needed to develop software (Alhazbi and Jantan, 2007;Kaur et al, 2007;Ahmed et al, 2012), improving the quality of the system (Capretz, 2005;Mohanty et al, 2011), reducing production costs through software reuse (Chen et al, 2012;Barnawi et al, 2012), reducing maintenance costs (Li et al, 2011;Sommerville, 2011), increasing development productivity (Barnawi et al, 2012;Aris and Salim, 2007;Shang et al, 2011), ensuring a greater degree of consistency (Crnkovic, 2003;Ganguly and Bhattacharyya, 2011;Brada, 2011), providing a wider range of usability (Selvi et al, 2008;Jun et al, 2012) and supporting the effective use of specialists (Sommerville, 2011;Cann et al, 2004;Kaur and Mann, 2010). However, despite the wide adoption of CBSD in the software industry and the tremendous number of publications about it in academic research, CBSD still lacks essential formal foundations for the specification, composition and verification of security requirements.…”