• 한국IT서비스학회:학술대회논문집
• /
• 2002.06a
• /
• pp.152-157
• /
• 2002

컴포넌트 기반 개발 프로세스는 그 동안의 구조적 분석/설계 기법과 정보공학, 객체지향 등의 공학적 분석기술을 수용하고 있다. 따라서 CBD를 적용하려는 조직은 다양한 소프트웨어 공학적 기법과 아키텍처 설계 기술들을 습득해야 하였다. 또한 CBD의 핵심 역량인 반복적 개발 프로세스와 아키텍처 설계 역량을 갖추기 위해 각 개발업체 들은 CBD기술의 도입초기에 상당한 혼돈과 어려움을 겪어야 했다. 이에 본 논문에서는 CBD를 조직차원에서 습득하고 적용하는 과정을 5개의 단계로 나누고 각 단계의 목표를 설정한 컴포넌트 개발 프로세스 성숙도 모형을 제시한다. CDMM(Component based Development capability Maturity Model)으로 명명한 본 개발 능력 성숙도 모형은 소프트웨어 개발조직이 CBD를 습득하기 위해 어떤 단계를 거쳐야 하는지 또한 컴포넌트 개발을 위한 핵심기술이 어떤 것들인지를 제시한다. 이는 향후 CBD를 확산시키고 컴포넌트 기술을 통한 생산성향상과 소프트웨어 개발비 절감을 위해 기업과 국가의 정책적 지표로 활용할 수 있을 것이다.

• Journal of the Korea Safety Management & Science
• /
• v.6 no.3
• /
• pp.211-235
• /
• 2004

Component based design is perceived as a key technology for developing advanced real-time systems in a both cost- and time effective manner. Already today, component based design is seen to increase software productivity, by reducing the amount of effort needed to update and maintain systems, by packaging solutions for re-use, and easing distribution. Nowdays, a thousand and one companies in If(Information Technology) industry such as Sl(System Integration) and software development companies, regardless of scale of their projects, has spent their time and endeavor on developing reusable business logic. The component software is the outcome of software developers effort on overcoming this problem; the component software is the way propositioned for quick and easy implementation of software. In addition, there has been lots of investment on researching and developing the software development methodology and leading If companies has released new standard technologies to help with component development. For instance, COM(Component Object Model) and DCOM(Distribute COM) technology of Microsoft and EJB(Enterprise Java Beans) technology of Sun Microsystems has turned up. Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, It suggest that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. about implements and accomplishes the modeling for the Product Control component development by applying CCD(Contract-Collaboration Diagram), one of component development methodology, to MRP(Material Requirement Planning) System

• Journal of the Korean Institute of Intelligent Systems
• /
• v.15 no.2
• /
• pp.211-223
• /
• 2005

The current software development type is based on CBD (Component Based Development). However, it requires a new component model that can support rapid and accurate component information on the web due to the cost increase of building new components using CBD. The purposed of this paper is to promptly develop an application on the web which fulfills users' demand and to provide specific interface regarding the small scales of distributed component in business domains. The e-BCOS(e-Business Component System) is the agent system for the users to register distributed components and to search component information, which would increase reusability through the e-business component development of distributed components in business domains and help the users understand the information about the component. Moreover, XML is employed for specification which allows smooth specification sharing and delivery to satisfy users' variable demands.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.495-497
• /
• 2000

CBD(Component-Based Development)는 이미 존재하는 소프트웨어 컴포넌트를 조립함으로써 시스템을 개발하는 방법이다. 컴포넌트를 이용하여 시스템을 개발하는 것은 개발시간과 비용을 줄이고, 생산성을 향상시키는 등 여러 가지 장점을 가진다. 그러나 여러 벤더에 의해 개발된 컴포넌트를 조립하는 것은 쉬운 일이 아니다. 이를 위해 컴포넌트가 어떤 문맥에서 사용되는지 이해하는 것이 필요하며 이 문맥은 아키텍쳐에 의해 결정된다. 따라서 본 논문에서는 컴포넌트 기반 개발을 위한 도메인 아키텍쳐를 제안한다. 도메인 아키텍쳐는 도메인을 구성하는 컴포넌트와 그들간의 관계에 대한 정보를 제공함으로써, 어플리케이션 개발을 쉽게 한다. 또한 도메인 아키텍쳐는 관련된 여러 시스템을 위한 아키텍쳐이므로, 도메인 아키텍쳐 상의 컴포넌트는 재사용이 높다.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.233-240
• /
• 2003

