• Journal of Computing Science and Engineering
• /
• 제4권4호
• /
• pp.253-275
• /
• 2010

In this article we review the metaphor of service-oriented architecture for enterprise computing. In typical definitions service-oriented architecture appears as a single message and a consistent roadmap for building flexible software system landscapes. But it is not. Different communities have elaborated different SOA (service-oriented architecture) concepts to address different problem areas, i.e., enterprise application integration, business-to-business, business process management, and software productizing. If software architects and software managers are aware of these strands of SOA when talking about SOA in their projects they can avoid misunderstandings and detours better. This article contributes a clarification of the different strands of SOA concepts and technologies and their mutual dependencies and identifies particular SOA concepts as instances of more general software engineering principles.

• Journal of Information Technology Applications and Management
• /
• 제17권4호
• /
• pp.107-126
• /
• 2010

IT capability is one of the main research topics in MIS area. Given the finding that IT investment does not necessarily contribute to better organizational performance, the concept of IT capability was selected as an alternative antecedent variable for IT's effect on performance. A number of existing MIS papers have shown that firms with the high level of IT capability lead to a better performance. However, very little research has been done concerning the issue of how the IT capability could be enhanced. Recently, enterprise architecture effort has been emerged as an avenue to better IT management. This study aims to empirically examine the relationship between EA effort and IT capability.

• 한국데이타베이스학회:학술대회논문집
• /
• 한국데이타베이스학회 2002년도 추계 컨퍼런스: 기업경쟁력 강화를 위한 디지털 컨텐츠 및 정보기술 컨퍼런스
• /
• pp.431-455
• /
• 2002

최근 Enterprise Architecture(EA)에 대한 관심이 매우 높아지고 있다. 공공분야 뿐만 아니라 민간분야에서도 정보화 노력에 아키텍처의 개념을 도입하려 하기 때문이다. 그러나 실제로 이들 조직에서 아키텍처의 개념을 도입하려는 노력은 매우 다양하다. 즉, 아키텍처 도입의 목적, 범위, 접근 등의 관점에서 매우 다양할 뿐만 아니라 시대에 따라 변해오고 있다. 이러한 아키텍처 도입의 다양성은 아키텍처의 본질적 모습에 대해 많은 혼란을 초래하고 있다. 최근 이 EA의 도입이 가시화되고 있는 실정에 비추어 이 EA의 개념적 실체를 보다 분명히 할 필요가 있다. 따라서, 본 연구에서는 현재 수행된 EA 산출물을 분석해봄으로써 EA 노력을 체계적으로 분류하고 이들 노력의 특성을 밝히고자 한다. 이러한 연구결과는 EA를 보다 정확하게 이해하고, EA 도입 프로젝트의 방향을 설정하는데 기여를 할 것이라고 본다.

• 한국전자거래학회지
• /
• 제2권2호
• /
• pp.31-54
• /
• 1997

While Electronic Commerce is believed to provide new opportunities and environments toward the information society, not many companies have achieved successful construction of Electronic Commerce systems regarding their own technology factors and business process types. This work provides a brief review of Electronic Commerce information infrastructure based on the technology architecture developed. Three major technologies-telecommunication, information processing, and process enhancement - support the architecture, and each major technology consists of its technical enablers. Also, the application factors of Electronic Commerce are defined and analyzed in term of inter-enterprise, intra-enterprise, and enterprise-consumer interactivity. Finally, the implementation strategy is drawn with respect to the technology architecture and three application types.

• 한국전자거래학회:학술대회논문집
• /
• 한국전자거래학회 2005년도 e-Biz World Conference 2005
• /
• pp.62-67
• /
• 2005

In traditional approach, enterprise-wide consistent security policy enforcement for applications is very difficult task. Therefore, industry is now moving towards new unified enterprise application security concept that consist of centralized authentication and authorization mechanism. The eXtensible Access Control Markup Language (XACML); an XML-based standard defined by OASIS, is most suitable choice which can support centralized, role based, context aware access control mechanism. It is designed to provide universal standard for writing authorization policies and access control request/response language for managing access to the resources. This paper includes a brief overview on XACML and discusses its benefits, limitations and a data flow process. We propose a new generic access control architecture that supports enterprise wide centralized application level access control mechanism using XACML. The other benefits which can be achieved through this architecture are, reduce adnministration cost and complexity, support of heterogeneous computing platforms, centralized monitoring system, automatic fail over, scalability and availability, open standard based solution and secure communication.

• 한국IT서비스학회지
• /
• 제9권2호
• /
• pp.179-192
• /
• 2010

