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

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.11b
• /
• pp.334-336
• /
• 2005

유비쿼터스 시대에 진입하면서 임베디드 소프트웨어의 개발에 대한 관심이 높아지고 있다. 국방 분야에서는 국방무기 및 비무기 내장형 소프트웨어 관리지침과 공군에서 운영되는 항공무기 소프트웨어 개발 프로세스 등이 운용되고 있으며, 국방 CBD 방법론은 주로 응용체계 개발을 위한 컴포넌트 기반의 구체적인 방법론이다. 이러한 국방 CBD 방법론을 임베디드 소프트웨어 개발에 적용가능 여부는 발표되지 않았다. 따라서 본 논문에서는 임베디드 소프트웨어개발을 위한 국방 CBD 프로세스 테일러링 방안을 고찰하고자 한다. 이를 위하여 국방 무기 및 비무기 내장형 소프트웨어 관리지침에 근거한 조정, 임베디드 소프트웨어 개발 방식에 따른 조정 컴포넌트 및 객체 지향기술, 그리고 UML 기술 적용으로 구분하여 테일러링 방안을 제시한다. 그 결과 국방 CBD 방법론의 적용 범위의 확대 및 개발 프로세스의 표준화에 기여할 것으로 기대된다.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2003.10a
• /
• pp.970-973
• /
• 2003

Recently, the development paradigm of enterprise information system has been moved from 2-tier environment to 3-tier environment. 3-tier environment makes possible to develop more efficient system in terms of the performance, extension, deployment and maintenance. The ship drawing process management system which manages a long-term drawing process and a great number of designers has to support an accuracy and a real-time of information but it is impossible because it is still served in 2-tier environment and some process of them is not developed yet. In this paper, we implemented the analysis and design of system based on CBD(Component Based Development) for the purpose of hanging the environment from two-dimensional Client/server architecture environment to COM＋ based 3-tier architecture environment. And by completing a development of total system, the productivity and the efficiency of the ship drawing process management system will be improved. And a wide reuse of components makes possible to improve the productivity and efficiency of system.

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

Recently, software quality evaluation based on ISO/IEC 9126 and ISO/IEC 14598 has been widely accepted in various areas. However, these standards for software quality do not provide practical guidelines to apply the quality model and the evaluation process of software product=5. And the qualify management in most software projects has been conducted by managing defects without applying the standards for software qualify. Thus, we present a quantitative quality evaluation approach of artifacts in the Component Based Development (CBD). Particularly, our evaluation approach allows most of the standard evaluation process and adopts a quantitative quality model which uses the weights of quality characteristics obtained through carefully selected questionnaires for stakeholder and Analytic Hierarchical Process(AHP). Moreover, we have also examined the proposed evaluation approach with applying the checklists for the artifacts of the CBD to a small-scale software project. As a result, we believe that the proposed approach will be helpful for acquiring the high quality software.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2003.10a
• /
• pp.978-981
• /
• 2003

Component-Based Development(CBD) for a system has benefits in terms of improvement of operation and maintenance as well as reduction of development period. But applying the CBD methodology to a system can give rise to difficulties, which are there should be specialists in CBD and domain to apply and there would be a lot of products resulting in the application. To solve the problems, we suggested a suitable methodology in overall process from analysis to implementation after investigating the methodology applicable to small and medium software system by software systems engineering approach. In the application of the suggested methodology to design a ship design process management system, we could confirm the efficiencies of the methodologies.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.8
• /
• pp.1939-1946
• /
• 2009

Modern enterprise may be in need of developing the right application programs under rapidly changing business environment in fast time-to-market. But Most of enterprise without business process mechanism are very hard to develop the application needed in time when it will be changing their business. To solve this problem, we propose the business process framework based on the closed architecture. This approach is to develop the right application with reusing software modules in time and easily under rapid business process changing/improving through mapping BPM(Business Process Model), SOA(Service Oriented Architecture), and CBD(Component Based Development). we also define 5-Layers of BPF(Business Process Framework), and BNF(Backus Naur Form) for structuring BPF.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.10a
• /
• pp.376-378
• /
• 2001

