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.

This thesis is focused on the competence of Enterprise Architecture, which is discussed in the introductory theoretical part as a comprehensive practice and subsequently in the relation between Enterprise Architecture and a specific aspect that is used in the EA initiatives - the reference models is discussed. In relation to the set objective the basic definitions of Enterprise Architecture are discussed and analyzed in the Chapter 2, and brief look at the description of the architectures along with the key business drivers and benefits of EA is also provided. In the Chapter 3 the content evolution of architectural disciplines is presented, particularly in terms of the scope of EA and maturity in the enterprises. A general analysis of the Enterprise Architecture is completed in the Chapter 4 where is addressed a crucial aspect of Enterprise Architecture - the architectural frameworks. The second part focuses on the key objectives of the thesis related to the reference models. The criterial evaluation system of reference models and the classification scheme for reference models are introduced as the key proposed approaches. In chapter 5.3 is also provided the structural analysis of five selected reference models that are evaluated on the basis of the predefined criteria and classified in the proposed scheme at the end. Both proposed approaches, the criterial evaluation system and the classification scheme for reference models, are in the chapter 5.6 assessed and verified by the subject matter experts in the field of EA.

The topic of this thesis is the application of business process management approach to an operating franchise network. The aim is to describe the current state of the company, iden-tify problem areas complicating further development and to propose the future state of the company and plan the transition to this state. The theoretical part presents the issue of franchising and the selected topics from the field of process management, which provides the basis for the practical part, devoted to design the proposed changes and plans for their implementation. Work can be interesting in terms of linking of franchising and process management, appli-cation of which it suggests.

Information systems (IS) are indelibly linked to the global economy and are indispensable to society and organizations. Despite the decisive function of IS in organizations today, IS development problems continue to plague organizations. The failure to get the system requirements right is considered to be one of the primary, if not the most significant, reasons for this high IS failure rate. Getting requirements right is most notably identified with Frederick Brooks' contention that requirements are the essence of what IT professionals do, all the rest being accidents or risk management. However, enterprise architecture (EA) may also provide the discipline to bridge the gap between effective requirements, organizational objectives, and the actual IS implementations. The intent of this research is to examine the relationship between IS development capabilities and requirements analysis and design capabilities within the context of enterprise architecture. To accomplish this, a survey of IT professionals within the Society for Information Management (SIM) was conducted. Results indicate support for the hypothesized relationship between IS development and requirements capabilities. The hypothesized relationships with the organizational demographics were not supported nor was the hypothesized positive relationship between requirements capabilities and EA perceptions. However, the nature of the relationship of requirements and EA provided important insight into the relationship leading to several explanations as to its meaning and contributions to research and practice. This research contributes to IS development knowledge by providing evidence of the essential role of requirements in IS development capabilities and in IS development maturity. Furthermore, contributions to the nascent field of EA research and practice include key insight into EA maturity, EA implementation success, and the role of IT professionals in EA teams. Moreover, these results provide a template and research plan of action to pursue further EA research in exploring EA maturity models and critical success factors, and the state of practice of EA in organizations

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

Master’s thesis deals with Service Desk application effectiveness assessment and proposal for its modification. This proposal will increase application’s effectiveness of suported processes. New version of application will be adapted to ITIL v3. The proposal for modification is created by adapted models of enterprise architecture. The thesis contains analysis of current version of application, which is an input for proposal of modification.

