• Proceedings of the CALSEC Conference
• /
• 2001.08a
• /
• pp.671-679
• /
• 2001

사례연구를 통하여 UML Component Design Process의 일관성 및 정확성을 검증한다. Business Concept Model과 Use Case Model을 이용하여 Component Specification Process의 산출물인 Interface, Component Specification 및 Component Architecture 작성 UML Notation을 확장해서 Component 명세에 적용하는 것이 올바른 것인지 확인한다. <>,<>,<>,<>,<>, <>:로 Component Specification이 충분한지를 확인 OCL을 이용하여 Component Specification 중 Component Specification, Interface Specification, Operation Specification, Constraint, Pre/Post Condition의 정의에 유용한지 확인(중략)

• Journal of KIISE:Software and Applications
• /
• v.31 no.10
• /
• pp.1286-1303
• /
• 2004

Component-based Development is gaining a wide acceptance as an economical software development paradigm to develop applications by utilizing reusable software components. Well-defined interface manages coupling and cohesion between components, minimizes the effect on the user in case of component evolvement, and enhances reusability, extendibility and maintainability. Therefore, study on systematic development process and design guidelines for component interface has been required since the component has been introduced. In this paper, we propose three types of interfaces based on software architecture layers and functionality types； Provided Interface which provides functionality of a component, Required Interface which specifies required functionality that is provided by other components, and Customize Interface which tailors the component to customer's requirement. In addition, we suggest design criteria for well-designed interface, and systematic process and instructions for designing interface. We firstly cluster operations extracted from use case model and class model to identify Provided interfaces, and design Customize interfaces based on artifacts for variability. We also specify Required interfaces by identifying dependency among interfaces. Proposed interface design method provides traceability, throughout the component interface design. And furthermore, proposed guidelines support practical design for high quality component based on a case study.

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

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

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.389-397
• /
• 2003

The component-based development methodology becomes famous as the new way for reuse. The goal of the reuse is improvement of quality, productivity and independence on the software development. For the improvement in the quality of a component-based system, it is necessary to research component metrics in the early phase of a component development. Hence, in this paper, we propose new component metrics using the information of a component analysis phase. Those are CCI(Complexity of Component Interface) and LCC(Lack Cohesion of Component interface). CCI indicates a difficulty about comprehension, modification, management, use of interface. LCC indicates a functional independence about how strong the elements are related with. Therefore, it is possible to predict and manage the quality of a component to be developed. Predicting a lowness of complexity and highness of cohesion as an independent functional unit by a component interface in the early phase of a component development, we can expect the improvement in the quality of a system.

• Journal of Institute of Control, Robotics and Systems
• /
• v.16 no.6
• /
• pp.608-616
• /
• 2010

Robot software components can be categorized into two types; the pure S/W component and the H/W-related one. Since interface testing of the robot software component is the labour-intensive and complicated work, an effective automated testing tool is necessary. Especially it is difficult to test all types of H/W-related components because it is hard work to prepare all H/W modules related to them. This paper proposes a new simulation-based interface testing automation tool(SITAT) which generates automatically test cases for interface testing of the robot software component and executes the interface test with the generated test cases where the simulator is used for simulation of the activity of a H/W module instead of the real H/W module. This paper verifies the effectiveness of the suggested SITAT with testing of the real H/W-related robot software component.

• International Journal of Aeronautical and Space Sciences
• /
• v.15 no.2
• /
• pp.113-122
• /
• 2014

The objective of the paper is to clarify a methodology based on the use of the existing component mode synthesis methods for the case of two damped substructures which are coupled through a linking viscoelastic flexible substructure and for which the structural modes with free geometrical interface are used for each main substructure. The proposed methodology corresponds to a convenient alternative to the direct use either of the Craig-Bampton method applied to the three substructures (using the fixed geometric interface modes) or of the flexibility residual approaches initiated by MacNeal (using the free geometric interface modes). In opposite to a geometrical interface which is a topological interface on which there is a direct linkage between the degrees of freedom of substructures, we consider a physical flexible interface which exists in certain present technologies and for which the general framework linear viscoelasticity is used and yields a frequency-dependent damping and stiffness matrices of the physical flexible interface.

• Proceedings of the Korean Information Science Society Conference
• /
• 2003.10a
• /
• pp.685-687
• /
• 2003

최근, VPN기술은 보안 통신을 위해 자주 사용되고 있다. 비록 IPsec이 표준화 되었지만 많은 Vender들의 구현은 아직까지 완전한 상호간의 호환성을 갖지는 못하고 있다. 본 논문은 IP-VPN에 있어 상호 호환성 문제를 연구했다. 연구결과, 서로 다른 IP-VPN 구현에 있어 상호 호환성을 지원할 수 있는 Common Interface Component(CIC)를 제안하게 되었다. CIC와 CIC-Manager는 다양한 IP-VPN 구현에 있어서 상호 호환성의 해결책물 제공한다. 또한 CIC를 이용하여 다양한 표준을 지원할 수 있다.

• The Journal of Korea Robotics Society
• /
• v.10 no.1
• /
• pp.24-32
• /
• 2015

This paper introduces a graphical user interface design that is aimed to apply to the surveillance and security robot, which is the pilot program for the army unmanned light combat vehicle. It is essential to consider the activities of robot users under the changing security environment in order to design the efficient graphical user interface between user and robot to accomplish the designated mission. The proposed design approach firstly identifies the user activities to accomplish the mission in the standardized scenarios of military surveillance and security operation and then develops the hierarchy of the interface elements that are required to execute the tasks in the surveillance and security scenarios. The developed graphical user interface includes input control component, navigation component, information display component, and accordion and verified by the potential users from the various skilled levels with the military background. The assessment said that the newly developed user interface includes all the critical elements to execute the mission and is simpler and more intuitive compared to the legacy interface design that was more focused on the technical and functional information and informative to the system developing engineers rather than field users.

• The KIPS Transactions:PartD
• /
• v.16D no.1
• /
• pp.65-72
• /
• 2009

Component based development has increasingly become important in the software industry. However, in the current component based development approach with UML, the absence of behavioral description of components brings about a cost problem which causes semantic errors on the testing phase. Accordingly we cannot grasp the usage pattern of component by its provided interfaces which refer to an abstraction of software component. And we cannot guarantee the behavioral conformance of the provided and required interfaces of components. In order to solve these problems, we describe the behaviors of component interfaces by state machine diagram and guarantee their behavior conformance at the modeling phase. We also propose a method to guarantee the behavior conformance of component interfaces with concept of observation equivalence and invocation consistency. And we provide an analyzing tool which checks interface behavior conformance.