CBD(Component Based development)가 이미 완성된 소프트웨어 모듈인 컴포넌트들을 특정 목적을 위해 배치하고 조립함으로써 품질 보증된 고생산성의 재사용을 가능하게 됨에 따라, 최근 IT 비즈니스 솔루션 도출을 위한 핵심 적인 기술 전략으로 인식되고 있다. 따라서 영 역에 적절한 컴포넌트의 추출과 개발 및 응용 시스템으로의 전개를 위한 컴포넌트들의 배치와 조립 등을 포함하는 일련의 CBD 프로세스를 실제화 하기 위해서는 아키텍쳐 기반의 접근과 제어가 매우 중요하다. 하지만 대부분의 CBD 연구는 비즈니스 로직들의 기능성을 그룹화한 컴포넌트의 생산에 초점을 두고 있지 컴포넌트간의 상호작용을 명시하는 아키텍쳐 정보의 관리를 간과함으로써 컴포넌트의 조립과 통합을 통한 CBD 시스템으로의 전개는 극히 어려운 실정이다. 따라서, 본 논문에서는 CHD 프로세스 상에서 아키텍쳐 접근의 중요성과 전개 방법을 살펴보고, 컴포넌트 프레임워크(Component Framework)를 위한 아키텍쳐의 계층을 새롭게 재정의 하며 그 의미를 설명한다. 이를 위해 영역 분석 및 설계 정보를 선언적으로 명시하는 수단이며, 도메인 내에서 특정 서비스를 제공하는 컴포넌트간의 일반적 결합 방식의 규정하기 위한 수단으로서 설계 패턴을 이용하여 서비스 아키텍쳐 패턴을 정의하고 실 예로 적용한다.

• International Journal of Computer Science & Network Security
• /
• v.22 no.9
• /
• pp.143-148
• /
• 2022

Component-based software development (CBD) is a methodology that has been embraced by the software industry to accelerate development, save costs and timelines, minimize testing requirements, and boost quality and output. Compared to the conventional software development approach, this led to the system's development being completed more quickly. By choosing components, identifying systems, and evaluating those systems, CBSE contributes significantly to the software development process. The objective of CBSE is to codify and standardize all disciplines that support CBD-related operations. Analysis of the comparison between component-based and scripting technologies reveals that, in terms of qualitative performance, component-based technologies scale more effectively. Further study and application of CBSE are directly related to the CBD approach's success. This paper explores the introductory concepts and comparative analysis related to component-based software engineering which have been around for a while, but proper adaption of CBSE are still lacking issues are also focused.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1205-1216
• /
• 2005

Component-based Development (CBD) is gaining popularity as an effective reuse technology. Especially commercial-off-the-shelf (COTS) components are mainly for inter-organizational reuse, rather than intra-organizational reuse. One of the essential tasks in CBD is to reuse the right components that provide the functionality and interface required by component consumers. If candidate components provide a limited applicability and customizability, a component consumer cannot reuse the components in application development. To resolve this partial matching problem, we need smart connectors that fill the gap between candidate components and the specification of components required. Previous researches about smart connector describe only connector types to resolve mismatch problems. However, previous researches do not address the identification and design method to resolve the problems. In this paper, we suggest taxonomy of various mismatch problems to identify partial match problems between requirements of the application and components. We identify smart connector types and suggest a systematic process for designing smart connectors using the taxonomy. Therefore, components that have the problems can be used to develop applications.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.715-722
• /
• 2001

In recent years, we recognize a new paradigm in the development process：From object oriented development, to the development process which has focused on the use of standard components. In recent years a lot of research related to the component-based development has been done, especially in business domain. but still there are many open and unresolved problems in this area. such as established development process for a distributed environment, formal process, infrastructure for COTS, development and management tool considering maintenance to guarantee a proper treatment of components. It also required a service and an application integration for component. In this paper, we propose cooperative information systems (CIS) that supports component based development. It must address for component based systems to achieve their full potential. We identify a set of CIS organized 3-tier which is a presentation layer, business logic layer and data control layer. We also discuss the specific roles and activities for the layers. we also define the behavior and managed information for business logic layer as core level. As an illustration of the CIS, we present a successful considerations which is widely helpful to user when they make decision in component development and assemble. Also, we expect to component reusability and efficiency in business domain.