• Journal of the Korea Computer Industry Society
• /
• v.10 no.3
• /
• pp.87-92
• /
• 2009

Identification of reusable software components should guide user to come up with information about candidate components when a proper component is not found. Reusable software components which is able to confidential are a few risk and more effective than redesign or encode same components about each new application program. In this paper reusable processes are considered previously. Reusable model and the method for construction are analyzed for construction reusable components and reusable components which take this method are proposed. These problem will go far toward solving the design and coding of effective program.

• 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.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.04a
• /
• pp.591-593
• /
• 2000

컴포넌트의 재사용은 기존 소프트웨어의 문제점인 소프트웨어의 수요충족, 신뢰성요구 및 유지보수 용이 등을 해결할 수 있는 방법중의 하나이다. 현재, 재사용 컴포넌트를 위한 웹 상에서의 정보서비스는 데이터요소의 불일치와 이미 검색된 정보를 다시 찾아야 하는 비효율적인 검색방법을 사용하고 있다. 이를 해결하기 위해, 본 논문에서는 이전에 찾은 컴포넌트 정보를 재사용 할 수 있도록 에이전트를 사용해 컴포넌트 정보를 수집하고 논문에서는 이전에 찾은 컴포넌트 정보를 재사용 할 수 있도록 에이전트를 사용해 컴포넌트 정보를 수집하고 XML 형태로 정보를 저장, 관리하는 컴포넌트 정보의 재사용 방법을 제시한다. 즉, 이용자별로 이미 검색된 정보를 저장, 갱신관리하여, 이후 컴포넌트 검색에 있어서 이런 정보를 재활용함으로써, 검색시간의 단축, 정확한 정보검색 그리고 이용자별 차별적인 정보제공과 컴포넌트 평가를 지원할 수 있다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2006.05a
• /
• pp.203-206
• /
• 2006

Ada는 객체지향 특성과 소프트웨어 모듈화 및 일반화 메커니즘을 통해 프로그래밍 언어 차원에서 소프트웨어의 재사용성을 제공하고 있다. 그러나 특정 언어 자체를 이용하는 것만으로 소프트웨어의 재사용이 확보되지는 않으며 설계자가 컴포넌트간의 유기적인 관계를 파악하고 재사용을 통해 얻을 수 있는 장.단점을 판단할 수 있어야 한다. 본 논문은 재사용 가능한 소프트웨어 객체와 인터페이스를 식별하고 재사용 모듈의 설계에 필요한 요소들을 파악함과 동시에 소프트웨어 설계 시 적용할 수 있는 코딩 패턴을 제시한다. 또한 이들을 보다 효율적인 설계도구인 Statemate에서 재사용 모듈로 활용할 수 있도록 기존 generic chart의 한계를 고려한 확장 개념의 재사용 모듈을 작성한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2017.04a
• /
• pp.621-624
• /
• 2017

소프트웨어의 적용 분야가 다양화되면서 시장 환경의 변화와 사용자 요구사항의 다양화가 급속도로 진행되고 있다. 하지만 부족한 시간, 예산, 인력 문제로 고품질의 소프트웨어 개발은 더 어려워졌다. 이런 문제의 해결을 위해 레거시 시스템의 모듈을 재사용하여 고품질화하고자 한다. 기존에는 정적 분석 기반의 재사용 모듈/덩어리 식별만 이루어졌지만, 실제 실행 환경에서 적용되는 동적 분석 기반의 재사용 식별이 더욱 중요하다. 이를 위해, 재사용 메트릭을 정의하고 재사용 모듈/덩어리 자동식별 및 가시화를 제안한다. 이는 새로운 프로젝트 개발의 재사용성을 높여, 신뢰성과 생산성 향상시키고 품질 개선에 기여한다.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.9 no.6
• /
• pp.583-590
• /
• 1999

We propose the reusability decision model of the object-oriented components, which can decide the potentiality of reusability of the object-oriented components actively. Fisrt, we select attributes for the reusability decision of the object-oriented components. Then, we acquire information from the reused components based on the quality measures and criteria proposed by many researches. Lastly, we generate algorithm for the reusability decision of the object-oriented components from the acquired information employing rough set.

• Proceedings of the Korean Information Science Society Conference
• /
• 1999.10a
• /
• pp.545-547
• /
• 1999

소프트웨어 애플리케이션에서 재사용성이 높고 기술적 자산으로서의 가치는 일반적으로 Business Logic 또는 Control 논리를 적용하고 있는 부분에 있다. User Interface나 DB 등 다른 구성 부분은 개발 환경의 변화에 따라 기존 산출물을 변형 적용하고 Control 및 논리 부분은 객체 컴포넌트화 하여 설계, 구현의 산출물을 재사용 저장소에 넣어, 유사 시스템이나 조직내 다른 응용 영역에서 재사용 할 수 있도록 저장소에 넣어, 유사 시스템이나 조직내 다른 응용 영역에서 재사용할 수 있도록 한다. 이러한 컴포넌트 자산들을 구축하는 과정을 정형화하는 프로세스를 정의하고 수운용 시스템 개발에 시범 적용한 사례를 살펴봄으로써 컴포넌트 중심의 재사용 모델을 제시하고 성공적인 재사용 체제의 구축 배경을 설정한다.

• 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.

• The Transactions of the Korea Information Processing Society
• /
• v.2 no.2
• /
• pp.176-184
• /
• 1995

The software reuse is a prospective way to improve software productivity and quality but not applied very well in practice, because there is no quantitative metric for software quality. In this paper we proposed the quantification of the reuse of software that we can measure the possibility of the reuse by applying the reuse assessment metric to the module after the extraction of a module from existing software. For measuring the module that can be reused, we divided the factors of quality by the generality, simplicity, maintainability and modularity, and identified and measured the module by the factors and finally decided the possibility of the software reuse. The advantage of the proposed metric is that we can find the inappropriate reuse of module exactly at the beginning by measuring quantitatively the module to be reused.