Dissertations / Theses on the topic 'Enterprise architecture'

Com o desenvolvimento das linguagens de computação as arquiteturas chamadas convencionais tornam-se ineficientes para executar programas escritos nestas linguagens. Por exemplo, Lips é uma linguagem baseada no processamento de listas, sendo necessário para melhorar o desempenho de sua execução uma arquitetura voltada para este princípio. Este trabalho mostra a configuração de um processador dedicado ao processamento Lips, o enterprise, que além de possuir uma arquitetura não convencional implementa a chamada coleta de lixo concorrente.
The evolution of computer languages becomes machines based upon conventional architectures ineficients to run programs in that new languages. Lisp is a language created to process lists, so a hardware implementation dedicated to process lists would be thee best solution to run Lisp programs. This essay describes a processor named Enterprese, a architecture dedicated to list processing. In addition, Enterprise executes concorrent garbage collection.

Enterprise architecture aligns organizations business processes, information systems andtechnical layers. Its role has become more challenging than ever before with the modern dayrapidly changing environment and technological advances. Considering these aspects, this thesistries to evaluate the success factors that affect enterprise architecture management.The thesis is done at Volvo Cars, in collaboration with Ferrologic. Twelve success factorssignificant for Volvo Cars’ enterprise architecture management are defined after a series of semistructuredinterviews with architects working at the company. This is followed by a surveyevaluating the factors sent to architects throughout Sweden. In the end, the factors are dividedinto four groups according to their impact level. The survey reveals that the businessunderstanding of the technical side, requirement definitions & handling requirement changes,high-level management involvement, and cross-functionality are perceived to be most impactfulsuccess factors for the industry professionals, in no particular order.
Enterprise Architecture är skapat för organisationens affärsprocesser, informationssystem ochtekniska lager. Dess roll har blivit mer utmanande än någonsin tidigare med modern tid somsnabbt förändrande miljö och tekniska framsteg. Med tanke på dessa aspekter försöker dennaavhandling utvärdera framgångsfaktorerna som påverkar företagsarkitekturhantering.Avhandlingen görs hos Volvo Cars, i samarbete med Ferrologic. Tolv framgångsfaktorer som ärbetydelsefulla för Volvo Cars företagsarkitekturledning definieras efter genomförandet avhalvstrukturerade intervjuer med arkitekter som arbetar hos företaget. Detta följs av enundersökning som utvärderar de faktorer som skickas till arkitekter. I slutändan delas faktorernain i fyra grupper beroende på deras påverkanivå. Undersökningen visar att ett bra förståelse avden affärs sidan för den tekniska sidan, kravdefinitioner, förändring i hanteringskrav,engagemang och överfunktionalitet är dem största framgångsfaktorerna.

Tato práce se věnuje problematice Enterprise Architecture (podnikové architektuře) a metodice vývoje informačního systému (vyvinuta na VŠE) MMDIS (Multidimensional Management and Development of Information Systems). V práci je zkoumáno zda metodika MMDIS je svým charakterem použitelná i v oblasti podnikové architektury. Pojem Enterprise Architecture zastřešuje veškeré elementy, které utvářejí podnik (či jakoukoliv organizaci) a o vztazích mezi nimi. Nahlíží na organizaci od jejich strategických cílů přes podnikové procesy a informace až po aplikace a technická řešení nezbytná pro její podnikání. Podnikovou architekturu se snažíme zachytit pomocí řady modelů a dokumentů, které vytváříme na základě konceptuálních rámců (framework). Můžeme použít již existující rámce (Zachman, FEAF, atd.) nebo vytvořit svůj vlastní. Tato práce se věnuje nejznámějším rámcům a na základě jejich rozboru definuje obecné požadavky na rámec. Metodika MMDIS je primárně určena pro vývoj informačních systémů. Její otevřený charakter a multidimenzionální přístup však vybízí k použití i v oblasti podnikové architektury. Na základě zkoumání oblasti Enterprise Architecture a rozboru nejznámějších rámců byly v této práci stanoveny obecné požadavky na rámec podnikové architektury. Metodika MMDIS pak byla konfrontována s těmito principy. Tato práce přináší zhodnocení použitelnosti metodiky MMDIS jako Enterprise Architecture rámce a v této souvislosti dále naznačuje možnosti jejího rozšíření a úprav.

As a consequence of the increasing requirements on enterprises caused by globalization, fusion of business and IT, new/changing technologies and especially new regulations Enterprise Architecture Management has gained increasing public attention. In this context Enterprise Architecture (EA) can be considered as a holistic view of an enterprise acting as a "collaboration force" between business aspects such as goals, visions, strategies and governance principles as well as IT aspects. For EAs to be useful and to provide business value their formal and comprehensive documentation (data collection and visualization) is essential. Due to the increasing information amount caused by the extending scope on the business as well as on the IT side the EA modelling is cost-intensive and time-consuming. Most of all the documentation is impaired by increasing linking and integration as well as by the striving for automated cross-company business processes. Consequently, the relevant data are widely scattered. Current approaches are largely determined by manual processes which are able to deal only to a limited extent with the new trends. However, a lot of the needed information, above all about the application landscape and the interrelations, is already present in existing Enterprise Service Bus systems used to facilitate the collaboration between applications both within and beyond boundaries. This allows avoiding the expensive task of data collection. This thesis is concerned with the automated documentation of Enterprise Architectures and the support of decision-making using the information provided by an existing Enterprise Service Bus, whereby as a concrete system SAP NetWeaver Process Integration is used. Therefore a tool-aided automated process for the creation and visualization of an Enterprise Architecture model instance is proposed. An essential aspect in this connection is the coverage of the EA information demand set up by EA frameworks such as CySeMoL and ArchiMate, the analysis of the quality as well as the implementation of the logic to transform SAP PI data into EA information. Moreover, several viewpoints are proposed to visualize the extracted data appropriately especially regarding decision problems in the area of the collaboration between applications both within and beyond boundaries.

The most important characteristic of enterprise architecture (EA) is that, it provides a holistic view of the enterprise. EA needs to consider about different aspects, views and viewpoints in an enterprise in order to make an enterprise more understandable and communicable to achieve organization goals and objectives. To do this matter EA needs to use different techniques or enterprise modeling methods to achieve different results of EA (documents/artifacts, models, goals/benefits). But many organization for building EA, use their own description techniques and conventions instead of using existing techniques or existing EMMs. They might use one technique which is not appropriate for modeling all aspects of EA. Our purpose is to discover the usefulness of EMMs in the process of construction EA to provide expected results of EA. We investigated about different EMMs to see its usefulness in producing which expected EA result. In order to increase the accuracy of the final results we investigated about different EMMs with respect to important EA aspects. To perform this study we have gone through a survey to validate EA important aspects and essential results of EA. Results of our study conducted based on both using literature review for studying about the usefulness of different EMMs and the results of our survey (EA aspects and results of EA). The results of this research show that Business, Organization, Technical, Information and Decision Making are five important aspects of EA; different EMMs can be used to produce several results of EA. We used table to illustrate the results of the study for each EA aspect separately. Our analysis revealed that the Decision Making and Information aspects of EA could get more help from EMMs compare to the other aspects, since the main focus of some of these methods such as GERAM, GRAI and GIM are mainly accumulated in these two aspects.

Thesis (Ph. D.)--Massachusetts Institute of Technology, Engineering Systems Division, 2009.
Cataloged from PDF version of thesis.
Includes bibliographical references (p. [301]-314).
Today, the design of business enterprises is much more art than science. The complex structure and behavior of enterprises makes it difficult to untangle cause and effect amidst its components and their relationships. In order for managers to understand how an enterprise's architecture affects its behavior, they need tools and techniques to help them to manage the complexity of the enterprise. The practice of enterprise architecting continues to make advances in this area with reference frameworks that can be used to guide the decomposition and communication of enterprise architectures, but it does not provide tools to analyze the potential behavior of a proposed enterprise architecture. This research seeks to extend the practice of enterprise architecting by developing an approach for creating simulation models of enterprise architectures that can be used for analyzing the architectural factors affecting enterprise behavior and performance. This approach matches the content of each of the "views" of an enterprise architecture framework with a suitable simulation methodology such as discrete event modeling, agent based modeling, or system dynamics, and then integrates these individual simulations into a single hybrid simulation model. The resulting model is a powerful analysis tool that can be used for "what-if" behavioral analysis of enterprise architectures. This approach was applied to create a hybrid simulation model of the enterprise architecture of a real-world, large-scale aerospace enterprise.
(cont.) Simulation model analysis revealed potential misalignments between the current enterprise architecture and the established strategy of the enterprise. The simulation model was used to analyze enterprise behavior and suggest relatively minor changes to the enterprise architecture that could produce up to a 20% improvement in enterprise profitability without increasing resources to the enterprise.
by Christopher Garrett Glazner.
Ph.D.

