Enterprise architecture model: an approach proposition. A case study of information systems in the hospitality industry

This paper discusses the role of enterprise architecture representation, in the context of ERP (Enterprise Resource Planning) information systems, as an instrument for an organization to reflect on itself and develop its business strategies and respective alignment with Information Systems. The paper proposes a representation model of enterprise architecture, as a tool for recommending good practices, and it emerges from a case study undertaken in the context of and investigation on advantages and limitations of ERP systems in the hospitality industry. The proposed approach is also inspired on other academic or market propositions suitable for the objectives of the investigation. It consists on a set of items representing the steps that must be taken by top managers and IS managers.

Enterprise Architecture notes/white papers

A collection of notes and white papers regarding Enterprise Architecture

HMEF: framework to evaluate merging of Higher Education Institutions – application of Enterprise Architecture

Mergers of Higher Education Institutions (HEIs) are organisational processes requiring tremendous amount of resources, in terms of time, work, and money. A number of mergers have been seen on previous years and more are to come. Several studies on mergers have been conducted, revealing some crucial factors that affect the success of mergers. Based on literature review on these studies, factors are: the initiator of merger, a reason for merger, geographical distance of merging institutions, organisational culture, the extend of overlapping course portfolio, and Quality Assurance Systems (QASs). Usually these kind of factors are not considered on mergers, but focus is on financial matters. In this paper, a framework (HMEF) for evaluating merging of HEIs is introduced. HMEF is based on Enterprise Architecture (EA), focusing on factors found to be affecting the success of mergers. By using HMEF, HEIs can focus on matters that crucial for merging.

Taxonomy of purpose of Enterprise Architecture

Initial phase of all Enterprise Architecture (EA) initiatives is important. One of the most crucial tasks in that phase is to sell EA to the top management by explaining its purpose. In this paper, by using semiotic framework we show that there is a clear gap between the definition of EA and its purpose. Contribution of this paper is a taxonomy that expands knowledge of pragmatics of EA, and that can be used as a tool for explaining the purpose of EA. Grounded theory is used to form the taxonomy. Data is collected from a discussion group used by EA practitioners. Results indicate that the purpose of EA is to meet organisations‟ stakeholder‟s goals and to create value to organisation. Results are in line with current literature. Most interesting result is that EA practitioners seem to realise that technical solutions are not the purpose of EA, but means for fulfilling it.

Measuring Enterprise Architecture success: a tentative model for measuring success

Interest towards Enterprise Architecture (EA) has been increasing during the last few years. EA has been found to be a crucial aspect of business survival, and thus the importance of EA implementation success is also crucial. Current literature does not have a tool to be used to measure the success of EA implementation. In this paper, a tentative model for measuring success is presented and empirically validated in EA context. Results show that the success of EA implementation can be measured indirectly by measuring the achievement of the objectives set for the implementation. Results also imply that achieving individual's objectives do not necessarily mean that organisation's objectives are achieved. The presented Success Measurement Model can be used as basis for developing measurement metrics.

Theoretical perspectives of enterprise architecture

The number of published Enterprise Architecture (EA) research has increased during the last few years. As a discipline, EA is still young and lacking theoretical foundation. Lately some research trying to ground EA to theory has been published, including linkage to systems theory. Enterprise Architecture can be defined as; (i) a formal description of the current and future state(s) of an organisation, and (ii) a managed change between these states to meet organisation’s stakeholders’ goals and to create value to the organisation. Based on this definition, this conceptual paper tries to shed light to theoretical underpinnings of EA from three theoretical perspectives; EA as a communication media, EA as an activity, and EA as an information technology system. Our conclusions are that; (i) EA can be categorised as a communication media and theoretically underpinned by ontology and semiotics, (ii) EA can be explained and theoretically underpinned by Activity Theory, and (iii) EA can be categorised as an information technology system and theoretically underpinned by General Systems Theory and Technology Acceptance Theory.

Modelling the resistance of Enterprise Architecture adoption: linking strategic level of Enterprise Architecture to organisational changes and change resistance

During the last few years Enterprise Architecture (EA) has received increasing attention among industry and academia. By adopting EA, organisations may gain a number of benefits such as better decision making,increased revenues and cost reduction, and alignment of business and IT. However, EA adoption has been found to be difficult. In this paper a model to explain resistance during EA adoption process (REAP) is introduced and validated. The model reveals relationships between strategic level of EA, resulting organisational changes, and sources of resistance. By utilising REAP model, organisations may anticipate and prepare for the organisational change resistance during EA adoption.

Enterprise Architecture adoption method for Higher Education Institutions

