scholarly journals A Transaction-Oriented Architecture for Structuring Unstructured Information in Enterprise Applications

2011 ◽  
pp. 285-299 ◽  
Author(s):  
Simon Polovina ◽  
Simon Andrews
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Added Value ◽  
Formal Concept ◽  
Lack Of Information ◽  
Wide Range ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Information Errors ◽  
Unstructured Information

As 80-85% of all corporate information remains unstructured, outside of the processing scope of enterprise systems, many enterprises rely on Information Systems that cause them to risk transactions that are based on lack of information (errors of omission) or misleading information (errors of commission). To address this concern, the fundamental business concept of monetary transactions is extended to include qualitative business concepts. A Transaction Concept (TC) is accordingly identified that provides a structure for these unstructured but vital aspects of business transactions. Based on REA (Resources, Events, Agents) and modelled using Conceptual Graphs (CGs) and Formal Concept Analysis (FCA), the TC provides businesses with a more balanced view of the transactions they engage in and a means of discovering new transactions that they might have otherwise missed. A simple example is provided that illustrates this integration and reveals a key missing element. This example is supported by reference to a wide range of case studies and application areas that demonstrate the added value of the TC. The TC is then advanced into a Transaction-Oriented Architecture (TOA). The TOA provides the framework by which an enterprise’s business processes are orchestrated according to the TC. TOA thus brings Service-Oriented Architecture (SOA) and the productivity of enterprise applications to the height of the real, transactional world that enterprises actually operate in.

scholarly journals A Transaction-Oriented Architecture for Structuring Unstructured Information in Enterprise Applications

2013 ◽  
pp. 299-313
Author(s):  
Simon Polovina ◽  
Simon Andrews
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Added Value ◽  
Formal Concept ◽  
Lack Of Information ◽  
Wide Range ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Information Errors ◽  
Unstructured Information

As 80-85% of all corporate information remains unstructured, outside of the processing scope of enterprise systems, many enterprises rely on Information Systems that cause them to risk transactions that are based on lack of information (errors of omission) or misleading information (errors of commission). To address this concern, the fundamental business concept of monetary transactions is extended to include qualitative business concepts. A Transaction Concept (TC) is accordingly identified that provides a structure for these unstructured but vital aspects of business transactions. Based on REA (Resources, Events, Agents) and modelled using Conceptual Graphs (CGs) and Formal Concept Analysis (FCA), the TC provides businesses with a more balanced view of the transactions they engage in and a means of discovering new transactions that they might have otherwise missed. A simple example is provided that illustrates this integration and reveals a key missing element. This example is supported by reference to a wide range of case studies and application areas that demonstrate the added value of the TC. The TC is then advanced into a Transaction-Oriented Architecture (TOA). The TOA provides the framework by which an enterprise’s business processes are orchestrated according to the TC. TOA thus brings Service-Oriented Architecture (SOA) and the productivity of enterprise applications to the height of the real, transactional world that enterprises actually operate in.

scholarly journals EDSOA: An Event-Driven Service-Oriented Architecture Model For Enterprise Applications

2011 ◽  
Vol 14 (3) ◽  
Author(s):  
Karina Hauser ◽  
Helgi S. Sigurdsson ◽  
Katherine M. Chudoba
Keyword(s):  
Software Development ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Architecture Model ◽  
Software Complexity ◽  
Enterprise Applications ◽  
Event Driven ◽  
Service Oriented

Enterprise Applications are difficult to implement and maintain because they require a monolith of code to incorporate required business processes. Service-oriented architecture is one solution, but challenges of dependency and software complexity remain. We propose Event-Driven Service-Oriented Architecture, which combines the benefits of component-based software development, event-driven architecture, and SOA.

scholarly journals A Transactions Pattern for Structuring Unstructured Corporate Information in Enterprise Applications

2010 ◽  
pp. 910-921
Author(s):  
Simon Polovina ◽  
Richard Hill
Keyword(s):  
Multi Agent Systems ◽  
Transaction Model ◽  
Lack Of Information ◽  
Enterprise Applications ◽  
Structured Information ◽  
Multi Agent ◽  
Information Errors ◽  
Unstructured Information ◽  
Missing Element ◽  
Corporate Information

