This research studies the six strategies of Project Risk Management defined by a Guide to Project Management Body of Knowledge (PMBOK) issued by U.S. Project Management Institute (PMI), the model of risk management invented by Boehm in 1991, and an enterprise architecture tool. As a result, this research comes out Architecture-Oriented Project Risk Management Model, abbreviated as AOPRMM, which emphasizes structure behavior coalescence within an organization. AOPRMM thoroughly describe the organization¡¦s integrity and the services provided by various structure elements. Moreover, AOPRMM is able to demonstrate the relationship of interaction among structure elements. Currently, most risk management models are categorized into the process-oriented approach. This research utilizes architecture-oriented as a new approach for modeling the project risk management. The model used in our approach is compared with those such as standard model of ISO 31000, standard model of New Zealand, and standard model of Taiwanese government. The result of this research shows that AOPRMM could help project managers master the whole project in a short period of time, implement the project easily, and lower the cost. By applying AOPRMM, the industries could regulate standard operations, and clarify the responsibility and authority in order to implement the project risk management successfully. This research achieves a beneficial model and knowledge for the project risk management. This accomplishment may be valuable for the business and academic circles to follow and refer.

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.

In order to solve a problem of Business and IT Alignment (BITA) it is important to consider various dimensions of it: strategic, structural, social and cultural. In the context of dealing with BITA, Enterprise Modeling (EM) is an acknowledged and widely used practice. On one hand, EM facilitates the creation of integrated models that capture and represent different focal areas of an enterprise, there-fore it allowing to obtain a multidimensional view on an enterprise and to inte-grate these multiple dimensions into a coherent structure. These capabilities make EM a powerful tool for dealing with the strategic and structural dimen-sions of BITA. On the other hand, solving a BITA problem requires dealing with the numerous points of view of the stakeholders and creating a shared under-standing between them, which refers to the social and cultural dimensions of BITA. In this regard EM is also able to provide support to the development of an understanding about the current multidimensional praxis and future vision and strategies. Thus, EM has a high potential for dealing with the strategic, structur-al, social and cultural dimensions of BITA. This licentiate thesis investigates the applicability of EM in the light of BITA and proposes a framework that allocates intentions of EM application within the frame of the Strategic Alignment Model. The framework positions EM conceptually in the context of BITA and identifies a number of EM challenges and recommendations to suggest how EM can be used to facilitate BITA.

