• Journal of the Institute of Electronics Engineers of Korea TE
• /
• v.39 no.3
• /
• pp.71-82
• /
• 2002

The software pattern is knowledge representation derived from the verified solutions or the experience of the experts. On account of the design varieties of software development, however, it is not the facilitated task to discover the best proper software pattern. This situation requires that software patterns be categorized in terms of their innate concepts. This paper proposes software pattern ontology(SPO) for the systematic categorization of software patterns by means of conceptual properties of patterns after the comparative analysis of association between software pattern and ontology. The SPO presented in this paper can establish the basis for the software pattern management system at the conceptual level. This paper also shows an idea for the application by unifying conceptual properties of software pattern and ontology. 

• The Journal of Society for e-Business Studies
• /
• v.7 no.3
• /
• pp.219-240
• /
• 2002

The various software engineering techniques have been appeared in order to cope with the software crisis since 1980's. Currently, the research against the techniques likes the Design pattern, Component which improve the software's re-use are spread out. Also S/W Development Process are interested intensively which attempts the quality and a increasing productivity of software development with the basic policy. The design pattern is the solution against the problem which occurs repeat in a specific area. Many design pattern are developed and researched, but the method which accommodates the developed design pattern efficiently in the phase of analysis and design software development process is not good enough, so it is the actual applying technique is difficult. In this paper we suggest and the “UML components+” which is a efficient component development process from customizing EJB based the J2EE using the “UML Components” which is a component development methodology. Applying J2EE pattern efficiently with UML components+, there is a possibility of efficiency in the component development based pattern.

• The KIPS Transactions:PartA
• /
• v.12A no.7 s.97
• /
• pp.589-596
• /
• 2005

Source code quality is very Important that software embedded into product is difficult to change. In order to improve source code quality, it should be considered the quality of analysis and design models as well as the quality of source code. In this paper, we suggest 'Practice Pattern' as one of practical techniques to improve embedded software source code quality. Practice pattern is a procedural pattern to guide modeling and coding activities in software development phases. We believe that applying our pattern provides the improvement of optimum performance, modularization, and portability for embedded software source code.

• Journal of the Korean Home Economics Association
• /
• v.47 no.2
• /
• pp.111-123
• /
• 2009

This study is to explore the usability of a pattern making software 'Looks tailor X' developed recently by the Digital Fashion in line with the cloth simulation software 'DressingSim'. When the software engineers develop software for clothes and clothing simulations, most often they lose touch of real-world craftsmanship of pattern making. As such, the software evaluation of the functionality and the usability is a crucial step in the field of virtual clothing. We carried out a detailed evaluation of the software via the process of making some basic types of pattern including tight skirts, pants, jackets, and one-piece dress. In this paper, we documented a step-by-step scenarios of making clothes using the Looks tailor X, and listed both the advantages and limitations of the software from the perspective of an enduser, i.e., a professional fashion designer. We also briefed suggestions on the refinement of the future software in the field.

• Journal of Software Engineering Society
• /
• v.26 no.1
• /
• pp.17-29
• /
• 2013

Software System Evolution is more planned and systematic maintenance process as well as a type of maintenance. The research of software evolution provides basis of decisions for maintenance value through cost-benefit analysis of legacy system and architecture-based software evolution enables engineers to reduce maintenance cost by automation of repetitive evolution tasks. This paper proposes a framework for software system evolution using architectural transformation pattern.

• The Journal of the Society of Korean Medicine Diagnostics
• /
• v.14 no.1
• /
• pp.70-78
• /
• 2010

Objectives : To qualify or enhance the diagnostic ability of students in Oriental Medicine, so called standardized patients are ideal modality, but because it's a man-based method, more convenient tools are required. Computer-based diagnostic ability test program gives effective way for the very purpose. So we made a pilot software evaluating Pattern Identification ability in Oriental Medicine. Methods and Materials : The pilot software was coded with Microsoft's EXCEL VBA. 87 names of Zheng (Symptom Pattern) and 674 names of symptom (including some signs) are adopted from the former standardization works conducted by Korean Institute of Oriental Medicine (KIOM) in 1996. Results : Compared with some manned modalities to test Pattern Identification ability, the test by this software shows superiority in convenience and objectivity. Conclusion : This software is world's first program to perform computer-based evaluation of Pattern Identification in Oriental Medicine, and it gives effective way to complement both written test and manned clinical performance test (CPX).

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.29 no.4A
• /
• pp.399-414
• /
• 2004

In this paper, an evolution of software reliability engineering in a large-scale software project is summarized. The considered software consists of many components, called functional blocks in software of switching system. These functional blocks are served as the unit of coding and test, and the software is continuously updated by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components in software reliability and reliability evolution. We analyze the static characteristics of the software related to software reliability using collected failure data during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of system software, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto(G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources fur a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.

• Electronics and Telecommunications Trends
• /
• v.14 no.4 s.58
• /
• pp.1-9
• /
• 1999

In this paper, we summarize the lessons learned from the applications of the software reliability engineering to a large-scale software project. The considered software is the software system of the TDX-10 ISDN switching system. The considered software consists of many components, called functional blocks. These functional blocks serve as the unit of coding and test. The software is continuing to be developed by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components to software reliability and with the analysis of the reliability evolution. We analyze the static characteristics of the software related to software reliability using failure data collected during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of software of the TDX-10 ISDN system, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto (G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources for a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.

• Journal of KIISE:Software and Applications
• /
• v.32 no.5
• /
• pp.346-356
• /
• 2005

Over the past decade, several types of design pattern have been defined in the software engineering area. But these patterns have not been used so often compared with data structure and algorithm. Likewise, methods to select and apply design patterns during analysis, design, and development are not mentioned in CBD methodologies such as CBD96, RUP, and MaRMI III. This paper suggests the process of effectively selecting design patterns which can be applied to analysis, design, and development for development of application software with based on those offered by GoF and J2EE pattern catalogs. It also demonstrates how to effectively pattern-based software and shows differences and relative advantages from RUP by applying the suggested process to the development of aviation job application.

• Journal of KIISE:Software and Applications
• /
• v.29 no.8
• /
• pp.555-564
• /
• 2002

Design patterns are used to utilize well-defined design information. As using these design patterns, we can get re-use in object-oriented paradigm, decrease the time of development and improvement the quality of software. Although these design patterns are widely used among practice, most of design patterns information is manually used, inconsistent and its utilization could be very low. Because the design patterns information that a designer applies does not appear in software, it is sometimes difficult to track them. In this paper, we propose a tool support for design pattern-oriented software development. This tool supports design pattern management, software design and automatic source code generation. The design pattern management has the function for storing, managing and analyzing the existing design pattern and registering new design pattern. The software design has the function for software design with UML and automatically generate design pattern elements. By using this design information, this system can automatically generate source code. In the result to include the tracking design pattern element that is not Included In the existing CASE tools into design information, we can build the stable and efficient system that provides to analyse software, manage design pattern and automatically generate source code.