Thesis (MPhil (Information Science))--University of Stellenbosch, 2010.
ENGLISH ABSTRACT: Knowledge assets can be defined as anything that affects a business’s disposition to act on data received from the environment. Knowledge assets are embedded in the objects within an organisation and are the source of an organisation’s competitive advantage, by being closely linked to what the organisation knows and by allowing the organisation to act and to be innovative. Knowledge assets evolve over time as knowledge agents, through a process of sense making, substitute physical resources for informational resources by codifying and abstracting knowledge assets, in the process increasing their value and ability to be diffused to wider audiences. These knowledge assets are internalised in an organisation and impact on the organisation when they are applied to concrete problems. Knowledge assets play an important role in the creation of information assets in an organisation. Information assets are created when a knowledge agent makes use of his or her knowledge to make sense of data received from sources in the environment. The creation of information through the sense making process creates new knowledge which is added to the agent’s knowledge base. Enterprise architecture is the process of designing future states for an organisation and then planning, leading and governing the organisation towards that future state. Enterprise architecture focuses mostly on the organisational process, on information and technology. Enterprise architects make use of enterprise architecture frameworks such as TOGAF or the Zachman framework, which are primarily concerned with the domains of business, information and technology architecture, yet none of these mainstream frameworks used by enterprise architects takes knowledge assets into account, despite the obviously important role that they play in the organisation and especially in the information creation process. This research proposes to show that knowledge assets have an important role to play in enterprise architecture by allowing enterprise architects to • identify or facilitate the creation of knowledge assets pertaining to a specific problem; • understand whether information assets are located in the ordered and complex or the chaotic regimes and what would be the implication of moving them between regimes; • plot knowledge assets movements and relationships to each other on the social learning cycle path, which would enable enterprise architects to balance the types of learning that the organisation employs; • define the level of codification, abstraction and diffusion of knowledge assets, based on the intended audiences and to understand where knowledge assets could be developed to improve quality and when outdated knowledge should be destroyed in favour of new knowledge. Knowledge assets are related to Enterprise Business Architecture (EBA) through the specific knowledge domains that exist within an organisation. Understanding whether knowledge assets exist in the ordered, complex or chaotic regimes will provide a more complete view of the organisation. Architecture of knowledge assets in this space will provide a better understanding of an organisation’s culture: this understanding can compensate for differences in knowledge agents’ spatio-temporal positions, how and when they receive data and their particular cognitive styles. The importance of knowledge assets in the creation of information links it emphatically with Enterprise Information Architecture (EIA). Knowledge asset architecture provides a better understanding of how information is created and flows through an organisation, taking into account the meaning of the information to the organisation, which compensates for that oversight in information theory, which regards the accuracy of data that is communicated as the only concern. Information technology has exponentially increased mankind’s ability to codify, abstract and diffuse knowledge assets. Enterprise Technical Architecture (ETA) is mainly concerned with the technology infrastructure implemented within an organisation. Enterprise architects can apply knowledge asset architecture to decide whether the technology should be used to enhance the codification and abstraction of information, allowing more efficient diffusion of information to a larger audience, or whether more concrete information should be diffused to a more closely-knit audience. This research will argue that the use of knowledge assets as a domain within enterprise architecture will greatly enhance the enterprise architect’s ability to understand and lead the organisation to a more desirable future state.
AFRIKAANSE OPSOMMING: Kennisbates is vasgelê in die konkrete en abstrakte voorwerpe in die organisasie. Hierdie voorwerpe omsluit alle voorwerpe wat ‘n effek het op hoe die organisasie reageer op data wat vanaf die omgewing ontvang word. Kennisbates is ‘n bron vir die kompeterende voordeel wat ‘n organisasie geniet omdat dit verband hou met wat die organisasie weet en dit die organisasie in staat stel om te innoveer. Kennisbates sal aangaande evolueer soos wat kennisdraers, deur die sinmaak proses, fisiese hulpbronne vervang met inligtings hulpbronne gedurende die proses van kodifisering en abstraksie en sodoende die kennisbates se waarde vir die organisasie te verhoog en beskikbaar te stel vir groter gehore. Die kennisbates word dan vasgelê in die organisasie wanneer die kennis toegepas word op konkrete probleme. Kennisbates speel ‘n belangrike rol in die skepping van inligtingsbates in die organisasie. Inligting word slegs geskep wanneer die kennisdraer gebruik maak van sy kennis om sin te maak van data onvang vanuit die omgewing. Die nuwe inligting word dan intern vasgelê in die kennisdraer as nuwe kennis. Ondernemingsargitektuur is ‘n proses waardeur die toekomstige staat van ‘n organisasie ontwerp word deur beplanning, en daar verder leiding gegee word ter uitvoering daarvan. Ondernemingsargitektuur fokus meestal op die organisasie se prosesse, inligting en tegnologie. Ondernemingsargitekte maak gebruik van ondernemingsargitektuurraamwerke soos TOGAF en die Zachmanraamwerk as riglyne vir hulle werk. Hierdie raamwerke fokus primêr op die besigheid, inligting en tegniese domeine van argitektuur. Nie een van die hoofstroom ondernemingsargitektuurraamwerke neem kennisbates in ag nie, ten spyte van die voordiehandliggende belangrike rol wat kennisbates in die organisasie se inligtingskeppingsproses speel. Hierdie navorsing stel voor dat kennisbates deel kan vorm van ondernemingsargitektuur deur ondernemingsargitekte toe te laat om • kennisbates aangaande ‘n spesifieke probleem te identifiseer of die skepping daarvan die fasiliteer, • te bepaal of die kennisbates in die geordende, komplekse of chaotiese regime bestaan en wat die implikasie sou wees om hulle na ‘n ander regime te skuif, en • die kennisbates op die sosiale leersiklus aan te stip, wat die ondernemingsargitek in staat sal stel om die leerbenaderings van die organisasie te balanseer, die vlak van kodifisering, abstraksie en verspreiding te definieer, gebaseer op die voornemende gehoor vir die spesifieke inligting. • beter begrip te hê daarvoor of die kennisbate na ‘n beter kwaliteit ontwikkel moet word of vernietig moet word om plek te maak vir nuwe kennisbates. Daar bestaan ‘n verwantskap tussen OBA (Ondernemingsbesigheidsargitektuur) deur die spesifieke kennisdomein wat reeds in die organisasie bestaan. Deur te verstaan of die kennisbates binne die geordende, komplekse of chaotiese regimes val sal beter begrip bied van die organisasie as geheel. Al hierdie gesigshoeke word in die geordende domein beskryf. Kennisbateargitektuur sal ‘n beter begrip van die organisasie se kultuur bewerkstellig. Die kultuur in ‘n organisasie word gebruik om te vergoed vir die verskille in die kennisdraer se tyd-ruimtelike ligging tydens die ontvangs van data asook hulle kognitiewe styl. Daar bestaan ‘n daadwerklike verwantskap tussen kennisbateargitektuur en Ondernemingsinligtingsargitektuur (OIA). Kennisbateargitektuur sal bydra tot die begrip van hoe inligting geskep word en vloei deur die organisasie. Dit sal die betekenis van inligting in ag neem en daardeur vergoed vir die tekortkoming van inligtingteorie wat slegs die korrektheid van die data wat vervoer word in ag neem. Inligtingstegnologie het die mens se vermoë om inligting te kodifiseer, abstraksie toe te pas en te versprei eksponensieël verbeter. Ondernemingstegnieseargitektuur (OTA) is hoofsaaklik verantwoordelik vir die tegnologiese infrastruktuur wat geïmplimenteer word binne die organisasie. Ondernemingsargitekte kan kennisbates gebruik om te besluit of tegnologie gebruik moet word om beter inligting te skep deur hoër kodifisering en abstraksie toe te pas, om daardeur die vermoë te skep om die inligting vir ‘n wyer gehoor beskikbaar te stel, of om meer konkrete inligting vir ‘n meer intieme gehoor beskikbaar te stel. Hierdie navorsing stel voor dat kennisbates as ‘n domein binne die ondernemingsargitektuur vervat word. Dit sal die ondernemingsargitek in staat stel om die organisasie beter te lei na ‘n wenslike toekomstige staat.

This thesis deals with subject of enterprise architecture management. Topcis covered are enterprise environment integration, enterprise architecture parts description and description of shift in enterprise architecture focus point. This trend can be described as shift from IT related activity for IT management through tool for IT and business alignment to the final state as a tool for business change implementation. There are four goals of this thesis. Description of enterprise architecture, description of trend for enterprise architecture shift toward business, analysis of enterprise architecture state in Czech Republic and analysis of enterprise architecture shift to business in Czech Republic. I will reach first two goals by analysis of literature of the solution domain and the other two goals with questionnaire and its analysis.

Various disciplines have contributed to Complexity Science by experiencing the problem of how to design, build and control more and more complex systems (i.e., to ‘beat the complexity barrier’) and tried to suggest some solutions. However, apart from the description of this problem, very few concrete proposals exist to solve it. The observation of this Conceptual Analytical dissertation is that while improved design methodologies, modelling languages and analysis tools can certainly lessen the designer’s problem, they only extend the complexity barrier that a designer (or group of designers) can deal with, but they do not remove that barrier. The hypothesis of this dissertation is that perhaps the system (or system of systems) and the designer (group of designers) should not be separated and systems should design themselves, out of component systems that have the same self-designing property. Therefore the informal research questions are: 1. Is it possible to remove this problem from the design of complex systems? 2. If yes how (or to what extent)? Many disciplines attempted to attack the question of complexity management, and as will be seen, an interdisciplinary approach seems necessary to be able to give useful answers. Enterprise Architecture as a discipline, which evolved in the past 20 to 30 years (initially called 'enterprise integration'), has defined as its mission to bring together all that knowledge which is necessary to maintain enterprises through life (ISO 15704, 2000). Therefore, this thesis will attempt to look at the problem through the eyes of an interdisciplinary EA researcher.
Thesis (PhD Doctorate)
Doctor of Philosophy (PhD)
School of Information and Communication Technology
Science, Environment, Engineering and Technology
Full Text

The concept of Enterprise Architecture (EA) has become increasingly common within enterprises today and aims to describe an enterprise’s structure in a standardized way. Implementing EA within an enterprise is a way to describe the how various domains affect each other and by defining uniform procedures and guidelines, particularly in the link between IT-activities and business activities, you can streamline you enterprise. An effective EA is a huge asset for an enterprise since it enables the full usage of the business potential of the IT-domain. However a malfunctioning EA can lead to an enormous drain of valuable organizational resources. The latter is too often more common. With EA, it is easier to understand how decisions made in one domain affects other domains, thereby increasing an enterprise's pro-activity and efficiency. By mapping the EA frameworks available on the market and how an implementation of an EA framework can affect how you work within SL, I give in this thesis a description of how an EA framework can be implemented in an enterprise regarding general needs and conditions. The framework which I think is best suited for SL to use in order to establish an EA within the enterprise is TOGAF. TOGAF is an established methodology framework, which also has a relatively well-defined ontology, i.e. a description of the components that a business should have and its relations. TOGAF is a generic framework intended to be used in a variety of environments, which enables the possibility for integration with other frameworks. TOGAF provides a flexible and extensible content which allows it to deliver a tailored approach that can be integrated into the processes and structures within the enterprise. The results of the requirement analysis carried out in the thesis shows that there is a great need and a great willingness to perform change management within SL. Of the surveyed respondents in the interview study, 83% answered that there are problem areas in SL that needs attention. The key problem area was considered by most of the respondents to be the lack of a link between the business domain and IT domains within SL, as well as who owns and manages information within the company. As for how these problem areas should be addressed most respondents (76%) answered that they agreed on Enterprise Architecture being a good tool for SL. Many also felt the need to clarify how the domains affect each other and clarify the benefits of implementing EA within SL.

