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

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

• The Korean Journal of Archival Studies
• /
• no.60
• /
• pp.283-315
• /
• 2019

The emergence of new business models software industry is demanding a change to technology that can cope quickly and flexibly. In this regard, microservices, which is being addressed as the architecture of the next-generation record management system, has emerged as an agile and convenient architecture. If record-management system with micro-service is developed, agility and expandability with basement of innovation can be ensured. The purpose of study is to suggest efficient ways when record-management system with micro-service is built. For this, tranditional architecture has been checked and main features of micro-service have been explained. Also, it was summarized that three points : 'Short history of micro-service', 'Maturity of technology' and 'Techical level of project team' have to be reviewed when record-management system with micro-service architecture is built. And we suggested some issues to consider when constructing the records management system applying microservices according to the domestic environment.

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

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

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

다양한 의료서비스를 정형화되고 효율적인 방법으로 제공하기 위하여 최근 의료기관의 EMR(Electronic Medical Record; 전자의무기록) 시스템의 도입이 급속도로 확산되고 있다. 그러나 국내에서 구축되고 있는 EMR은 초기에 기대했던 EMR의 도입목적을 중분하게 달성하지 못하고 있다. 이는 근본적으로 EMR의 방향성과 구조에 한계를 지니고 있기 때문이다. 국내에서 구축되고 있는 대부분의 전자의무기록시스템은 자료수집원 지향 의무기록 (Source Oriented Medical Record; SOMR) 방식으로 개별 사실을 수집하고 제시하기 위한 관찰자 중심, 서식중심의 시스템이며 차트 이송과 종이를 없애는 것이 주목적이다. SOMR 방식은 EMR의 다양한 도입목적, 특히 임상자료의 효과적 활용을 충족시킬 수 없는 태생적인 한계를 지니고 있기 때문에 문제지향 의무기록 (Problem Oriented Medical Record; POMR) 방식의 EMR과 적절한 혼용전략 (Hybrid Strategy)이 절실히 요구된다. 본 연구의 목적은 SOMR 시스템과 POMR 시스템이 보완적으로 결합된 하이브리드 EMR 아키텍처를 제시하고 아키텍처를 구성하는 데 필요한 기술적 요소들과 그들간의 상호관계 틀 파악한 후 이를 기반으로 개발방법론을 도출하는 것이다. 또한 만성신부전증 환자 사례를 이용하여 앞서 제시된 개발방법론에 따라 프로토타입을 개발하였다. 본 연구는 EMR 시스템이 SOMR 구조에만 편향됨으로써 발생될 수 있는 다양한 문제들을 해결함으로써 진료의 품질 항상, 임상연구의 활성화, 조직적이고 과학적인 진료계획의 수립과 같은 소외되어 왔던 EMR의 목표를 실현할 수 있을 것으로 기대 된다.

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

• The Monthly Technology and Standards
• /
• s.85
• /
• pp.31-35
• /
• 2009

• Proceedings of the Korea Association of Information Systems Conference
• /
• 2005.05a
• /
• pp.266-272
• /
• 2005

비즈니스 전략 및 환경이 정적인 환경에서 동적인 환경으로 변화의 필요성이 요구되는 유비쿼터스 환경에 제공되는 서비스가 언제, 어디서나, 쉽게 접근하기 위한 이동성을제공하기 위한 기술로 모바일 서비스의 중요성이 대두되고 있다. 현재 웹 서비스에서 사용하고 있는 요청-응답방식의 모바일 환경에서 일관성을 유지하기 힘들다. 서비스 지향 아키텍처를 기반으로 이동성을 고려한 아키텍처를 정의할 필요가 있다. 따라서 에이전트 컴퓨팅아키택처에 의해 상호운영성이 높은 모바일 에이전트 컴퓨팅을 통하여 모바일 환경에서 사용자의 접근을 용이하게 하고 컴포넌트를 이용한 개발의 효율성을 향상시킬 수 있어야 한다. 본 논문에서는 PDA 서비스를 위해 모바일 에이전트를 이용하여 이를 위한 컴퓨팅 환경을 제공하기 위해서 모바일 에이전트 아키텍처를 정의하고 각 레이어에서 식별된 컴포넌트를 개발하기 위한 프로세스를 제시하고자 한다.