Practice Of Software Reuse Research Articles

How Freelance Developers Embrace Software Reuse Practice? A perspective analysis using clustering techniques

The advancement of ICT technologies has modernized software development practices, thus presenting opportunities for developers to reuse software components in developing new software. These practices allow developers to use reliable reusable software components to quickly develop software. However, not much research has reported how freelance developers capitalize on these practices, despite the rapid rise of freelancing development. This research investigates how freelance developers embrace software reuse practices to achieve project success. A survey that gathers 351 responses from freelancers was analyzed using clustering techniques, revealing high levels of self-efficacy and satisfaction towards deploying software reuse practices and highlighting the need for software development firms to embrace this method.

“Snapshot” of the State of Software Reuse in Colombia

Due to competitive markets, the software business wants faster, better, and cheaper solutions in a short amount of time. Software reuse emerges as a viable solution to these demands since it offers significant benefits, such as increased quality and efficiency and lower development costs and effort, as well as shorter commercialization times. This research aims to study and understand the state of the practice of software reuse in Colombia, to make comparisons with related works, and to offer an instrument for decision-making in companies that adopt these practices. To reach these objectives, three stages were proposed. In the first stage, the research questions were defined. In the second stage, a survey was developed, evaluated, and carried out to validate successful practices and adoption barriers in the context of the Colombian software industry. Finally, the results were analyzed and reported. This paper showed and evidenced the expectations, adoption barriers, and factors influencing the success of software reuse in Colombian industrial environments. In the same way, the experience from the development of this work serves as a roadmap for other regions that want to analyze the current state of reuse. Nevertheless, each organization needs to determine its capabilities and find the appropriate factors to be adopted to its context.

An exploratory study of the standard reuse practice in a medium sized software development firm

Reuse has been a topic of interest in software engineering since 1968. Although many academic papers have been written about adopting software reuse in companies, such a process in practice has proven difficult, long and costly to implement. At present, rigorous studies on the current practice of reuse in industry are scarce. Objective: The aim of this paper was to study the current practice of software reuse at a medium sized company, in particular, we aimed to alleviate the lack of data and identify barriers and success factors. Method: An exploratory study based upon descriptive surveys. Results: The predominant practice of reuse is ad hoc (73%) and the reusable artefacts were shared by means of a central repository (81%). Most practitioners use the Web to look for artefacts (92%), trying to understand them by studying code snippets or the artefact's documentation. The existence of a well-established reuse process (81%) and a high quality of the artefacts (70%) were the two most mentioned facilitators for reuse. Conclusions: All participants view software reuse as a beneficial process and believe that management should promote it. The results offer opportunities for further interpretation and comparison to software developers, project leaders, and researchers. However, these results cannot be generalized due to the specificity of the context we have studied. Replications of this study, in other business domains, are needed to generalize the results.

Comparing development approaches and reuse strategies: An empirical evaluation of developer views from the aerospace industry

ContextThere is a debate in the aerospace industry whether lessons from reuse successes and failures in nonembedded software can be applied to embedded software. Reuse supposedly reduces development time and errors. The aerospace industry was an early advocate of reuse, but in Aerospace, not all reuse experiences have been as successful as expected. Some major projects experienced large overruns in time, budget, as well as inferior performance, at least in part, due to the gap between reuse expectations and reuse outcomes. This seemed to be especially the case for embedded systems. ObjectiveOur goal is to discover software reuse practices in the aerospace industry. In particular, we wish to learn whether practitioners who develop embedded systems use the same development approaches and artifacts as software practitioners who develop nonembedded systems. We wish to learn whether reuse influences selection of development approaches and artifacts and whether outcomes are impacted. MethodWe developed a survey given to software practitioners in a major Aerospace Corporation developing either embedded or nonembedded systems. The survey probed to identify development methods used, artifacts reused and outcomes resulting from the reuse. We used qualitative and quantitative methods such as descriptive statistics, MANOVA, Principle Component Analysis and an analysis of freeform comments to compare reuse practices between embedded systems and nonembedded systems development. ResultsWe found that embedded systems were more likely to include component based development, product line development and model based development in their development approach, whereas nonembedded systems were more likely to include Ad Hoc and COTS/GOTS in their development approach. Embedded systems developers tended to reuse more and different reuse artifacts. ConclusionWe found that, while outcomes were nearly identical, the development approaches and artifacts used did, in fact, differ. In particular, the tight coupling between code and the platform in embedded systems often dictated the development approach and reuse artifacts and identified some of the reasons.

Design Pattern Mining by Product of Sum (POS) Expression for Graphs

