• Journal of Computing Science and Engineering
• /
• v.4 no.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 Services
• /
• v.9 no.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.

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.25 no.8 s.219
• /
• pp.9-14
• /
• 2007

• The Journal of Society for e-Business Studies
• /
• v.14 no.3
• /
• pp.1-13
• /
• 2009

EAI(Enterprise Application Integration) as an infrastructure of application integration had played an important role for many companies to make epochal changes, expense reduction, and new application services. The continuous monitoring and management of data covering whole environment of system operations should be well-supported so that the data consistency and system stability are guaranteed to implement and operate the services effectively. In this paper, the requirements and functions of monitoring system are defined for the stable EAI service. An actual web-based system is designed and implemented. This web-based monitoring system is broadly applicable to general EAI environments.

• The Journal of Society for e-Business Studies
• /
• v.11 no.2
• /
• pp.71-91
• /
• 2006

Nowadays most enterprise want to organize all Information Technology elements for their vision and mission accomplishments by integration view Enterprise architecture is used by the solution. But IT is so more complex that it can't cover application development. This research defines software architecture framework by enterprise view and designs enterprise architecture framework for embracing application development. Software architecture framework consists of meta architecture, conceptual architecture, logical architecture, physical architecture. For enterprise architecture framework including enterprise software architecture framework, this research analyzes its perspectives and Views. After all, This research able to apply to systematic application development based on enterprise architecture and completely IT elements organization by enterprise view.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.30 no.4
• /
• pp.96-102
• /
• 2007

The most fundamental method in IT innovation up to today is the SOA which has been accepted as the standard for the system integration and makes the business more flexible. Although it is important to classify the workflow of enterprise into the unit of services, there is no systematical research on this topic yet. This paper proposes a SOA deployment methodology, which composed of 6 steps. By utilizing this methodology, an enterprise can build up the SOA applied environment easily to achieve its business objectives and to make a linkage between services and business processes more effectively and efficiently, which is proved through Analytic Hierarchy Process. It is considered that Service Oriented Architecture can be the future standard for the IT integration beyond the individual application.

• IE interfaces
• /
• v.19 no.1
• /
• pp.62-69
• /
• 2006

In these days companies are rapidly implementing the extended enterprise collaboration to provide enhanced management services and products based on the enterprise integration that human resources, technologies and the management process. In this corporate environment, ASP (Application Service Provider) which is the developed type of outsourcing in the area of information technology, is a good alternative for corporate information system management. ASP defines as a software leasing service which is supplied through networks instead of purchasing application software with high price. For successful implementation of ASP, it is necessary to develop the certification methodology to ensure safety and reliability of ASP. The paper provides the safe and reliable certification methodology for ASP. In order to develop it, the critical issues related to service quality and certification of ASP are identified and the systematic certification methodology of application and service provider(service environment) domains of ASP are provided. A evaluation method for the developed certification methodology is also proposed.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.4
• /
• pp.392-404
• /
• 2010

Recently, as both business processes and IT systems become ever more complex. Especially, enterprise applications tend to become unmanageably complex and increasingly costly to maintain. Therefore complexity is the insidious enemy of software development. It is critical to have a methodology that recognizes and manages this enemy effectively. In this paper, we propose ISIS (Integrated System of Independent Subsystems) - the architectural style needed to develop the complex enterprise applications. The ISIS was developed to meet the challenge of reducing the complexity of a larger enterprise application today. It gives us architecture models for reducing development complexity and composite application. The enterprise application is partitioned into a collection of independent subsystems using ISIS decomposition schemes and equivalence relations. We use middleware named ISIS engine that provides a service for subsystems interoperability by enabling the integration of distributed, cross-platform subsystems. We have implemented an ITSM system that achieves our objectives, reducing development complexity, using the ISIS architecture. Finally, ISIS architecture provides greater flexibility and productivity when an organization needs either to change its business processes, or to update the underlying systems.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.21 no.45
• /
• pp.33-45
• /
• 1998

The typical characteristic of PDM(Product Data Management) System seperates the databases to store the meta data and applications. Therefore, meta data contains the information for the location of file, user profiles, relationships between the files, and process. PDM utilizes these information efficiently and does file management, configuration management, and process management. In this view, the integration strategy of PDM is to merge data and process. In the view of architecture, the interface between data and application and the actions of each application execute seamlessly. This architecture is viewed as integrated data and process among enterprises and implemented with client/server technology in distributed process environment that interfaced with open object-oriented technology which is developed with business object in the object-oriented infrastructure. In this paper, we studied the definition, function, and scope of PDM and researched the core technologies to implement the PDM integration environment. We also researched the PDM utilization in distributed enterprise environment and implementation of PDM integration environment with this technical background.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.11 no.1
• /
• pp.56-65
• /
• 2007

Existing application systems of enterprises can process and collect a lot of information within enterprises, but it could be difficult to share validated information with partners and other system in the process of contacting to other legacy systems required in cooperation environment. For solving these problems, EAI systems are introduced in cooperation environment so that data sharing and integration can be achieved. The integration based on EAI is not limited to particular business system but all systems of an enterprise so that standard of suitable metadata level is needed for forwarding consistently between each business of systems. Therefore this paper maintains consistency of data sharing and integrating among legacy systems in cooperative environment for proposing message exchanging based on bridge XMDR.