• Journal of Korea Multimedia Society
• /
• v.9 no.6
• /
• pp.750-761
• /
• 2006

As CBD technologies and researches have been matured, component framework as a larger reuse unit than component is being introduced. Especially issues related with adaptation and integration of components in CBD are being raised as a new research topic. The component framework is given as a solution to resolve these issues. However, current approaches don't suggest a sound and comprehensive reference model and development process applying reference model. In order to develop practical and stable component framework, reference model and concrete guidelines are essential elements. In this paper, we propose a generic reference model integrating existing reference models and a design technique of component framework based on it. Especially, we propose concrete and pragmatic guidelines such as how to design component framework architecture's view and style, how to design commonality and variability of component framework, how to design macro workflows among components, and so on. We believe that the proposed reference model becomes basis for component framework development, and the proposed design technique will support reliable and effective development of the component framework.

• Proceedings of the Korea Society for Simulation Conference
• /
• 2001.10a
• /
• pp.484-484
• /
• 2001

The sophistication of current software applications results in the increasing cost fur software development time. The component-based software development framework is proposed to overcome the difficulty and time-consuming requirements by modularity and reusability. As is the general software case, a component-based simulation framework encourages the reusability of the real system model based on the modularity of the applied simulation methodology. This paper presents a component-based simulation environment that is based on the DEVS/COM run-time infrastructure. The DEVS (Discrete Event System Specification) formalism provides a formal modeling and simulation framework for the generic dynamic systems [1] and Microsoft's COM (Component Object Model) is one of the strongest competitor fur the component standard. The reusability by the DEVS/COM simulation environment saves model development time remarkably and component technology make simulator itself to be a subparts of real application.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.3
• /
• pp.842-851
• /
• 2000

Developers can reuse not only class code but also wide range of knowledge on domain by reusing framework. Existing Object-Oriented Methodology and Catalysis Methodology were presented when redefining component in the course of redesigning framework. However, existing methodologies have weakness that entire process is waterfall mode or design of interface lays too much stress on implementation stage. So, this thesis will present Component-Oriented Methodology for the reuse of framework, and construct the environment for framework and domain development. That is, domain is analyzed by input of domain knowledge on real world to create software based on component, and hotspot is identified through analyzed information, and refactoring by putting additional information on users and developers. After that, I will create domain framework and application framework depending on domain. In this Component-Oriented Methodology, information is searched, understood and extracted or composite through component library storage internally. Then this information is classified into the information on component, and used as additional information in redesigning. With this, developer can obtain reusability, easiness and portability by constructing infrastructure environment that allows to register, update and delete component through Component Management System(CMS) under he development environment which can be easily applied to his own application using framework component, in this thesis, CoRBA(Common Object Request Broker Architecture) environment.

• Journal of Institute of Control, Robotics and Systems
• /
• v.16 no.8
• /
• pp.780-785
• /
• 2010

The OPRoS (Open Platform for Robotic Services) framework is proposed as an application runtime environment for service robot systems. For the successful deployment of the OPRoS framework, fault tolerance support is crucial on top of its basic functionalities of lifecycle, thread and connection management. In the previous work [1] on OPRoS fault tolerance supports, we presented a framework-based fault tolerance architecture. In this paper, we extend the architecture with component-based fault tolerance techniques, which can provide more simplicity and efficiency than the pure framework-based approach. This argument is especially true for fault detection, since most faults and failure can be defined when the system cannot meet the requirement of the application functions. Specifically, the paper applies two widely-used fault detection techniques to the OPRoS framework: 'bridge component' and 'process model' component techniques for fault detection. The application details and performance of the proposed techniques are demonstrated by the same application scenario in [1]. The combination of component-based techniques with the framework-based architecture would improve the reliability of robot systems using the OPRoS framework.

• Proceedings of the CALSEC Conference
• /
• 2002.01a
• /
• pp.441-443
• /
• 2002

iComponent란ㆍ e-Business 환경에서 컴포넌트 재사용 및 비즈니스 Template를 통한 신속한 컴포넌트 작성과 분석/설계에서 구현으로 유연한(seamiess)전이를 지원하는 컴포넌트 Framework →개발 생산성 향상 및 표준화 지원도구 COM+Based Component Framework(중략)

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

CBD(Component Based Development) can make use of component of block unit that is implementation beforehand and shorten software development cost and time. Also, component can reduce complexity for the large application development because it can hide detail part of internal and offer interface. Common requirement of family in the enterprise framework environment can express workflow, but it is very difficult that express special workflow in single component on various family member's requirement. Therefore, necessity about workflow variability management between component for family member and implementation method had been required constantly. This treatise presents implementation techniques for component workflow variability in enterprise framework under Banking Loan Presented component workflow variability implementation techniques supposes that commonness business workflow that family can use in enterprise workflow was created already in component, and improve workflow's extensity between component by worikflow composition between special component and techniques for practice to various family member.

• Proceedings of the Korean Society of Precision Engineering Conference
• /
• 2001.04a
• /
• pp.703-706
• /
• 2001

This paper presents a component-based integration framework and its software component architecture for supporting the rapid integration of legacy design supporting systems in the distributed environment. Also, using standard interface, this software component architecture provides flexibility, extensibility and compatibility which ensure software components to be independent of the integration middleware and systems to be integrated.

• The Journal of Society for e-Business Studies
• /
• v.9 no.2
• /
• pp.145-161
• /
• 2004

CBD(Component Based Development) can make use of component of block unit that is implementation beforehand and shorten software development cost and time. Also, component can reduce complexity for the large application development because it can hide detail part of internal and offer interface. Common requirement of family in the enterprise framework environment can express workflow, but it is very difficult that express special workflow in single component on various family member's requirement. Therefore, necessity about workflow variability management between component for family member and implementation method had been required constantly This treatise presents implementation techniques for component workflow variability in enterprise framework under .NET base. Presented component workflow variability implementation techniques supposes that commonness business workflow that family can use in enterprise workflow was created already in component, and improve workflow's extensity between component by workflow composition between special component and techniques for practice to various family member.

• Journal of KIISE:Computing Practices and Letters
• /
• v.9 no.3
• /
• pp.241-253
• /
• 2003

SCA (Software Communication Architecture), which has been adopted as a SDR(Software Defined Radio) Forum standard, provides a framework that successfully exploits common design patterns of embedded systems software. However, the SCA is inadequate as a component framework since it does not explicitly specify (1) a component model that defines how to express a component interface and how to implement it, (2) a package model that defines what and how to package in deployment units, and (3) a deployment model that defines the deployment environment and deployment process. In this paper, we propose a SCA-based component framework for SDR. Specifically, we present (1) a component model that defines a component as a specialized CORBA object that implements object management functionality, (2) a package model exploiting the existing XML descriptors of the SCA, and (3) a deployment model that defines a SCA-based deployment environment, a boot-up process that restores the deployment state, and a deployment process that supports lazy application instantiation and dynamic component replacement.

• Proceedings of the CALSEC Conference
• /
• 1999.07b
• /
• pp.431-445
• /
• 1999

This paper introduces a development of component based framework of supply-chain management. The existing legacy system, which is not designed for object-oriented paradigm, is re-modeled using unified modeling language. Components are extracted from the legacy application, and frameworks are also designed in order to increase productivities of software development. Design issues concerning component and framework development are discussed with real situation. Performance and development productivity issue are also discussed with discussing component size and scope. A real case is presented in connection with the discussed issues.