It is known that 80-85% of all corporate information remains unstructured. As such, many enterprises rely on information systems that cause them to risk transactions that are based on lack of information (errors of omission) or misleading information (errors of commission). To address this concern, the fundamental business concept of monetary transactions is extended to include qualitative business concepts. A Transaction Model (TM) is accordingly identified that provides a structure for these unstructured but vital aspects of business transactions. By highlighting how unstructured information can be integrated into transactions, the TM provides businesses with a much more balanced view of the transactions they engage in or to discover novel transactions that they might have otherwise missed. A simple example is provided that illustrates this integration and reveals a key missing element. This discovery points to a transactions pattern that can be used to ensure that all the parties (or agents) in a transaction are identified, as well as capturing unstructured and structured information into a coherent framework. In support of the TM as a pattern, more examples of its use in a variety of domains are given. A number of enterprise applications are suggested such as in multi-agent systems, document text capture, and knowledge management.

Enterprise Service Bus for Building Integrated Enterprises

2012 ◽  
pp. 618-636
Author(s):  
M. Antonia Martínez-Carreras ◽  
Francisco J. García-Jiménez ◽  
Antonio F. Gómez-Skarmeta
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Enterprise Application Integration ◽  
Enterprise Service Bus ◽  
Enterprise Application ◽  
Business Environments ◽  
Wide Range ◽  
Service Oriented ◽  
Legacy Applications ◽  
Future Business

Lately, the building of Enterprise Application Integration (EAI) where different legacy-applications may interoperate between them has gained the focus of business research. In this sense, the Service Oriented Architecture (SOA), and particularly the utilization of Web services standards, has attracted the attention of several researchers and practitioners for implementing the needs of EAI. More concretely, the emergence of Enterprise Service Bus (ESB) has brought a layer for favouring the mediation, transformation, and thus, the communication between these diverse applications, services, or business processes in a decoupled way. Indeed, the ESB technology integrates a wide range of current technologies and business standards. The aim of this chapter is to offer the design and necessities of Future Business Environments comparing how open ESBs fulfils these requirements. Furthermore, this chapter compares six of the most well-known open ESBs considering the characteristics provided in the design of Future Business Environments.

scholarly journals Introduction to Containerization

2020 ◽  
Vol 6 (12) ◽  
pp. 294-300
Author(s):  
Raghav Goel and Dr. Bhoomi Gupta
Keyword(s):  
Large Scale ◽  
Software Engineer ◽  
Service Oriented Architecture ◽  
Use Case ◽  
Production Environment ◽  
Code Base ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Multiple Services ◽  
Local Machine

Are you a software engineer/developer/coder or maybe even a tech enthusiast who is thinking of agility, parallel development and reducing cost. In the early twentieth century, we witnessed the rise of Service Oriented Architecture (SOA), which is a software architecture pattern that allows us to construct large-scale enterprise applications that require us to integrate multiple services, each of which is made over different platforms and languages through a common communication mechanism, where we write code and multiple services talk to each other’s for a business use case, but sometimes we end up with one big monolithic code base whose maintenance becomes difficult. Nowadays clients are using cloud and paying for on-demand services without effectively utilizing resources. These problems invite micro-services. In this paper, I am going to discuss how one should use scale application in a production environment and local machine

Patterns for Migration of SOA Based Applications to Microservices Architecture

2021 ◽  
Author(s):  
Vinay Raj ◽  
Ravichandra Sadam
Keyword(s):  
Programming Languages ◽  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Loose Coupling ◽  
Enterprise Service Bus ◽  
Web Based ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Key Features ◽  
Microservice Architecture

Service oriented architecture (SOA) has been widely used in the design of enterprise applications over the last two decades. Though SOA has become popular in the integration of multiple applications using the enterprise service bus, there are few challenges related to delivery, deployment, governance, and interoperability of services. To overcome the design and maintenance challenges in SOA, a new architecture of microservices has emerged with loose coupling, independent deployment, and scalability as its key features. With the advent of microservices, software architects have started to migrate legacy systems to microservice architecture. However, many challenges arise during the migration of SOA to microservices, including the decomposition of SOA to microservice, the testing of microservices designed using different programming languages, and the monitoring the microservices. In this paper, we aim to provide patterns for the most recurring problems highlighted in the literature i.e, the decomposition of SOA services, the size of each microservice, and the detection of anomalies in microservices. The suggested patterns are combined with our experience in the migration of SOA-based applications to the microservices architecture, and we have also used these patterns in the migration of other SOA applications. We evaluated these patterns with the help of a standard web-based application.