Increasingly, eGovernment (the use of ICTs in order to achieve better government) is moving its focus from web presence and electronic service provision to striving for an interoperable public sector. Interoperability refers to the ability for information exchange across organizational borders, concerning technology as well as business aspects. Policy for such change has been formulated and implementation is currently taking place in many government sectors. In such programs there is a strong need for coordination with regard to the way in which interoperability is to be implemented. Interoperability work requires coordination, as it is a complex endeavour because of the interrelatedness of information systems, public services, departments and organizations, as well as policies, constraints and regulations. In order to achieve interoperability, architectural approaches are increasingly used in the public sector to try to coordinate interoperability work. One such approach, Enterprise Architecture (EA), is becoming increasingly influential. EA has been defined as an overview of the complete business processes and business systems, both in terms of how they overlap and their interrelatedness. However, previous research show that state-of-the-art EA is seldom fully applied in practice. Previous research has also proposed that information infrastructures and architectures should be seen as evolving dynamically during the implementation process through changing relationships between actors. The implementation of IS architecture for interoperability is thus seen as an evolving process of social production. As the research field is still immature further research on the evolution of public information infrastructures and architectures is needed, as well as how the strategic alignment of handling of goals, and ambiguities in implementation is done.   This thesis hence addresses the challenges of implementing national public sector interoperability as an evolving process by addressing the research question: How is interoperability interpreted and enacted by different actors in public sector implementation?   In order to approach the research question, an interpretive case study is performed. The case studied in this thesis is from the implementation of the Strategy for eHealth in Sweden, where healthcare is mainly publicly funded, and catered for by 20 county councils (who mainly focus on healthcare, and 290 municipalities (who also cater for a great deal of other public services). The case is an example of how interoperability is implemented, from the early stages of outlining a general picture of goals and requirements, to the formulation of a strategy and an architecture. This case is also an example of how EA influences an interoperability program through enterprise thinking.   The research uses an interpretive case study approach influenced by Actor-Network Theory (ANT). ANT is used as a toolbox for telling stories about technology in practice, as emergent in socio-material relations. A number of complementary qualitative methods are used. These include semi-structured interviews, observations and document analysis, with the foremost part of the empirical material being first-hand.   In order to understand interoperability implementation in the public sector I examine the background to eGovernment implementation, by contrasting conceptualizations of eGovernment evolution to contemporary theories of public policy implementation. It is shown that, during the last decade, stage models have been used as tools for describing, predicting and directing the evolution of eGovernment.  The stage model approach has been criticized for presenting a linear development which has little empirical support and delimits the understanding of eGovernment development as a dynamic process. Newer stage models have started to take this criticism into consideration and alternative models on eGovernment have also been developed. Consequently, eGovernment implementation is in this thesis perceived as a process in which technologies, policies and organizations are in a process of mutual shaping, where policymaking and policy implementation are intermingled. Implementing interoperability is hence not a matter of disseminating a policy that is to be implemented in every setting exactly as stated on paper, but a process in which the goals and means of interoperability are constantly being negotiated. Also, EA has been proposed as an approach to treat technology and business in the public sector as interrelated. However, since previous research show that state-of-the-art EA is seldom fully applied in public sector practice, the concept of enterprise thinking is developed in this thesis. Enterprise thinking is intended to be a concept that describes EA as a contemporary zeitgeist which in practice is adopted in varying ways.   The results of the thesis show how interoperability in eHealth was roughly outlined before implementation although still containing conflicts and ambiguities. Central to this thesis is the controversy of defining “the enterprise”, as the health care sector was delimited as one enterprise, which became increasingly problematic during implementation. This to a large extent concerned municipalities, whose business area stretched much wider than just the health care sector, and hence the definition of the enterprise became problematic. Another central aspect was legal obstacles to cooperation, as there was a clash between the values of efficiency and patient privacy as a result of a new law that had been implemented in order to allow for information sharing. The legal grounds for sharing information proved to be problematic, which lead to that several involved actors perceived that a large portion of the patients in health care could not benefit from interoperability as their information could not be shared despite this law. The legal challenges also dampened the enthusiasm for the eHealth program as a whole.    The program had also outlined a technology architecture before implementation. This architecture was however treated in conflicting ways, both as a blueprint (something to be implemented) and a tool for communication (as a way of discussing what was to be implemented). For instance, several municipalities perceived that the planned infrastructure was unsuitable to their business needs (as it did not meet the requirements of other actors in eGovernment), and thus questioned it, using it as a tool for communication rather than a blueprint. Meanwhile, other actors argued that the blueprint had already been decided, and thus needed to be implemented.  The case also shed light on the use of informal networks, outside traditional bureaucracy, as a means to deal with interoperability. Such networks were used in order to align actions and perceptions of a large number of autonomous municipalities. This revealed issues concerning local decision as knowledge of, and resources for, ICT and architectural work was lacking in several municipalities. Also, as the networks lacked formal power no decisions could be taken jointly, but in the end had to be negotiated locally. This made coordinated decision making hard as the processes were lengthy and often lacked clear incentives. Furthermore, ambiguous feedback from national authorities, as well as an overall lack of understanding among local actors, concerning what was legal to do in terms of procurement and information sharing, complicated the situation further. These findings are summarized in four main conclusions;   The process of defining which organizations are to be made interoperable, or what is to be considered as “the enterprise”, is a political process which might be brought into question and require re-negotiations throughout implementation, as the drawing of boundaries of “the enterprise” can be filled with conflict.   Different perspectives on an enterprise, from different architectural viewpoints, are often described as complementary, and it has previously been shown that different architectural metaphors can be used by different actors during implementation. However, in practice, different use of metaphors for architectures can open up for discussion and conflict. These may not only be different, but may also contradict other actors’ use of metaphors, since different metaphors might clash.   Interoperability work can be a novel task for some local governments. Therefore, there is a need for negotiation and to establish forms of formal decision making and informal dissemination because such structures might be lacking. It should be anticipated that implementation might be slow because of a lack of understanding about interoperability programs (particularly in terms of something other than ICT). In addition, there may be few forums for coordinated decision making, or there may be obstructions in the form of prior formal and legal arrangements.    Enterprise thinking is interconnected with Enterprise Architecture as a zeitgeist for interoperability work. It draws upon EA as an ideal, whilst acknowledging that public organizations are influenced by this zeitgeist, although practical conditions might not allow for adoption of an EA approach. Enterprise thinking thus refers to the notion of EA as an ideal, not as a specific way of applying EA.  Enterprise thinking has a process focus on interoperability. ICT, business goals, and work practices are perceived as interconnected, and hence need to be treated from a holistic perspective. How this is approached is, however, dependent upon the context in which it is implemented.   Further research efforts could approach how enterprise thinking affects interoperability work in the long run with a longitudinal approach. Also, as this thesis has shown how the use of different architectural metaphors can clash, further research could focus on the positive and negative effects of negotiations being initiated by such conflict. From a project management perspective the risks and benefits of using smaller projects as “enrolment devices” for interoperability programs, where an architecture cannot be pushed but is voluntary, should be of interest. Furthermore the use of EA as an ideal which cannot be fully followed in several public settings, although might intentionally be used as a guiding light, is interesting for further research.  For instance, it would be of interest to see how the rhetoric of EA may be applied in practice in order to legitimate programs. This is of interest as to examine to which extent the use of such concepts influence actual practice, or if they are only “empty words”. The conceptualization of enterprise thinking proposed in the conclusions of this thesis can be used in further research. Indeed, they could be useful for investigating different approaches, influenced by EA, in different contexts. For instance, it may be of interest to countries that might not share the same institutional characteristics of Sweden, but are influenced by enterprise thinking in different ways. This would be of interest for outlining different practical approaches to enterprise thinking. Also, the further development in Sweden specifically could be of interest, as other sectors are at the time of writing preparing their own interoperability programs, and aim to benefit from the lessons learned in the healthcare sector. / I ökande utsträckning har e-förvaltningens (användningen av IKT för att förbättra verksamheten i offentlig sektor) fokus förflyttats från webb-närvaro och elektroniska tjänster mot att sträva efter en interoperabel offentlig sektor. Interoperabilitet avser möjligheten för informationsutbyte över verksamheters olika gränser, vilket innefattar teknologiska såväl som organisatoriska aspekter. Policys för sådana förändring har utarbetats och implementeras för närvarande i flera offentliga organisationer. I sådana program finns det ett starkt behov av samordning gällande det sätt på vilket interoperabilitet skall genomföras. Interoperabilitetsarbete kräver således samordning, eftersom det är en komplex uppgift på grund sammanvävda informationssystem, offentliga tjänster, organisationer, policys, begränsningar och regler. För att uppnå interoperabilitet används arkitekturella tillvägagångssätt alltmer inom den offentliga sektorn, för att försöka samordna arbetet. Ett sådant tillvägagångssätt, Enterprise Architecture (EA), har fått ett ökande inflytande. EA har definierats som en översikt av hela affärsprocesser och affärssystem, både vad gäller hur de överlappar med varandra och hur de hänger samman. Dock visar tidigare forskning att EA i praktiken sällan tillämpas fullt ut. Tidigare forskning har också påvisat att informationsinfrastrukturer och arkitekturer bör ses som dynamiskt framväxande under implementeringsprocessen, genom förändrade relationer mellan aktörer. Implementering av informationssystemsarkitektur för interoperabilitet bör därmed ses som en framväxande och socialt producerad process. Då forskningsområdet fortfarande är omoget behövs ytterligare forskning om framväxten av offentliga informationsinfrastrukturer och arkitekturer, samt hur strategisk sammanjämkning av mål och oklarheter i implementeringen sker.   Denna avhandling behandlar därför utmaningarna som finns i implementeringen av interoperabilitet i offentlig sektor, som en framväxande process, genom att behandla frågeställningen: Hur tolkas och sätts interoperabilitet i praktiken av olika aktörer under implementering i offentlig sektor? För att närma sig frågeställningen utförs en tolkande fallstudie. Fallet som studerats i denna avhandling är från implementeringen av strategin IT-strategin för vård och omsorg (eHälsostrategin) i Sverige, där vården i huvudsak är offentligt finansierad, och tillhandahålls av 20 landsting (som huvudsakligen fokuserar på sjukvård), och 290 kommuner (som också tillhandahåller en mängd andra offentliga tjänster). Fallet är ett exempel på hur interoperabilitet implementeras, från de tidiga skeden då en generell bild av mål och krav målas upp, till utformningen av en strategi och en arkitektur. Detta fall är också ett exempel på hur EA påverkar ett interoperabilitetsprogram via ”enterprise thinking”. En fallstudie genomförs med en tolkande ansats, influerad av Actor-Network Theory (ANT). ANT används som en verktygslåda för att berätta historier om teknik i praktiken, som framväxande genom sociomateriella relationer.  Merparten av det empiriska materialet har samlats in i förstahand och ett antal kompletterande kvalitativa metoder används. Dessa metoder inkluderar semi-strukturerade intervjuer, observationer och dokumentanalys. För att förstå interoperabilitetsimplementering i offentlig sektor undersöker jag bakgrunden till implementation av e-förvaltning, genom att kontrastera begreppsbildningar av hur e-förvaltningen växer fram mot samtida teorier om implementation i offentlig sektor. Jag påvisar att under det senaste decenniet har stegmodeller använts som verktyg för att beskriva, förutsäga och styra utvecklingen av e-förvaltning. Denna typ av modeller har kritiserats då de framhåller en linjär utveckling som har bristande empiriskt stöd och begränsar förståelsen för e-förvaltningens framväxt som en dynamisk process. Nyare stegmodeller har börjat ta hänsyn till denna kritik och alternativa modeller på e-förvaltning har också utvecklats. Följaktligen ses i denna avhandling implementeringen av e-förvaltning som en process där teknik, policy och organisationer är i en ständig process av ömsesidig påverkan, där policyskapande och policyimplementering är sammanvävt. Att implementera interoperabilitet är därför inte en fråga om att sprida en policy som skall genomföras av varje aktör så som det står angivet på pappret, utan en process där mål och metoder för interoperabilitet ständigt omförhandlas. EA har föreslagits som ett tillvägagångssätt för att behandla teknik och verksamhet som integrerade. Dock, eftersom tidigare forskning visar att EA sällan tillämpas fullt ut i praktiken i offentlig sektor, så utvecklas begreppet enterprise thinking i denna avhandling. Enterprise thinking är avsett att vara ett koncept som beskriver EA som en samtida tidsandan som i praktiken närmas på olika sätt. Resultaten i avhandlingen visar hur interoperabilitet i e-hälsa skisserades ut grovt innan implementeringen, i en bild som innehöll konflikter och tvetydigheter. Centralt för denna avhandling är problematiken i att definiera verksamheten (”the enterprise”), då hälso- och sjukvårdssektorn var avgränsad som en verksamhet, vilket blev allt mer problematiskt under implementeringen. Detta berörde till stor del kommuner, vars verksamhetsområde sträcker sig mycket bredare än bara hälso- och sjukvården. Därmed blev definitionen av verksamheten problematisk. En annan central aspekt var juridiska hinder för samverkan, då det fanns en konflikt mellan värdena effektivitet och patientens integritet. Detta var delvis en följd av en ny lag som hade införts just i syfte att möjliggöra informationsutbyte. De rättsliga grunderna för att dela information visade sig vara problematiska, vilket ledde till att flera inblandade aktörer uppfattade att en stor del av patienterna i vården inte kunde dra nytta av interoperabilitet, eftersom deras information inte kunde delas trots denna lagändring. De rättsliga utmaningarna dämpade också entusiasmen för eHälsoprogrammet som helhet.    Programmet hade också skisserat ut en teknikarkitektur innan implementeringen. Denna arkitektur behandlades dock på motstridiga sätt, både som en ”ritning” (en klar bild av vad som skulle genomföras) och som ett verktyg för kommunikation (som ett sätt att diskutera vad som skulle genomförts). Till exempel uppfattade flera kommuner att den planerade infrastrukturen var olämpliga för deras verksamhetsbehov (då den inte uppfyllde kraven från andra aktörer inom e-förvaltning), och ifrågasatte därmed den genom att använda arkitekturen som ett verktyg för kommunikation snarare än en ritning. Samtidigt menade andra aktörer att man redan hade tagit beslut om denna ritning och att den därmed skulle följas. Fallstudien kastar också ljus på användningen av informella nätverk, utanför den traditionella byråkratin, som ett sätt för att arbeta med interoperabilitetsfrågor. Sådana nätverk användes i syfte att sammanjämka åtgärder och uppfattningar hos ett stort antal självstyrande aktörer. Detta visade på en problematik gällande lokalt beslutsfattande och resurser gällande IKT och arkitekturellt arbete, då kompetenser och erfarenheter för detta saknades hos flera kommuner. Relaterat till detta är att i de nätverk där diskussionerna fördes saknades även formell makt, och inga beslut kunde fattas gemensamt därigenom. I slutändan var man istället tvungna att diskutera de frågor som togs upp där lokalt. Detta gjorde samordnat beslutsfattande svårt eftersom processerna var långa och ofta saknade tydliga incitament. Dessutom fanns en problematik i att nationella aktörer ofta gav tvetydig respons på frågor, samt en allmän brist på förståelse bland lokala aktörer, gällande vad som var lagligt att göra beträffande upphandling och informationsutbyte. Detta komplicerade situationen ytterligare. Dessa resultat sammanfattas i fyra huvudsakliga slutsatser; 1. Processen med att definiera vilka organisationer som skall göras interoperabla, eller vad som ska betraktas som ”verksamheten”, är en politisk process som kan ifrågasättas och kräva omförhandlingar under implementeringen, eftersom hur man definierar gränserna kring ”verksamheten” kan vara konfliktfyllt. 2. Olika perspektiv på en verksamhet, från olika arkitekturella perspektiv, beskrivs ofta som komplementära, och det har tidigare visats att olika arkitekturella metaforer kan användas av olika aktörer under implementeringen. I praktiken kan dock olika användning av arkitekturella metaforer öppna upp för diskussion och konflikt. Dessa är inte nödvändigtvis bara annorlunda och komplementära, utan kan också motsäga andra aktörers användning av metaforer, då olika metaforer kan kollidera. 3. Interoperabilitetsarbete kan vara en ny uppgift för lokala aktörer. Det finns därför ett behov av förhandlingar och att upprätta former för formellt beslutsfattande och informell ”spridning” av information eftersom strukturer för detta kan saknas. Detta kan vara en långsam process på grund av bristande förståelse för interoperabilitetsprogram (särskilt i fråga om att de skulle handla om något annat än bara IKT). Dessutom finns ibland få (om ens några) forum för samordnat beslutsfattande, och det kan även finnas formella och legala hinder för detta. 4. Enterprise thinking (”verksamhetstänkande”) är sammankopplat med Enterprise Architecture, som är en tidsanda för interoperabilitetsarbete. Det bygger på EA som ett ideal, då offentliga organisationerna påverkas av denna tidsanda, men att praktiska förutsättningar kanske inte möjliggör att man antar en EA-strategi. Enterprise thinking hänvisar således till EA-begreppet som ett ideal, och är alltså inte ett specifikt sätt att tillämpa EA. Enterprise thinking har ett processfokus på interoperabilitet. IKT, verksamhetens mål och arbetsrutiner ses som sammanlänkade och måste därför behandlas utifrån ett helhetsperspektiv. Hur man närmar sig detta i praktiken är dock beroende på i vilken kontext det implementeras. Vidare forskning skulle kunna behandla hur enterprise thinking påverkar interoperabilitetsarbete på lång sikt, med en longitudinell ansats. Då denna avhandling visar på hur användningen av olika arkitekturella metaforer kan kollidera föreslås ytterligare forskning som fokusera på de positiva och negativa effekterna av att förhandlingar initieras av sådana konflikter. Från ett projektledningsperspektiv kan riskerna och fördelarna med att använda mindre projekt som symboler för att få med flera aktörer i interoperabilitetsprogram fokuseras. Detta är i synnerhet intressant i arkitekturprogram där en arkitektur inte kan tvingas på aktörerna, men att implementation är frivillig. Användning av EA som ett ideal som ofta inte kan följas fullt ut i offentlig sektor, men avsiktligt användas som en ledstjärna, är intressant för vidare forskning. Till exempel skulle det vara intressant att se hur EA-retorik kan tillämpas i praktiken för att legitimera program. Det är av intresse att undersöka i vilken utsträckning användningen av dessa begrepp påverkar verksamheten, eller om de bara är tomma ord. Begreppet enterprise thinking föreslås som användbart för vidare forskning. Det kan vara användbart för att undersöka olika tillvägagångssätt, influerade av EA, i olika kontexter. Exempelvis kan det vara av intresse att se till länder som inte har samma institutionella egenskaper som Sverige, men påverkas av enterprise thinking på olika sätt. Detta skulle vara av intresse för att undersöka på vilka olika sätt enterprise thinking närmas i praktiken. Även den fortsatta utvecklingen i Sverige kan vara av särskilt intresse, då andra sektorer i skrivande stund förbereder egna interoperabilitetsprogram och ämnar dra nytta av lärdomar från arbetet inom vårdsektorn.

Magister Commercii (Information Management) - MCom(IM) / The aim of this study is to investigate why the implementation of Enterprise Architecture (EA)in the Provincial Government of the Western Cape (PGWC)adopted in 2006,failed to be ineffective to address application duplication.

Value-based hospital is a concept that is causing a major transformation of hospitals and their information systems. Currently, hospitals are organized by medical units and by specialties that tend to operate as separate silos, without much communication between them. The transitions of care are not optimal for the patients, thus negatively impacting patient outcomes. Value-based hospitals focus on groups of patients with similar conditions, and end-to-end care pathways like Hip & Knee Replacement. They organize service lines that provide end-to-end care for these patient groups through the Emergency Department, Diagnostic Imaging, Lab tests, the surgical procedure in the Operating Room, the stay in the Surgery unit, Rehabilitation, and then discharge from the hospital. To enact such a transformation, hospitals have to redesign their Clinical Operations Management (care processes and organization) and the supporting information systems. Enterprise Architecture is the discipline, defined by international standards bodies, which concerns itself with transformational change of large complex organizations supported by information technology. Model-Driven Engineering is an approach to designing and generating information systems based on models. This thesis proposes an Enterprise Architecture for Model-Driven Clinical Operations Management (COM) to address the required transformation and improvement of clinical information systems to support value-based hospitals. The first thesis contribution is an Enterprise Architecture for Model-Driven COM in value-based hospitals, including COM Models, UML/BPMN/DMN Models, an Architecture and Design for a Clinical Operations Support System (COSS) for COM, and four COM Diagrams and Templates. The COM Models are the Business Architecture of the Enterprise Architecture; they are the foundation of our model-driven transformation approach. The UML/BPMN/DMN Models are derived from the COM Models, and are the Information System Architecture of the Enterprise Architecture. The COSS for COM, generated from the above models, is the Technology Architecture of the Enterprise Architecture. Finally, the COM Diagrams and Templates enable to better communicate the Enterprise Architecture; they are the COM Functions Table, the COM Enterprise Architecture Diagram, the COM Service Line Template, and the COSS Architecture Diagram. A second thesis contribution is the design of two domain-specific model-driven tools, based on the Eclipse environment, which support the design and generation of information systems support of COM in a value-based hospital. The COMP Tools include a Modeling Tool for COM based on a COM Functions Table for Hospitals, a Domain-Specific Modeling Language for COM (COMP: the COM Profile), and its Meta Model. The COSBench software development workbench provides support to the Model-Driven Engineering of information systems for COM. Finally, a third contribution is examples of COM Models for Joint Replacement service line and for Cardiac Procedures service line, used in our case studies to illustrate and validate the approach. There are also examples of COSS Decision Support Systems for patient flow management, operational business intelligence, full-capacity protocol, demand management, and capacity management.

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.

The topic of this thesis is the introduction and use of the ArchiMate enterprise architecture modeling language. The main goal of the thesis is to describe the basic principles and elements of the ArchiMate language. Other objectives are creating of an overview of CASE tools which support ArchiMate and demonstration of the capabilities of the language in a practical example which deals with the modeling of enterprise architecture of a selected organization. The thesis is divided into four parts. Introductory part uses available sources to define basic concepts of the enterprise architecture. Second part introduces basic principles and elements of the ArchiMate language based on an official documentation. This part also includes a market research of CASE tools which support the ArchiMate language. The third part of the thesis describes an example of the ArchiMate language use for the modeling of enterprise architecture of a selected organization. The final part discusses pros and cons of ArchiMate and summarizes results of the entire thesis. The main contribution of this thesis is that it provides a manual for potential users of the ArchiMate modeling notation. Other benefits include creation of a list of available CASE tools supporting the language and a showcase of possible practical uses of the ArchiMate language.

Although architectural services have been for a long time a common part of civil engineering, they are very rarely mentioned in theory and practice of enterprise architecture. Author of this thesis deals with formulation of the model of enterprise architecture as a service and its solution. The model is defined by a set of constructs and assumptions, which take into account current knowledge in the fields of enterprise architecture and services. In model solution a set of architectural services, which provide Enterprise Architecture agile and flexibly, is identified and defined. Validity of the model and of its solution is practically verified in two real-world cases: in a shared services center and in an external service provider.

This final thesis is dealing with the theme of outsourcing and its influence on company in connection with enterprise architecture as the main carrier of ongoing changes. Main focus of this thesis is to provide the overview of the area of Enterprise architecture and outsourcing as well as the description of the selected notation of Enterprise architecture modeling, which will be main instrument in describing the transformation. Theoretical part of the work is divided into three parts. Firstly there is description of the enterprise architecture and chosen connected areas, followed by description of the outsourcing process and description of the modeling language ArchiMate. Practical part of the work is composed of analysis, description and evaluation of the transformation of the selected company. Among the main contribution of this thesis there is description of the changes during the transformation using the ArchiMate modeling language and identifying of concrete impacts of outsourcing on Enterprise architecture of the company.