• Journal of Korea Society of Digital Industry and Information Management
• /
• v.8 no.4
• /
• pp.167-175
• /
• 2012

Service-oriented Architecture(SOA) is one of the most recent trends in IT solutions. SOA is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains and implemented using various technology stacks. From a technical perspective SOA, can be considered a method for designing and developing IT systems where applications are constructed from loosely coupled and autonomous building blocks. And SOA is a very effective response to the problems faced by companies in terms of reusability, interoperability and reduce coupling between systems that implement their information systems. To exploit these advantages many organizations have decided to evolve their legacy systems towards this architecture. This paper proposes a modeling for SOA based business process generation and testing, and introduces its implementation in the BPEL. And we analyze business process between enterprises, modeling the service-oriented business process with BPEL to realization level. Also, we suggests that UML is used from high-level business problems to the process of low-level problem for Visual and effectively.

• 한국IT서비스학회:학술대회논문집
• /
• 2005.11a
• /
• pp.575-582
• /
• 2005

웹서비스가 등장 하면서 주목받기 시작한 서비스 지향 아키텍처 (Service-Oriented Architecture)는 이 기종 애플리케이션 간의 상호운용성을 보장하는 웹서비스 기술의 이론적 배경을 제시할 뿐만 아니라 보다 전사적인 관점에서 시스템과 시스템 간의 연계 및 통합을 위한 방법론을 제시하고 있다. 전사적 체계통합 방안인 전사적 아키텍처(Enterprise Architecture)는 조직 내 정보 기술 자원을 효율적으로 통합, 관리 할 수 있는 방안을 제시한다. 서비스 지향 아키텍처와 전사적 아키텍처의 관계는 여러 가지 다양한 관점에서 바라볼 수 있으며, 그 관계를 바라보는 관점에 따라 전혀 다른 형태의 EA를 구축할 수 있다. 글로벌 IT환경 하에 정보체계 간 상호운용성 수준을 향상시키기 위해서는 SOA와 EA간의 관계를 명확히 이해하고, 애플리케이션 수준의 SOA적용을 넘어 전사적 체계통합 관점에서 SOA개념의 효과적인 적용방안을 찾아내는 것이 보다 더 절실히 요구된다. 본 연구에서는 일반적인 소프트웨어 아키텍처 관점에서 EA틀 구성하는 정보기술의 한 요소로 SOA를 적용하는 방안을 살펴보았으며, 비즈니스와 정보기술을 연결하는 연결고리로 전사적 차원에서 SOA를 도입, 적용하는 방안을 제시하였다.

• Journal of Information Technology Services
• /
• v.9 no.2
• /
• pp.193-203
• /
• 2010

Service-Oriented Architecture (SOA) is a new trend for the design of application architecture to enhance the degree of share and reuse with the concept of service. It comes from the current situation where the business environments are changing rapidly and therefore competitions are getting bitter. To cope with such business challenges, business (and/or applications) architecture needs considerably flexibility and reusability, and that's why SOA is accepted as one of the most effective framework for the business applications in these days. In this paper we propose an analysis and design methodology for the applications of SOA. To implement the proposed methodology, the service ontology needs to be defined first, and the tasks such as service profiling, workflow design and service orchestration need to be followed. To validate the expected effects on flexibility and reusability, the proposed methodology was compared with CBD (Component Based Development).

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.25 no.1 s.212
• /
• pp.34-39
• /
• 2007

국내외적으로 차세대 아키텍처인 SOA(Service Oriented Architecture)에 대한 관심이 높아지고 있으며, 수년 내에 SOA가 일반적인 아키텍처가 될 것으로 전망되고 있다. 하지만, SOA를 실제로 구축하고 활용하기에는 많은 장벽들이 존재하고 있다. 본 논문에서는 SOA기반의 Application을 구축하기 위해 필요한 컴포넌트 규격에 대한 연구와 함께 기존의 분산 객체 컴포넌트를 확장하여 비즈니스 컴포넌트로 구축 가능하게 지원하는 SCA(Service Component Architecture)를 기반으로 SOA를 구축하는 방안을 제시하여, SOA의 장점인 유연성과 상호운용성을 보장하는 Application 구축에 활용이 가능하도록 하고, 이론 및 사상적인 측면에서 벗어나 현실화된 Architecture로써 SOA가 도입 될 수 있도록 하고자 한다.

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

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.169-178
• /
• 2006

In both inside and outside of our country, the interest of the new generation S/W architecture, the SOA(Service Oriented Architecture) is whooped up. We expect that the SOA will become general S/W architecture in several years, but the most compaines of S/W Industry still think that the SOA have much risk to adapt as their s/w architecture. In this paper, We performed the senario based verification of the SOA quantitatively and qualitatively, and presented the validity of the S/W architecture view and the method of adoption of the SOA.

• International journal of advanced smart convergence
• /
• v.7 no.3
• /
• pp.79-91
• /
• 2018

Service Oriented Architecture (SOA) has appeared as an absorbing architectural approach that empowers the available systems to reveal their performance in the act of services, without creating important changes to the systems. This approach, due to its flexibility of adoption, has been widely recognized as an appropriate approach for implementing in organizations by many scholars and practitioners. Though, there are many studies that depict success factors of SOA; at the same time a few minor cases of failure has also been reported in the literature. In spite of the availability of rich material on SOA (in general), there is no systematic literature review on the potential aspect of SOA adoption factors. Hence, this article presents a systematic review of existing studies related to the SOA adoption and its success and failure factors from 2009 to 2015. The principle purpose of the study is to bring forward the existing issues and share our findings with researchers. Moreover, the findings of this paper would help IT experts in organizations to concentrate on the key factors highlighted in this study, so that they could decide whether it is advisable to adopt SOA or not in their context.

• Journal of the Korea Society of Computer and Information
• /
• v.12 no.4
• /
• pp.21-31
• /
• 2007

This Paper presents an SOA framework that enables smooth provision of service to ordinary users while also replacing the current B2B environment-oriented SOA framework. To that end, the proposed SOA will be reviewed for its concept, characteristics, and components. Key to its design is that it will be implemented using the prospective next-generation P2P platform known as JXTA. The proposed framework includes all the basic functions of other SOA frameworks, and will make Provision and use of services more easy compared with other frameworks. Under this service, data and applications controlling these data are provided in an enabling format, thereby addressing security problems. Another advantage of this proposed framework is that each peer is able to play all roles of a service provider, service client, and service registry.

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

• Journal of Digital Contents Society
• /
• v.8 no.2
• /
• pp.107-112
• /
• 2007

With the evolution to distributed computing technology, the concept of conventional client/server function has been advanced to Service-Oriented Architecture, which can share the information between heterogeneous systems as services. To success Service-Oriented Architecture, the conjunction between business layer and application layer is one of the important techniques. In this paper, we classify services into two views, vertical and horizontal, and introduce matching technique with service classification for SOA.