To develop high-quality software systems satisfying the customer's needs, user-centered design (UCD) process has been emphasized in the area of human-computer interaction. And component-based development (CBD) has been extensively studied to realize a systematic software reuse, thereby reducing the time-to-market and the development cost. Balanced integration of user-centered design process and CBD process will be a promising way for successful software construction, which effectively achieves three goals: the quality of software, the cost of software development, and the time-to-market. However, traditional CBD methodology seems to lack the concept of user-centered design process and the relevant methods. This paper proposes a way of incorporating user-centered design process into a CBD methodology. Firstly, this paper gives the brief introduction of UCD. Secondly, we explain typical UCD activities and methods along the phase of systems development lifecycle and propose the use of usability maturity model (UMM) for integrating UCD activities and methods with those of CBD methodology. Finally, as a case study, we describe the results of comparing the UCD activities to the activities of MaRMI-III, which has been developed as a CBD methodology at ETRI.

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

• Journal of Korea Multimedia Society
• /
• v.11 no.2
• /
• pp.237-246
• /
• 2008

According to the development of information & web technology and the amount of information increases, there have been numerous problems exposed. Although, software engineers try to overcome the limitations by using software agent and web service, there hasn't been satisfactory result in the paradigm of current software agent being a provider to the user's demand. Moreover, the latest configuration of software development is based on CBD (Component Based Development). However, to construct new component using CBD costs great deal of expenses and therefore, a new model which can acquirecomponent information on the web promptly and accurately with low expenses is required. In this paper, the repository management system which acquires and manages on the Semantic web is designed and compare them to the existing component repository management and present its analysis result. In addition, to overcome the limitations of existing component repository system; low accuracy of search result, restrictive search vocabulary and faulty information, the specific plan is presented to perform a knowledge search for the component.

• Journal of KIISE:Software and Applications
• /
• v.31 no.1
• /
• pp.43-53
• /
• 2004

Component-based development(CBD) has acquired a substantial acceptance in both academia and industry as an effective inter-organizational reuse technology. A component framework in product line engineering(PLE) which consists of related components, connectors and their semantics has a greater potential for reusability than components. In frameworks, components are glued with association, dependency and connections. Problems occur like affecting the implementation code of components when they are glued and replaced because the association and dependency relationships between COTS components which are acquired for application development do not match exactly. Especially, a connector may not only connect related components, but also mate partially-matched COTS components fit together. However, little has been studied to date about connectors that can be used practically. In this paper, we present a meta-model for connectors and show how a connector can be designed and implemented in practice. We propose five main patterns of connectors. Proposed major patterns Provide design guidelines for practical and efficient connector configuration based on component framework. And also, applying techniques and applied case studies of the major patterns show greatly increased applicability and reusability of the component without component modification.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.671-682
• /
• 2004

As new and diverse information technologies are being introduced and software complexity is increased, software development cost and efforts are also sharply increased. Component-Based Development (CBD) technology is appealing as a new way to reduce the cost and effort by increasing reusability and maintainability. Component in CBD has variability infernally which enables customization of the component within the specific domain. A component user can easily set up internally variability parts though Required interface which is provided by the component. Enterprise JavaBeans (EJB) is utilized as a commercial standard to implement Java-based components. However, EJB constructs are limited in directly implementing Required interfaces of coarse-grained components［8］. In this paper, we define Required interface and propose interface-storage technique, class-storage technique, interface-generation technique, and Plug -in technique for implementing required interface of component. Interface-storage technique stores variable value in Required interface and class-storage technique take the Bean containg variability as Required interface without modification of component model. Interface-generation technique generates new Bean which takes the role of Required interface for component variability and Plug-in technique sets up component variability that component user plugged-in variable part externally The proposed four techniques conform to the semantics of CBD component interface and enable the implementation of high quality components.

• The Journal of Information Systems
• /
• v.12 no.1
• /
• pp.87-116
• /
• 2003

One of the important applications for business-to-business electronic commerce is in procurement and inventory management using electronic data interchange(EDI). Using online catalogs and approved supplier lists, firms can easily create requisitions and purchasing documents. The emerging trend in EDI technology is changed from VAN(Value Added Network) based EDI to XML based EDI. This paper intends to suggest a component-based XML/EDI system using Unified Modeling Language(UML), as an application system for automobile part industry. Applying component based XML/EDI systems designed with UML methodology, we analyzed the workflow and the document on procurement process between trading partners and implemented a prototype of efficient XML/EDI system, as a surrogate of existing VAN/EDI. The result of applying object-oriented CBD(Component Based Development) technique is to minimize the risk of life cycle and facilitate the reuse of software as mentioned to limitation of information engineering methodology. It enables the interoperability with corporate legacy systems such as ERP(Enterprise Resource Planning), SCM(Supply Chain Management). This system proposes a solution to apply analysis phase and design phase in implementation of XML/EDI system. The implementation of XML/EDI system using CBD shows the ease of use in software reuse and the interoperability with corporate internal information system. The purchasing department with XML/EDI system can electronically communicate purchase orders, delivery schedules to external suppliers and interoperate with other application systems.