The desire to obtain value and justify investments from the different Information Systems in place in organizations has been around for a long time. Organizations constantly theorize and implement different approaches that provide some sort of alignment between their different business objectives and Information Systems. Unfortunately, the environments in which these organizations operate are often dynamic, constantly changing with influence from external and internal factors that require continual realignment of the Information Systems with business objectives to provide value. When businesses evolve, leading to changes in business requirements, it is hard to know what direct Information System changes are needed to respond to the new requirements. Similarly, when there are changes in the Information System, it is not often easy to discern which business objectives are directly affected. Whilst the different Enterprise Architecture frameworks available today provide and propose some form of alignment, in their implementation, they do not show links between business objectives and Information Systems, i.e., indicating what Information System is directly responsible for different business objectives thereby allowing for anticipation and support of changes as the business evolves. This thesis utilizes insights from Business Intelligence and uses the User Requirements Notation (URN), which enables modeling of business processes and goals, to provide a framework that exploits links between business objectives and Information Systems. This Business Intelligence - Enabled Adaptive Enterprise Architecture framework allows for anticipating and supporting proactively the adaptation of Enterprise Architecture as and when the business evolves. The thesis also identifies and models levels within the enterprise where responses to change as the business evolves are needed and the ways the changes are presented. The tool-supported framework is evaluated against the different levels and types of changes on a realistic Enterprise Architecture at a Government of Canada department, with encouraging results.

ITC/USA 2009 Conference Proceedings / The Forty-Fifth Annual International Telemetering Conference and Technical Exhibition / October 26-29, 2009 / Riviera Hotel & Convention Center, Las Vegas, Nevada
With the introduction of networking into telemetry applications, these systems have become increasingly complex. This imposes significant strain on information security for architecture designs. It has been recognized that an organized or structured approach to developing security architectures is needed. Several enterprise architecture frameworks are available today that address system complexity. However they fall short of addressing security at a high enough level in the enterprise and address security too late in the design process. In this paper a methodology is proposed that bridges the gap between security requirements and architecture design development at the enterprise level. This approach is consistent with and traceable to the original needs of the customer. This paper introduces a systems engineering approach to develop an enterprise level methodology, and presents a worked example of this approach for the integrated Network Enhanced Telemetry system.

A common challenge in organizations is a perception of that different languages are spoken among IT and other departments. Co-workers come from different background, have different knowledge base and sometimes even different objectives which can make an alignment more challenging. Enterprise Architecture (EA) can align IT investments with business directions and potentially solve issues regarding business-IT misalignments and bring value to organizations. Technical Debt (TD) is a well-established concept in software development and means that a solution that is “quick and dirty” is applied in order to earn time in short term and be able to provide a function in a system more quickly. This primitive implementation will at a later stage need to be corrected and rewritten, and the longer it takes, the more advanced, complex and time-consuming the correction will be. As EA has grown, major scientific and academic contributions have been developed. What is still missing is insight and ability to include a debt concept, which not only address TD but also business aspects. By adapting the TD concept in the EA domain, a new metaphor, providing a holistic perspective, has been proposed; Enterprise Architecture Debt (EAD). Up to the present debts for measuring EAD has been identified, but current research projects has not yet identified when a certain measure is to be considered of high or low quality. There is a need to develop a process for deriving such thresholds and identifying them. To be able to communicate the severity of an EAD to stakeholders, thresholds for EAD measures plays an important role. These thresholds will in the long term play a role in providing a tool for computer scientist working in organizations exploiting EA, and also contribute to current research within the field of IT-management and EA. By adopting a systematic process for defining expert driven thresholds a first version of a process for defining EAD thresholds could be presented and tested with domain experts. Five common opinions were detected, regarding the process, among the experts. The process could potentially facilitate useful communication and it was considered positive that it highlighted the context of the EAD. Also, that clearer process description and real-world EA model examples was needed, and that the moment of selecting membership function was unnecessary came up. Further, drivers for EAD thresholds and areas where it is perceived as important to have thresholds for EADs was a focus during the study. Cost and time, responsibility and engagement and context are perceived to be important drivers for EAD thresholds. While the business-it alignment and master data are seen as important areas. Also, context can play an important role when determine important areas.
En vanlig utmaning inom organisationer är uppfattningen av att olika språka talas på IT-avdelningen och övriga avdelningar. Medarbetare kommer från olika bakgrund, har olika kunskapsbas och ibland till och med olika mål, vilket kan göra fastställandet av riktning mer utmanande. Enterprise Architecture (EA) kan säkerställa att IT investeringar och affärs direktiv går i samma riktning och kan därmed potentiellt lösa problem i anslutning till IT och övrig affärsverksamhet som uppstått på grund av detta och skapa värde till organisationen. Teknisk skuld är ett väletablerat koncept inom mjukvaruutveckling och syftar till att enlösning som är ”quick and dirty” tillämpas för att vinna tid på kort sikt och kunna tillämpa en funktionalitet i ett system snabbare. Denna primitiva implementation kommer vid senare tillfälle behöva korrigeras och skrivas om. Ju längre tid det tar desto mer avancerad, komplex och tidskrävande kommer ändringen att bli. I takt med att EA har vuxit har stora vetenskapliga och akademiska bidrag utvecklats. Vad som fortfarande saknas är insikt och förmåga att inkludera ett skuldkoncept som inte bara adresserar tekniks skuld utan även affärsaspekter. Genom att introducera konceptet teknisk skult i EA domänen har en ny metafor, som tillhandahåller ett helhetsperspektiv, föreslagits; Enterprise Architecture Debt (EA Debt). Fram tills idag har skulder för att mäta EA Debt blivit identifierade, men aktuella forskningsprojekt har ännu inte identifierat när en viss EA Debt är hög eller låg. Det finns ett behov av att utveckla en process för att härleda sådana gränsvärden och identifiera dem. För att kunna kommunicera all varlighetsgraden för en EA Debt till intressenter kan gränsvärden för EA Debt spela en viktig roll. Dessa gränsvärden kommer på lång sikt spela en roll när det kommer till att tillhandahålla verktyg för datavetare som arbetar i organisationer som tillämpar EA, och också bidra till aktuell forskning inom IT-förvaltning och EA. Genom att anta en systematisk process för att definiera expertdrivna gränsvärden har en första version av en process för att definiera EA Debt-gränsvärden kunnat presenteras och testas med domän-experter. Fem vanliga uppfattningar, gällande processen, kunde uppräckas bland experterna. Processens skulle också potentiellt kunna främja användbar kommunikation och det ansågs positivt att den belysta och tog hänsyn till kontext gällande EA Debt. Att tydligare processbeskrivning och verklighetstrogna EA-modeller som exempel behövdes samt att momentet där medlemsfunktion skulle väljas var onödigt kom också upp. Vidare så fokuserade studien på drivkrafter för att ta fram gränsvärden för EA Debt och områden där uppfattningen är att detta är viktigt. Kostnad och tid, ansvar och engagemang och kontext är uppfattade som viktiga drivkrafter när det kommer till gränsvärden för EA skuld, medan inriktningen för IT och övrig affärsverksamhet och basdata ses som viktiga områden. Även kontexten kan ha en viktig roll när det kommer till att avgöra vilka områden som är viktiga.

Enterprise Architecture is so far the highest development step in IT's architectural description of enterprises. At the beginning, just technological architecture existed. However, with the quickly growing complexity of IT other domains occurred, that had to be described. Information or application architectures can serve as examples. IT then realized, that it needed to add to its IT architectures a business view and consequently the discipline Enterprise Architecture came into being. Strategic management is crucial for the development of each enterprise. The thesis focuses on the strategic management of business and the strategic management of IT. The strategic management of business consists of a business strategy and an operating model. To the strategic management of IT then belongs an information strategy and IT governance. Business-IT alignment further explores and ensures the accord between the strategic management of business and the strategic management of IT. The aim of the thesis is to describe the relationship of Enterprise Architecture and the different forms of strategic management and to express to which rate Enterprise Architecture supports them. The explored relationships are: - The relationship of Enterprise Architecture and business strategy - The relationship of Enterprise Architecture and operating models - The relationship of Enterprise Architecture and information strategy - The relationship of Enterprise Architecture and IT governance - The relationship of Enterprise Architecture and business-IT alignment The goals of the thesis are reached via theoretical research and subsequent deduction. The author's personal asset consists of creating a hierarchical model of Enterprise Architecture, of defining Enterprise Architecture's reaction to business strategies, of modifying the methodology MMDIS in respect of information strategy, of depicting, how Enterprise Architecture can be used in IT governance, of illustrating, where Enterprise Architecture contributes to business-IT alignment and of assessing, to which rate Enterprise Architecture supports the different forms of strategic management.

The aim of this thesis is to find the relationship between enterprise architecture (EA) and project management. This objective is achieved through two milestones - the first aims to answer the question whether EA can be controlled (in the case of this work represented an architectural framework, TOGAF), using the principles of project management (where this work represented CzNCB standard) and the second deals with issue of the outputs of EA (TOGAF) as a reference for development projects (controlled by CzNCB). The first - EA management and project management focuses on project management of one iteration of the process of building enterprise architecture process model according to architectural framework, TOGAF ADM. It examines whether the EA project manage the building and what is or should be in project management according CzNCB add to the building through the allow EA to drive. In the second of them - EA and project development objectives are achieved partial identification information, which adds to the architecture project and a comparison with the standard for project management CzNCB. The benefit of this work is the best link building practises used in the EA through TOGAF ADM and project management based on standard CzNCB. This work may be a practical benefit for the company that has implemented project management by IPMA and intends to build the enterprise architecture. Such enterprise content of this work will provide guidance on how to manage the building through the EA CzNCB and consequently help to apply EA outputs to development projects. In the first part of this work is to analyze the state of knowledge in project management and EA. The second part is devoted to characterizing concepts closely related to both areas. In the third part of the methodological basis set out analysis of the relationship of project management and EA. The following two chapters, which are separately engaged in sub-goals of this work - Management EA and the EA and project management and development projects.

Enterprise architectures are exposed to fast emerging business and information technology capabilities. A prominent example is the paradigm of service-orientation, which leads to its own architectural requirements and impacts the design and ongoing evolution of Enterprise Architectures. This thesis develops the first theoretical model describing enterprise architecture evolution and outcomes in light of a changing IT landscape such as service-oriented architectures. The developed theoretical model explains enterprise architecture evolution, its main stages and related capabilities. This model can be used to derive theoretical, sound guidelines to manage enterprise architectures in a changing environment.

