• Journal of KIISE:Software and Applications
• /
• v.35 no.6
• /
• pp.357-365
• /
• 2008

Requirements traceability enables to reuse various kinds of software artifacts, which are the results from software development life cycle, rather than reuse source code only. To support requirements traceability for reuse of software artifacts, 1) artifacts should be described based on requirements and 2) a requirements tracing method should be supported. In this paper, we provide a description model for annotating requirements information to software artifacts by using requirements ontology. We also provide semantic tagging method users to efficiently annotate artifacts with the requirements ontology. And we finally present how requirements traceability is supported based on requirements ontology and also suggest the system architecture for requirements traceability support.

• Journal of Convergence for Information Technology
• /
• v.9 no.2
• /
• pp.23-33
• /
• 2019

Research and development(R&D) activities consist of analytical survey and state-of-the-art report writing for technical information. As R & D activities become more concrete, it often happens that they refer to related technical documents that were created in previous steps or created in previous similar projects. This paper proposes a research-task based reuse recommendation framework(RTRF), which is a reuse recommendation system that enables researchers to efficiently reuse the existing artifacts. In addition to the existing keyword-based retrieval and reuse, the proposed framework also provides reusable information that researchers may need by recommending reusable artifacts based on task similarity; other developers who have a similar task to the researcher's work can recommend reusable documents. A case study was performed to show the researchers' efficiency in the process of writing the technology trend report by reusing existing documents. When reuse is performed using RTRF, it can be seen that documents of different stages or other research fields are reused more frequently than when RTRF is not used. The RTRF may contribute to the efficient reuse of the desired artifacts among huge amount of R&D documents stored in the repository.

• The KIPS Transactions:PartD
• /
• v.12D no.7 s.103
• /
• pp.1001-1006
• /
• 2005

The Ministry of National Defense has developed MND-AF and Defense-CBD methodology to make the integration and management of standardization effective through enhancing the interoperability and reusability of information systems. Yet no explicit guidelines or procedures have not been developed for the applying range and mutual relationship of the artifacts between MND-AF and Defense-CBD methodology. Thus, the development time is unnecessarily extended and budget also is increasing because both methodologies produce the artifacts respectively. This paper presents a reusability enhancement scheme for producing MND-AF artifacts according to Defense-CBD process by analyzing artifacts of two methodology les at each element level, so that it will reduce the overhead of producing the artifacts and enhance the completeness of the artifacts. In result, in the case of applying Defense-CBD methodology for developing a information system34 artifacts out of 37 MND-AF artifacts can be reusable.

• Journal of Digital Convergence
• /
• v.11 no.12
• /
• pp.439-445
• /
• 2013

There has been a growing amount of research on combining Agile methods and software reuse. Most of it introduces Agile into software product line rather than software reuse into Scrum method. Meanwhile, some assets such as backlogs and incremental artifacts in Scrum development are reusable. In this paper, we identify a backlog binder that aggregates reusable Scrum assets and proposes a backlog binder reuse technique. In addition, we can apply the proposed technique and show prototyping of backlog binder reuse in job matching applications.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2007.10a
• /
• pp.42-43
• /
• 2007

• Journal of the Korean Institute of Landscape Architecture
• /
• v.34 no.6 s.119
• /
• pp.111-129
• /
• 2007

Industrial heritage artifacts may include the industrial products, technologies and infrastructures that have contributed to modernization beginning with the Industrial Revolution. The history of our industrial heritage spans 50 to 150 years and can be characterized by taking into account the site and the technology. This paper analyzes 13 precedents in Japan, Canada, and the United States in terms of these concerns, with focus on the reuse of abandoned mines as industrial heritage. Field surveys and interviews about each abandoned mine were used to obtain historical records and material. The results describe progress in three phases (1) recognizing phase, (2) organizing phase, and (3) maintenance management phase. A proper methodology for reuse is necessary to ensure the authenticity of the abandoned mine, particularly in the face of poor tourism-oriented approaches. As a result of analyzing the 13 cases, we determined that the following principles should be considered during the reuse process. Firstly, reuse of abandoned mines should not be compulsory but should be a spontaneous process and especially, should be carried out by inhabitants. Secondly, education and real experiences in the abandoned mine should be used to ive visitors a feeling of authenticity. Thirdly, creative remodeling methods can be used to enhance the abandoned mine's facilities and the site. Finally, historic and new functions should be the focus of the revitalization. Because this paper mainly focused on 13 precedents, there are likely more diverse cases. However, the conclusions of this report have practical value for reuse of abandoned mines and can be used in establishing methods for reusing Korean abandoned mines as industrial heritage.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.04a
• /
• pp.597-600
• /
• 2010

소프트웨어 재사용(Software Reuse)은 소프트웨어 생산성을 높이는 방법임에도 불구하고 내장형 소프트웨어 개발 분야에서의 적용은 많은 어려움이 있다. 내장형 소프트웨어는 개발된 소프트웨어의 실행환경이 서로 다르고, 하드웨어 의존성이 높기 때문이다. 국방 분야에서의 내장형 소프트웨어는 보안성이라는 특성상 타 프로젝트의 모범사례를 적용하는 데는 정보 공유의 어려움이 있어 왔다. 본 논문에서는 MIL-STD-498에 기반하여 국방 분야의 내장형 소프트웨어 재사용 프로세스에 관해 연구하고 적용 결과를 제시하였다.

• The KIPS Transactions:PartD
• /
• v.15D no.3
• /
• pp.361-374
• /
• 2008

In the latest intelligent computing environments, the self-adaptive software, as new software paradigm, which modifies its own behavior in response to changes in its operating environment is needed. To develop the self-adaptive software, it is necessary to analyze and design the context of software as well as the structure and the behavior of software. We need more efforts for self-adaptive software development than for traditional software development because we need more activities and technologies like context modeling and adaptation to develop the self-adaptive software. In this paper, we present the product line architecture for self-adaptive software and templates of artifacts to improve the efficiency of development through a reuse methodology. The artifacts of the architecture support the systematic reuse activities of core assets by expressing the commonality and variability of product line.

• Journal of the Korean Society of Systems Engineering
• /
• v.8 no.1
• /
• pp.29-39
• /
• 2012

The conventional systems engineering has been performed mainly based on documentation artifacts. Although the Document-Based Systems Engineering has played a very important role in developing and deploying systems, it is difficult for systems engineers to build, to clarify, and to reuse the operational, functional and physical views of the System of Interest (SOI) efficiently. An information-age approach to this problem is the Model-Based Systems Engineering which has been emerging as a very productive solution for stakeholders to define, and understand the desired systems easily, to communicate and collaborate efficiently among each other, and also to verify and validate the systems solutions effectively. This paper proposes a set of MBSE process, methods, and models for use during the systems analysis and design phase of the naval combat system development. An example application of the proposed approach was exercised and a set of artifacts was generated for an export combat system project to demonstrate its effectiveness.