Relevant bibliographies by topics / Enterprise architecture

Academic literature on the topic 'Enterprise architecture'

Author: Grafiati
Published: 4 June 2021
Last updated: 25 May 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Enterprise architecture.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Enterprise architecture"

1

Seigerroth, Ulf. "Enterprise Modeling and Enterprise Architecture." International Journal of IT/Business Alignment and Governance 2, no. 1 (January 2011): 16–34. http://dx.doi.org/10.4018/jitbag.2011010102.

Full text
Abstract:
Several scholars have argued for the need to integrate both the IT perspective and the business perspective during development of enterprises and IS/IT architectures. In this process, it is necessary to be able to deal with a number of sub-areas to succeed with the transformation. One challenge is the need to move beyond a narrow focus on one tradition or technology, as well as to use and integrate different concepts within an enterprise. This integrated view also includes the use and development of guidelines (methods, tools, etc.), in addition to research methodologies and human aspects. Therefore, enterprise modeling and enterprise architecture must treat all slices in a comprehensive alignment context. In this paper, the author presents a conceptualization of the research area Enterprise Modeling and Enterprise Architecture with a focus on transformation and alignment of business and IT.
APA, Harvard, Vancouver, ISO, and other styles
2

Mišovič, Milan. "Application architectures of enterprise information systems versus service oriented architecture." Acta Universitatis Agriculturae et Silviculturae Mendelianae Brunensis 55, no. 6 (2007): 233–42. http://dx.doi.org/10.11118/actaun200755060233.

Full text
Abstract:
There are two different enterprise IS architectures, older application architecture and younger service oriented architecture. The application architecture its structural element is a classical web-based application can accept a partial or complex solution of enterprise IS. The first has got problems with data-process-communication integrity disturbing among IS applications. The second is convenient for large enterprises not for small and intermediate. Classical web-based applications are too inflexible to accepted necessary changes concerning a progress in the enterprise market-production environment.The service oriented architecture of IS can be based on enterprise web-services. Computerization of such small and flexible units can be given by classical web-services. There is constructed a new web-based application that plays a structural unit role for service oriented architecture. This application consists of a sequence formed by enterprise web-services calling. Enterprise web-services can easily accept necessary changes concerning a progress in the enterprise market-production environment. That‘s why contemporary younger service oriented architecture seems to be more acceptable for any enterprise than older application architecture.
APA, Harvard, Vancouver, ISO, and other styles
3

Trad, Antoine. "Enterprise Transformation Projects." ARIS2 - Advanced Research on Information Systems Security 3, no. 1 (August 30, 2023): 4–33. http://dx.doi.org/10.56394/aris2.v3i1.31.

Full text
Abstract:
This article presents the ETP-HSC and a corresponding enterprise transformation framework, where the focus is on the application of Enterprise Architecture (EA) to support Security (EA4S) and it is the central topic. The EA4S is a Polymathic-holistic approach, which adopts a clear EA as the main ETP constraint for the implementation of a secured Information and Communications System’s (ICS). EA and all other ICS related architecture disciplines, are inspired from the term Architecture that comes from civil engineering, and in this domain, secured building objects are achieved by implementing robust building and urbanistic architectures, like the famous case of Hausmann’s Architecture and Urbanistic plan for the (re)Architecture of Paris in France, in which its primary objective was to assert Paris’ security. Therefore, the author considers that EAS’ first step is to build an enterprise security concept. But for enterprises that have been archaically built and do not have the needed resources to implement a Haussmannian security concept, therefore an iterative ETP-HSC implementation process can transform the enterprise’s security. ETP-HSC’s feasibility and integrity can be supported by an integrated Applied Holistic Mathematical Model (AHMM) for EAS (AHMM4EAS), and the author’s various research works on the applications of holistic security concepts, ETPs, Artificial Intelligence (AI), Cloud Services (CS), and AHMM. The ETP-SRC is based on a multi-disciplinary proprietary-mixed research method.
APA, Harvard, Vancouver, ISO, and other styles
4

Ngurah Suryantara, I. Gusti, Jusia Amanda Ginting, and Dewi Candani Sulaiman. "PENGEMBANGAN ARSITEKTUR ENTERPRISE PADA DEPARTEMEN FINANCE (STUDI KASUS: DEALER MOBIL PT.XYZ)." Infotech: Journal of Technology Information 8, no. 1 (June 30, 2022): 1–12. http://dx.doi.org/10.37365/jti.v8i1.124.