There are many recurring patterns of classes which exist in several object oriented software as an experience of developers. Design Pattern Mining is an important part of many solutions to Software Reuse practices. Design pattern instances are highly important and useful for program understanding and software maintenance. Hence an automatic and reliable design pattern mining capability is required. Here we are proposing a new method for design pattern detection based on Boolean functions.

面向特征的软件复用技术——发展与现状

Most traditional industries focus on the reproduction-based mass production of physical products, which is not suit for the software industry. To achieve efficient and effective production in the software industry, software reuse is a realistic approach, which focuses on the customization-based mass production of software products. Feature-oriented software reuse provides a technical approach to enforcing the customization-based mass production of software products, and has shown important influence on the research and practice of software reuse. This paper clarifies basic concepts and key ideas in feature-oriented software reuse, and presents important achievements in recent years in this field. In particular, this paper: (1) inspects the existing definitions of features from the two viewpoints of intension and extension, and analyzes the responsibilities of features in software reuse; (2) explains the basic structure of feature models and its semantics based on the propositional logic, and presents three kinds of extension to the structure and semantics of feature models; (3) describes two general ways of modeling the traceability between feature models and implementation artifacts, and surveys research work on traceability between feature models and three kinds of implementation artifacts (i.e. use case, software architecture, and source code), respectively. We hope that this paper could facilitate the understanding of essential problems and state-of-the-art and further improve the research progress in the field of feature-oriented software reuse.

공유기 및 RFID를 이용한 옥내 측위 웹 서비스 구현

위치기반 서비스는 일상생활에서도 널리 이용되는 매우 편리한 서비스임으로 GPS 신호가 잡히지 않는 빌딩, 대형상가, 지하상가와 같은 건물 내부에서도 제공되어야 한다. 이처럼 건물 내부에서 제공되는 위치기반 서비스를 옥내 위치기반 서비스라 하는데, 옥내 위치기반 서비스 개발에 있어서 가장 중요한 기술은 옥내측위이다. 옥내측위 방법 중 가장 범용성이 있는 것은 무선근거리통신망의 공유기 신호를 이용하는 것이다. 한편, 근래에는 웹 서비스가 뛰어난 소프트웨어 재사용 기술로 판명되고 있다. 따라서 옥내측위가 웹 서비스로 프로그램 개발자에게 제공된다면 옥내 위치기반 서비스의 실용화를 크게 촉진할 것이다. 본 논문은 공유기 신호를 이용한 삼각측량 및 K-NN 옥내측위 서비스와 RFID를 이용한 옥내측위 서비스를 제공하는 웹 서비스 구현 사례를 소개한다. LBS (Location Based Service) services are very useful to our daily life and it should be available inside a building: a huge building, a shopping mall, a large scale underground shopping center, and so on where GPS (Global Positioning System) signal is not available. An LBS which is provided inside a building is called an ILBS (Indoor Location Based Service). One of the most important techniques for ILBS development is indoor positioning. Among the indoor positioning techniques, APs (access points) of WLAN based ones are most economical because WLAN is available almost everywhere. Meanwhile, the web service has been proved to be an excellent practice of software reuse. Therefore, if indoor positioning is provided in the form of web service to programmers then development of ILBS would be greatly accelerated. This paper introduces the AP based trilateration and K-NN indoor positioning and RFID based indoor positioning web services we have developed.

Design patterns detection using SOP expressions for graphs

Several recurring patterns of classes exist in many object oriented software as an experience of developers. Design Pattern Detection is an important part of many solutions to Software Reuse practices. Design pattern instances are highly important and useful for program understanding and software maintenance. Hence an automatic and reliable design pattern mining capability is required. Here we are proposing a new method for design pattern detection based on Boolean functions.

Assessing software reuse in Indian information technology firms: a structural equation modelling approach

Software reuse, despite being relatively new to the Indian software industry, generates a lot of interest amongst the cross-section of people in the industry. The reuse philosophy as well as its practice evokes varied response across sections even in the same organisation, from top management to project managers to developers. This article reviews the present status of software reuse practices in the Indian information technology firms on the basis of a questionnaire survey, field visits, and a number of interviews with industry participants and researchers. Adequate review of literature, supported by expert opinion survey and questionnaire survey, helped develop the conceptual model for software reuse. The structural equation model was tested with the data obtained from the questionnaire responses. The output model throws light on the causes of reuse and its consequences and also confirms the findings from the statistical analysis of the questionnaire data.

A domain model of Web recommender systems based on usage mining and collaborative filtering

