Resources-Events-Agents Design Theory: A Revolutionary Approach to Enterprise System Design

Enterprise systems typically include constructs such as ledgers and journals with debit and credit entries as central pillars of the systems’ architecture due in part to accountants and auditors who demand those constructs. At best, structuring systems with such constructs as base objects results in the storing the same data at multiple levels of aggregation, which creates inefficiencies in the database. At worst, basing systems on such constructs destroys details that are unnecessary for accounting but that may facilitate decision making by other enterprise functional areas. McCarthy (1982) proposed the resources-events-agents (REA) framework as an alternative structure for a shared data environment more than thirty years ago, and scholars have further developed it such that it is now a robust design theory. Despite this legacy, the broad IS community has not widely researched REA. In this paper, we discuss REA’s genesis and primary constructs, provide a history of REA research, discuss REA’s impact on practice, and speculate as to what the future may hold for REA-based enterprise systems. We invite IS researchers to consider integrating REA constructs with other theories and various emerging technologies to help advance the future of information systems and business research

A knowledge based reengineering approach via ontology and description logic.

Traditional software reengineering often involves a great deal of manual effort by software maintainers. This is time consuming and error prone. Due to the knowledge intensive properties of software reengineering, a knowledge-based solution is proposed in this thesis to semi-automate some of this manual effort. This thesis aims to explore the principle research question: “How can software systems be described by knowledge representation techniques in order to semi-automate the manual effort in software reengineering?” The underlying research procedure of this thesis is scientific method, which consists of: observation, proposition, test and conclusion. Ontology and description logic are employed to model and represent the knowledge in different software systems, which is integrated with domain knowledge. Model transformation is used to support ontology development. Description logic is used to implement ontology mapping algorithms, in which the problem of detecting semantic relationships is converted into the problem of deducing the satisfiability of logical formulae. Operating system ontology has been built with a top-down approach, and it was deployed to support platform specific software migration [132] and portable software development [18]. Data-dominant software ontology has been built via a bottom-up approach, and it was deployed to support program comprehension [131] and modularisation [130]. This thesis suggests that software systems can be represented by ontology and description logic. Consequently, it will help in semi-automating some of the manual tasks in software reengineering. However, there are also limitations: bottom-up ontology development may sacrifice some complexity of systems; top-down ontology development may become time consuming and complicated. In terms of future work, a greater number of diverse software system categories could be involved and different software system knowledge could be explored

Needs of Service Identification for Service-Oriented Business Process Management

Since the trend of adopting SOA into enterprise applications, the needs for definition and identification of services have been recognized. There is a growing body of research carried out on the identification of different types of services. Identifying right granularity services is important: if the service is of large size, it goes against the reusability principle of SOA, whereas if the service is of small size, then it causes unnecessary computing power for implementing any business functions. Without a formal (semi)- automatic approach to identify services, it is difficult in migrating existing systems into service-oriented systems. This paper explores the need for service identification for service-oriented business process management systems. The current approaches, techniques and methods of service identification are reviewed, and limitations of the each approach is analysed. New requirements and techniques are demonstrated in creating improved dynamic services with consideration for interoperability, modularity, reusability within information environment

Migration to PaaS Clouds - Migration Process and Architectural Concerns

In the cloud computing technology stack, infrastructure has matured more than platform or software service technologies with respect to languages and techniques used for architecting and managing respective applications. Platform-asa- Service (PaaS) emerges as a focus for the near future that we will focus on. We look at software architecture and programming concerns in the context of migration to PaaS solutions, i.e. the transition of platform systems from on-premise to cloud solutions. We investigate best-practice approaches in cloud-aware coding in the form of patterns and formulate these as a migration process. While one-to-one mappings of software from on-premise to cloud platforms are possible, statelessness and data externalisation from stateful sessions and applications emerge as solutions if cloud benefits such as elasticity and performance are aimed at

A matching approach to business services and software services

Recent studies have shown that service-oriented architecture (SOA) has the potential to revive enterprise legacy systems (Cai et al., 2011; Gaševic and Hatala, 2010; De Castro et al., 2011; Chengjun, 2008; Elgedawy, 2009; Tian et al., 2007; Chen et al., 2009; Zhang et al., 2006; Sindhgatta and Ponnalagu, 2008; Khadka, 2011), making their continued service in the corporate world viable. In the process of reengineering legacy systems to service-oriented architecture, some software services extracted in legacy system can be reused to implement business services in target systems. In order to achieve efficient reuse to software services, a matching approach is proposed to extract the software services related to specified business services, where service semantics and structure similarity measures are integrated to evaluate the similarity degree between business service and software services. Experiments indicate that the approach can efficiently map business services to relevant software services, and then legacy systems can be reused as much as possible