This study explores the application of EA for business network planning, where it builds upon relevant and well-established descriptive and prescriptive aspects of EA. Prescriptive aspects include integrated models for services, business processes, and resources among other organizational artifacts, at both business and IT levels. Descriptive aspects include ontological classifications of business functionality, which allow EA models to be aligned semantically to both business operations and business strategy. In order to explore and develop the extension of EA, a list of six novation constraints were conceptualised and defined through a literature review and insights from the case studies.

Over the last two decades competition amongst organisations including financial institutions has increased tremendously. The value of information is critical to competition in different organisations. In addition, the management of cost of delivery and cohesiveness of information flow and use in the organisations continue a challenge to information technology (IT). In an attempt to address these challenges, many organisations sought various solutions, including enterprise information architecture (EIA). The EIA is intended to address the needs of the organisation for competitive advantage. This research article focused on the role of principles in the development and implementation of EIA. The article aimed to investigate how EIA could be best leveraged, exploited, or otherwise used to provide business value. The research brings about a fresh perspective and new methodological principles required in architecting the enterprise information.

The goals for this study were twofold. The first goal was to identify planning variables for linking both organizational and architectural objectives for developing enterprise integration architecture. The second goal was to validate enterprise integration modeling methodology as a viable planning tool for the design, development, and maintenance of the enterprise integration architecture. This lack of linkage at the intellectual dimension level can be characterized as having a dysfunctional effect on enterprise integration strategy formulation and infrastructure development. There is a disjoint between adoptions of appropriate information technology in relation to organizational objectives. This includes misapplication of investments in information technology selection and business systems development portfolio, failed information systems projects, architectures that do not support the strategic direction, and the organization's inability to manage change associated with environmental imperatives that impact the firm's ability to define information technology and systems requirements for competitive positioning. In order to achieve the objectives the author in this research, developed a conceptual Enterprise Integration Architecture Planning Model and Methodology (EIAPMIM) model as the basis for linking enterprise integration architecture objectives and organizational objectives. Research data confirmed the need to effect linkages between organizational objectives and architectural objectives to achieve enterprise integration and validated enterprise integration modeling as the means by which enterprise integration architecture is developed.

Thesis (MTech (Information Technology))--Cape Peninsula University of Technology, 2012.
South Africa has a complex financial and retail service industry with high reliance on the use of IT systems to ensure effectiveness and maintainability. Decision making and improved outcomes may be done through an IT aligned enterprise architecture (EA) strategy. EA is a capability that contributes to the support and success of an organisations' IT. Organisations are currently using EA to better align IT and the business strategy which provides a comprehensive v.ew of the IT system. Thus, EA is increasing in organisations yet the measurement and value of EA is limited to organisations and enterprise architects. The discussions of the benefits and value of EA has been discussed for several years, however there are still no consensus about how the benefits and value of EA can be measured. The lack and clear understanding of the benefits and value of EA needs to consider different aspects of IT as well as the shareholders when measuring the benefits and value of EA to an organisation.

Contemporary enterprises depend to great extent on software systems. During the past decades the number of systems has been constantly increasing and these systems have become more integrated with one another. This has lead to a growing complexity in managing software systems and their environment. At the same time business environments today need to progress and change rapidly to keep up with evolving markets. As the business processes change, the systems need to be modified in order to continue supporting the processes. The complexity increase and growing demand for rapid change makes the management of enterprise systems a very important issue. In order to achieve effective and efficient management, it is essential to be able to analyze the system modifiability (i.e. estimate the future change cost). This is addressed in the thesis by employing architectural models. The contribution of this thesis is a method for software system modifiability analysis using enterprise architecture models. The contribution includes an enterprise architecture analysis formalism, a modifiability metamodel (i.e. a modeling language), and a method for creating metamodels. The proposed approach allows IT-decision makers to model and analyze change projects. By doing so, high-quality decision support regarding change project costs is received. This thesis is a composite thesis consisting of five papers and an introduction. Paper A evaluatesa number of analysis formalisms and proposes extended influence diagrams to be employed for enterprise architecture analysis. Paper B presents the first version of the modifiability metamodel. InPaper C, a method for creating enterprise architecture metamodels is proposed. This method aims to be general, i.e. can be employed for other IT-related quality analyses such as interoperability, security, and availability. The paper does however use modifiability as a running case. The second version of the modifiability metamodel for change project cost estimation is fully described in Paper D. Finally, Paper E validates the proposed method and metamodel by surveying 110 experts and studying 21 change projects at four large Nordic companies. The validation indicates that the method and metamodel are useful, contain the right set of elements and provide good estimation capabilities.
QC20100716

The Enterprise Architecture Analysis Tool, EAAT, is a software tool developed by the department of Industrial Information- and Control systems, ICS, at the Royal Institute of Technology, Stockholm, Sweden. EAAT is a modeling tool that combines Enterprise Architecture (EA) modeling with probabilistic relational modeling. Therefore EAAT makes it possible to design, describe and analyze the organizational structure, business processes, information systems and infrastructure within an enterprise. During this study EAAT has been validated in order to assess the usability of the tool and to provide suggestion of improvement. To reach conclusions EA models of IT systems out in the industry has been created in EAAT. A usability study has been performed in order to find weaknesses and strength in the tools user interface. The results of the study consist of a couple of scenarios of how the tool might be used by the industry. An important feature to improve is the possibility to easily find the weak parts of the system. The user interface should provide more feedback to the user. The modeling process could be improved by providing the user with suggestions on what to do next in order to reach a full and complete model.

We believe there to be a possible problem with Enterprise Architecture, in that in using standardizations such as frameworks stifles creativity and innovations, focusing on IT-environments. This assumption is not new as there already are thoughts in existence on this subject, each side discussing if there is a fault or not. Out of our own interest we delve deeper into the subject of Enterprise Architecture to see if there is any truth in our assumption and to see if there is anything anyone can do to compensate or solve this perceived problem. We look into what Enterprise Architecture consists of and examine four different popular frameworks associated with it: TOGAF, FEA, Gartner and Zachman. We learn about creativity in Information Systems organizations and its connection to IT. Our research strategy for this thesis is deduction together with two separate phases, one phase is exploratory and the other descriptive. We examine the nature of creativity and innovation, there too with an emphasis on IT. In order to find out if our assumption is correct we seek out literature, articles and other sources of information on innovations, creativity and frameworks. Armed with this information we seek out and perform interviews with people from large commercial organizations who have hands-on work experience working with Enterprise Architecture in order to see if our assumptions have any form of validity and to gain some insight into the subject matter. The method components for this thesis are literature review, document study and interviews. Analyzed with the help of SWOT we use the data gathered from the interviews to gain a visual representation of the results, to see the pros and cons of Enterprise Architecture. The results show that supplements or tools are used in order to produce or support business innovations, using departments, business related social networks or techniques to compensate. Hampering factors for business innovation can be internal conflicts, struggles between different groups for different EA solutions. Promoting business innovation through EA can come from mixing framework bits together, giving the result of a flexible and adaptive framework. It can also come from acting as a common language and a bridge between different hierarchies. EA aids with difficult decisions, evaluating which alternatives for realization and the order services are realized. Meetings can be used to compensate the lack of creativity and innovation rising from EA. A negative consequence of EA can occur during implementation of things related to EA in larger companies. No examples of companies that failed with creating business innovation in their IT with EA were found.
Program: Kandidatutbildning i informatik

Thesis (S.M. in Engineering and Management)--Massachusetts Institute of Technology, Engineering Systems Division, 2013.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 56-57).
This paper reports results of a study done to understand the Enterprise Architecture (EA) landscape in Singapore Government Agencies, to gather some best practices in doing EA in these agencies, and to postulate how the Singapore Government might get more value out of EA. Firstly, this paper reviews the EA field on why EA is important and what are some key challenges EA practitioners face. Secondly, this paper reviews and analyzes data from a EA survey of 18 Singapore Government Agencies. The analysis is done by comparing against data from a similar survey collected from over 100 organizations worldwide. In addition, the analysis also draws upon EA research done by MIT's Center for Information System Research. Thirdly, this paper reviews best practices and a case study collected from a subset of the studied Singapore Government Agencies. This paper concludes by rounding up the key findings and hypothesizing that there is a need for stronger inhouse design/architecting capabilities within the Singapore Government.
by Ming Fai Wong.
S.M.in Engineering and Management

