• The KIPS Transactions:PartD
• /
• v.10D no.5
• /
• pp.763-772
• /
• 2003

Design patterns are known widely by the techniques to improve software qualify. The design patterns are efficient solutions for problems occurring frequently in software development. Recently there are wide researches for design patterns to find them and to verify usability for them. But there are very few researches to define systematic development approaches about constructing application using design patterns. In this paper, we propose an approach for the pattern-oriented software development process using incremental composition for design patterns. For this proposal, first we define a development process using design patterns, propose technique for incremental composition for design patterns and view ports for software in the process. Also we deal with the problem of efficient traceability and maintenance to design patterns in the software system. And we use a feedback framework system as an illustrative example to show how the process can be used to develop the pattern-oriented software. In the development of software, the systematic development approach and usage increase efficiency to develop the system by using design experience and technique early in the development lifecycle. Therefore the system will assure the high stability and reusability and offer the low cost and time for development.

• The KIPS Transactions:PartD
• /
• v.12D no.1 s.97
• /
• pp.73-80
• /
• 2005

The purpose of using CBD in the object-oriented modeling is to improve the software capability by reducing iterative time and space complexity. Despites many achievements of CBD, it is needed to study about design patterns and it's standardization for the increment of CBD design reusability. However, it is rather possible that impetuous constructing meta-pattern languages and pattern repositories make adapting patterns to software development more complicate and difficult. By applying GoF design patterns to the design of the TMDL(Total Maximum Daily Load) environmental software discipline, this study suggests a method which specifies Pattern names at class names for retrieving, exploring the adapted patterns on the stage of software design without meta-pattern language which is a redundant abstraction, nor additional pattern repositories. Thus, this study can contribute on the reducing iterations and repetitions that are frequently occurred in the process of the environmental software developments.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.23 no.56
• /
• pp.19-34
• /
• 2000

Impact of business process re-engineering requires the fundamental rethinking of how information systems are analyzed and designed. It is no longer sufficient to establish a monolithic system for fixed business environments. Information systems must be adaptive in nature. This demand is also applied in production domain. Enabling concept for the adaptive information system is reusability. This paper presents a new object-oriented analysis process for creating such reusable software components in production domain, especially for production planning and scheduling. Our process called MeCOMA is based on three meta-models: physical object meta-model, data object meta-model, and activity object meta-model. After the three meta-models are extended independently for a given production system, they are collaboratively integrated on the basis of integration pattern. The main advantages of MeCOMA are (1) to reduce software development time and (2) to consistently build reusable production software components.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.9
• /
• pp.2857-2866
• /
• 2000

As software technology has made progress, object-oriented CASE tools have become more important. This paper presents the process and similarity in design and implementation of OODesigner, an object-oriented CASE tool, on three platfonns and outlines a kind of generic architecture for the design and the implementation of CASE tools. OODesigner is a tool that was initially developed to support OMT. An initial Unix version has been developed since 1994. In 1997, after the completion of the Unix version, we began developing a Java version and a Windows version supporting UML. The development of a CASE tool is a typical application of the Model-View-ControllerO'vIVC) paradigm. Thus, we obtained a common design pattern among the versions in the MVC point of views. This design similarity can be used to develop several kinds of CASE tools with the corresponding design notations.