• The KIPS Transactions:PartD
• /
• v.17D no.1
• /
• pp.25-40
• /
• 2010

Service-Oriented Architecture (SOA) is a development paradigm for reusing services as an independent reuse unit. A service delivers a cohesive functionality through its external interface. Since services have unique characteristics which are not typically presented in conventional development approaches, there is a demand for effective approaches to developing services. Most of the current SOA methodologies presenta process where services are designed and developed from the requirements rather than reusing existing assets, which demands high cost and effort. Hence, a desirable approach is to be able to develop services by migrating from their existing legacy systems such as object-oriented system. A difficulty in this migration is that objects in object-oriented systems reveal characteristics which differ considerably from those of services. That is, objects are designed without considering commonalities among several consumers. In this paper, we first define mapping relationships between key artifacts in object-oriented system and those in SOA services. By these relationships and considering commonalities among several applications in a domain, we propose three systematic methods to migrate from object-oriented system to SOA services. Each method consists of a list of input and output artifacts and detailed guidelines which are performed in order. Through these methods, service developers can easily develop services with less effort.

• The Journal of Society for e-Business Studies
• /
• v.18 no.2
• /
• pp.27-46
• /
• 2013

To reduce time to market for converged services, the service provider needs to combine external services and internal processes together, and IT architecture for converged services has to support it. Service Oriented Architecture (SOA) enables the development of a converged service by combining external services and internal processes effectively. However, it is difficult for the existing SOA methods to support the evolution of a converged service, even though the service which consists of the converged service changes over time. In this paper, we argue that a method for profile-based dynamic service binding is required to support evolution of converged services. In order to identify requirements for the proposed method, a business scenario with a smart athletic equipment is given. We then present the concept and architecture of the method for profile-based dynamic service binding to meet the identified requirements. We also demonstrate a prototype implementation for evaluating the proposed method.

• 한국IT서비스학회:학술대회논문집
• /
• 2007.11a
• /
• pp.230-235
• /
• 2007

현대의 조직은 급격한 업무 환경의 변화와 극심한 경쟁에 대응하기 위하여 정보기술에 상당부분 의존하고 있다. 업무 체계가 다양하고 복잡해지면서 이들 체계 간의 연계를 효과적으로 하여 조직의 전략들 달성하는 것이 중요하며, 또한 업무의 민첩성과 유연성을 확보할 수 있도록 정보체계를 구축하는 것이 필요하다. 이를 위하여 전사적 아키텍처(EA)와 서비스 지향 아키텍처(SOA)가 각광을 받고 있으나, 이들은 일회성 프로젝트로 추진하여서는 섬과를 얻을 수 없으며, 지속적인 관리가 필요하다. 이를 뭐하여 EA 거버넌스와 SOA 거버넌스가 필요하다. 이들 간의 어떤 관계가 있는지를 고려하며 어떻게 구축할 것인가를 설명하였다.

• Journal of Digital Contents Society
• /
• v.15 no.1
• /
• pp.77-85
• /
• 2014

The Service Oriented Architecture has been adopted to be able to handle various types of user requirement flexibly. This concept supports to identify service units, organize that units and integrate them to make a software system. In this paper, we introduce SOA to improve legacy system for reducing duplicated functions and relax the difficulties of maintenance. We try to analyze function flow of warehouse management system and reorganize it to reduce duplicated implementation. Also the system architecture is tried to improve considering connection with other ERP systems.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.14 no.6
• /
• pp.131-137
• /
• 2014

Service Oriented Architecture(SOA) is a flexible structure which does not affect other services even when a specific service is changed. It provides the platform with neutral interfaces independent of any others, where services are loosely coupled in a standard way. While ESB (Enterprise Service Bus) is a key technology for service-oriented architecture, few research and development for ESB has been done. In this paper, we designed and implemented the key components of ESB such as mediation service, message oriented middleware service, operation service, monitoring service, application connection service, and database connection service. The performance evaluation was done by measuring the message processing time for the number of messages with various sizes.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.3
• /
• pp.257-262
• /
• 2010