Full text
Abstract:
Along with advances in technological developments, the development of making applications in a enterpriseis also experiencing development. This is in line with the increasingly complex business developments today. For this reason, careful planning is needed to invest in IT / IS (Information Technology / Information Systems) in a enterprise. The failure of IT/IS investment in a enterprise is one of the factors due to not having an IT/IS investment roadmap in a enterprise in the form of Enterprise Architecture. To get maximum results from an IT/IS investment in a enterprise, it is necessary to develop Enterprise Architecture. Enterprise architecture is a blueprint for a enterprise in achieving the enterprise's vision and mission supported by the implementation of IT/IS. So the selection of an Enterprise Architecture development framework is very important, one of the frameworks that can be used in the development of Enterprise Architecture such as the Zachman Framework. The Zachman Framework uses a 6-row and 6-column matrix to generate a blueprint. With the existence of the Enterprise Architecture blueprint, the enterprise can then use it for a roadmap for the development of applications needed by the enterprise, so that IT/IS technology investment in the enterprise can help the enterprise's business processes to achieve the vision and mission.
APA, Harvard, Vancouver, ISO, and other styles
5

Amelia Wulan Sari Sapitri. "Perancangan Enterprise Architecture HMI Sampit Menggunakan TOGAF." Kompak :Jurnal Ilmiah Komputerisasi Akuntansi 16, no. 1 (July 1, 2023): 154–61. http://dx.doi.org/10.51903/kompak.v16i1.1080.

Full text
Abstract:
The Islamic Student Association (HMI) is an umbrella organization with a clear model of being Indonesian and Islamic, providing a platform to train and develop leaders with honesty and quality determination, faith and responsibility. The factors that provide direction within the organization to adopt an Enterprise Architecture (EA) system are aimed at enhancing what the organization needs. Enterprise architecture or what can be called Enterprise Architecture (EA) is a description of the task in question consisting of knowledge, actions, direction from the organization and architectural performance parameters in the description of the design or plan and development of an integrated system. TOGAF (The Open Group Architecture Framework) is a framework that is widely used in creating enterprise or organizational architectures. TOGAF offers methods and tools for creating, running, implementing, and maintaining enterprise architectures in existing systems. The results of this study are in the form of a blueprint that is expected to be useful for organizations as material to assist IT development in HMI.
APA, Harvard, Vancouver, ISO, and other styles
6

PYLYPENKO, Andriy. "ENSURING THE SUSTAINABILITY OF THE REORGANIZATION OF CORPORATE ENTERPRISES AND THEIR INTEGRATED ASSOCIATION’S ACTIVITIES." Ukrainian Journal of Applied Economics 5, no. 2 (May 7, 2020): 78–87. http://dx.doi.org/10.36887/2415-8453-2020-2-9.

Full text
Abstract:
Introduction. In terms of the ISO 22301 requirements about ensuring the enterprise continuity under the increasing external environment variability, it is necessary to form control contours for maintaining the reorganization sustainability of corporate enterprises and their integrated associations. The purpose of scientific research is to develop theoretical and methodological bases for ensuring the sustainability of the reorganization of the activities of integrated associations of corporate enterprises. Results. The corporate architecture concept usage to ensure the sustainability of the enterprise activities reorganization has been proposed. The connection between the enterprise activities reorganization, its reorganization as a legal entity, and the redistribution of corporate control have been determined. The Open Group Architecture Framework (TOGAF), the architectural modeling language Archimate, and the OMG Essence standard (the kernel and Language for Software Engineering Methods) have been used as the research's methodological basis. The author's approach specific distinction is the program of enterprise activities reorganization subordination to the vision of key stakeholders about the list of practices used to create consumer value. The possibility of maintaining the stability reorganization of the enterprise and its activities by using the concept of successful organizational transformations has been reflected. The practical significance of the developed technology of the reorganization sustainability is laid in providing business entities the tools for matching critical elements of the current and future enterprise’s business model. This matching gives to the enterprise management possibility to develop the organizational transformation program. Conclusions. The proposed technology of enterprise reorganization sustainability ensuring is focused on creating a successful socio-economic system and based on taking into account the interests of main stakeholders. However, the presented technology reveals only a higher level of corporate enterprise activity organization. Therefore, the prospects for further author’s research consist of detailing particular enterprise architecture elements and forming a model basis for their coordinated development. Keywords: the enterprise activity reorganization, corporate enterprise, integrated association of enterprises, enterprise architecture, and corporate control.
APA, Harvard, Vancouver, ISO, and other styles
7