Considering the increasing demand of multi-agent systems, the practice of software reuse is essential to the development of such systems. Multi-agent domain engineering is a process for the construction of domain-specific agent-based reusable software artifacts, like domain models, representing the requirements of a family of multi-agent systems in a domain, and frameworks, implementing reusable agent-based design solutions to those requirements. This article describes the domain modeling tasks of the MADEM methodology and a case study on the application of GRAMO, a MADEM technique, for the construction of the domain model of ONTOWUM, specifying the common and variable requirements of a family of Web recommender systems based on usage mining and collaborative filtering.

Reusable Security for Segmented Data Domains

For firms providing software development outsourcing services, the practice of software reuse can reduce overhead and increase margins. At the current time, an alarming number of enterprise software development projects are over budget, delivered late, or both. As software development organizations mature, so too should their ability to deliver increasingly complex software solutions on time and on budget. One strategy for achieving this is to identify opportunities for software reuse. In traditional manufacturing nomenclature, this process would be expressed as 'manufacturing efficiency' or 'economy of scale'. This paper explores one way in which open source Java 2 Enterprise Edition Security Realms can be used to facilitate code reuse - and thus manufacturing efficiency - into the enterprise software manufacturing process. Subsequently, enterprise software development firms who employ this methodology should expect to deliver software with greater efficiency and predictability at a lower cost.

Three empirical studies of a software reuse reference model

The contribution of this paper is a reference model for the practice of software reuse. Our research thesis is that software development based upon a software reuse reference model improves quality of products, productivity of processes and product time-to-market for many software development enterprises. The definition and investigation of such a model has been carried out using three steps. First, the reference model is developed based on existing software reuse concepts. Second, this reference model is empirically studied using both legacy studies and lessons learned studies. Third, the impact of the reference model on software development productivity, quality, and time-to-market is empirically derived. Copyright © 2000 John Wiley & Sons, Ltd.

Three empirical studies of a software reuse reference model

The contribution of this paper is a reference model for the practice of software reuse. Our research thesis is that software development based upon a software reuse reference model improves quality of products, productivity of processes and product time-to-market for many software development enterprises. The definition and investigation of such a model has been carried out using three steps. First, the reference model is developed based on existing software reuse concepts. Second, this reference model is empirically studied using both legacy studies and lessons learned studies. Third, the impact of the reference model on software development productivity, quality, and time-to-market is empirically derived. Copyright © 2000 John Wiley & Sons, Ltd.

Three empirical evaluations of a software reuse reference model

The contribution of this paper is three empirical evaluations of a reference model for the practice of software reuse. Our research thesis is that software development based upon a software reuse r...

An empirical study of a software reuse reference model

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.

A Performance Measure for Software Reuse Projects

The efficient development of software has become a critical factor to the success of many organizations. Significant competitive advantage can be realized by reducing the time to complete software development, while maintaining or improving quality levels. Project management activities, including the measurement of performance at the level of the project, can help the organization to both control projects and learn from experience. Traditionally, the productivity of a software development project has been measured as the complexity of code produced per unit of labor involved. An increasing number of organizations, however, are adopting the practice of software reuse, and under such conditions, such a traditional measure of productivity does not fully capture all the relevant elements of the reuse‐driven development environment. This research develops a new performance measure that considers four major components of performance: productivity associated with development of new code, productivity associated with the reuse of previously written code, quality of the reuse decision, and relative value of reuse to the company. To illustrate the feasibility of the measure, a real‐world productivity assessment is presented for an example company, and related implementation issues are discussed.

Software reuse in Japan

Software reuse in Japan has been mainly carried on by mainframers as a means to develop effectively their business applications. Each of the Japanese mainframers has developed its own integrated software development environments that support software reuse as one of their major functionalities. Now that they have succeeded in reusing program code and design, they are trying to broaden the target of reuse to include software architectures. The importance of the managerial aspect of software reuse is now being understood. Some companies are putting much stress on the technology transfer issue of software reuse, and others are applying incentive systems to encourage software engineers who participate in software development. This paper outlines the current status of the research and practice of software reuse in Japanese industries and research organizations.

An integrated approach to software reuse practice

Since 1993, Sodalia's Software Engineers have been studying a reuse program whose goal is making software reuse a significant and systematic part of the software process. The Sodalia's Corporate Reuse Program is intended to develop a Software Reuse Process that incorporates reuse-specific activities along the Object-Oriented Software Development Process, and a reuse library to support the classification and management of reusable components. This paper focuses on the on-going experience of Sodalia in the gradual introduction of reuse practice in the organization, illustrates the evolutionary stages, and the reached results.