• The KIPS Transactions:PartD
• /
• v.17D no.5
• /
• pp.317-326
• /
• 2010

Service Oriented Architecture (SOA), which supports various features such as interoperability and reusability of IT resources, comes into the spotlight as an effective approach for adapting new business environmental changes. SOA, however, has some problems including the high realization complexity and low Return on Investment (ROI). To solve these problems, Web Oriented Architecture (WOA) has gained attention. However, it also has some drawbacks about security concerns and unstable message transmissions. In this paper, we design a novel integrated architecture that classifies services into inside and outside ones and applies SOA for the former and WOA for the latter, respectively. By converging the advantages of SOA and WOA simultaneously, the proposed architecture becomes more simple and service-oriented, and can satisfy diverse requirements of customers. The usefulness evaluation of the proposed architecture is conducted through the Analytic Hierarchy Process (AHP) scheme.

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

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

• Journal of the Korea Society for Simulation
• /
• v.16 no.1
• /
• pp.49-57
• /
• 2007

Service-Oriented Architecture(SOA) is improving rapidly in IT Environment. Enterprise companies interest in implementation infrastructure based on SOA to adapt quick changes of large and complex distributed environment. SOA is a component model that inter-relates the different functional units of an application, called services, through interfaces and contacts between theses services. In this paper, we studied the concept of the relationship between SOA and standard web service core and therefore, we model the web service based on SOA. We implemented the application and business service architecture using web service that include the XML and SOAP. We confirmed that how the each SOA characters like interoperability, reusability, scalability and flexible business process adapted to web service and present a web service modeling that is maintained the neutrality using loose service coupling through the method of service model process and web service architecture designing methodology based on SOA.

• Journal of the Korea Society for Simulation
• /
• v.16 no.4
• /
• pp.33-41
• /
• 2007

Service-Oriented Architecture(SOA) define the interaction method between two computing entities that one entity performs a unit task instead of another entity. This, unit task, is called "Service" and interaction of these services should have independency and loosely coupled task. The effect of SOA's main functions such as loosely coupled task and independent interoperability with influence the possibility of flexible message communication between different way and different users. In this article, we analyzed the performance about system stabilization between general web service and SOA based application that implemented through WCF based messaging framework using .NET Framework and integrated data presentation method. As the result of test, we confirmed that SOA environment using WCF have more advantages.

• The Journal of Society for e-Business Studies
• /
• v.12 no.2
• /
• pp.75-93
• /
• 2007

Recently, Service-Oriented Architecture(SOA) is on the rise to reduce the complexity of IT infrastructure, minimize cost for maintaining it and maximize the productivity and flexibility in business. SOA increases the adaptability by loosely coupling and it's main feature is that three elements such as service provider, service requester and service registry are connected with each other systematically. These make difficult to adopt traditional development methodologies to implement SOA. In this paper, we suggest a service-oriented development process with regard to the aspect of service provider and service requester. The process consists of six phases and each phase sets up with guidelines and artifacts. It can choose the process type along with the goal in Development Planning.

• Journal of Korea Multimedia Society
• /
• v.14 no.4
• /
• pp.554-566
• /
• 2011

Service-oriented architecture(SOA) is a paradigm where reusable units are independently executable and only accessible through outer interfaces. Standardized methodology based on SOA has not been decided yet although a lot of efforts have been made for systems using SOA. Therefore Development of system using SOA is facing many difficulties currently. In this paper, service oriented methodology of function based model for supporting legacy system is proposed. Standardized methods for function based reusability through analysing SOA methodology are proposed and guide lines for improvement of service reusability are presented.

• The KIPS Transactions:PartD
• /
• v.15D no.4
• /
• pp.513-522
• /
• 2008

