The Experts below are selected from a list of 63768 Experts worldwide ranked by ideXlab platform
David C. Rine - One of the best experts on this subject based on the ideXlab platform.
-
An empirical study of a Software Reuse reference model
Information and Software Technology, 2000Co-Authors: David C. Rine, Nader NadaAbstract:Abstract In Software engineering there is a need for technologies that will significantly decrease effort in developing Software products, increase quality of Software products and decrease time-to-markets. The Software development industry can be improved by utilizing and managing Software Reuse with an “empirically validated reference model” that can be customized for different kinds of Software development enterprises. Our research thesis is that Software development based on a Software Reuse reference model improves the competitive edge and time-to-market of many Software development enterprises. The definition and study of such a model has been carried out using four steps. First, the reference model developed here is based on the existing Software Reuse concepts. Second, this reference model is an empirical study which uses both legacy studies and lessons learned studies. Third, the impact of the reference model on Software development effort, quality, and time-to-market is empirically derived. Fourth, an initial set of successful cases, which are based on the Software Reuse reference model utilization, are identified. The main contribution of this paper is a reference model for the practice of Software Reuse. A secondary contribution is an initial set of cases from Software development enterprises which are successful in the practice of Reuse in terms of decreased effort, increased quality and a high correlation in their application of our Software Reuse reference model activities.
-
investments in reusable Software a study of Software Reuse investment success factors
Journal of Systems and Software, 1998Co-Authors: David C. Rine, Robert Michael SonnemannAbstract:Abstract This research supports the thesis that there is a set of success factors which are common across organizations and have some predictability relationships to Software Reuse. For completeness, this research also investigated to see if Software Reuse had a predictive relationship to productivity and quality. The individual success factors were grouped into the following categories: management commitment, investment strategy, business strategy, technology transfer, organizational structure, process maturity, product-line approach, Software architecture, availability of components, and quality of components. A questionnaire was developed to measure Software Reuse capability, productivity, quality, and the set of Software Reuse success factors. A survey was conducted to determine the state-of-the practice. The data from the survey was statistically analyzed to evaluate the relationships among Reuse capability, productivity, quality, and the individual Software Reuse success factors. The results of the analysis showed some of the success factors to have a predictive relationship to Software Reuse capability. Software Reuse capability also had a predictive relationship to productivity and quality. Based on the research results, the leading indicators of Software Reuse capability are: product-line approach, architecture which standardizes interfaces and data formats, common Software architecture across the product-line, design for manufacturing approach, domain engineering, management which understands Reuse issues, Software Reuse advocate(s) in senior management, state-of-the-art tools and methods, precedence of reusing high level Software artifacts such as requirements and design versus just code Reuse, and trace end-user requirements to the components which support them.
-
A measurement framework for organizational Software Reuse influence factors
1998Co-Authors: James Baldo, David C. RineAbstract:The organizational objective of achieving enterprise-wide Software Reuse has been an elusive goal for many organizations. Many promising Software Reuse technology based approaches that have been successfully demonstrated on pilot projects have failed to achieve success within an organization's Software development environment. These observations indicate that an organization's successful adoption, utilization, and management of Software Reuse is influenced by more than just technical attributes. The effects of attributes such as organizational culture and structure have been conjectured as having significant impact on an organization's potential to successfully adopt, utilize, and manage Software Reuse activities. Therefore, the measurement of organizational Software Reuse is a manifestation of both technical and organizational attributes. Yet there does not exist a validate set of organizational Software Reuse attributes. This dissertation identified a set of Software Reuse organizational attributes and developed a framework to validate these attributes. The framework was used to test hypotheses on Software Reuse organizational attributes (i.e., independent variables) for their effects on organizational Software Reuse adoption, utilization, and management (i.e., dependent variables). The framework assessed organizational data that was collected from the open literature and World Wide Web sources on past organizational Software Reuse programs for validating the organizational Software Reuse attributes under study.
-
Exploratory study of Software Reuse success factors
1996Co-Authors: Robert Michael Sonnemann, David C. RineAbstract:The problem researched is that there presently does not exist a set of success factors which are common across organizations and have some predictability relationship to Software Reuse. For completeness, this research also investigated to see if Software Reuse had a predictive relationship to productivity and quality. A literature search was conducted to identify a set of Software Reuse success factors. The individual success factors were grouped into the following categories: management commitment, investment strategy, business strategy, technology transfer, organizational structure, process maturity, product-line approach, Software architecture, availability of components, and quality of components. A questionnaire was developed to measure Software Reuse capability, productivity, quality, and the set of Software Reuse success factors. A survey was conducted to determine the state-of-the-practice. The data from the survey was statistically analyzed to evaluate the relationships among Software Reuse capability, productivity, quality, and the individual Software Reuse success factors. The results of the analysis showed some of the success factors to have a predictive relationship to Software Reuse capability. Software Reuse capability also had a predictive relationship to productivity and quality. Based on the research results, the leading indicators of Software Reuse capability are: (1) product-line approach, (2) architecture which standardizes interfaces and data formats, (3) common Software architecture across the product-line, (4) design for manufacturing approach, (5) domain engineering, (6) Reuse process, (7) management which understands Reuse issues, (8) Software Reuse advocate(s) in senior management, (9) state-of-the-art Reuse tools and methods, (10) precedence of reusing high level Software artifacts such as requirements and design versus just code Reuse, and (11) trace end-user requirements to the components (systems, subsystems, and/or Software modules) which support them.
Will Tracz - One of the best experts on this subject based on the ideXlab platform.
-
ICSE - Software Reuse myths revisited
Proceedings of 16th International Conference on Software Engineering, 1Co-Authors: Will TraczAbstract:In ACM Software Engineering Notices, vol. 13, no. 1, pp. 17-21 (1988), the author published the paper "Software Reuse myths". This paper comments on these "myths" in the light of recent technology advances: (1) Software Reuse is a technical problem; (2) special tools are needed for Software Reuse; (3) reusing code results in huge increases in productivity; (4) artificial intelligence will solve the Reuse problem; (5) the Japanese have solved the Reuse problem; (6) Ada has solved the Reuse problem; (7) designing Software from reusable parts is like designing hardware using integrated circuits; (8) Reused Software is the same as reusable Software; and (9) Software Reuse will just happen. >
Robert Michael Sonnemann - One of the best experts on this subject based on the ideXlab platform.
-
investments in reusable Software a study of Software Reuse investment success factors
Journal of Systems and Software, 1998Co-Authors: David C. Rine, Robert Michael SonnemannAbstract:Abstract This research supports the thesis that there is a set of success factors which are common across organizations and have some predictability relationships to Software Reuse. For completeness, this research also investigated to see if Software Reuse had a predictive relationship to productivity and quality. The individual success factors were grouped into the following categories: management commitment, investment strategy, business strategy, technology transfer, organizational structure, process maturity, product-line approach, Software architecture, availability of components, and quality of components. A questionnaire was developed to measure Software Reuse capability, productivity, quality, and the set of Software Reuse success factors. A survey was conducted to determine the state-of-the practice. The data from the survey was statistically analyzed to evaluate the relationships among Reuse capability, productivity, quality, and the individual Software Reuse success factors. The results of the analysis showed some of the success factors to have a predictive relationship to Software Reuse capability. Software Reuse capability also had a predictive relationship to productivity and quality. Based on the research results, the leading indicators of Software Reuse capability are: product-line approach, architecture which standardizes interfaces and data formats, common Software architecture across the product-line, design for manufacturing approach, domain engineering, management which understands Reuse issues, Software Reuse advocate(s) in senior management, state-of-the-art tools and methods, precedence of reusing high level Software artifacts such as requirements and design versus just code Reuse, and trace end-user requirements to the components which support them.
-
Exploratory study of Software Reuse success factors
1996Co-Authors: Robert Michael Sonnemann, David C. RineAbstract:The problem researched is that there presently does not exist a set of success factors which are common across organizations and have some predictability relationship to Software Reuse. For completeness, this research also investigated to see if Software Reuse had a predictive relationship to productivity and quality. A literature search was conducted to identify a set of Software Reuse success factors. The individual success factors were grouped into the following categories: management commitment, investment strategy, business strategy, technology transfer, organizational structure, process maturity, product-line approach, Software architecture, availability of components, and quality of components. A questionnaire was developed to measure Software Reuse capability, productivity, quality, and the set of Software Reuse success factors. A survey was conducted to determine the state-of-the-practice. The data from the survey was statistically analyzed to evaluate the relationships among Software Reuse capability, productivity, quality, and the individual Software Reuse success factors. The results of the analysis showed some of the success factors to have a predictive relationship to Software Reuse capability. Software Reuse capability also had a predictive relationship to productivity and quality. Based on the research results, the leading indicators of Software Reuse capability are: (1) product-line approach, (2) architecture which standardizes interfaces and data formats, (3) common Software architecture across the product-line, (4) design for manufacturing approach, (5) domain engineering, (6) Reuse process, (7) management which understands Reuse issues, (8) Software Reuse advocate(s) in senior management, (9) state-of-the-art Reuse tools and methods, (10) precedence of reusing high level Software artifacts such as requirements and design versus just code Reuse, and (11) trace end-user requirements to the components (systems, subsystems, and/or Software modules) which support them.
Nader Nada - One of the best experts on this subject based on the ideXlab platform.
-
An empirical study of a Software Reuse reference model
Information and Software Technology, 2000Co-Authors: David C. Rine, Nader NadaAbstract:Abstract In Software engineering there is a need for technologies that will significantly decrease effort in developing Software products, increase quality of Software products and decrease time-to-markets. The Software development industry can be improved by utilizing and managing Software Reuse with an “empirically validated reference model” that can be customized for different kinds of Software development enterprises. Our research thesis is that Software development based on a Software Reuse reference model improves the competitive edge and time-to-market of many Software development enterprises. The definition and study of such a model has been carried out using four steps. First, the reference model developed here is based on the existing Software Reuse concepts. Second, this reference model is an empirical study which uses both legacy studies and lessons learned studies. Third, the impact of the reference model on Software development effort, quality, and time-to-market is empirically derived. Fourth, an initial set of successful cases, which are based on the Software Reuse reference model utilization, are identified. The main contribution of this paper is a reference model for the practice of Software Reuse. A secondary contribution is an initial set of cases from Software development enterprises which are successful in the practice of Reuse in terms of decreased effort, increased quality and a high correlation in their application of our Software Reuse reference model activities.
S R De Lemos Meira - One of the best experts on this subject based on the ideXlab platform.
-
a survey on Software Reuse processes
Information Reuse and Integration, 2005Co-Authors: E S De Almeida, Alexandre Alvaro, Daniel Lucredio, Vinicius Cardoso Garcia, S R De Lemos MeiraAbstract:Software Reuse processes have been under continuous attention in the Software engineering and Software Reuse research communities during past years. Although several processes have been investigated to develop reusable Software, there are not available studies that compare them. In this way, this paper presents a detailed survey on Software Reuse processes.
-
rise project towards a robust framework for Software Reuse
Information Reuse and Integration, 2004Co-Authors: E S De Almeida, Alexandre Alvaro, Daniel Lucredio, Vinicius Cardoso Garcia, S R De Lemos MeiraAbstract:Software Reuse is a critical aspect for companies interested in the improvement of Software development quality and productivity, and in costs reduction. However, achieving it is a nontrivial task. In this paper, we present a robust framework for Software Reuse, based on previous success factors, in order to guide organizations in the effective Reuse. Nontechnical and technical aspects compose the framework.
-
IRI - A survey on Software Reuse processes
IRI -2005 IEEE International Conference on Information Reuse and Integration Conf 2005., 1Co-Authors: E S De Almeida, Alexandre Alvaro, Daniel Lucredio, Vinicius Cardoso Garcia, S R De Lemos MeiraAbstract:Software Reuse processes have been under continuous attention in the Software engineering and Software Reuse research communities during past years. Although several processes have been investigated to develop reusable Software, there are not available studies that compare them. In this way, this paper presents a detailed survey on Software Reuse processes.