SOA (Service-Oriented Architecture), which has become very popular recently, is a new paradigm for software development and application. In this paper, we propose an integrated architecture which is able to effectively manage and control a variety of services for U-City projects focusing on the importance of service integration. SOA has a number of important features such as loose coupling, standard bases, and distributed computing, all of which are the essential elements for merging and providing various services in U-City projects. We exploit the ESB (Enterprise Service Bus) for reflecting those features, which is a core module linking mutually heterogeneous components so that the communication of services can be implemented. In this paper, we discuss the necessity of SOA in U-City services and a possible scenario and method for the implementation. Finally, we propose an integrated architecture for the U-City Integration and Management Center.

• 한국IT서비스학회:학술대회논문집
• /
• 2007.11a
• /
• pp.413-418
• /
• 2007

국내 외 많은 컨설팅 및 SI회사들이 나름대로의 SOA방법론을 개발 및 적응하고 있다. 하지만 각 회사의 방법론 마다, SOA 사상 관점에 따라 접근 방향이 상이하고, 수행 방법과 태스크 또한 실제 적응하기에는 상세성이 부족하다. 이 연구에서는 국내 외 SOA 방법론을 비교 분석하고, 실제 적응된 사례를 통하여 특정 도메인에 무관한 현업 사용자 위주의 서비스 식별이라는 명제를 반영한 유저인터페이스 기반의 서비스 분석 및 모델링 방법론을 제시한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2010.06b
• /
• pp.126-131
• /
• 2010

IT 자원의 상호운용성 및 재활용성 등의 장점 통하여 새로운 비즈니스 환경변화에 가장 빠르게 대응할 수 있는 최적의 대안으로 서비스 지향 아키텍처(SOA : Service Oriented Architecture)가 최근 각광받고 있다. 그러나 구현의 복잡성 및 그에 따른 낮은 ROI(Return on Investment) 평가와 같은 SOA의 문제점들을 보완하기 위해 웹 지향 아키텍처(WOA: Web Oriented Architecture)가 제안되었다. 하지만 WOA 또한 보안 및 안정적인 메시지 전달 등의 문제점들을 안고 있다. 본 논문에서는 SOA와 WOA 구현의 핵심 개념을 연구하고, SOA 또는 WOA를 이용하여 서비스를 구현할 경우 중요한 핵심 개념의 복잡도를 AHP(Analytic Hierarchy Process) 기법을 통하여 평가하였다. 이를 통하여 SOA 또는 WOA 구현 시 요구되는 핵심 요구사항의 중요도를 평가하고 개발자에게 미치는 구현 복잡도를 측정할 수 있다.

• Journal of Korea Multimedia Society
• /
• v.12 no.1
• /
• pp.122-129
• /
• 2009

Incorporating proprietary existing it solutions like legacy systems or vendor specific with new technologies is an expensive and time consuming task. Such situations take place due to the lack of ability of proprietary software to cooperate with other parties or to cooperation only with specific vendor products. Such a situation is undesirable and causes a prolonged adaptation period for new applications. This thesis is to show the new approach to creation of Internet applications in Service Oriented Architecture through loose coupling, introduces fare more flexibility into a system composed of connected applications. This approach allows one to integrate through XML based Web Service and reuse a number of arbitrary services available over the Internet in a complex processes specified as a workflow model.

• Journal of KIISE:Software and Applications
• /
• v.35 no.2
• /
• pp.70-80
• /
• 2008

Today, businesses have to respond with flexibility and speed to ever-changing customer demand and market opportunities. Service-oriented architecture (SOA) is the best methodology for minimizing the complexity and the cost of enterprise-level infrastructure and for maximizing the productivity and the flexibility of an enterprise. Most of the enterprise-level SOA delivery strategies deal with the top-down approach, which organization has to define the business processes, to model business services, and to find the required services or to develop new services. However, a lot of peoples want to maximally reuse legacy component-based systems as well as to deliver SOA into their organizations. In this paper, we propose a bottom-up approach for identifying business services with proper granularity. It can improve the reusability and maintenance of services by considering not data I/O of components of legacy applications but GUI event patterns. Our proposed method is applied to MIS with 129 GUIs and 13 components. As a result, the valiance of the coupling value of components is increased five times and three business services are distinctly exposed. It also provides a 49% improvement in reducing the relationship problems between services over a service identification method using only partitioning information of components.