La plupart des projets de développement logiciel actuel dépendent de l'utilisation des solutions existantes pour gagner du temps et réduire les coûts de développement. Pour atteindre cet objectif, les entreprises doivent tirer parti des fonctionnalités offertes par les services techniques ou les interfaces de programmation applicatives exposées par les solutions existantes. La collecte et la qualification de ces composants ou services techniques permet de les réutiliser directement ou par orchestration. L'objectif de ce travail est double. Tout d'abord, nous visons la conception d'un conteneur de capacités logicielles qui offre une vision plus large des solutions applicatives internes ou externes d'une organisation. Le deuxième objectif est de définir un modèle d'exploitation de ces profils de capacités logicielles en adéquation avec l'ingénierie des besoins et l'architecture d'entreprise, afin de combler l'écart entre les objectifs des parties prenantes et ce qui peut être fourni comme solution pratique. Cependant, pour atteindre les objectifs susmentionnés, il y a de nombreux défis à relever pour gérer la complexité de l'exploitation des profils de capacités logicielles internes ou externes, afin de sélectionner les meilleurs composants candidats pour servir d'éléments constitutifs dans un nouveau système. Parmi ces défis, on peut citer l'identification des connaissances architecturales pour l'évaluation et la réutilisation des composants techniques, ou l'alignement des besoins et des artefacts d'architecture dans un cycle d'ingénierie pour la consolidation et le raffinement des exigences, afin de faciliter la découverte et la réutilisation des solutions applicatives existantes. A cet effet, nous définissons un Framework offrant un processus de qualification qui permet de recueillir les exigences initiales utilisées pour guider le développement des applications existantes et des services techniques exposés. Le processus de qualification est4basé sur un profil de capacité d'architecture d'entreprise proposé et de son ontologie associée. Cette dernière est utile pour spécifier formellement le profil de capacité produit qui offre une qualification couvrant les aspects organisationnels, opérationnels et techniques des applications orientées services. De plus, une méthodologie d'exploitation du conteneur conçu pour agréger ces profiles est proposée avec le Framework et basée sur l'alignement du processus d'ingénierie des besoins avec une méthode de développement d'architecture. Ces derniers évoluent ensemble pour étudier la plus grande compatibilité fonctionnelle et technique des fonctionnalités souhaitées et des contraintes associées, pour répondre aux besoins des utilisateurs finaux et réutiliser efficacement les solutions qualifiées.Notre contribution vise à améliorer l'évaluation, la découverte et la réutilisation des applications et des services techniques associés. Par ailleurs, l'originalité de ce travail de recherche consiste à mettre à niveau la recherche sur la consommation et l'orchestration des services au niveau des besoins des utilisateurs finaux, afin d'accélérer et de faciliter le développement d'applications métier futures. Une implémentation du Framework ainsi qu'une étude de cas industriels sont proposés pour valider et démontrer l'efficacité de cette approche
Most of today's software development projects depend on the usage of existing solutions to save time and development cost. To achieve this goal, companies should take advantage of the features provided by services or application programming interfaces exposed by existing solutions. Collecting and qualifying IT components and services helps to reuse them directly or via orchestration. The goal of this work is twofold. First, we target the design of a software capability container that provides a broader view of an organization’s internal and external software. The second objective is to define an exploitation model of the software capability profiles in line with requirements engineering and enterprise architecture, to fill the gap between the goals of the stakeholders and what can be delivered as a practical solution. However, to achieve the above-stated objectives, there are many challenges to manage the complexity of the exploitation of internal or external’s software capability profiles, to select the best candidate components to act as a building blocks in a new system. Among those challenges, one can mention the identification of architectural artifacts for the evaluation and reuse of software components. Adding to this challenge, the alignment of requirements and architectural artifacts in engineering cycle for requirements consolidation and refinement to facilitate the discovery and reuse of existing solutions.For this purpose, we define a Framework offering a qualification process that helps to retrieve and gather initial requirements used to guide the development of existing software and related services. The qualification process is based on a proposed Enterprise Architecture Capability Profile and its associated ontology. This latter is useful to formally specify and encode the produced capability2profile that offers a qualification and covers business, operational and technical aspects for service-oriented software. Furthermore, an exploitation methodology of the designed container is proposed along with the Framework and based on the alignment of requirements engineering process with an architecture development method. These latter evolve together to investigate the highest functional and technical compatibility of the desired functionalities and related constraints, to respond to end-user’s requirements and efficiently reuse the qualified solutions.Our contribution aims to improve the evaluation, discovery, and reuse of existing software and related services. Besides, the originality of this research work consists in upgrading research on services consumption and orchestration to the level of end-users’ requirements, mapped with advanced service assets as an enabler for accelerating business application development. An implementation of the Framework along with an industrial case study are proposed to validate and demonstrate the effectiveness of this approach

This research examines the rationale and impact of Enterprise Architecture (EA) adoption in the UK Higher Educational (HE) sector. EA supports alignment of Information Systems (IS) capability and high-level Strategic Planning for organisations. Previous studies in HE sector show that IS planning difficulties are increasingly affecting required levels of effectiveness and future changes. Institutions identify the need for a business-like approach, to support senior managers in the decision-making in times of unprecedented economic and sector revolution. Adopters spearheading the process claim that EA concepts and tools will enable institutions capture IT resources, align administrative processes, leverage IS investments and coordinate information requirements and regulations effectively. This claim is supported by the identification of benefits of EA in other public and private sectors. Using 4 UK universities, this study reviews the practices and effects of EA in the larger but more traditional universities and medium-sized but newer universities. The institutions were investigated using interpretive research methods. Data was collected through semi-structured interviews and thematic analysis was used to analyse the data and interpret the findings based on a combination of existing and new theoretical constructs. A summary of the research findings states four key success factors for the adoption and institutionalisation of EA in HE institutions. They are: (i) Senior management support, appropriate organisational structures, actors and scope of EA work (ii) Key stakeholder buy-in and commitment (iii) Resources (iv) Evaluation metrics. HE institutions are not adverse to EA adoption; but are aware that institutional actors and cultures shape the adoption. There are necessary support structures that should be in place: (i) institutions need to have a formalised governance structure, which ensures proper planning procedures are enforced and change is monitored effectively, (ii) the right people skill and availability would ensure success, (iii) adopting a systematic and continuous approach to business process review (iv) institutions need to develop simple and flexible IT infrastructure to enable requirements for integration, accessibility, and agility.

Thesis (MTech (Information Technology))--Cape Peninsula University of Technology, 2011.
The adoption of Enterprise Architecture (EA) methodologies within organizations is causing an interest in the methodologies and supporting technologies available. Service Oriented Architecture (SOA) supports EA in many facets. However, there is much suspension with regard to the relationship between EA and SOA within organizations as well as the guidelines that organisations should follow in order for SOA to enable EA. There are potential problems that may arise if this relationship between SOA and EA is not agreed to at the outset of implementing an EA. The purpose of this research is to investigate the guidelines that are needed for SOA to enable EA, in order to provide practical steps that organisations can use to begin aligning SOA and EA, ensuring that these initiatives are driven from a business perspective. A qualitative approach using a case study was used as a methodology for this research. The data collection was conducted using semi-structured interviews, and the guidelines that were derived were validated through a survey that was distributed to industry architecture practitioners. The contribution of this research was a set of guidelines that can be used for SOA to enable EA. Further research areas were highlighted, including investigating the mapping of the guidelines that were derived from this research, into the EA frameworks that exist such as TOGAF and ZACHMAN.

Contemporary Enterprise Information Architecture (EIA) design practice in the industry still suffers from issues that hamper the investment in the EIA design. First and foremost of these issues is the shortcoming of EIA design research to bridge the gap between business and systems (or information) architectures. Secondly, contemporary developed business process architecture methods, and in particular object-based ones have not been fully exploited for EIA design and thus widening the gap between business processes and systems. In practice, knowledge-driven approaches have been thoroughly influencing EIA design. Thirdly, the lack of using knowledge representation methods adversely affected the automation (or semi-automation) of the EIA design process. Software Engineering (SE) technologies and Knowledge Representation using ontologies continue to prove instrumental in the design of domain knowledge. Finally, current EIA development methods have often resulted in complex designs that hampered both adopting and exploiting EIA in medium to large scale organisations. This research is aimed at investigating the derivation of the EIA from a given semantic representation of object-based Business Process Architecture (BPA), and in particular Riva-based BPA using the design science research-based methodology. The key design artefact of this research is the development of the BPAOntoEIA framework that semantically derives EIA from a semantic representation of Riva-based BPA of an enterprise. In this framework, EIA elements were derived from the semantic Riva BPA elements and associated business process models, with forward and backward traceability from/to the derived EIA to/from the original BPA. The BPAOntoEIA framework has been evaluated using the semantic Cancer Care and Registration BPA in Jordan. This framework has been validated using an authentic concern-based evaluation framework employing both static and dynamic validation approaches. The BPAOntoEIA framework contributes to bridging the gap between the business and systems world by providing a business/IT alignment through the EIA derivation process, and using the semantic knowledge of business processes within the resultant EIA. A major novel contribution is the introduction of new evaluation metrics for EIA design, which are quantitative, and are not only indicative of the quality of the semantic EIA derivation from the associated BPA but also the extent of utilising business process knowledge and traceability amongst EIA elements. Amongst other novel contributions is the semantic EIA derivation process that comprises a suite of the Semantic Web Rules Language (SWRL) rules applied on the semantic BPA elements. The derivation scheme utilises the generic EIA (gEIAOnt) ontology that was developed in this research and represents a semantic meta-model of EIA elements of a generic enterprise. The resultant EIA provides a highly coherent semantic information model that is in-line with the theory of EIA design, semantically enriched, and fully utilises the semantic knowledge of business processes. Benefits of this research to industry include the semantic EIA derivation process and a resultant information model that utilises the semantic information of business processes in the enterprise. Therefore, this enables the enterprise strategic management to plan for a single, secure and accessible information resource that is business process driven, and enabled in an agile environment. The semantic enrichment of the EIA is a starting point for a simplistic design of a domain-independent semantic enterprise architecture for the development of systems of systems in loosely coupled enterprises.

Thesis (Ph.D)--Industrial and Systems Engineering, Georgia Institute of Technology, 2008.
Committee Chair: Dr. William B. Rouse; Committee Member: Dr. Amy Pritchett; Committee Member: Dr. Leon McGinnis; Committee Member: Dr. Mike Cummins; Committee Member: Dr. Steve Cross. Part of the SMARTech Electronic Thesis and Dissertation Collection.

Made available in DSpace on 2016-08-29T15:33:18Z (GMT). No. of bitstreams: 1 tese_5494_.pdf: 2904195 bytes, checksum: c6fded7753ec6bae38735ba2962dbb09 (MD5) Previous issue date: 2012-08-31
The need to relate the various architectural domains captured in partial descriptions of an enterprise is addressed in virtually all enterprise modeling approaches. One of these domains, namely that of organizational behavior, has received significant attention in recent years in the context of business process modeling and management. Another important domain, that of organizational structure is strongly inter-related with the process domain. While the process domain focuses on how the business process activities are structured and performed, the organizational structure domain focuses on who performs these activities, i.e., which kinds of entities in an organization are capable of performing work. Given the strong connection between the organizational behavior and organizational resources, we argue that any comprehensive enterprise modeling technique should explicitly establish the relations between the modeling elements that represent organizational behavior, called here behavioral elements, and those used to represent the organizational resources (organizational actors) involved in these activities, called here active structure elements. Despite the importance of the relations between these architectural domains, many of the current enterprise architecture and business process modeling approaches lack support for the expressiveness of a number of important active structure allocation scenarios. This work aims to overcome these limitations by proposing a framework for active structure assignment that can be applied to enterprise architecture and business process modeling approaches. This framework enriches the expressiveness of existing techniques and supports the definition of precise active structure assignments. It is designed such that it should be applicable to a number of enterprise architecture and business process modeling languages, i.e., one should be able to use and apply different (enterprise and business process) modeling languages to the framework with minor changes.