Qumer Gill, Asif, and Muhammad Atif Qureshi. "Adaptive Enterprise Architecture Modelling." Journal of Software 10, no. 5 (May 2015): 628–38. http://dx.doi.org/10.17706/jsw.10.5.628-638.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Clarke, Michael, Jon G. Hall, and Lucia Rapanotti. "Enterprise Architecture." International Journal of IT/Business Alignment and Governance 4, no. 1 (January 2013): 1–10. http://dx.doi.org/10.4018/jitbag.2013010101.

Full text
Abstract:
Enterprise Architecture (EA) has been portrayed as one of the cornerstones of modern IT Governance, with increasing numbers of organisations formally recognising an EA function and adopting EA frameworks such as TOGAF (http://www.opengroup.org/togaf/) (The Open Group Architectural Framework). Many claims have been made of the benefits of EA, yet little is known as to what organisations actually do or evidence of the benefits they accrue through EA. In this paper we report on the results of a small scale survey painting a snapshot of current EA practice in large UK organisations across the private and public sectors.
APA, Harvard, Vancouver, ISO, and other styles
9

Perez-Castillo, Ricardo, Francisco Ruiz, Mario Piattini, and Christof Ebert. "Enterprise Architecture." IEEE Software 36, no. 4 (July 2019): 12–19. http://dx.doi.org/10.1109/ms.2019.2909329.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Winter, Robert, and Elmar J. Sinz. "Enterprise Architecture." Information Systems and e-Business Management 5, no. 4 (June 12, 2007): 357–58. http://dx.doi.org/10.1007/s10257-007-0054-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Enterprise architecture"

1

Hariharan, Charanya Cameron Brian H. "Enterprise architecture & service oriented architecture." [University Park, Pa.] : Pennsylvania State University, 2009. http://etda.libraries.psu.edu/theses/approved/PSUonlyIndex/ETD-4880/index.html.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

OLIVEIRA, FABIANO SALDANHA GOMES DE. "ENTERPRISE AN ARCHITECTURE LISP." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 1991. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=8981@1.

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

Canat, Mert. "Enterprise Architecture Success Factors." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-247884.

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

Hloušek, Matouš. "MMDIS A ENTERPRISE ARCHITECTURE." Master's thesis, Vysoká škola ekonomická v Praze, 2008. http://www.nusl.cz/ntk/nusl-3369.

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

Grunow, Sebastian. "Automated Enterprise Service Bus Based Enterprise Architecture Documentation." Thesis, KTH, Industriella informations- och styrsystem, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-92240.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
6

Sahebi, Ladan, and Danial Araghi. "On Using Enterprise Modelling Methods for Building Enterprise Architecture." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH, Data- och elektroteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-22644.

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

Glazner, Christopher G. "Understanding enterprise behavior using hybrid simulation of enterprise architecture." Thesis, Massachusetts Institute of Technology, 2009. http://hdl.handle.net/1721.1/55171.

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

Joubert, Francois. "Knowledge assets in enterprise architecture." Thesis, Stellenbosch : University of Stellenbosch, 2010. http://hdl.handle.net/10019.1/5433.

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

Sládek, Pavel. "Enterprise Architecture v systému řízení." Master's thesis, Vysoká škola ekonomická v Praze, 2008. http://www.nusl.cz/ntk/nusl-15526.

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

Kandjani, Hadi Esmaeilzadeh. "Engineering Self-designing Enterprises as Complex Systems Using Enterprise Architecture Cybernetics." Thesis, Griffith University, 2013. http://hdl.handle.net/10072/367332.

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

Books on the topic "Enterprise architecture"

1

Op ’t Land, Martin, Erik Proper, Maarten Waage, Jeroen Cloo, and Claudia Steghuis. Enterprise Architecture. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-85232-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Whittle, Ralph. Enterprise Business Architecture. London: Taylor and Francis, 2004.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Arnold, Ingo. Enterprise Architecture Function. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-84589-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Musukutwa, Sheunopa Chalmers. SAP Enterprise Architecture. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-8575-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Banger, Daljit Roy. Enterprise Systems Architecture. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-8646-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

McDowall, John D. Complex Enterprise Architecture. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-4306-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Perroud, Thierry, and Reto Inversini. Enterprise Architecture Patterns. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-37561-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Graves, Tom. Everyday Enterprise Architecture. Berkeley, CA: Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-8904-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Mulder, Jeroen. Modern Enterprise Architecture. Berkeley, CA: Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9066-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Cloud enterprise architecture. Boca Raton, Fla: CRC Press, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Enterprise architecture"

1

Vasconcelos, André, and Pedro Sousa. "Enterprise Architecture." In Enterprise Architecture and Cartography, 29–77. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-96264-7_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Hanschke, Inge. "Enterprise Architecture." In Strategic IT Management, 55–104. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-05034-3_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Grant, Gerald G., and Robert Collins. "Enterprise Architecture." In The Value Imperative, 99–112. New York: Palgrave Macmillan US, 2016. http://dx.doi.org/10.1057/978-1-137-59040-4_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Subramanian R, Kannan, and Dr Sudheesh Kumar Kattumannil. "Enterprise Architecture." In Event- and Data-Centric Enterprise Risk-Adjusted Return Management, 339–455. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-7440-8_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Wang, Liang, and Jianxin Zhao. "Enterprise Architecture." In Studies in Big Data, 25–57. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-55885-6_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Agievich, Vadim, Rinat Gimranov, Victor Taratoukhine, and Jörg Becker. "Towards Enterprise Architecture Using Solution Architecture Models." In Enterprise Interoperability, 89–94. Chichester, UK: John Wiley & Sons, Ltd, 2014. http://dx.doi.org/10.1002/9781118846995.ch9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Op ’t Land, Martin, Erik Proper, Maarten Waage, Jeroen Cloo, and Claudia Steghuis. "The Need for a New Instrument." In Enterprise Architecture, 5–24. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-85232-2_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Op ’t Land, Martin, Erik Proper, Maarten Waage, Jeroen Cloo, and Claudia Steghuis. "The Results of Enterprise Architecting." In Enterprise Architecture, 49–83. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-85232-2_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Op ’t Land, Martin, Erik Proper, Maarten Waage, Jeroen Cloo, and Claudia Steghuis. "The Enterprise Architect." In Enterprise Architecture, 113–25. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-85232-2_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Op ’t Land, Martin, Erik Proper, Maarten Waage, Jeroen Cloo, and Claudia Steghuis. "Conclusion." In Enterprise Architecture, 127–36. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-85232-2_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Enterprise architecture"

1

Tambo, Torben. "Enterprise Architecture beyond the Enterprise - Extended Enterprise Architecture Revisited." In 19th International Conference on Enterprise Information Systems. SCITEPRESS - Science and Technology Publications, 2017. http://dx.doi.org/10.5220/0006277103810390.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Pereira, Carla Marques, and Pedro Sousa. "Enterprise architecture." In the 2005 ACM symposium. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1066677.1066980.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Veneberg, R. K. M., M. E. Iacob, M. J. Van Sinderen, and L. Bodenstaff. "Enterprise Architecture Intelligence: Combining Enterprise Architecture and Operational Data." In 2014 IEEE 18th International Enterprise Distributed Object Computing Conference (EDOC). IEEE, 2014. http://dx.doi.org/10.1109/edoc.2014.14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Jung, Chan-ki. "Actionable Enterprise Architecture." In 2009 10th ACIS International Conference on Software Engineering, Artificial Intelligences, Networking and Parallel/Distributed Computing. IEEE, 2009. http://dx.doi.org/10.1109/snpd.2009.106.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Daoudi, Wissal, Karim Doumi, and Laila Kjiri. "Adaptive Enterprise Architecture." In ICIST '20: 10th International Conference on Information Systems and Technologies. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3447568.3448539.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Feodoroff, Ray. "Intentional enterprise architecture." In 2016 Annual IEEE Systems Conference (SysCon). IEEE, 2016. http://dx.doi.org/10.1109/syscon.2016.7490555.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Winter, Robert, and Joachim Schelp. "Enterprise architecture governance." In the 2008 ACM symposium. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1363686.1363820.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Byrne, R., and V. Hodge. "Enterprise architecture in action." In IET Seminar on Enterprise Architecture Frameworks. IEE, 2008. http://dx.doi.org/10.1049/ic:20080619.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

""DATA GOVERNANCE, ENTERPRISE ARCHITECTURE AND ENTERPRISE AGILITY"." In 16th International Conference Information Systems 2023. IADIS Press, 2023. http://dx.doi.org/10.33965/is2023_202301l013.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Costa, Ana B., and Miguel A. Brito. "Enterprise Architecture Management : Constant maintenance and updating of the Enterprise Architecture." In 2022 17th Iberian Conference on Information Systems and Technologies (CISTI). IEEE, 2022. http://dx.doi.org/10.23919/cisti54924.2022.9820068.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Enterprise architecture"

1

Ender, Tommer, Santiago Balestrini-Robinson, Daniel Browne, Jennifer DeLockery, Aaron Hansen, William Marshall, Rob McColl, Drew Pihera, Valerie Sitterle, and Timothy Van Heest. Enterprise Architecture Tradespace Analysis. Fort Belvoir, VA: Defense Technical Information Center, February 2014. http://dx.doi.org/10.21236/ada603143.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Lewis, Grace A., Santiago Cornella-Dorda, Pat Place, Daniel Plakosh, and Robert C. Seacord. An Enterprise Information System Data Architecture Guide. Fort Belvoir, VA: Defense Technical Information Center, October 2001. http://dx.doi.org/10.21236/ada399203.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Roboam, Michel, Mark S. Fox, and Katia Sycara. Enterprise Management Network Architecture: The Organization Layer. Fort Belvoir, VA: Defense Technical Information Center, November 1990. http://dx.doi.org/10.21236/ada233070.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Roboam, Michel, Mark S. Fox, and Katia Sycara. Enterprise Management Network Architecture Distributed Knowledge Base Support. Fort Belvoir, VA: Defense Technical Information Center, November 1990. http://dx.doi.org/10.21236/ada230113.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Rose, Scott. Planning for a Zero Trust Architecture. Gaithersburg, MD: National Institute of Standards and Technology, 2022. http://dx.doi.org/10.6028/nist.cswp.20.

Full text
Abstract:
NIST Special Publication 800-207 defines zero trust as a set of cybersecurity principles used when planning and implementing an enterprise architecture. These principles apply to endpoints, services, and data flows. Input and cooperation from various stakeholders in an enterprise is needed for a zero trust architecture to succeed in improving the enterprise security posture. Some of these stakeholders may not be familiar with risk analysis and management. This document provides an overview of the NIST Risk Management Framework (NIST RMF) and how the NIST RMF can be applied when developing and implementing a zero trust architecture.
APA, Harvard, Vancouver, ISO, and other styles
6

Knight, John C., Jack W. Davidson, David Evans, Westley Weimer, Anh Nguyen-Tuong, Hao Chen, Karl N. Levitt, Jeff Rowe, Zhendong Su, and Felix Wu. Helix: A Self-Regenerative Architecture for the Incorruptible Enterprise. Fort Belvoir, VA: Defense Technical Information Center, November 2012. http://dx.doi.org/10.21236/ada579086.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

DiDuro, John, Robert Crosslin, Debra Dennie, Paul Jung, and Christopher Louden. A Practical Approach to Integrating Information Security into Federal Enterprise Architecture. Fort Belvoir, VA: Defense Technical Information Center, October 2002. http://dx.doi.org/10.21236/ada408768.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Michelson, Brenda. Designing a Fluid Enterprise Using an Adaptive, Customer-Centric IT Architecture. Boston, MA: Patricia Seybold Group, December 2004. http://dx.doi.org/10.1571/bda12-9-04cc.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Malloy, Mary A., Edward V. Masek, Robert W. Miller, and Daniel G. Winkowski. An Information Architecture Framework for the USAF: Managing Information from an Enterprise Perspective. Fort Belvoir, VA: Defense Technical Information Center, March 2010. http://dx.doi.org/10.21236/ada576472.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Urquidi, Manuel, Gloria Ortega, Víctor Arza, and Julia Ortega. New Employment Technologies: The Benefits of Implementing Services within an Enterprise Architecture Framework: Executive Summary. Inter-American Development Bank, July 2021. http://dx.doi.org/10.18235/0003403.

Full text
Abstract:
Public employment services (PES) offer tools through different channels to both employers and job seekers. The multiplicity of services and channels, paired with processes that are sometimes inadequately mapped, creates challenges when implementing digital systems. This document discusses how using enterprise architecture can provide a framework for defining and representing a high-level view of the organizations processes and its information technology (IT) systems, as well as their relationship with different parts of the organization and external entities. Having a strategic vision and a high-level design allows implementing systems in phases and modules to organize services to improve their efficiency and effectiveness. This document aims to support policy makers, managers and officials working with employment policies in understanding the benefits of implementing a comprehensive digital transformation in institutions within the framework of a strategic tool such as enterprise architecture.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Enterprise architecture' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography