• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 94
  • 21
  • 19
  • 16
  • 10
  • 6
  • 5
  • 5
  • 2
  • 1
  • 1
  • 1
  • Tagged with
  • 188
  • 188
  • 76
  • 63
  • 52
  • 48
  • 44
  • 36
  • 33
  • 32
  • 28
  • 27
  • 24
  • 23
  • 20
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
31

Defining Thresholds for Enterprise Architecture Debt / Definiera gränsvärden för Enterprise Architecture Debt

Larsson, Malin January 2021 (has links)
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.
32

Reference Architectures as Means to Aid in System Development

Zeito, Maurice January 2013 (has links)
In comparison with the ever increasing development of enterprise architectures and frameworks, reference architectures has yet to reach the same maturity level. This brings questions regarding definition, implementation and governance of reference architectures at different levels; Business, System, Technical. In this report, an in-depth analysis of the concept of reference architctures is made, focusing on the abovementioned attributes. The purpose of the report is to provide the reader with an insight on how reference architectures can be implemented in order to aid in the work of system development.
33

Enterprise Architecture Modeling of Core Administrative Systems at KTH : A Modifiability Analysis

Rosell, Peter January 2012 (has links)
This project presents a case study of modifiability analysis on the Information Systems which are central to the core business processes of Royal Institution of Technology in Stockholm, Sweden by creating, updating and using models. The case study was limited to modifiability regarding only specified Information Systems. The method selected was Enterprise Architecture together with Enterprise Architecture Analysis research results and tools from the Industrial Information and Control Systems department of the same University. Jointly used with the ArchiMate modelling language, to create the models and perform the analysis. The results demonstrated to be very varied in regards to system models and modifiability. The Alumni Commu-nity system seemed to have very high modifiability whereas the Ladok på Webben system seemed to have the low modifiability, and other systems ranging differently or in between. The case study results found three slightly more critical systems of all the systems analysed: Ladok på Webben, Nya Antagningen & La-dok Nouveau. The first two showed to have either very low or low modifiability while being highly coupled to the other systems. Therefore any modification to these two systems would most likely cause effects that would require change in interconnected systems. Whereas Ladok Nouveau, while having average modifia-bility, has a critical position to process activities, is nearly isolated from all other systems, making them indi-rectly dependent on the system through the interconnected LADOK database. The study showed that the systems developed at KTH are comparable with systems developed by commercial enterprises in terms of modifiability. The study also provided insight into an Enterprise Architecture where the systems have dif-ferent development origins and how this could affect modifiability and analysis.
34

Detecting Enterprise Architecture Smells based on Software Architecture Smells / Upptäcka verksamhetsrötor baserat på mjukvaruarkitekturrötor

Tieu, Benny January 2021 (has links)
Software architecture (SA) smells are design problems in the internal structure and behavior of an SA. These can be seen as a specific category under the umbrella concept of technical debt (TD). TD is a central concept in software development projects and having the means to detect and measure the smells is essential to understand impairments they may cause. However, TD is only limited to the technical aspects and does not describe smells found on an enterprise level. Enterprise architecture debt (EAD) expands the concepts of TD beyond the technical aspects such that it covers the debts that can be found in all layers of an Enterprise Architecture (EA). EA smells give a measurement for EAD by providing means for identifying and detecting the smell, hence enabling a method to quantify the level of debt. The goal of this thesis is to find EA smells derived from existing SA smells. In total, three new EA smells were presented based on existing SA smells. Each new smell was described by a short description that informally summarizes the smell. This was followed by an indication of the smell’s origin and reasoning about the effects on the quality. Then, an illustrative example of the smell was provided. Finally, a detection algorithm was also provided and implemented in a prototype detection program. This thesis serves as a basis for measurements of the quality of an EA and motivation for future research in this area. It is argued that the finding of EA smells can facilitate quality assessment in an EA. / Mjukvaruarkitektursrötor (MA-rötor) är designproblem i den interna strukturen och beteende i en mjukvaruarkitektur. Dessa kan ses som en specifik kategori under samlingsbegreppet teknisk skuld (TS). TS är ett centralt begrepp inom projekt i mjukvaruutveckling och att ha en metod att upptäcka och mäta dessa rötor är viktigt för att förstå försämringar dessa kan orsaka. TS är dock enbart avgränsat till de tekniska aspekterna och beskriver inte rötorna som kan finnas på en verksamhetsnivå. Verksamhetsarkitektursskulder (VAS) expanderar konceptet av TS utöver de tekniska aspekterna så att de även täcker skulderna som kan finnas på alla nivåer i en verksamhetsarkitektur (VA). VA-rötor ger ett mätvärde för VAS, genom att förse ett sätt att upptäcka rötorna och därmed möjliggöra ett sätt att kvantifiera graden av skuld. Målet i denna avhandling är att hitta VA-rötor som är härledda från befintliga MA-rötor. Totalt har tre nya VA-rötor presenterats baserat på befintliga MA-röter. Varje ny röta har beskrivits med en kort beskrivning som informellt summerar rötan. Detta följt av en indikation av rötans ursprung och resonemang om dess effekt på kvalitén. Ett illustrativt exempel har även presenterats. Slutligen, har en algoritm för att upptäcka rötan också presenterats och implementerats i ett prototypprogram för att upptäcka rötan. Denna avhandling används som en grund för mätvärden av kvalité i en VA och motivation för framtida studier i detta område. Det argumenteras för att identifieringen av VA-rötor kan förenkla kvalitetsbedömningen av en VA.
35

Understanding the Value of Enterprise Architecture for Organizations: A Grounded Theory Approach

Nassiff, Edwin Frank 01 January 2012 (has links)
There is a high rate of information system implementation failures attributed to the lack of alignment between business and information technology strategy. Although enterprise architecture (EA) is a means to correct alignment problems and executives highly rate the importance of EA, it is still not used in most organizations today. Current literature only gave anecdotal reasons why EA was not more widely adopted. This study explored the problem of EA underutilization by understanding how organizational executives value EA. This research used the grounded theory methodology to obtain the EA perspectives of organizational executives responsible for EA. Seventeen executives were selected using theoretical sampling and interviewed using a semi-structured interview approach. The interview data was recorded and coded, and interviewing continued until theoretical saturation was reached. The executives identified four distinct meanings of EA, i.e., business and IT alignment, a holistic representation of the enterprise, a planned vision of the future, and a process, methodology, or framework enhancing enterprise decision making. In addition, they identified 16 unique benefits that EA provided. Depending on the meaning of EA, it was possible to predict what benefits they expected. For example, if the meaning of EA was a holistic representation of the enterprise, then the benefits of increase operational effectiveness, planning, product selection, and speak a common language were expected. However, regardless of which of the four meanings of EA was selected, executives expected EA to facilitate the alignment of business and IT, the decision making process, and the simplification of system and architecture management. Based on the findings, an analytic story and a theoretical model were produced. The model depicted the influencers on what meaning an executive chose and, based on the meaning, the expected benefits of EA. The understanding of executives' perceptions of EA is critical because they are the most influential leaders within organizations. Without their understanding, it becomes less likely that EA initiatives would meet organizational expectations and have favorable outcomes. Furthermore, it is hoped that this study shapes future EA initiatives so that they become more aligned with the views of the executives who are responsible for them.
36

En ansats för effektivare kontroll och uppföljning vid upprättande av femårsplaner inom Försvarsmakten : En undersökning kring möjligheten att kombinera ramverk inom Försvarsmaktens Enterprise Architecture-funktion / An approach for effective control and monitoring when establishing five-yearplans within the Swedish Armed Forces : A study of the possibility to combine frameworks within Enterprise Architecture of the Swedish Armed Forces

Elgh, Jaquline January 2016 (has links)
Enterprise Architecture (EA) kan sägas vara det som kopplar samman en verksamhets strategi med dess design. Genom att arbeta med EA ges verksamheten det stöd som behövs i processen att modellera ett önskat framtida läge. I ett samhälle som konstant förändras och utvecklas ställs verksamheter inför en rad utmaningar. Ett av de största problemen tycks vara den ständigt ökande komplexiteten inom verksamheternas olika områden. Med hjälp av EA-arbete är det möjligt att upprätta standarder och arkitekturer som kan underlätta dels organisering, men också förståelse av, den breda mängd information som är i omlopp i dagens verksamheter. Arbetet med EA bidrar också till ökad förståelse kring verksamhetens övergripande strategi. För att lyckas med EA-arbetet kan olika hjälpmedel och verktyg användas, exempelvis ramverk. Ramverk kan sägas vara en kombination av olika strukturer som används vid utveckling av arkitekturer. Det är ett hjälpmedel baserat på redan beprövade lösningar som kan bidra med ett enhetligt arbetssätt att tillämpa i verksamheten. Användningen av ramverk kan dock vara en utmaning, främst på grund av dess komplexitet och en överhängande risk att fastna i en särskild struktur. Försvarsmaktens EA-funktion har upplevt många av de problem som ofta förknippas med EA-arbete och användningen av ramverk. I dagsläget finns inget enhetligt tillvägagångssätt vid upprättande av femårsplaner till Försvarslogistikplanen. De sakkunniga får själva bestämma hur femårsplanerna upprättas och hur de ser ut. Detta arbetssätt gör att det idag inte finns vare sig en strategisk koppling mellan verksamheten och femårsplanerna eller någon som helst möjlighet till uppföljning. Syftet med denna C-uppsats är att undersöka möjligheten att pröva en ny ansats där olika delar av ramverken TOGAF, MODAF och DoDAF kombineras, för att sedan skapa en ny struktur som Försvarsmaktens EA-funktion kan nyttja som en dokumentmall vid upprättande av femårsplaner till Försvarslogistikplanen. Undersökningen har bedrivits som en kvalitativ studie genom samtal med chefsarkitekten inom EA-funktionen samt dokumentanalys av ett antal direktiv från Försvarsmakten. Datainsamlingen har resulterat i ett antal problem som verksamheten upplever i nuläget och följaktligen ett önskemål om att upprätta en ny struktur i form av en dokumentmall som kan nyttjas vid upprättande av femårsplaner i framtiden. Baserat på väl beprövade ramverk har ett antal fundamentala delar valts ut. Dessa delar har sedan kombinerats för att på bästa möjliga vis uppfylla den funktionalitet som verksamheten efterfrågat. Den nya strukturen ger EA-funktionen möjlighet att tydligt se kopplingen mellan varje upprättad femårsplan och Försvarsmaktens strategiska inriktning. De ges också möjligheten att följa upp föregående års utfall, vilket inte har varit möjligt tidigare. Undersökningen har även visat hur viktigt det är att det finns en utbredd förståelse för den strategiska inriktningen i verksamheten så att alla parter strävar efter samma mål. Det har också visat sig vara av vikt att alla förändringsåtgärder är både mätbara och spårbara för att kunna härleda varje femårsplan till operationell förändring, liksom att kunna mäta graden av måluppfyllelse.
37

Towards a reference architecture for integrated knowledge networks

Gous, Johannes Hendrik 12 1900 (has links)
Thesis (PhD) -- Stellenbosch University, 2014. / ENGLISH ABSTRACT: This thesis has as its focus the engineering of integrated knowledge networks (IKNs) through the use of a reference architecture. The purpose of the study is to gain a deeper understanding of the constructional principles underlying this class of collaborative networks. Although IKNs and enterprise engineering are both seen as promising approaches to the challenges of the Information Age, significant challenges still exist in the engineering of IKNs. Our globalised and commercialised society may currently be characterised by both extreme complexity and extreme rates of change. Enterprise engineering is seen as a promising approach to equip enterprises with the characteristics that are desirable in the modern economy, including flexibility and agility. Enterprise architecture contributes to this endeavour by providing a high-level design of the enterprise that allows for integrated engineering of the enterprise. From a commercial point of view, it has been widely recognised that the ability to innovate and generate new knowledge through the development of new products, services and processes is a key factor in the survival of enterprises. The latest trends in innovation management, however, show that the innovation process is no longer one that is executed inside a single enterprise, giving rise to the development of inter-organisational innovation networks. Furthermore, the importance of knowledge as a dynamic enabler of this networked innovation approach is highlighted. This has lead to the emergence of IKNs in which knowledge is created and shared between network stakeholders in order to foster sustainable innovation. The increasing rate of change means that enterprises, including IKNs, have progressively less time to react to market changes and opportunities. The emphasis is therefore on the potential of the EE and EA disciplines as tools to adapt to the dynamic landscape of the Information Age. At present, the ability to apply comprehensive enterprise engineering to IKNs is hampered by the lack of resources that describes sound constructional principles for these networks. The focus of this study is therefore on the application of the enterprise engineering discipline to IKNs through the development of a reference architecture. The reference architecture for IKNs is developed through design science research within a pragmatic and qualitative research strategy. The research problem is first identified and motivated. Various solution objectives are subsequently defined. This is followed by the design and development of the reference architecture through four iterative design cycles. A qualitative systematic review is conducted and serves as the foundation for the development of various reference models. The reference architecture for IKNs is demonstrated and evaluated through a series of illustrative scenarios, after which the utility, novelty and design rigour of the artefact is communicated. It was found that the reference architecture provides constructional principles in the engineering of IKNs, thus enabling the design, operation and research of this class of collaborative networks. The study therefore takes a first step toward extending the concept of EE to IKNs, and collaborative networks in general. This enables the greater adaptability of these networks to the dynamic environment of the Information Age. / AFRIKAANSE OPSOMMING: Hierdie tesis ondersoek die ontwikkeling van geïntegreerde kennisnetwerke (GK’s) aan die hand van ‘n verwysingsargitektuur. Die doel van die studie is om ’n beter begrip van die onderliggende ontwerpbeginsels van hierdie klas kollaborasie netwerke te kry. Alhoewel beide GK’s en ondernemingsingenieurswese beskou word as belowende benaderings tot die uitdagings van die Inligtingsera, bestaan beduidende uitdagings steeds in die ontwikkeling van GK’s. Ons geglobaliseerde, gekommersialiseerde samelewing word tans gekenmerk deur beide buitengewone kompleksiteit en buitengewone tempo-verandering. Ondernemingsingenieurswese word beskou as ’n belowende benadering om ondernemings toe te rus met die eienskappe wat in aanvraag is in die moderne ekonomie, insluitend aanpasbaarheid en vlugheid. Ondernemingsargitektuur dra by tot hierdie poging deur ’n hoëvlak ontwerp van die onderneming te voorsien wat geïntegreerde ontwikkeling van die onderneming toelaat. Vanuit ’n kommersiële oogpunt word dit ruim aanvaar dat die vermoë om te innoveer en nuwe kennis te ontwikkel deur die ontwikkeling van nuwe produkte, dienste en prosesse ’n kernfaktor in die oorlewing van ondernemings is. Die jongste benadering in innovasiebestuur toon aan dat die innovasieproses nie meer slegs in een onderneming uitgevoer word nie. Dit lei dan tot interorganisasie-innovasienetwerke. Die belangrikheid van kennis as ’n dinamiese instaatsteller van hierdie netwerk-innovasiebenadering word verder beklemtoon. Dit het gelei tot die ontstaan van GK’s waarin kennis tot stand gebring en gedeel word tussen netwerk belanghebbendes om sodoende volhoubare innovasie te bevorder. Die toenemende tempo in verandering beteken dat ondernemings, insluitende GK’s, toenemend minder tyd het om op markveranderings en -geleenthede te reageer. Die klem val daarom op die ondernemingsingenieursweseen ondernemingsargitektuur-dissiplines as hulpmiddels om by die dinamiese landskap van die Inligtingsera aan te pas. Tans word die vermoë om omvattende ondernemingsingenieurswese in GK’s te beoefen, gekniehalter deur die tekort aan hulpbronne wat grondige konstruksie-beginsels vir hierdie netwerke beskryf. Die fokus van hierdie studie is daarom die toepassing van die ondernemingsingenieurswese-dissipline op GK’s deur die ontwikkeling van ’n verwysingsargitektuur. Die verwysingsargitektuur vir GK’s word ontwikkel deur ontwerpwetenskapnavorsing binne ’n pragmatiese en kwalitatiewe navorsingstrategie. Die navorsingsprobleem word eers geïdentifiseer en gemotiveer. Verskeie oplossingsdoelwitte word vervolgens bepaal. Hierna geskied die ontwerp en ontwikkeling van die verwysingsargitektuur deur middel van die vier herhalende ontwerpsiklusse. Die verwysingsargitektuur vir GK’s word gedemonstreer en geëvalueer deur ’n reeks beeldende scenario’s, waarna die bruikbaarheid, nuutheid en ontwerpstrengheid van die artefak gekommunikeer word. Dit is bevind dat die verwysingsargitektuur konstruksiebeginsels in die ontwikkeling van GK’s voorsien en sodoende die ontwerp, werk en navorsing in hierdie klas kollaborasie netwerke moontlik maak. Dié studie neem ‘n eerste tree in die rigting om die konsep van ondernemingsingenieurswese tot GK’s uit te brei. Dit maak die groter aanpasbaarheid van hierdie netwerke by die dinamiese omgewing van die Inligtingsera moontlik.
38

Proposition d'une approche unificatrice pour la gouvernance des systèmes d'information / Proposition of a unified approach for the governance of information systems

Makhlouf, Mohamed 04 June 2012 (has links)
La gouvernance des SI a été étudiée par les chercheurs et par les praticiens sous différents angles de vue. Du point de vue académique, des études ont été faites sur les structures de prise de décision, sur les facteurs impactants et sur les caractéristiques de la gouvernance des SI. Les praticiens se sont plutôt intéressés aux mécanismes de gouvernance de SI. Ainsi plusieurs approches et référentiels pour la gouvernance des SI ont vu le jour, ayant chacun des objectifs spécifiques (gestion de projet, gestion de service informatique, audit et contrôle de SI, maturité des processus, gestion de risques, qualité, etc.). Ces approches sont en général basées sur une vue processus. Comme elles affichent des objectifs différents, on peut observer, dans certaines grandes entreprises, des projets de mise en place simultanée et indépendante de plusieurs approches processus. Dans un tel cas, malgré les bénéfices apportés à l’entreprise par chacune des approches, on peut supposer que vont apparaître des problèmes de cohérence. Mais aucune étude ne semble avoir été faite pour savoir quels sont les apports et les conséquences d'une mise en place simultanée de différentes approches processus dans l'entreprise. De façon plus large, malgré la richesse de la recherche sur la gouvernance des SI, il n y a pas eu d’étude prenant la gouvernance des SI dans sa globalité et sous tous les angles de vue. Dans cette thèse, nous allons donc étudier la question suivante : Est-il pertinent d’adopter une approche globale de la gouvernance des SI ? Si oui, comment peut-on procéder ? Deux études sur le terrain chez deux grands opérateurs de télécommunications européens de deux ans chacune ont été menés. La première est une recherche-intervention en tant que observateur-participant complet, et la deuxième est une étude de cas avec une position d’observateur privilégié. Ces deux études ont permis d’apporter des éléments de réponses à cette question. La thèse est structurée de la façon suivante. D’abord, une étude approfondie de la littérature sur la gouvernance des SI (ch.1) a conduit à établir un méta-modèle unificateur de la gouvernance des SI (ch.2). La problématique (ch.3) et la méthodologie de recherche (ch.4) sont ensuite exposées. Puis, la première étude terrain teste la pertinence et la faisabilité de la mise en place d’une approche unificatrice de la gouvernance des SI : elle comporte une phase de diagnostic (ch.5) et une phase thérapeutique (ch.6). La seconde étude terrain permet d’explorer les conséquences d’une situation de mises en place simultanées et non coordonnées de plusieurs approches relevant de la gouvernance des SI : les données collectées sont décrites (ch.7) et analysées (ch.8). La thèse s’achève par la proposition du modèle GISUF « Governance of Information Systems Unified Framework», qui constitue une approche permettant de considérer la gouvernance des SI dans sa globalité. Après une première description de GISUF (ch.9), nous détaillons le système d’information sur lequel s’appuie la gouvernance, c’est-à-dire le référentiel de gouvernance (ch.10). Puis, nous décrivons le fonctionnement idéal d’une gouvernance globale unifiée à travers ses processus (ch.11). Enfin, nous exposons comment on peut mettre en place GISUF dans l’entreprise (ch.12). La conclusion indique les apports et les limites de la recherche / IS governance has been studied by researchers and practitioners from different angles. From the academic point of view, studies were made on the structures of decision making, the impacting factors, and the characteristics of IS governance. Practitioners are rather interested in the mechanisms of IS governance. Thus, several approaches and frameworks for IS governance have emerged, each with specific objectives (project management, service management, audit and control of IS, process maturity, risk management, quality, etc..). These approaches are generally based on a process view. As these approaches have different objectives, several process approaches simultaneous implementation projects can be observed in some large companies. In such case, despite the benefits of each of these approaches, we can assume that coherence problems will appear. Yet, no study has been conducted to find out what are the contributions and the consequences of several process approaches simultaneous implementation. More broadly, despite the richness of the research on IS governance, there has been no study that considers all the angles of view of the IS governance in a holistic manner. In this PhD, we will therefore consider the following question: Is it appropriate to adopt a holistic approach to IT governance? If so, how can we proceed? Two field studies at two major European telecommunications operators of two years each were conducted. The first is an action-research as a full participant-observer, and the second is a case study with a position of privileged observer. These two field studies permitted to answer this question. This thesis is structured as follows. First, a thorough review of the IS governance literature (ch.1) led to establish a unifying meta-model of IS governance (ch.2). The research problem (ch.3) and research methodology (ch.4) are then exposed. Then, the first field study tests the relevance and feasibility of establishing a unifying approach of IS governance: it consists in a diagnosis phase (ch.5) and a therapeutic phase (ch.6). The second field study explores the consequences of a situation where several IS governance approaches were implemented simultaneously and without coordination: the data collected are outlined (ch.7) and analyzed (ch.8). The thesis concludes with the proposed model GISUF "Governance of Information Systems Unified Framework", which is an IS governance holistic approach. After an initial description of GISUF (ch.9), we detail the information system on which governance is based, that is to say, the repository of governance (ch.10). Then, we describe the ideal operational functioning of the unified holistic governance through its processes (ch.11). Finally, we discuss how we can implement GISUF in an organization (ch.12). The conclusion shows the contributions and limitations of research
39

Arquitectura Empresarial para el proceso de compra de prestaciones de salud / Enterprise Architecture for the purchase process of Health benefits in Essalud

Guerrero Guerrero, Jean Marco, Tupia Vidal, Francisco Alberto 10 June 2019 (has links)
El actual proyecto surge a través de una necesidad, la cual es realizar un modelo de Arquitectura Empresarial del proceso de Compra de Prestaciones de Salud para la empresa estatal ESSALUD, con la finalidad de poder cubrir las inconsistencias que existen entre los procesos, usuarios, stakeholders, etc., las mismas que ocasionan pérdida de recursos, tiempo, además de afectar directamente la reputación y seriedad de la compañía. Así mismo, existe la necesidad de expandir la cobertura de los servicios de salud ofrecidos en el plano de una serie de restricciones financieras y políticas aplicadas por el gobierno de turno. De esta manera, gracias al desarrollo de la arquitectura empresarial para el proceso de compra de prestaciones de salud se puede optimizar y reducir los costos, gastos y tiempos utilizados actualmente en la entidad de salud; lo cual genera no solo un cuello de botella en el procedimiento general no solo internamente afectando al personal, sino, también, a la sociedad, pues existe actualmente un porcentaje muy alto de personas disconformes con el servicio que se ofrece. Para ello, es necesario que los procesos a los que se recurren esten correctamente definidos, de igual manera sus entradas, flujo interno y salidas, de tal manera que, al auditar estos procedimientos los números y estadísticas cuadren con el balance anual que se realiza para las entidades reguladoras de los presupuestos. / The current project comes through a necessity, which is to make a design model of the Enterprise Architecture Process Purchase benefits for the state company ESSALUD, in order to be able to cover the inconsistencies between processes, users, stakeholders, etc., the same that cause loss of resources, time, as well as directly affect the reputation and reliability of the company. Also, there is a need to expand the coverage of health services offered in terms of a number of financial and political restrictions imposed by the government. In this way, thanks to the development of the enterprise architecture for the process of buying health services in EsSalud, costs, expenses and time of use can be optimized and reduced at the health entity. Don’t make a change in this procedure generates not only a trouble in the general procedure, so it is not only internally affecting the staff, also affects to society, since there is a very high percentage of people that doesn’t like the service offered. For this, it is necessary that the processes that are used should be correctly define, as well as their inputs, the internal flow and outputs, this can generate that the numbers and the statistics match the annual balance that is made for the budgets regulatory entities. / Tesis
40

Arquitectura empresarial en una microfinanciera en el Perú / Enterprise architecture for credits in the microfinance sector in Perú

Santos Rodríguez, Brenda Alicia, Ugarte Robles, David Nigel 14 June 2019 (has links)
El aumento de cartera pesada de clientes es un problema que se presenta en las empresas del sector microfinanciero, considerándose como una de las razones por las cuales muchas microfinancieras pequeñas entran en bancarrota y terminan traspasando sus deudas a otras con mayor poder adquisitivo. Existen algunas soluciones para el problema de cartera pesada, pero en su mayoría usan términos y conceptos de Economía, que no toman en cuenta la interacción o integración de los procesos principales de las microfinancieras, como la colocación de productos crediticios, iniciando por el diseño y elaboración de estos hasta la cobranza. Este trabajo propone una arquitectura empresarial como respuesta al aumento de cartera pesada. Es por ello por lo que se usarán los artefactos del marco de trabajo TOGAF, siguiendo su metodología ADM para el desarrollo de la arquitectura. Asimismo, se considerará el modelo de procesos presentes en el estándar BIAN para verificar su aplicabilidad en las microfinancieras al momento de establecer los procesos base. Como resultado final se obtuvo que la venta de cartera pesada se reduzca significativamente, debido a un mayor control del proceso y el uso de sistemas que permiten gestionar y conocer mejor a las personas que solicitan créditos, evitando futuros endeudamientos. / The increase in the heavy portfolio of clients is a problem that occurs in companies in the microfinance sector, considered as one of the reasons why many small microfinance institutions go bankrupt and end up transferring their debts to other institutions with greater purchasing power. There are some solutions for the heavy portfolio problem, but they deal more with the economic issue than the technological or business processes, not taking into account the interaction or integration of the main processes of the microfinance, such as the placement of credit products, starting with the design and elaboration of these until collection. This paper proposes a business architecture in response to the heavy portfolio increase. It is for this reason that the TOGAF frameworks will be used, following its ADM methodology for the development of architecture. Likewise, the model of processes present in the BIAN standard will be considered to verify its applicability in microfinance institutions when establishing the starting processes. The final result was that the sale of the heavy portfolio was significantly reduced, due to a greater control of the process and the use of systems that allow managing and getting to know the people who apply for loans, avoiding future indebtedness. / Tesis

Page generated in 0.1033 seconds