This master thesis attempted to create an enterprise architecture tool implementationof the new EU legislation General Data Protection Regulation. Using the archimatestandard as well as the tool EAAT (Enterprise Architecture Analysis Tool) changes havebeen proposed so that compliance with the legislation can be veried. 19 of the legislationsarticles are discussed and implemented with another eight discussed why they are notimplemented. Each implemented article is followed by a model snapshot as well as somepseudo-code for easier implementation independent of the tool used. Due to unforeseenproblems, no working implementation was not created but the proposed changes can bemade to t any tool built on Archimate's standard. Finally the proposed modication isdiscussed and future work related to modelling of the General Data Protection Regulationis proposed.
Detta examensarbete försökte skapa en implementation för enterprisearkitektursprogramav den nya EU-lagen Allmän Uppgiftsskyddsförordning. Genom att användaArchimates standard tillsammans med verktyget EAAT (Enterprise Architecture AnalysisTool) har förslag om modifikationer lagts fram så att foglighet med lagen kan testas. 19 avlagens artiklar diskuteras och har implementerats med åtta andra diskuterade varför de inteär implementerade. Varje implementerad artikel följs upp av en modell-bild samt pseudokodför att underlätta implementationer i andra verktyg. På grund av oförutsedda problemhar ingen fungerande implementation gjorts men the föreslagna modifikationerna kan implementerasi andra verktyg som desginats med Archimates standard i åtanke. Slutligendiskuteras de föreslagna modifikationerna och framtida arbeten relaterade till modelleringav den Allmänna Uppgiftsskyddsförordningen har lagts fram.

Technical debt is used to describe the changing or to maintain a system due to expedient shortcuts done during its development. In the context of the software development industry, technical debt is regarded as a critical issue in terms of the negative consequences such as increased software development cost, low product quality, decreased maintainability, and slowed progress to the long-term success of developing software. Code Smells are well informed in the domain of Technical Debt. They indicate to the common bad practices that may impair the future quality of the software system. By identifying those Code Smells, it is possible to give an improved solution or make the developers aware of a possible deficiency. I explore the premise that technical debt within the enterprise should be viewed as a tool. Extensible and Appropriate tools can check the Code Smells automatically and improve the quality assessment accordingly. However, in the field of Enterprise Architecture(EA), common bad habits in EA can be called EA Smells. EA Smells itself can be a component of EA Debt. Enterprise Architecture Debt can be defined as such a metric that depicts the deviation of the currently present state of an enterprise from a hypothetical ideal state.In this thesis, we introduce SmellCull as an extensible tool for capturing, tracking and managing Enterprise Architecture debt in the EA field. SmellCull allows measuring different kinds of Enterprise Architecture debts for EA Model. SmellCull is extensible since different types of Model can be integrated as input into the tool environment and provides developers with a lightweight tool to capture EA debt and make it easier to understand them indicating corresponding parts in the implementation. The tool is used to create propagation paths for the EA debt. This allows for an up-to-date and accurate presentation of EA debt to be upheld, which enables developer conducted implementation-level micromanagement as well as higher-level debt management.Since the tool is sophisticated enough, automated detection supports the design process and ongoing change of EAS(Enterprise Architecture System). This includes the strategic development of EAS with the corresponding roadmaps, as well as design assurance and performance monitoring to assess the quality of data in EA repositories and the compliance with certain standards defined by EA Smells. Due to the limited scope of master thesis, the tool will identify a few number of EA debt. At the end, some future work suggestions in the context of identifying more salable Enterprise Architecture Debts with this tool are given.
Teknisk skuld dvs dålig eller kortsiktig programutveckling som belastning på IT-system måste förr eller senare återbetalas. I industrin betraktas teknisk skuld som en kritisk fråga när det gäller de negativa konsekvenserna som ökad mjukvaruutvecklingskostnad, låg produktkvalitet, minska underhåll och långsammare framsteg till den långsiktiga framgången med att utveckla programvara. Dålig kodkvalitet “code smell” är vanligt förekommande teknisk skuld. Det uppkommer i vanliga dåliga metoder “anti-patterns” som försämrar programvarans framtida kvalitet. För att kunna identifiera bristande kodkvalitet är det möjligt att skapa en förbättrad lösning eller göra utvecklare medvetna om de möjliga bristerna. Jag undersöker förutsättningarna att en sådan teknisk skuld i företag bör undersökas med en programvara. Utbyggbara och ändamålsenliga programvaror kan analysera källkod och hitta var kvaliteten behöver förbättras. Företagens tekniska skuld kan definieras som ett mått som visar avvikelsen från ett hypotetiskt idealtillstånd genom att jämföra det aktuella tillståndet med praktiska rekommendationer “best practice”. I detta examensarbete introducerar jag SmellCull som ett utbyggbart verktyg för att hitta, spåra och hantera bristfällig kodkvalitet inom företagsarkitektur (EA). SmellCull tillåter mätning av olika typer av tekiska skulder för EA modellen. SmellCull är utbyggbart genom att olika typer av datamodeller kan integreras som indata i miljön, och det ger utveck-lare ett lätt verktyg för att hantera teknisk skuld i programmeringsprojekt och hjälpa projektdeltagarna i programmeringsprojekt att förstå vad orsakar brister i kodkvalitet.  Eftersom verktyget är tillräckligt sofistikerat finns det automatiserad spårning, designprocess och kontinuerlig förbättring av EAS (Enterprise Architecture System). Detta inkluderar strategisk utveckling av EAS med motsvarande färdplan, samt konstruktionssäkerhet och prestandäovervakning för att bedöma kvaliteten på data i EA förvar och efterlevnaden av vissa standarder som definieras av EA code smell detection. På grund av den begränsade omfattningen av examensarbetet kommer verktyget att  identifiera några få EA skuld. I slutet, några framtida arbetsförslag i samband med identifiering mer säljbara företagsarkitekturskulder med detta verktyg ges.

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.

Enterprise architecture frameworks (EAFs) have been used to plan and manage large-scale enterprise deployments for more than four decades. EAFs are important tools used by systems engineers and are integral to characterize enterprise information architectures. They are increasingly being used as a proxy for managing entire organizations – enterprises. Enterprises represent complex, multi-disciplinary, socio-technical systems. They are ubiquitous, and involve and affect a vast number of humans every day. However, as inter-disciplinary tools for the management of the enterprise, there are certain limitations to the efficacy of existing enterprise architecture frameworks. The effective management of enterprises presents significant challenge and opportunity for the systems engineering community. This research discusses the limitations of, and proposes enhancements to, existing EAFs, based on research into extant business management frameworks. An historical perspective is provided on both systems engineering and business enterprise domain frameworks. Research into the common elements of successful business management frameworks confirms the limitations of existing systems engineering frameworks and suggests key additions for enhanced efficacy. The applicability and relevance of enhancing extant enterprise architectures with elements from extant business frameworks is examined. Finally, recommendations are made for enhancements to extant frameworks and suggestions advanced on future research into efficacy. This dissertation concludes with implications of these findings for systems engineers engaged in enterprise architecture and enterprise transformation efforts and a recommendation that systems engineers take a more holistic approach in their enterprise architecture and enterprise transformation efforts.

The research focuses on the relationship and interlinking between the different architectural domains within the enterprise architecture of an enterprise. The architectural domains are grouped together as business architecture, information architecture and technology architecture. First, a literature review of the definitions, history, role, functions and qualities, existing frameworks, models and domains of enterprise architecture was conducted. The definitions; role and benefits; models, frameworks, ontologies and descriptive languages of the different architectural domains were then studied as background and basis. New definitions were deduced. Second, the modelling methodology, process, elements and deliverables were investigated. An integration metamodel for enterprise architecture was developed, according to this modelling methodology. The metamodel is called the Relational Enterprise Architecture Metamodel or the REAM. Third, the research methodology for the empirical research section was investigated and determined. The proposed conceptual metamodel has been assessed through a case study within three different industries each. The feedback from the case studies was used to modify/enhance the metamodel. The possibilities for application of the modified model were then assessed at the University of Pretoria. The contribution of this research lies mainly in the development, empirical testing and refining of an integrated EA metamodel (REAM) as well as the development of new definitions for enterprise, business, information and technology architecture and relating them.
Thesis (PhD)--University of Pretoria 2015.
Information Science
Unrestricted

Made available in DSpace on 2014-06-12T15:51:46Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008
O crescimento do tamanho, complexidade e demanda por qualidade dos sistemas de software são alguns dos motivos que tem aumentado o interesse na área de arquitetura de software. Consequentemente, processos de arquitetura de software surgiram a fim de auxiliar os arquitetos na construção dessas arquiteturas. Arquitetura Orientada a Serviços (SOA) surgiu como um tipo de arquitetura de software para construir sistemas através da composição de serviços. Assim como o paradigma de orientação a objetos, o paradigma de orientação a serviços tem trazido uma abordagem de projeto distinta que introduz princípios que governam o posicionamento e o projeto dos componentes arquiteturais. Além disso, SOA é um paradigma para organização e utilização de capacidades distribuídas que podem estar sob o controle de diferentes domínios. No contexto empresarial, SOA permite que organizações, que tenham uma infra-estrutura de aplicações fragmentadas sob a administração de diferentes áreas de negócio, possam integrar estas aplicações no nível de serviço. Por um lado, os processos de arquitetura tradicionais não abrangem estes aspectos de SOA. Por outro lado, as abordagens de SOA disponíveis não satisfazem todos os fundamentos da arquitetura de software. Neste sentido, esta dissertação propõe um processo sistemático de arquitetura de software baseado em SOA que compreende os principais fundamentos da arquitetura de software e características inerentes a SOA a fim de guiar os arquitetos na construção de uma descrição arquitetural para SOA. Adicionalmente, um estudo experimental foi definido, planejado, executado e analisado a fim de avaliar o processo proposto

