The art of shooting the moving goal - explorative study of EA pilot

Enterprise Architecture (EA) has been recognised as an important tool in modern business management for closing the gap between strategy and its execution. The current literature implies that for EA to be successful, it should have clearly defined goals. However, the goals of different stakeholders are found to be different, even contradictory. In our explorative research, we seek an answer to the questions: What kind of goals are set for the EA implementation? How do the goals evolve during the time? Are the goals different among stakeholders? How do they affect the success of EA? We analysed an EA pilot conducted among eleven Finnish Higher Education Institutions (HEIs) in 2011. The goals of the pilot were gathered from three different stages of the pilot: before the pilot, during the pilot, and after the pilot, by means of a project plan, interviews during the pilot and a questionnaire after the pilot. The data was analysed using qualitative and quantitative methods. Eight distinct goals were recognised by the coding: Adopt EA Method, Build Information Systems, Business Development, Improve Reporting, Process Improvement, Quality Assurance, Reduce Complexity, and Understand the Big Picture. The success of the pilot was analysed statistically using the scale 1-5. Results revealed that goals set before the pilot were very different from those mentioned during the pilot, or after the pilot. Goals before the pilot were mostly related to expected benefits from the pilot, whereas the most important result was to adopt the EA method. Results can be explained by possibly different roles of respondents, which in turn were most likely caused by poor communication. Interestingly, goals mentioned by different stakeholders were not limited to their traditional areas of responsibility. For example, in some cases Chief Information Officers' goals were Quality Assurance and Process Improvement, whereas managers’ goals were Build Information Systems and Adopt EA Method. This could be a result of a good understanding of the meaning of EA, or stakeholders do not regard EA as their concern at all. It is also interesting to notice that regardless of the different perceptions of goals among stakeholders, all HEIs felt the pilot to be successful. Thus the research does not provide support to confirm the link between clear goals and success

Enterprise reference architectures for higher education institutions: Analysis, comparison and practical uses

Enterprise Architecture (EA) is currently accepted as one on the major instruments for enabling organisations in their transformation processes to achieve business-technology alignment. Despite that over the last years EA has been successfully adopted in many industries, Higher Education still represents one of the sectors with lower levels of adoption and maturity of EA practices. The present thesis puts the emphasis particularly on the study Enterprise Reference Architectures (ERAs), as a particular type of EA artefact, in Higher Education Institutions (HEIs). After formally clarifying the concept of ERAs and giving a panoramic view of the current state-of-the-art of existing HEI-oriented ERAs, the thesis proposes an artefact framework build through a Design Science Research (DSR) approach aimed to facilitate practitioners their (re-)use or application in their own real practical settings. The purpose of the constructed artefact is to support practitioners when conducting the necessary adjustments to exiting HEI-oriented ERAs in order to be successfully applied for their specific needs.La Arquitectura Empresarial (AE) es actualmente reconocida como una disciplina que permite configurar procesos de trasformación organizativa a objeto de alinear el negocio con la tecnología. A pesar de que en los últimos años la AE se ha ido adoptando progresivamente de forma exitosa en diversas industrias, la educación superior representa todavía hoy en día uno de los sectores con menores niveles de adopción y de madurez en lo que se refiere a las prácticas de AE. La presente tesis hace especial hincapié en el estudio de las Arquitecturas de Referencia Empresariales (AREs), entendidas como un artefacto específico de AE, en Instituciones de Educación Superior (IES). Así, después de clarificar formalmente el concepto de ARE y de ofrecer una visión panorámica del estado del arte relativo a las AREs para IES existentes, la tesis propone un framework de trabajo construido a través de un enfoque de investigación basado en la Ciencia del diseño destinado a facilitar su (re-)utilización o aplicación práctica en dominios de trabajo reales. El objetivo del artefacto es proporcionar soporte práctico a los profesionales para realizar los ajustes necesarios a las AREs para IES existentes para que puedan aplicarlas con éxito a sus necesidades específicas.L'Arquitectura Empresarial (AE) és actualment reconeguda com una disciplina que permet configurar processos de transformació organitzatius a fi d'alinear el negoci amb la tecnologia. Tot i que en els darrers anys l'AE s'ha anat adoptant progressivament amb èxit en diverses indústries, l'educació superior representa encara avui dia un dels sectors amb menors nivells d'adopció i de maduresa pel que fa a pràctiques d'AE. Aquesta tesi posa especial èmfasi en l'estudi de les Arquitectures de Referència Empresarials (AREs), enteses com un artefacte concret d'AE, a Institucions d'Educació Superior (IES). Així, després d'aclarir formalment el concepte d'ARE i oferir una visió panoràmica de l'estat de l'art relatiu a les ARE per a IES existents, la tesi proposa un framework de treball construït a través d'un enfocament de recerca basat en la ciència del disseny destinat a facilitar-ne la seva (re-)utilització o aplicació pràctica en dominis de treball reals. L'objectiu de l'artefacte és proporcionar suport pràctic als professionals per realitzar els ajustaments necessaris a les AREs per a IES existents de forma que les puguin aplicar amb èxit a les seves necessitats específiques.Tecnologies de la informació i de xarxe

Towards an understanding of business design within enterprise architecture management: a cautionary tale

Includes bibliographical references.Business Design represents a set of concepts that are described in the literature as providing a sound foundation for sustainable competitive advantage into the future. The particular values underpinning Business design are based on the enablement of a design thinking approach to solving the imponderable problems that organisations regularly encounter. In particular, the application of a design thinking approach to Business Design requires that resultant system designs are economically viable and technologically feasible. Enterprise Architecture Management plays a vital role in supporting these latter two requirements. Yet the definition of Enterprise Architecture Management as the 'normative restriction of design freedom' (Deitz, 2011) implies constraints that could impose limits on such business design. Consequently, the qualitative inductive research described in this document was undertaken to explore the perceived paradoxical relationship between Business Design and Enterprise Architecture Management. This dissertation recounts the process and results of this research initiative based on data recorded during interviews with a number of management level staff at a leading South African Insurance organisation. The participants were intimately involved in a programme to, amongst other objectives, establish a platform to support enterprise-wide Business Design within Enterprise Architecture Management, a programme that was experiencing a number of challenges and that was still underway at the time of completion of this research. Findings arising from this research were that the varying perceptions and levels of commitment of business and IT stakeholders associated with the programme and its requirements, contributed significantly to these challenges. In addition to providing a rich description of the case organisation's journey towards the establishment of a Business Design platform, a sensitising framework – 'The 6 Cs Framework in Support of the Successful Enablement of Business Design within Enterprise Architecture Management' – is proposed as a useful tool to assist organisations that might be considering a similar programme in the future

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

An investigation into the impact of enterprise architecture decisions on the responsibilities of software developers in companies that develop software

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts.ComputingM. Sc. (Information Systems