• The Transactions of the Korea Information Processing Society
• /
• v.6 no.3
• /
• pp.580-588
• /
• 1999

The reuse of software components from existing software system enhances productivity and reliability, decreases the cost of production in software development. The extraction of software components with high reusability from existing software system is very important in software reuse. The reuse of a class is classified into white-box reuse to reuse with modification and black-box reuse to reuse without modification. A class has the property of procedural language and object-oriented language. Therefore, it must measure reusability in consideration of two properties. In black-box reuse, independence of class is important quality. It can quantify through information hiding, coupling between objects, cohesion, etc. In white-box reuse, modification is the best important quality. It can quality through class complexity, coupling, cohesion, documentation, etc. We propose a new model for measurement of class reusability and the measure criteria in object-oriented program. A class that is measured by proposed model can judge whether the reuse with modification has the advantage or the reuse without modification has the advantage.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 1998.11a
• /
• pp.43-50
• /
• 1998

The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.

• Journal of Software Engineering Society
• /
• v.24 no.1
• /
• pp.9-17
• /
• 2011

Software reuse the concept of developing software by using existing software assets, rather than developing it from scratch. Developers may face difficulties of reusing existing software assets because existing assets are normally developed by other developers for different purposes. Developers tend to seek appropriate knowledge about effectively reusing software assets from the developers who have faced and solved similar problems in reusing software assets previously. In other words, the reuse-related knowledge of domain experts or other developers usually provides important clues to solve reuse-related problems. Such reuse-relalted knowledge can help developers to reduce the time and effort to identify and solve the difficulties and problems that may arise in reusing software assets and in minimizing the risks of reusing them by allowing them to reuse reliable software assets in an appropriate way and by recognizing similar requirements or constraints of resuing the assets. In this paper, we describe a model to represent reuse-related knowledge in a formal way, and explain the architecture and a prototype implementation of Software Reuse Wiki (SRW) that enables collaborative organization and sharing of software reuse-related knowledge. We have conducted an experiment pertaining to problem solving in reusing assets based on reuse-related knowledge. We also discuss about our evaluation plan for showing the benefits and contributions of reuse knowledge representation model and management methods in SRW. We expect that SRW can contribute to facilitate users' participations and make efficient sharing and growing of reuse-related knowledge. In addition, the representation model of reuse-related knowledge and management methods can make developers acquire more reliable and useful reuse-related knowledge in a straightforward manner without spending additional efforts to find solutions to solve reuse-related problems.

• ETRI Journal
• /
• v.31 no.3
• /
• pp.304-314
• /
• 2009

Component-based software reuse has been generally regarded as a promising approach to improving software productivity and quality within software development. However, progress in component-based software reuse has been slower than expected. Much of the software reuse literature points to the lack of software components that can maximize users' benefits as the most important source of the slow progress. Considering that the underlying processes behind component-based software reuse are strikingly similar to commercial software marketing, this paper attempts to identify the aspects of software components that consumers value and to establish relationships between the identified aspects and consumer behavior in the software component market. More specifically, this paper focuses on the perceived subjective features of software components. This study was conducted in a web-based artificial market environment called "SofTrade."

• Journal of the Korea Society of Computer and Information
• /
• v.9 no.3
• /
• pp.103-107
• /
• 2004

Software Reuse have the advantages of increasing productivity and software reliability reducing the period for software development and cost, sharing the information which is related to software. Vertical Reuse is the method which reuse is restricted to a specific area and can increase the reliability of software reuse due to high understanding of related area. Bottom-up approach of Vertical Reuse classifies the related information and s the results. It allows the reuse of not only pure source code but also informal documents.

• Journal of Digital Convergence
• /
• v.12 no.12
• /
• pp.337-343
• /
• 2014

There have been many efforts to find a new way to combine software reuse and agile software development methods. This paper studies the integration of software reuse techniques in agile methods, such as Scrum. Agile methods have the advantage of accepting frequent requirement changes, while software reuse reduces development time. Despite the rapid acceptance of the Scrum method in industry, not much emphasis has been placed on active reuse in the Scrum method, and most studies have focused on introducing agile practices into software product line engineering. However, the iterative development and backlog refinement activities of the Scrum method present the advantage of facilitating software reuse. In this paper, we identify sprint characteristics and components for reuse and suggest extended backlog refinement steps. Based on the results of this research, we integrate a backlog factoring technique into backlog refinement to support reuse in agile methods. In addition, we apply the proposed technique and demonstrate a prototype of product backlog reuse in backlog refinement for an Internet shopping mall application.

