• Journal of Internet Computing and Services
• /
• v.4 no.1
• /
• pp.67-74
• /
• 2003

According to change of software development technique as design pattern, component based development etc.., web server development part is applied activity to fit in various user requirement. Especially, EJB as sewer side component model much researches and introduce by easy and various development support. Also, component composing techniques is receiving many interests by easy and efficient application way that architecture based C2 style architecture with message handling. But, in case of EJB component that can not cail thread, C2 framework modification is unavoidable for component composition by C2 style architeccture. For this, we propose techniques to use Adapter pattern to be one of structure pattern among pattern. That is, did so that component composition by C2 style architecture may can consist changing to be able to call thread function in EJB by Adapter pattern.

• Advances in Computational Design
• /
• v.2 no.4
• /
• pp.293-311
• /
• 2017

There are several claimed benefits for the impact of design patterns (DPs) on software quality. However, the association between design patterns and fault-proneness has been a controversial issue. In this work, we evaluate the fault-proneness of design patterns at four levels: the design level, category level, pattern level, and role level. We used five subject systems in our empirical study. As a result, we found that, at the design level, the classes that participate in the design patterns are less fault-prone than the non-participant classes. At the category level, we found that the classes that participate in the behavioral and structural categories are less fault-prone than the non-participant classes. In addition, we found that the classes that participate in the structural design patterns are less fault-prone than the classes that participate in the other categories. At the pattern level, we found that only five patterns show significant associations with fault-proneness: builder, factory method, adapter, composite, and decorator. All of these patterns except for builder show that the classes that participate in each one of them are less fault-prone than the non-participant classes in that pattern. The classes that participate in the builder design pattern were more fault-prone than the non-participant classes and the classes that participate in several patterns: the adapter, the composite, and the decorator design patterns. At the role level, the most significant differences were between the classes that participate in some roles and the non-participant classes. Only three pairs of design pattern roles show significant differences. These roles are concrete-product vs. concrete-creator, adapter vs. adaptee, and adapter vs. client. The results recommend the use of design patterns because they are less fault-prone in general except for the builder design pattern, which should be applied with care and addressed with more test cases.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.322-324
• /
• 2005

컴포넌트기반 개발에 있어서 레거시프로그램의 재활용은 사업 기간과 범위 그리고 효율성이라는 부분에서 상당히 중요한 요소이다. 레거시프로그램을 재활용하기 위해 레거시 프로그램을 Wrapping하는 프로그램이 필요하며, 이를 위한 연구들이 활발히 진행되고 있다. 본 논문에서는 그 중 Adapter 패턴을 분석하여 상속과 위임의 장단점을 제시하고 상속 방식을 이용하는 패턴에 대하여 심층적으로 분석한다. 이를 바탕으로 레거시 프로그램을 통합함에 있어 개별적 Wrapper 구성을 통해 Adapter의 크기를 최소화하고 유지보수에 편리하도록 지역화하며, 단점인 인터페이스의 복잡성을 해결하기 위해 Facade 패턴을 활용하여 문제를 해결하는 방법을 제안한다.

• Journal of Advanced Navigation Technology
• /
• v.19 no.4
• /
• pp.330-337
• /
• 2015

A service in the environments of internet of things (IoT) exist various types with automation facilities and sensors. There can configure so many communication protocols to networking facilities and sensors. To provide efficient various kind of service, a middleware platform, is based on the internet protocol network, is needed a unified access with devices, controlling and monitoring huge kind of facilities and sensors, to provide a efficient IoT service and application configurations. In this paper, we propose a middleware that an application and service interact with automation facilities and monitor sensors. The proposed middleware is designed with adapter pattern that one of the software engineering design pattern. The adapter pattern is to ensure communication with each sensor and to make sure of service scalability. Finally, the proposed component middleware shows that variety sensors can be easily configure the service in the IoT environment.