Cloud ERP: a new dilemma to modern organisations?

For almost two decades, on-premise ERP has been adopted very prevalently in the industry. Accompanied with the emergence of cloud computing technologies in the late 2000s, there is an increasing trend for companies to migrate their hitherto internal ERP applications and databases into the cloud. Such ERP resources re-migration, which can offer a range of opportunities to user companies, is also associated with new challenges. The study reported in this paper aimed to explore potential benefits and barriers associated with the adoption of cloud ERPs. A set of in-depth interviews were conducted with 16 ERP and cloud consultants. The findings, derived from a thematic analysis, identified that whilst the economic and technical benefits promised by cloud vendors are attractive, the success of cloud ERP adoption can be affected by critical challenges related to diverse organisational factors as well as with current legal and technical complexity in the cloud environment

Cloud computing : developing a cost estimation model for customers

Cloud computing is an essential part of the digital transformation journey. It offers many benefits to organisations, including the advantages of scalability and agility. Cloud customers see cloud computing as a moving train that every organisation needs to catch. This means that adoption decisions are made quickly in order to keep up with the new trend. Such quick decisions have led to many disappointments for cloud customers and have questioned the cost of the cloud. This is also because there is a lack of criteria or guidelines to help cloud customers get a complete picture of what is required of them before they go to the cloud. From another perspective, as new technologies force changes to the organizational structure and business processes, it is important to understand how cloud computing changes the IT and non-IT departments and how can this be translated into costs. Accordingly, this research uses the total cost of ownership approach and transaction cost theory to develop a customer-centric model to estimate the cost of cloud computing. The Research methodology used the Design Science Research approach. Expert interviews were used to develop the model. The model was then validated using four case studies. The model, named Sunny, identifies many costs that need to be estimated, which will help to make the cloud-based digital transformation journey less cloudy. The costs include Meta Services, Continuous Contract management, Monitoring and ITSM Adjustment. From an academic perspective, this research highlights the management efforts required for cloud computing and how misleading the rapid provision potential of the cloud resources can be. From a business perspective, proper estimation of these costs would help customers make informed decisions and vendors make realistic promises.Cloud Computing ist ein wesentlicher Bestandteil der Digitalisierung. Es bietet Unternehmen viele Vorteile, wie Skalierbarkeit und Agilität. Cloud-Kunden sehen Cloud Computing als einen Zug, auf den jedes Unternehmen aufspringen muss. Das bedeutet, dass Einführungsentscheidungen schnell getroffen werden, um mit dem neuen Trend Schritt zu halten. Solche Schnellschüsse haben zu vielen Enttäuschungen bei Cloud-Kunden geführt und die Kosten der Cloud in Frage gestellt. Dies ist auch darauf zurückzuführen, dass es keine Kriterien oder Leitlinien gibt, die den Cloud-Kunden helfen, sich ein vollständiges Bild davon zu machen, was von ihnen erwartet wird, bevor sie in die Cloud gehen. Aus einem anderen Blickwinkel ist es wichtig zu verstehen, wie Cloud Computing IT- und Nicht-IT-Abteilungen verändert und wie sich dies auf die Kosten auswirkt, da neue Technologien Veränderungen in der Organisationsstruktur und den Geschäftsprozessen erzwingen. Dementsprechend werden in dieser Forschungsarbeit der Total Cost of Ownership-Ansatz und die Transaktionskostentheorie verwendet, um ein kundenorientiertes Modell zur Schätzung der Kosten von Cloud Computing zu entwickeln. Die Forschungsmethodik basiert auf dem Design Science Research Ansatz. Zur Entwicklung des Modells wurden Experteninterviews durchgeführt. Anschließend wurde das Modell anhand von vier Fallstudien validiert. Das Modell mit dem Namen Sunny identifiziert viele Kosten, die geschätzt werden müssen, um die Reise zur digitalen Transformation in der Cloud weniger wolkig zu gestalten. Zu diesen Kosten gehören Meta-Services, kontinuierliches Vertragsmanagement, Überwachung und ITSM-Anpassung. Aus akademischer Sicht verdeutlicht diese Forschung, welcher Verwaltungsaufwand für Cloud Computing erforderlich ist und wie irreführend das schnelle Bereitstellungspotenzial von Cloud-Ressourcen sein kann. Aus Unternehmenssicht würde eine korrekte Einschätzung dieser Kosten den Kunden helfen, fundierte Entscheidungen zu treffen, und den Anbietern, realistische Versprechungen zu machen