The goal of this study is to examine how small and medium-sized enterprises (SME) describe and model the part of Enterprise Architecture (EA) that is concerned with the business architecture by looking at four common modelling perspectives within business architecture – processes, information, IT systems and business capabilities. The study both examines if general models and descriptions have been created by the SMEs for the aforementioned perspectives, as well as if the SMEs have created target architectures for change management. Finally, this study also examines what the businesses consider that they need to be able to work more with business architecture, as well as if there are any differences between the small and the medium-sized enterprises in the study. The study was conducted by means of a survey, that was sent to around 1170 enterprises. 140 of them answered the survey, and the answers show that a clear majority of the SMEs have created some descriptions, completely or partly, of their business architecture for all the studied perspectives. In addition, around half of them have created target architectures, complete or partial ones, for all the perspectives. Process description was the most common type of business architecture description among the respondents, over 80 % of respondents have described them at least partly, whereas description of information was the least common one, around 50 % have described their information at least partly. The main things the SMEs say they need to be able to work more with business architecture are time and resources, some also request more knowledge about method, and some external support, and some are/were waiting for a major enterprise crisis to begin their business architecture work.  Medium-sized enterprises, as well as enterprises that have a certain position for a business architect, work more with all types of descriptions and models than smaller enterprises and those that do not have an architect. However, the differences were only found to be statistically significant for a few of the perspectives. / Målet med denna studie är att undersöka hur arbetet med verksamhetsarkitektur (som en del av enterprisearkitektur-arbete) ser ut i små och medelstora företag (SMF:er) genom att titta på fyra vanliga modelleringsperspektiv inom verksamhetsarkitekturen: processer, information, IT-miljö och verksamhetsförmågor. Studien undersöker både om generella modeller och beskrivningar skapats inom ovanstående områden, samt om verksamheterna skapat någon målarkitektur för förändringsarbete. Slutligen undersöks även vad SMF:erna anser sig behöva för att arbeta mer med verksamhetsarkitektur, samt om det finns skillnader mellan de små och de medelstora företagen. Undersökningen genomförs med hjälp av en enkät som skickades ut till runt 1170 företag. 140 företag besvarade enkäten och svaren visar att en majoritet av verksamheterna i studien arbetar med verksamhetens ingående delar helt eller delvis. De arbetar även med målarkitekturer inom de studerade områdena. Vanligast är att verksamheterna beskriver sina processer, över 80 % har tydligt beskrivit sina processer helt eller delvis, och minst vanligt är att de beskriver sin information, vilket runt 50 % helt eller delvis hade gjort. Det främsta verksamheterna anser sig behöva för att arbeta mer med verksamhetsarkitektur är tid och resurser, vissa efterfrågar även mer kunskap om tillvägagångssätt och yttre stöd, och några anser sig behöva en akut kris för att börja med verksamhetsarkitektur. Mellanstora företag, samt de företag som har en verksamhetsarkitekt, arbetar mer med beskrivning och modellering (helt eller delvis) för alla undersökta perspektiv än de mindre företagen och de som inte har någon arkitekt, men endast inom några områden var skillnaderna statistiskt signifikanta.

Digital Transformation (DT) opens up to new opportunities for companies by providing organizational flexibility and improving their business models. Due to lack of resources in form of financial power and qualified employees, family-owned manufacturing companies have a hard time reaching DT. However, these companies try their best to reach DT and along the road various challenges arise. The challenges that arise, result in a complex situation that is hard to understand. Organizations with complex situations have difficulties to perform successful IT initiatives that are required to reach DT. The aim of this study was to identify challenges that family-owned manufacturingSMEs (FOMSMEs) encounter when striving for DT. Another aim of this research was to investigate how useful Soft Systems Methodology (SSM) is in helping family-owned manufacturing SMEs to understand their own complex situation. Also, the managerial practice called Enterprise Architecture Management (EAM) has been investigated regarding its usefulness in helping family-owned manufacturing SMEs to reach DT faster and easier. As a fourth and final aim in this study, an artefact has been created with suggested actions that address the identified challenges that FOMSMEs encounter when striving for DT. By interviewing employees who have participated in IT initiatives at a family-owned manufacturing SME, this research has been able to answer the research questions. Several challenges were identified; communication errors, old systems and exceeding deadlines in projects. All of these challenges can, with the help of SSM, be associated with the identified root challenge: Lack of overview of IT-landscape and strategy. The informants’ thoughts of usefulness of SSM in family-owned manufacturing SMEs were positive. In contrast, the informants’ thoughts of usefulness of EAM in family-owned manufacturing SMEs were negative. The argument expressed by the informants was that as long as the owner family makes most of the decisions, a new managerial practice as EAM will not be useful in family-owned manufacturing SMEs.

In this Master Thesis an Enterprise Architecture Decision Making analysis is proposed within the field of Enterprise Architecture. A case study at a company within the financial sector has been conducted for validation of the proposed analysis. Firstly, the Enterprise Architecture Analysis Tool (EAAT), which has been developed by the Industrial Information and Control Systems (ICS) department of KTH, is described. This tool has been used during the whole Case Study in order to create present and possible future state models for measuring Service Availability. These models, which are based on a Metamodel, make possible the analysis of the Service Availability. Finally, some future research suggestions in the context of decision-making in Enterprise Architecture with EAAT are given.

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.