Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

An Architecture-Centric Approach for Information System Architecture Modeling, Enactement and Evolution

International audienc

The Value Proposition of Service-Oriented Architecture

The author of this thesis evaluates Service-Oriented Architecture (SOA) design and implementation strategies. The purpose is to provide the reader with the definition of Service-Oriented Architecture. This report discusses: (1) The definition of Service-Oriented Architecture, (2) The problems solved by Service-Oriented Architecture, (3) Application of design principles to achieve Service-Oriented Architecture. As a result of this investigation, Service-Oriented Architecture is a design style that is fundamentally about sharing and reuse of functionality across diverse applications, so that organizations can quickly adapt to changing business requirements while increasing IT asset reuse and minimizing integration and development costs

E-Governance Frameworks - Agenda Ahead

Electronic governance may be defined as the delivery of the government services and information to the public using electronic means. Use of IT in the government facilitates an efficient, speedy and transparent process for disseminating information to the public and other agencies, and for performing the government administration activities

Benefits and challenges of applying Semantic Web Services in the e-Government domain

Joining up services in e-Government usually implies governmental agencies acting in concert without a central control regime. This requires the sharing of scattered and heterogeneous data. Semantic Web Service (SWS) technology can help to integrate, mediate and reason between these datasets. However, since few real-world applications have been developed, it is still unclear which are the actual benefits and issues of adopting such a technology in the e-Government domain. In this paper, we contribute to raising awareness of the potential benefits in the e-Government community by analyzing motivations, requirements, and expected results, before proposing a reusable SWS-based framework. We demonstrate the application of this framework by a compelling use case: a GIS-based emergency planning system. We illustrate the obtained benefits and the key challenges which remain to be addressed

Technical Risk Management on Enterprise Integration Projects

Enterprise Integration (EI) is essential to organisations wishing to fulfill broader business objectives related to e-business, customer relationship management (CRM), supply chain management (SCM) and business-to-business (B2B) commerce. This paper describes and presents the results of a study into practices for managing technical risk on EI projects. In the study, 21 managers participated in a facilitated workshop or interview sessions to identify areas of risk (RAs) associated with EI projects and risk management practices (RMP) for addressing those RAs. Risks were identified in four separate phases in the lifecycle of an EI project, namely the strategy, planning, implementation and rollout phases. Many of the risks identified were not specific to EI projects, but were applicable to large IT projects in general. The paper is primarily concerned with technical risk although some aspects of business and organizational risk are discussed briefly

Pragmatic Approach for Business Process Migration

With the increasing growth in popularity of software architecture middleware, scalability and availability of a software application in a Service Oriented Architecture becomes a significant challenge .We have developed a strategy to dynamically manage business processes. We target the separation of the two concerns, on one side architectural features, on the other side business features. Our strategy provides an approach to design business process using our "mobile process migration" template. We ensure the availability of process definition when the administrators of the service bus need to reconfigure sites where the business processes are placed. This evolution has to be done during execution. We also ensure the scalability and the autonomy of the business process. This means a process which is able to move from one site to another one unless the business process engine is installed. The business process can become mobile between two service busses and we improve the availability of business processes

An Adaptive Integration Architecture for Software Reuse

The problem of building large, reliable software systems in a controlled, cost-effective way, the so-called software crisis problem, is one of computer science\u27s great challenges. From the very outset of computing as science, software reuse has been touted as a means to overcome the software crisis issue. Over three decades later, the software community is still grappling with the problem of building large reliable software systems in a controlled, cost effective way; the software crisis problem is alive and well. Today, many computer scientists still regard software reuse as a very powerful vehicle to improve the practice of software engineering. The advantage of amortizing software development cost through reuse continues to be a major objective in the art of building software, even though the tools, methods, languages, and overall understanding of software engineering have changed significantly over the years. Our work is primarily focused on the development of an Adaptive Application Integration Architecture Framework. Without good integration tools and techniques, reuse is difficult and will probably not happen to any significant degree. In the development of the adaptive integration architecture framework, the primary enabling concept is object-oriented design supported by the unified modeling language. The concepts of software architecture, design patterns, and abstract data views are used in a structured and disciplined manner to established a generic framework. This framework is applied to solve the Enterprise Application Integration (EM) problem in the telecommunications operations support system (OSS) enterprise marketplace. The proposed adaptive application integration architecture framework facilitates application reusability and flexible business process re-engineering. The architecture addresses the need for modern businesses to continuously redefine themselves to address changing market conditions in an increasingly competitive environment. We have developed a number of Enterprise Application Integration design patterns to enable the implementation of an EAI framework in a definite and repeatable manner. The design patterns allow for integration of commercial off-the-shelf applications into a unified enterprise framework facilitating true application portfolio interoperability. The notion of treating application services as infrastructure services and using business processes to combine them arbitrarily provides a natural way of thinking about adaptable and reusable software systems. We present a mathematical formalism for the specification of design patterns. This specification constitutes an extension of the basic concepts from many-sorted algebra. In particular, the notion of signature is extended to that of a vector, consisting of a set of linearly independent signatures. The approach can be used to reason about various properties including efforts for component reuse and to facilitate complex largescale software development by providing the developer with design alternatives and support for automatic program verification