Information technology has become increasingly important to individuals and organizations alike. Not only does IT allow us to do what we always did faster and more effectively, but it also allows us to do new things, organize ourselves differently, and work in ways previously unimaginable. However, these advantages come at a cost: as we become increasingly dependent upon IT services, we also demand that they are continuously and uninterruptedly available for use. Despite advances in reliability engineering, the complexity of today's increasingly integrated systems offers a non-trivial challenge in this respect. How can high availability of enterprise IT services be maintained in the face of constant additions and upgrades, decade-long life-cycles, dependencies upon third-parties and the ever-present business-imposed requirement of flexible and agile IT services? The contribution of this thesis includes (i) an enterprise architecture framework that offers a unique and action-guiding way to analyze service availability, (ii) identification of causal factors that affect the availability of enterprise IT services, (iii) a study of the use of fault trees for enterprise architecture availability analysis, and (iv) principles for how to think about availability management. This thesis is a composite thesis of five papers. Paper 1 offers a framework for thinking about enterprise IT service availability management, highlighting the importance of variance of outage costs. Paper 2 shows how enterprise architecture (EA) frameworks for dependency analysis can be extended with Fault Tree Analysis (FTA) and Bayesian networks (BN) techniques. FTA and BN are proven formal methods for reliability and availability modeling. Paper 3 describes a Bayesian prediction model for systems availability, based on expert elicitation from 50 experts. Paper 4 combines FTA and constructs from the ArchiMate EA language into a method for availability analysis on the enterprise level. The method is validated by five case studies, where annual downtime estimates were always within eight hours from the actual values. Paper 5 extends the Bayesian prediction model from paper 3 and the modeling method from paper 4 into a full-blown enterprise architecture framework, expressed in a probabilistic version of the Object Constraint Language. The resulting modeling framework is tested in nine case studies of enterprise information systems.
Informationsteknik blir allt viktigare för både enskilda individer och för organisationer. IT låter oss inte bara arbeta snabbare och effektivare med det vi redan gör, utan låter oss också göra helt nya saker, organisera oss annorlunda och arbeta på nya sätt. Tyvärr har dessa fördelar ett pris: i takt med att vi blir alltmer beroende av IT-tjänster ökar också våra krav på att de är ständigt tillgängliga för oss, utan avbrott. Trots att tillförlitlighetstekniken går framåt utgör dagens alltmer sammankopplade system en svår utmaning i detta avseende. Hur kan man säkerställa hög tillgänglighet hos IT-tjänster som ständigt byggs ut och uppgraderas, som har livscykler på tiotals år, som är beroende av tredjepartsleverantörer och som dessutom måste leva upp till verksamhetskrav på att vara flexibla och agila? Den här avhandlingen innehåller (i) ett arkitekturramverk som på ett unikt sätt kan analysera IT-tjänsters tillgänglighet och ta fram rekommenderade åtgärder, (ii) ett antal identifierade kausalfaktorer som påverkar IT-tjänsters tillgänglighet, (iii) en studie av hur felträd kan användas för arkitekturanalys av tillgänglighet samt (iv) en uppsättning principer för beslutsfattande kring tillgänglighet. Avhandlingen är en sammanläggningsavhandling med fem artiklar. Artikel 1 innehåller ett konceptuellt ramverk för beslutsfattande kring IT-tjänsters tillgänglighet som understryker vikten av variansen hos nertidskostnaderna. Artikel 2 visar hur ramverk för organisationsövergripande arkitektur (s.k. enterprise architecture -- EA) kan utvidgas med felträdsanalys (FTA) och bayesianska nätverk (BN) för analys av beroenden mellan komponenter. FTA och BN är bägge etablerade metoder för tillförlitlighets- och tillgänglighetsmodellering. Artikel 3 beskriver en bayesiansk prediktionsmodell för systemtillgänglighet, baserad på utlåtanden från 50 experter. Artikel 4 kombinerar FTA med modelleringselement från EA-ramverket ArchiMate till en metod för tillgänglighetsanalys på verksamhetsnivå. Metoden har validerats i fem fallstudier, där de estimerade årliga nertiderna alltid låg inom åtta timmar från de faktiska värdena. Artikel 5 utvidgar den bayesianska prediktionsmodellen från artikel 3 och modelleringsmetoden från artikel 4 till ett fullständigt EA-ramverk som uttrycks i en probabilistisk version av Object Constraint Language (OCL). Det resulterande modelleringsramverket har testats i nio fallstudier på verksamhetsstödjande IT-system.

QC 20120912

Thesis (M.S. in Information Technology) Naval Postgraduate School, September 1994.
Thesis advisor(s): Magdi Kamel, Arthur Schoenstadt. v.2 is Appendix D. "September 1994." Bibliography: v.1 (p. 242-271). Also available online.

Organisations globally are communicating their environmental sustainability impact to stakeholders by means of the widely used sustainability report. A key benefit of environmental sustainability reporting is that organisations can gain a positive reputation when these reports are presented to stakeholders. Organisations in South Africa are faced with many challenges regarding managing sustainability information and producing an environmental sustainability report. Two of the primary challenges are the many diverse standards for sustainability reporting and data quality issues. Information Technology (IT) can be used to support and improve the process of sustainability reporting but it is important to align the environmental sustainability strategies with the strategies of business and also with the IT strategy to avoid silos of information and reporting. Enterprise Architecture (EA) can be used to solve alignment problems since it supports business-IT alignment. EA is defined by the International Standards Organisation (ISO) as “The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution”. It can be argued, therefore, that EA can be used to support environmental sustainability information management and the reporting process by means of its support of improved business-IT alignment and ultimately integrated systems. The main objective of this study is to investigate how EA can be used to support environmental information management (EIM) and reporting. A survey study of thirty one prominent South African organisations was undertaken in order to investigate the status of their EA adoption and environmental reporting and EIM processes. An EA for EIM Toolkit and a set of guidelines are proposed which can provide support for EIM through the use of EA. These guidelines were proposed based on best-practice for each of the three process levels of an organisation, namely, the strategic level, the operational level and the technological level. The toolkit and guidelines were derived from theory and the results of the industry survey were then validated by an in-depth analysis of a case study consisting of multiple cases with key employees of seven South African organisations which have proved to be successful at EA and EIM and reporting. The results of the case study show that the EA for EIM Toolkit and related guidelines can assist organisations to align their environmental sustainability strategies with their organisational and IT strategies.

With the divergent information within the underlying enterprise architecture (EA) repositories, automated techniques for supporting enterprise architecture planning (EAP) activities has become a crucial task in order to support enterprise architects. Pragmatically, manual approaches for supporting impact and similarity analysis, which are the main EAP activities, are error-prone, time consuming, and cumbersome. This is due to the fact that enterprise architects need to drill down different architectural models in the EA repository databases in order to assess the impact of change and the similarity between distinct models. Consequently, knowledge discovery techniques are considered to be imperative in terms of supporting impact and similarity analysis. In this research, a knowledge management model has been conceptualized in order to identify the knowledge resources that are needed to support enterprise architects in aligning business and IT resources. The knowledge resources that are needed to support impact and similarity analysis have been addressed from a technical perspective using an agent based approach for knowledge discovery in enterprise architect~re. Such an agent employs an embedded ontology as a knowledge base in order to serve as a vocabulary through which the agent and enterprise architects will communicate without making assumptions about each others language. The inference engine of the agent consists of two ontologically driven knowledge discovery mechanisms, which are association rules mining and hierarchical agglomerative clustering (HAC). Association rules mining is a means to derive the hidden patterns and the relationships between different EA components to support: impact analysis in EA. HAC, on the other hand, is mainly concerned with clustering similar EA models in an EA repository database in order to support EA similarity analysis. Prior to the application of association rules mining and HAC techniques to EA repository databases, the latter are typically pre-processed, indexed, and converted to tabular structures that are ready for quantitative analysis. The association rules and HAC techniques have been implemented and evaluated based on empirical experiments on an illustrative example repository database, which is a part of the ARIS (architecture for integrated information systems) toolset, and represents the different architectural models of a real world automobile company.

IT Consumerization is the phenomenon of consumer-originated and consumer-oriented technologies entering organizations and their corresponding organizational impacts, risks, and opportunities. IT Consumerization has fundamentally changed the way organizations respond to the technology needs of business users as well as the corresponding governance, management, and operational maintenance of information technology. Enterprise Architecture (EA), a practice and body of knowledge that views organizations and enterprises through architectural layers, has been posited as an effective tool in supporting the needs of IT Consumerization. This thesis addresses the question of what roles EA can play in the context of IT Consumerization as well as the general effectiveness and comprehensiveness of current EA frameworks in addressing IT Consumerization needs. Using a single case study design, this research study applied directed content analysis and a deductive thematic analysis approach to answer these questions. The initial set of codes and themes were derived from sensitizing concepts within The Open Group Architectural Framework (TOGAF). Findings from this research suggest that IT Consumerization is a complex domain characterized with unpredictability, unknown decision variables, and no single correct answer in the context of problem solving and decision making. Our research suggests that in order for an EA practice to help in IT Consumerization initiatives, organizations must ensure that EA practices are not limited to technical problem solving, and that they have the resources and skills required for business problem solving. While EA has often been positioned as an information technology function within many organizations, we argue that based on our findings, EA’s role within organizations can go beyond this traditionally technical focus, to include both advisory and strategic roles leveraging business skillsets to solve business problems. Our EA role framework is a significant departure from the widespread belief that EA practices start at the translation of business strategy to technology strategy, by proposing that EA can play a valuable role earlier in strategic processes such as business strategy development, direction setting, and change prioritization. This inquiry highlights some of the key interrelationships between EA and IT Consumerization.

Software systems are becoming increasingly complex. A single application needs to provide capabilities and functionalities that cut across an entire enterprise scope. At the same time, many different applications may need to interact with each other as part of an overall business process. Traditional approaches for software system development do not provide efficient solutions to address this problem. This thesis explores how to leverage emerging standards, BPEL (Business Process Execution Language for Web Service), XForms, SOA (Service Oriented Architecture) and XML (eXtensible Markup Language), to implement a Model-based SOA software development approach. It also compares Model-based SOA approach with two other traditional software development approaches in the implementation of an example application in the area of health care: an approval process for accessing data in a medical data warehouse.

