• The KIPS Transactions:PartD
• /
• v.8D no.1
• /
• pp.54-61
• /
• 2001

Software architectures can be restructured by modification and replacement during design processes, and appropriate software architectures for developments can be more than one. Therefore, developers are required to specify efficiently the modification elements of architectures, and manage different versions of an architecture designed for various aspects. In this paper, we propose a mechanism that can restructure legacy architecture and a new software architecture designed with reuse of it in integrated form, and define the specification elements and structure of the proposed architecture restructuring specification. It provides the method that can reference and reuse architectures designed with various aspects of developers in architecture design processes.

• Journal of the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.65-72
• /
• 2018

In this paper, we have studied how to reuse common data link software by applying software product line engineering. Existing common data link software performed different stages of design, implementation, and testing without sharing the accumulated knowledge of different developers. In this situation, developers agreed that sharing the assets of each project and reusing the previously developed software would save human and time costs. Even with the initial difficulties, the common Data Link is a continually proposed project in the defense industry, so we decided to build a product line. The common data link software can be divided into two domains. Among them, the initial feature model for the GUI software was constructed, and the following procedure was studied. Through this, we propose a plan to build a product line for core assets and reuse them in newly developed projects.

• 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 the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.341-350
• /
• 2002

Software architectures can be restructured by modification and update during design processes, and appropriate software architectures for developments can be designed more than one. Therefore, it is required to specify efficiently the modification elements of architectures and restructuring method of designed architecture through various aspects. In this paper, we proposed software architecture restructuring mechanism that can restructure legacy architecture and a new software architecture designed with reuse of it in integrated form. And, we define specification elements and structure of the proposed restructured architecture specification. It provides the method that can reference and reuse architectures designed with various aspects of developers in architecture design processes. In addition, it supports flexible specification method for specification of modification elements such as revision, substitution, update of legacy software architecture.

• The Transactions of the Korea Information Processing Society
• /
• v.4 no.1
• /
• pp.97-106
• /
• 1997

Software reuse techniques make reapplication of various well-organized information knowledge to system development so that improve productivity and make it easy to maintain software. This paper describes the design and implementation of CSORUS(C and C++ SOurce ReUse System) which can extract reuse components using reverse engineering, and store, retrieve, merge them written with C of C++ programming language. The construction components using reverse engineering has advantage in quality assurance because they are reliable components already tested in real environments.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.4
• /
• pp.168-176
• /
• 2008

In an environment where manufacturing conditions such as product lines keep changing, manufacturing control systems need to be continually maintained and upgraded according to the change. This requires an effective system implementation methodology. In this paper, a methodology based on the multi-criteria similarity comparison of manufacturing processes is proposed. A newly introduced process is compared with existing ones based on the multi-criteria similarity, and candidates for software reuse are selected from stored modules according to the overall process characteristics. The proposed methodology has been tested for an electronics manufacturing company's manufacturing control system, and the result has been satisfactory in that it can save time and efforts for system implementation.

• Journal of Information Processing Systems
• /
• v.8 no.4
• /
• pp.539-554
• /
• 2012

Model-driven and component-oriented development is increasingly being used in the development of embedded systems. When combined, both paradigms provide several advantages, such as higher reuse rates, and improved system quality. Performing model-driven and component-oriented development should be accompanied by a component model and a method that prescribes how the component model is used. This article provides an overview on the MARMOT method, which consists of an abstract component model and a methodology for the development of embedded systems. The paper describes a feasibility study that demonstrates MARMOT's capability to alleviate system design, verification, implementation, and reuse. Results indicate that model-driven and component-based development following the MARMOT method outperforms Agile development for embedded systems, leads to maintainable systems, and higher than normal reuse rates.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.6
• /
• pp.1803-1809
• /
• 2000

With the wide usage of the Internet, there use of pre-developed software is becoming important more and more in the development of various communication software. In this paper, the architecture to reuse the communication software is proposed. It is applied to the development of MIB-II system group of SNMP agent software for reusing. If Communication software is developed using this architecture, the software development life cycle will be abridged and the development cost will be reduced.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.8
• /
• pp.2088-2097
• /
• 1999

We propose the software framework construction method that increases reusability through use case extraction and structuring of software system's dynamic behavior of which identifying behavior patterns from software domain models. Most behavior models do not provide a consistent modeling technique for harmonizing user's heterogeneous requirements, and not yet prepared to a detailed optimizing technique for redevelopment and maintenance. Therefore, we need a software reuse framework to support consistency and reusability of existing development models using use cases with functional characteristics. a lattice model is used to this approach for structuring use cases, and the reuse process that can be driven to reusable components is introduced in this paper,.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.11
• /
• pp.147-155
• /
• 2020

System support software is one of the software that makes up ship combat management system and has the characteristics of being mounted in the combat management systems of all ships but with little functional change. However, despite these characteristics, software modifications due to equipment, etc. are inevitable in the application of new ships. Modification of software causes software reliability testing which is a key factor in increasing development costs. In this paper, the structure of the existing system support software was analyzed to identify and supplement the code change factors, and the system support standardization architecture was designed. The feature model elicited common and variable elements of system support software, and applied white-box reuse to improve software design. In addition, the results of comparing existing system support software with the new architecture in terms of development elements and time to perform reliability test were presented to verify the effectiveness of the new one.