• 한국IT서비스학회:학술대회논문집
• /
• 2002.11a
• /
• pp.425-430
• /
• 2002

Over the years, several different approaches have been proposed to enhance the practice of software reuse. These approaches vary in reuse abstraction levels or application domains they focus on. However, it seems that they do not adequately meet the needs of software designers in planning and managing reuse. One reason may be the lack of conceptually well-established framework supporting work domain analysis and modeling. As a new viable solution to this problem, Sutcliffe and his colleagues developed Domain Theory , which is introduced in this paper. Utilizing multidisciplinary perspective, such as cognitive psychology, management science, human-computer interaction, and software engineering. it provides a schematic framework that defines a comprehensive library of generic and reusable models of domain knowledge in terms of generic tasks and meta-domains. It also provides useful methods and guidelines for software reuse, emphasizing the concept of abstraction process in a designer s mind. This paper firstly gives a brief overview of fundamentals of software reuse. Next, it explains the foundation of domain theory and discusses its applicability to software reuse. In particular, the taxonomy of meta-domains and the types of generic tasks are described in more detail. Finally, the future research framework, which primarily addresses the problem of how to apply the domain theory to various work domains, is proposed.

• The KIPS Transactions:PartD
• /
• v.13D no.2 s.105
• /
• pp.271-278
• /
• 2006

This paper presents industry feedback and a case of improvement trial on enabling reuse driven software development which is one of several activities to improve software quality and productivity in a company which develops software that are embedded into consumer electronic products. Several case studies will be introduced that are related to software reuse strategies and practices to show how to establish environment for reuse basis in a company, how to apply it to development team and project and how to improve that through trials and errors. To enable reuse-oriented software development in a huge company, integrated and focused approach is needed among technical, management and environmental point of view. We tried to solve that problem in technical field with reuse method, in management filed with reuse metric and in environment field with reuse repository. The characteristics of our software development environment could be summarized as below. The first, embedded software which would not independent to hardware devices and the second, it is very huge company which develops extremely various products by many different organization with different domain characteristics and the third, development lead time is extremely short and many variation models are stems from basic models. We expect that our study would give contribution to industry struggling to solve similar problem for presenting our experience and could be a reference model for enabling software reuse in a real world practically.

• Journal of Digital Convergence
• /
• v.13 no.12
• /
• pp.171-177
• /
• 2015

The aim of the study is to introduce a software reuse technique into a generalized agile process for a reuse of a product backlog item. The software engineering community has made some efforts to integrate software reuse and agile methods. Most studies have emphasized the use of agile practices in software product line engineering, whereas reuse in agile methods has received little focus. Nevertheless, the activities and artifacts that provided by an agile method exhibit characteristics that promote reuse. In this paper, we identify catalytic activities and characteristics that promote reuse in a generalized agile process, and we suggest a reuse technique for a product backlog item. Based on our results, we integrate a backlog factoring technique into a generalized agile process for reuse. In addition, we apply the proposed technique and demonstrate a prototype of backlog item reuse in agile methods for a restaurant chain application.

• Journal of Digital Convergence
• /
• v.14 no.11
• /
• pp.297-304
• /
• 2016

The aim of the study is to combine software reuse with agile methods through reuse in the early stage of agile development. Although agile methods and software reuse have different practices and principles, these methods have common goals, such as reducing development time and costs and improving productivity. Both approaches are expected to serve as viable solutions to the demand for fast development or embracing requirement changes in the rapidly changing environments. In the present paper, we identify economical agile reuse and its type and study a reuse technique for input queue in Kanban board at the early stage of hybrid agile methods. Based on our results, we can integrate software reuse with agile methods by backlog factoring for input queue item in the hybrid Scrum and Kanban method. The proposed technique can be effectively applied to e-class applications and can reuse the input queue items, showing the combination of the two approaches. With this study, we intend to contribute to reuse in the early stage of agile development. In the future, we plan to develop a software tool for economical agile reuse.