Multichannel Service Delivery Architecture

2015 ◽  
pp. 589-601
Author(s):  
Randall E. Duran ◽  
Anh Duc Do
Keyword(s):  
Real Time ◽  
Service Oriented Architecture ◽  
Mobile Banking ◽  
Time Service ◽  
System Architectures ◽  
Banking Services ◽  
Wide Range ◽  
Service Oriented ◽  
Multichannel Service ◽  
Service Channels

System architectures that deliver real-time services to customers must be flexible, scalable, and support a wide range of communication channels. This chapter presents an architecture that was designed to support multiple delivery channels and was successfully used to implement mobile banking services. The considerations behind the design and the approach used to deliver SMS-based mobile services using service-oriented architecture principles are reviewed and some of the practical challenges that were encountered with the implementation are explored. The ability for this solution architecture to support other real-time service channels is also examined.

Dynamic Reconfiguration of Component-Based Systems

2014 ◽  
pp. 76-102
Author(s):  
Tony Clark ◽  
Balbir S. Barn ◽  
Vinay Kulkarni
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Dynamic Reconfiguration ◽  
System Component ◽  
Ripple Effect ◽  
Dynamic Architecture ◽  
Component Architecture ◽  
Service Oriented ◽  
Typical Component

Component-based approaches generalize basic object-oriented implementations by allowing large collections of objects to be grouped together and externalized in terms of public interfaces. A typical component-based system will include a large number of interacting components. Service-Oriented Architecture (SOA) organizes a system in terms of components that communicate via services. Components publish services that they implement as business processes. Consequently, a change to a single component can have a ripple effect on the service-driven system. Component reconfiguration is motivated by the need to evolve the component architecture and can take a number of forms. The authors define a dynamic architecture as one that supports changing the behavior and topology of existing components without stopping, updating, and redeploying the system. This chapter addresses the problem of dynamic reconfiguration of component-based architectures. It proposes a reification approach that represents key features of a language in data, so that a system can reason and dynamically modify aspects of it. The approach is described in terms of a new language called µLEAP and validated by implementing a simple case study.

Semantic Web Services-Based Knowledge Management Framework

2016 ◽  
pp. 429-438
Author(s):  
Vili Podgorelec ◽  
Boštjan Grašič
Keyword(s):  
Knowledge Management ◽  
Web Services ◽  
Semantic Web ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Semantic Web Services ◽  
Semantic Web Technologies ◽  
Management Framework ◽  
Knowledge Based ◽  
Service Oriented

In this chapter, a Semantic Web services-based knowledge management framework that enables holistic knowledge management in organizations is presented. As the economy is becoming one single global marketplace, where the best offer wins, organizations have to search for competitive advantage within themselves. With the growing awareness that key potentials of an organization lie within its people and their knowledge, efficient knowledge management is becoming one of key focuses in organizational activities. The proposed knowledge management framework is based on Semantic Web technologies and service-oriented architecture, supporting the operational business processes as well as knowledge-based management of services in service-oriented architecture.

Enterprise Integration With the Structural Services Architectural Style

2019 ◽  
pp. 352-392 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Architectural Style ◽  
Enterprise Integration ◽  
Representational State Transfer ◽  
Advantages And Disadvantages ◽  
Architectural Styles ◽  
State Transfer ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Structural Compliance

The Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles are the most used for the integration of enterprise applications. Each is more adequate to a different class of applications and exhibits advantages and disadvantages. This chapter performs a comparative study between them. It is shown that SOA and REST are dual architectural styles, one oriented towards behavior and the other towards state. This raises the question of whether it is possible to combine them to maximize the advantages and to minimize the disadvantages. A new architectural style, Structural Services, is proposed to obtain the best characteristics from SOA and REST. As in SOA, services are able to offer a variable set of operations and, as in REST, resources are allowed to have structure. This style uses structural interoperability, based on structural compliance and conformance. A service-oriented programming language is also introduced to instantiate this architectural style.

Sign in / Sign up

Export Citation Format

Share Document