eFörvaltning ses som ett medel för att göra kommunalt förvaltningsarbete mer effektivt och interoperabelt. Dock begränsas kommuner av oförmåga att uppnå det vilket försvårar genomförandet av deras uppdrag. En orsak till varför införandet av eFörvaltning inte ger de systematiska fördelar som efterfrågas beror på att införandet av informations och kommunikations teknologier (IKT) inte är tillräckligt. Förändringen som krävs kan inte ske över en natt utan är en gradvis förändring över tid som även kräver nya sätt att arbeta på. Kommuner behöver hantera sin eFörvaltningsutveckling på ett mer strukturerat sätt för att öka möjligheterna att förverkliga de fördelarna som sägs kunna erhållas. Enterprise Architecture (EA) har på senare tid kommit att ses som en möjlig lösning för att komma tillrätta med denna problematik. Genom att arbeta mot en EA skapas möjligheten att brygga IKT system med affärsprocesser och därigenom leda till effektivitet och interoperabilitet. Dock är EA inom offentlig sektor ifrågasatt. Forskare menar att EA saknar tydlig definierad omfattning och begreppsvärld, vilket gör användningen av EA inom förvaltningsarbete svår. De omfattande logiska EA ramverk som finns idag saknar innehåll som är specifikt relaterade till offentlig sektor. Vari det blir problematiskt att arbeta mot en EA inom offentlig sektor. Denna licentiatavhandling lägger följande forskningsfråga: ”Vilken roll har EA för införandet av eFörvaltning inom Svenska kommuner?” Samt följande underfrågor ”Vilka förutsättningar finns för att använda EA vid eFörvaltningsutveckling?” ”Vad har Örebro kommun uppnått genom att arbete mot en EA i deras eFörvaltningsutveckling?” Och ”Vilka problem har Örebro kommun upplevt av att arbeta mot en EA vid eFörvaltningsutvecklingen?”. En longitudinell fallstudie av ett eFörvaltningsutvecklingsprojekt i Örebrokommun genomfördes mellan 2007 och 2009 med syfte att utröna dessa frågor och för att skapa insikt om EAs roll för eFörvaltningsutveckling. Förutsättningar, resultat och upplevda problem vid eFörvaltningsutvecklingen studerades. I anslutning till detta empiriska arbete genomfördes även en jämförandestudie av eFörvaltningsmål såsom de anges i officiella statliga dokument inom så väl Sverige som i EU gentemot förmodade fördelarna med EA som diskuteras i samtida EA-litteratur. Studien visar att EA som fenomen ses som en förutsättning för att lyckas med eFörvaltning. 7 viktiga aspekter gällande förutsättningen för att lyckas med kommuners eFörvaltningsutveckling identifierades: Skillnaden mellan administrativa och politiska ansvaret, Politiskt mandat, Politisk timing, Resursfördelning, Samordning under NPM, Leverantörsberoende, Val av standard och bäst praxis. För att förbättra möjligheten att röna framgång i eFörvaltningsutveckling behöver dessa aspekter aktualiseras och hanteras. New Public Management (NPM) som styrmodell utgör ett strukturellt hinder för eFörvaltningsutveckling som förhindrar en mer explicit användning av EA-ramverk, vilket påverkar möjligheten att uppnå uppsatta mål negativt. Trots den strukturella problematik som föreligger, kan stöd erhållas genom att arbeta utifrån ett ”EA-tänk”. Ett ”EAtänk” kan här ses som ett medel för att påbörja förändringen mot en EA utan att för den delen explicit använda sig av ett EA-ramverk, eller -metod. Dock är det viktigt skapa en förståelse för att ”EA-tänk” som fenomen i sin tur ger upphov till strukturer och således kan leda till problem som även de måste hanteras för att eFörvaltningsutveckling skall lyckas. eFörvaltning, NPM och ett ”EA-tänk” skapar en strukturell triad där olika strukturella egenskaper i vissa fall sammanfaller med varandra vari de kan stödja kommuner i dess arbete och således bidra till positiv utveckling. Medan det i andra fall leder till negativ utveckling där administrationen upplever problem att ta till sig av de rekommendationer eFörvaltningsprojektet kan tänkas ge till organisationen som helhet. Paradoxalt nog skapar denna strukturella triad en situation där kommuner måste arbete runt sig själv för att komma framåt. Normer och befintliga strukturer i kommuner förhindrar effektiv samarbete både internt mellan olika förvaltningar och externt gentemot andra kommuner och landsting vilket leder till fragmentariska framsteg mot projektmålen och i slutänden även kommunens övergripande mål gällande eFörvaltningsutveckling. Givet de i många fall motstridiga strukturella egenskaper som finns mellan NPM och eFörvaltning innebär att det initiala arbetet mot EA i eFörvaltningsutveckling är ett ytterst komplext fenomen. För att öka möjligheten att eFörvaltningsutvecklingen blir lyckad krävs det att kommuner känner till och hantera den negativa inverkan NPM har på eFörvaltningsutveckling. Samtidigt behöver de känna till och hanterar problematiken som uppstår av att arbeta mot en EA genom ett ”EA-tänk”, Samt att som studien visat, EA ger inget stöd för mer politiseras mål, vari kommuner behöver annat sätt och andra strategier för sådant arbete. Detta är viktigt att beakta, speciellt med tanke på att mer politiserade mål i mångt och mycket är de mål som kommer premieras av politiker. Av just den enkla orsaken att politiker inte blir omvalda på grund av “effektiva IKT integrerade interna processer” utan blir omvalda utifrån förbättringar som är synliga och som gagnar medborgare positivt. Avhandlingen bidrar till forsknings genom att öka förståelse för och behovet av att hantera både positiva och negativa faktorer som påverkar möjligheten att lyckas med eFörvaltningsutveckling inom kommunalt arbete. Vilket inkluderar de 7 identifierade kritiska faktorer måste aktualiseras och hanteras för att öka möjligheten att lyckas. Den negativa effekt NPM har på eFörvaltningsutveckling och hur ett ”EA-tänk” kan leda till positiv utveckling, även om det som denna studie visat inte kan bidra till mer politiserade mål. Vad gäller denna licentiatavhandlings bidrag till praktiken så bidrar den med att belysa den problematiska situation som föreligger av att institutionaliserade strukturer i många fall verkar som ett hinder mot förändring. Studien möjliggör även till att kommuner kan skapa en förståelse för sin egna eFörvaltningsutveckling och möjligtvis kan verka för att inte uppleva samma problematik som identifierats i Örebros eFörvaltningsutveckling samt visa på hur en kommun kan arbeta för att hantera den problematik som inte kan förhindras alternativ som uppstår trots denna kunskap.
Governments struggle with inefficiencies and an inability to achieve interoperable information communication technology (ICT) systems. Apparent issues include a failure of local government to realize the benefits of electronic government (eGov) initiatives, high project failure rates, administrations hampered with inefficiencies, and a lack of interoperability between systems within the local government. Thus, local governments need to address their eGov initiatives in a structured way to improve their chances of providing the benefits that are sought after. Sweden’s eGov model is decentralized, following a strict new public management (NPM) model. Whilst eGov ought to bring benefits to local government, Sweden is still hampered by inefficiencies and an inability to achieve interoperable ICT systems. This has been the case for quite some time. One reason why systemic gains from adopting eGov have not reached the levels sought after could be that, in many cases, ICT implementations are not enough. The transformation needed for eGov is not instantaneous; it requires various new ways of working. Enterprise Architecture (EA) has come to be seen as a possible solution to the apparent issues of developing, adopting and managing eGov successfully. By utilizing EA, it is argued that it is possible to bridge ICT systems and business processes, thus making the organization more efficient. However EA’s usefulness for eGov development and adoption is the subject of debate. Some researchers argue that EA lacks clearly defined scopes and concepts, which makes the use of EA in government difficult. Whereas other argues that although EA frameworks are comprehensive logical frameworks, they lack content that is related specifically to government organizations. The thesis posits the following research questions: What is the role of EA in eGov adoption in Swedish local government? together with three sub questions: What are the prerequisites for using EA in Swedish local eGov adoption? What has the Swedish local government in Örebro achieved with its use of EA in eGov adoption? And What problems have the Swedish local government in Örebro experienced in its use of EA when adopting eGov? To explore the role of EA in eGov adoption a longitudinal case study is carried out on the municipality of Örebro’s eGov project MovIT, a project launched in 2007 that ended in 2009. I study the prerequisites, results and problems associated with using EA in Swedish local government as part of eGov adoption. A comparative study is conducted of the goals of eGov, as stated in official eGov documents at EU and Swedish governmental levels will attest as to the supposed benefits of EA in contemporary EA-literature. From the study, it can be concluded that EA, as a phenomenon, is thought to be, if not a silverbullet, then at least a prerequisite to eGov success. In term of prerequisites, EA use cannot assist Swedish local government where there are more politicized objectives; in this situation, local government is required to look elsewhere to find support for its work. The study identify several critical issues from the empirical study of the prerequisites: distinction between administrative and political responsibilities; political mandate; political timing; resource allocation; coordination under NPM; dependence on providers; and choosing among standards and best practices. These issues need to be acknowledged and handled appropriately by Swedish local government in order to improve the chances for success in eGov adoption. The study also showed that NPM as governance model becomes a hindrance in eGov adoption, preventing the project from a more explicit use of an EA-framework and negatively affecting the projects possibility to adopt eGov. However, despite this structural problem, it is still possible – as observed – for a project that is based on EA-thinking to begin working. EGov, NPM and EA-thinking form a triad, with structural properties that, in some instances, correlate. In such cases, this can lead to positive changes. However, in other situations, they are contradictory, resulting in Swedish local government having a difficult time in adhering to the suggestions endorsed by the eGov project. This lead to incoherent progressions towards requested results. The existing structures hindered effective cooperation, both internally between different departments and externally with other local governments. This licentiate thesis has shown that the initial use of EA in local government eGov adoption is complex. Given the contradictory nature of NPM and eGov, local government has to acknowledge the negative impacts of NPM on eGov adoption. As well as acknowledging the issues that arise from EA use, a key area is a lack of support of local government in an area that is most likely to be endorsed by politicians. Politicians do not get re-elected based on efficient internal processes with a highly integrated ICT; rather, changes must be visible to citizens and businesses. This licentiate thesis has also shown that ‘EA-thinking’, as a means for local government, can move towards an EA without the explicit use of an EA framework or EA method. However, ‘EA-thinking’ may give rise to other issues that need to be acknowledged and dealt with. This licentiate thesis contributes to research by improving our understanding of the nature and importance of promoting and inhibiting different factors. Including critical issues for succeeding with eGov adoption, the negative effects of NPM and how EA-thinking can lead to positive changes, even though it cannot assist local government in all aspects deemed important to eGov adoption. In terms of practice, this thesis contributes by highlighting the problematic nature of institutionalized structures and the effect that this has on eGov adoption. It also contributes by enabling local governments to acknowledge the problems identified. This allows them to better understand their own development and possibly avoid similar problems or at least have a better understanding of how to handle the issues that arise.