In order to resolve the problems of traditional Enterprise Application Integration (EAI) for system integration and to establish flexible enterprise IT environments, Enterprise Service Bus(ESB) which have distributed architecture and support Service Oriented Architecture(SOA) has introduced. Particularly, JBI which developed by the Java Community Process is most widely used to implement ESB for advantages of Java technology. In ESB based on JBI, reliable message delivery is very important to ensure stability of services and systems because it is a message driven architecture. But, it is difficult to verify messages and trace messages when system fault or service error occurred because JBI specification is not enough to address them. In this paper we has proposed the Message Monitoring Framework for JBI-based ESBs which for using in monitoring messages efficiently. It provides foundations for gathering and tracing message-related information about component installation, message exchange, service deploy by using proxy-based change tracking and delegation mechanism for data processing. The proxy which used in our solutions collects data about message automatically when it changed, and the delegation mechanism provides users flexibility for data processing. Also, we describe the performance evaluation results of our solution which is acceptable. We expect to it enables users to ensure reliability and stability of the JBI-based ESB by systematic monitoring and managing messages being used to interact among components.

• 정보화연구
• /
• 제10권4호
• /
• pp.451-466
• /
• 2013

기업들은 정보기술 리스크(IT Risk)에 대하여 어떻게 대처하고 있을까? 금융기관이나 공공기관은 태생적으로 이미 위험관리를 적극적으로 수행하고 있다. 정보기술에 대한 위험관리도 지난 10년동안 전산망 마비, 해킹 사고, 디도스 공격, 고객정보 유출 등을 겪으면서 적극적으로 대응해 왔다. 특히 2011년 농협사태는 IT 성과보다는 IT 보안을 훨씬 중요하게 보는 계기가 되었다. IT 보안 인력과 예산이 대폭 강화되고 망분리 사업이 추진되는 것이 대표적인 사례이다. 하지만 그동안 IT 위험관리는 특정 기술에 대한 사전 대응 및 사후 대응 강화에 집중되었다. 현재 IT 위험관리는 단편적 관리에서 종합적 관리로 전환되고 있다. 최근에 많은 기업들이 전사 차원의 정보기술 리스크 거버넌스(IT Risk Governance) 체계를 구축하고 있거나 구축하는 계획을 갖고 있다. 하지만 아직도 IT보안은 전사적으로 통합되지 못하였으며, IT 위험관리 프로세스는 조직에 내재화 되지 못 하였고, IT 성과관리와 연계성은 고려하지 못하고 있다. 본 논문에서는 IT 관리와 기술을 효과적으로 연계하기 위하여, 그리고 IT 성과와 IT 위험을 균형되게 관리하기 위하여 엔터프라이즈아키텍처(EA: Enterprise Architecture) 활용을 제안하고자 한다.

• 한국IT서비스학회지
• /
• 제7권4호
• /
• pp.45-60
• /
• 2008

Networked enterprise (NE) is an organization of independent companies that collaborate with each other temporary or permanently for accomplishing common goals. The USA and EU have been developing principal concepts, techniques, and solutions to enhance the competitiveness of traditional industries including small-and-medium enterprises (SMEs). In Korea, however, implementation as well as R&D of NE is very few, which we believe comes from lack of understanding on Its meaning and lack of effective information systems for it. This paper is to suggest an Enterprise Architecture (EA) framework or reference model of NE and an Information Technology Architecture (ITA) of NE. The EA framework will help stakeholder of NE (e,g., policy makers, members of NE, IT solution providers, and researchers) understand structural and behavioral characteristics of NE. The ITA will be used as a guideline of developing information systems for NE that is essential for spreading networked business models, The focus of this paper is not on logical-level design but on conceptual-level modeling of NE. As verification of the suggested framework and architecture is still required, so we'll apply them to various manifestations of NE, e.g., dynamic supply chain, vertical integration of extended enterprises, and P2P-style virtual enterprises.

• Journal of Information Technology Applications and Management
• /
• 제14권1호
• /
• pp.37-55
• /
• 2007

Enterprise Architecture (EA) is one of controversial subjects theses days. Some organizations, public or private, are very impetuous in adopting it and some are quite Indifferent to it. What makes this difference come about? This is our research question. One previous research has studied on this issue under the theory of diffusion of innovation. Instead, we here attempt to investigate, in the context of technology transfer theory, the influencing factors on the adoption of EA. We are especially interested In whether korea local organizations are more Influenced by 'need pull' factors than 'institutional push' factors or vice versa.

• 한국전자거래학회지
• /
• 제8권1호
• /
• pp.35-54
• /
• 2003

소프트웨어 개발공정 상의 요구사항 문서적 분석에 치중되어 있던 요구사항 분석에 관한 논의는 기업 통합을 더욱 효과적으로 하기 위해 소프트웨어적 차원을 넘어 기업 아키텍처 기반의 정보시스템 개발 및 통합의 필요성에 대한 논의로 확대되고 있다. 본 연구에서는 궁극적으로 기업 아키텍처의 효과적인 수립을 지원하는 요구사항 분석, 관리 프레임 웍과 분석 프로세스를 제시한다. 요구사항 분석 프로세스는 기업 아키텍처의 개념을 바탕으로 다양한 사용자와 관점이 구별하고, 이를 다시 요구사항 추출을 위해 업무적 관점과 정보시스템 관점으로 구분한다. 이러한 요구사항 분석을 위한 프로세스는 기업 아키텍처의 수립을 효율적으로 지원할 것이다.