2016iJARS International Journal of EngineeringRequires access

Software Reuse Knowledge Map

Mohamed E. Fayad, Charles A. Flood

Open publisher page 0 citations

Abstract

The term Software Reuse can be defined as a process of developing software systems from existing ones, instead of creating them from scratch [2, 3, 4, 5]. In many software engineering disciplines, systems are designed by recomposing existing software components that have been used in other systems. It has become a topic of renewed interest in the software community because of its potential benefits, which include increased product quality, decreased product cost and schedule. Software is rarely built completely from scratch. To a great extent, existing software documents (source code, design documents, etc.) are copied and adapted to fit new requirements. Software engineering is focused more on original development. However, it is now recognized that to create better software in a time efficient and cost effective way, we may need to adopt a design process that is based on systematic software reuse factors. This paper aims at applying Software Stability Model (SSM) approach towards creating a model for Unified Software Reuse that is applicable in all scenarios and diverse domains. The software stability notion ensures high reuse ability, stability and a more design efficient model, which is domain independent too. The key contribution of this Paper is to present an idea of having a stable analysis pattern listing the Enduring business themes (EBTs) and Business Objectives (BOs) involved in the area of Unified Software Reuse. Such a generic model can further be applied to any possible scenario. .

About this research paper

What this paper is about

The term Software Reuse can be defined as a process of developing software systems from existing ones, instead of creating them from scratch [2, 3, 4, 5]. In many software engineering disciplines, systems are designed by recomposing existing software components that have been used in other systems. It has become a topic of renewed interest in the software community because of its potential benefits, which include increased product quality, decreased product cost and schedule. Software is rarely built completely from scratch. To a great extent, existing software documents (source code, design documents, etc.) are copied and adapted to fit new requirements. Software engineering is focused more on original development. However, it is now recognized that to create better software in a time efficient and cost effective way, we may need to adopt a design process that is based on systematic software reuse factors. This paper aims at applying Software Stability Model (SSM) approach towards creating a model for Unified Software Reuse that is applicable in all scenarios and diverse domains. The software stability notion ensures high reuse ability, stability and a more design efficient model, which is domain independent too. The key contribution of this Paper is to present an idea of having a stable analysis pattern listing the Enduring business themes (EBTs) and Business Objectives (BOs) involved in the area of Unified Software Reuse. Such a generic model can further be applied to any possible scenario. .

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The term Software Reuse can be defined as a process of developing software systems from existing ones, instead of creating them from scratch [2, 3, 4, 5]. In many software engineering disciplines, systems are designed by recomposing existing software components that have been used in other systems. It has become a topic of renewed interest in the software community because of its potential benefits, which include increased product quality, decreased product cost and schedule. Software is rarely built completely from scratch. To a great extent, existing software documents (source code, design documents, etc.) are copied and adapted to fit new requirements. Software engineering is focused more on original development. However, it is now recognized that to create better software in a time efficient and cost effective way, we may need to adopt a design process that is based on systematic software reuse factors. This paper aims at applying Software Stability Model (SSM) approach towards creating a model for Unified Software Reuse that is applicable in all scenarios and diverse domains. The software stability notion ensures high reuse ability, stability and a more design efficient model, which is domain independent too. The key contribution of this Paper is to present an idea of having a stable analysis pattern listing the Enduring business themes (EBTs) and Business Objectives (BOs) involved in the area of Unified Software Reuse. Such a generic model can further be applied to any possible scenario. .

Key concepts: Computer science, Software engineering, Software construction, Domain engineering, Software development, Package development process, Social software engineering, Software sizing

Related papers

Back to paper searchBrowse research topicsOriginal source
Software Reuse Knowledge Map — Research Paper | ScholarLens