During the last few years Enterprise Architecture has received increasing attention among industry and academia. Enterprise Architecture (EA) can be defined as (i) a formal description of the current and future state(s) of an organisation, and (ii) a managed change between these states to meet organisation’s stakeholders’ goals and to create value to the organisation. By adopting EA, organisations may gain a number of benefits such as better decision making, increased revenues and cost reductions, and alignment of business and IT. To increase the performance of public sector operations, and to improve public services and their availability, the Finnish Parliament has ratified the Act on Information Management Governance in Public Administration in 2011. The Act mandates public sector organisations to start adopting EA by 2014, including Higher Education Institutions (HEIs). Despite the benefits of EA and the Act, EA adoption level and maturity in Finnish HEIs are low. This is partly caused by the fact that EA adoption has been found to be difficult. Thus there is a need for a solution to help organisations to adopt EA successfully. This thesis follows Design Science (DS) approach to improve traditional EA adoption method in order to increase the likelihood of successful adoption. First a model is developed to explain the change resistance during EA adoption. To find out problems associated with EA adoption, an EA-pilot conducted in 2010 among 12 Finnish HEIs was analysed using the model. It was found that most of the problems were caused by misunderstood EA concepts, attitudes, and lack of skills. The traditional EA adoption method does not pay attention to these. To overcome the limitations of the traditional EA adoption method, an improved EA Adoption Method (EAAM) is introduced. By following EAAM, organisations may increase the likelihood of successful EA adoption. EAAM helps in acquiring the mandate for EA adoption from top-management, which has been found to be crucial to success. It also helps in supporting individual and organisational learning, which has also found to be essential in successful adoption.

The synergies between goal sketching and enterprise architecture

This paper introduces a pragmatic and practical method for requirements modeling. The method is built using the concepts of our goal sketching technique together with techniques from an enterprise architecture modeling language. Our claim is that our method will help project managers who want to establish early control of their projects and will also give managers confidence in the scope of their project. In particular we propose the inclusion of assumptions as first class entities in the ArchiMate enterprise architecture modeling language and an extension of the ArchiMate Motivation Model principle to allow radical as well as normative analyses. We demonstrate the usefulness of this method using a simple university library system as an example.

Strategic planning to build transformational preparedness : an application of enterprise architecture practice

Enterprises are continuously evolving systems; this evolution can be directed or emergent. Enterprise transformation has special aspects due to the enterprise being a socio-technical system whereupon evolution happens on the levels of individuals / humans / organisation, on the level of the technology and on the level of the Information Systems that integrates the activities performed by humans and by technology. Furthermore, changes are typically continuous, due partly to external factors and partly to strategic foresights. Either way, transformation needs to happen so that the enterprise can keep satisfying its objectives. An important transformation mechanism is to perform mergers or acquisitions (M&As). Interestingly, literature reveals that an unacceptably high percentage of M&As do not achieve the aimed objectives and (as we demonstrate) the success of such trajectory depends on several factors. This article proposes a methodology to overcome potential problems by making necessary anticipatory transformations opening up a possibility to perform M&As with a better chance of success.

Progetto e strumenti di federazione di endpoint sparql per Enterprise Architecture

La Federazione è un concetto molto utilizzato ed implementato in vari ambiti dell’informatica. In particolare sta avendo grande interesse nel Semantic Web, e risulta essere significativo e importante il suo utilizzo in una disciplina in grande evoluzione come l’Enterprise Architecture. L’obiettivo di questa tesi è stato implementare il concetto di Federazione di Endpoint SPARQL, dove l’elemento centrale è stata la condivisione del modello dei dati tra i vari membri, il quale rappresenta il patto della federazione. Successivamente sono stati messi in luce i benefici che questo tipo di soluzione apporta alla disciplina dell’Enterprise Architecture, in particolar modo nell’ambito dell’analisi dei dati. In relazione a quest’ultimo aspetto, il Semantic Web offre un linguaggio flessibile e facilmente evolvibile per rappresentare l’azienda e i suoi dati, oltre che ad un protocollo standard per la loro interrogazione, ovvero lo SPARQL. La federazione, invece, apporta dei miglioramenti rendendo le fonti dato omogenee dal punto di vista del modello, utilizza un unico protocollo per l’accesso ad essi (SPARQL), ed elimina le criticità in relazione alla normalizzazione dei dati nei processi di analisi. Questi due aspetti risultano abilitanti proprio per l’Enterprise Architecture. Infine sono state definite due possibili evoluzioni, in particolare un costrutto che permetta l’implementazione e la gestione della federazione a livello di linguaggio SPARQL, ed una ontologia standard e condivisibile tramite la quale gestire la federazione in modo trasparente.

Evolving a core Banking enterprise architecture: leveraging business events exploitation

Business information has become a critical asset for companies and it has even more value when obtained and exploited in real time. This paper analyses how to integrate this information into an existing banking Enterprise Architecture, following an event-driven approach, and entails the study of three main issues: the definition of business events, the specification of a reference architecture, which identifies the specific integration points, and the description of a governance approach to manage the new elements. All the proposed solutions have been validated with a proof-of-concept test bed in an open source environment. It is based on a case study of the banking sector that allows an operational validation to be carried out, as well as ensuring compliance with non-functional requirements. We have focused these requirements on performance.