Service-Oriented Architecture(SOA) is an method to develop applications by developing and publishing reusable services which potentially be used in various applications, and discovering and composing right services dynamically. SOA adopts a paradigm of publish-discover-invoke, which is considerably different from object-oriented and component-based development(CBD) approaches. The service in SOA is different from function in procedural programming, object in object-oriented programming, and component in CBD, and its fundamental requirement is a high level of reusability and applicability. In SOA, service providers and service consumers are loosely coupled since the providers try to develop reusable services and the consumers try to locate right services without knowing much about the providers and their published services. Moreover, the process of searching, choosing and invoking right services is not presented in conventional programming paradigms. Therefore, conventional approaches to developing user interfaces and invoking the functionality on servers through JSP, and RMI in object-oriented programming cannot well be applicable to designing clients’ programs in SOA. Therefore, there is a high demand for a practical and systematic process for developing clients’ applications, and the such a process should be devised by considering key characteristics of services and SOA. However, little work on this area is known to date, and there has not a process for client side just except few guide lines for developing service client. In this paper, we propose a practical and systematic development process for developing clients' applications in SOA. Then, we define instructions for carrying out each activity in the process. To show the applicability of the proposed work, we show the result of applying our process in developing a services application for searching and booking hotels.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2007.05a
• /
• pp.225-228
• /
• 2007

차세대 보험시스템에서 지향하는 실시간 기업(RTE: Real Time Enterprise) 서비스가 오픈 프레임 플랫폼 기반의 다운사이징으로 구체화됨에 따라 서비스 지향 아키텍처(SOA: Service Oriented Architecture)와 이벤트 기반 아키텍처(EDA: Event Driven Architecture)가 비즈니스 어플리케이션을 변화시키는 주요한 설계 스타일로 등장하게 되었다. 이에 따라 엔터프라이즈 서비스 버스를 통한 서비스 흐름이 업무 서비스간 유연한 결합이 되도록 프로세스 관리 목적에 부합하는 연계성 방안이 필요하게 되었다. 본 연구에서는 이러한 설계 스타일의 SOA 구현방식에 있어서 비즈니스 프로세스관리(BPM: Business Process Management)에 대한 비즈니스 측면과 IT 측면의 연계성 방안을 마련하였다. 이 방안을 도출하기 위하여 관련 디자인 패턴을 연구한 후 BPM 솔루션을 활용하여 연계테스트를 통한 검증을 수행하였고, 이러한 분석결과는 향후 SOA 로 차세대프로젝트를 진행하려는 이용자들에게 아키텍처 수립 및 시스템 개발에 필요한 효율적인 방안을 제공할 수 있을 것이다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2007.05a
• /
• pp.245-248
• /
• 2007

서비스 지향 아키텍처(SOA)는 기업이 적정한 비용으로 오늘날 가장 중요한 IT 요구사항인 민첩성과 유연성을 만족시킬 수 있는 IT 아키텍처 수립의 토대로, 경영환경이 빠르게 급변하는 최근에 떠오른 이슈이다. 기존의 서비스 지향 아키텍처의 서비스 개발은 주로 비즈니스 환경에서 어플리케이션방향으로 접근하는 하향식 방법이 대부분이었으나, 본 논문에서는 이미 개발된 컴포넌트 기반 시스템에서 접근하는 상향식 서비스 식별법을 제안한다. 본 논문에서 제안하는 방법은 사용자의 이벤트 정보를 담고 있는 GUI Flow-Event 를 이용하여 컴포넌트를 서비스로 식별하고, 서비스 식별시 발생하는 서비스간 연관관계에 따른 문제점을 최소화함으로써 비즈니스 도메인에 더욱 가깝고, 약결합을 지향하는 서비스로 식별할 수 있다.

• The Journal of Society for e-Business Studies
• /
• v.16 no.2
• /
• pp.129-142
• /
• 2011

Traditionally research in Service Oriented Architecture(SOA) security has focused primarily on exploiting standards and solutions separately. There exists no unified methodology for SOA security to manage risks at the enterprise level. It needs to analyze preliminarily security threats and to manage enterprise risks by identifying vulnerabilities of SOA. In this paper, we propose a metric-based vulnerability assessment method using dynamic properties of services in SOA. The method is to assess vulnerability at the architecture level as well as the service level by measuring run-time dependency between services. The run-time dependency between services is an important characteristic to understand which services are affected by a vulnerable service. All services which directly or indirectly depend on the vulnerable service are exposed to the risk. Thus run-time dependency is a good indicator of vulnerability of SOA.