• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.137-153
• /
• 2006

SOA(Service Oriented Architecture) can be a technique to make compassable software from mapping business service to software component. To support effective SOA, it is important that services have to be defined or classified more independently for dynamic and reusable composition. Several methods have been issued but no ways to defined service granularities, service type or service unit. In this paper we introduce 3 level views, service level, service granularity to reuse effectively. And, we suggest service definition guidelines using them.

• 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 Korea Society of Industrial Information Systems
• /
• v.17 no.1
• /
• pp.73-93
• /
• 2012

The primary objective of this research is to explain how to implement the Service Oriented Architecture (hereafter SOA) enabled Enterprise Resource Planning (hereafter ERP) system successfully for service industries. An implementation of the ERP system help many organizations to alleviate the difficult job of supporting inflexible or legacy systems that in most cases result in cost increases, data redundancy and inaccuracy, and various inefficiencies. However, the ERP system is losing its market share rapidly to the cloud computing system which utilizes the Software-as-a-service (hereafter SaaS) and SOA. The SOA is an approach to integrate various types of IT resources to leverage existing ERP system, while at the same time building an infrastructure that can readily respond to new business environment and offer new dynamic applications. The companies that implement this system have less of a need for the kinds of all-in-one ERP system that have dominated the back office for decades and can move freely to best-of-breed applications. This research will identify the benefits and costs of the SOA enabled ERP system through case studies and its impact on competitive priorities such as cost, quality, delivery, and flexibility.

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

• The KIPS Transactions:PartD
• /
• v.14D no.7
• /
• pp.829-840
• /
• 2007

Dirty Data Cleansing technique so far have aimed to integrate large amount of data from various sources and manage data quality resided in DB so that it enables to extract meaningful information. Prompt response to varying environment is required in order to persistently survive in rapidly changing business environment and the age of limitless competition. As system requirement is recently getting complexed, Service Oriented Architecture is proliferated for the purpose of integration and implementation of massive distributed system. Therefore, SOA necessarily needs Data Exchange among services through Data Cleansing Technique. In this paper, we executed quality management of XML data which is transmitted through events between services while they are integrated as a sole system. As a result, we developed Dirty Data Cleansing Service based on SOA as focusing on data cleansing between interactive services rather than cleansing based on detection of data error in DB already integrated.

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

Various business model and computing environments are currently merged into web services and many web related application products are also develop. Most of IT enterprises in Korea use the Service-oriented architecture (SOA) whenever they develop the web applications. SOA is an approach to loosely coupled, protocol independent, standards-based distributed computing where software resources available on the network are considered as Services. SOA is believed to become the future enterprise technology solution that promises the agility and flexibility the business users have been looking for by leveraging the integration process through composition of the services spanning multiple enterprises. But, There are no specific development methodology to apply into SOA standard model until now. The developer uses the currently existing methodology to develop the application with SOA. The users have some limitations to use it. In this paper, we suggest a Frameworks for applying agile methodology into SOA to address the productivity and quality of small web related project. We design and implement a frameworks architecture for applying the agile method into SOA and describe the process model to implement it. We finally evaluate the frameworks with productivity, flexibility and maintainability.

• The KIPS Transactions:PartD
• /
• v.18D no.6
• /
• pp.461-480
• /
• 2011

Component-Based Development (CBD) focuses on developing reusable components and assembling them into target applications. Service-Oriented Computing (SOC) is a relatively new paradigm where reusable services are developed, published, and composed into target service applications. Due to the popularity of CBD, many organizations already have CBD models for their applications. Hence, it is feasible and appealing to develop SOC applications economically by transforming existing CBD models, rather than developing SOC applications from the scratch. Our research is to develop a methodology for transforming existing CBD design into Service-Oriented Architecture (SOA) design. In this paper, we first compare the two paradigms and their key elements for the design; CBD design and SOA design. Then, we define mapping relationships of the transformation. For each transformation mapping, we present step-wise instructions. The benefit of applying this transformation is to increase reusability of existing design assets, to maintain the consistency between existing CBD and SOC models, and reduced cost for deploying service-oriented applications.

• Journal of the Korea Safety Management & Science
• /
• v.12 no.4
• /
• pp.247-254
• /
• 2010

In this study, we reviewed SOA from the points of the concept, definition, technical components. Additionally, we derived seven critical factors which can lead SOA project to success: top level support, employees education, problem definition, service identification, appropriate development method, continuous development, start from small success.

• Information Systems Review
• /
• v.12 no.2
• /
• pp.105-119
• /
• 2010

SOA has become the focus of attention as it is perceived as a concept toward integrative service which helps companies respond quickly to the changes in market needs. This study is aimed to find out success factors for building SOA. We carried out two case studies on companies that adopted SOA successfully in Korea and conducted a survey to collect opinions from experts and experienced managers whose job is related to SOA. The critical successful factors found in this study include: 1) establishment of the SOA taskforce based on CIO's strong support, 2) formation of the corporate-wide consensus and the adoption of standards, 3) active user participation in defining services and obliterating duplication, 4) accomplishment of flexibility in services and business agility based on integrated infrastructure, and 5) securing project budget and consistent support by way of using measurement index for SOA investment effects.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2007.11a
• /
• pp.610-613
• /
• 2007

SOA(Service Oriented Architecture)는 컴포넌트와 서비스의 재활용을 최대화하도록 설계된 아키텍쳐이다. 서비스와 컴포넌트의 재활용뿐만 아니라 기존 레거시 시스템의 재활용도 주요한 이익의 하나이다. 레거시 시스템의 활용도는 프로젝트 내에서 레거시 컴포넌트를 재사용한 횟수와 레거시 컴포넌트를 다른 시스템이나 프로젝트에서 재사용한 횟수를 더하고 이를 프로젝트의 전체 서비스 컴포넌트 수로 나눠서 계산할 수 있다. 본 연구에서 도출한 레거시 컴포넌트의 재활용도 측정한 향후 SOA기반의 프로젝트를 수행하고 난 후 기조의 레거시 시스템을 어느정도 재활용하였는지 측정할 수 있게 되어 IT투자 분석의 기초 자료로 활용될 수 있을 것이다.