To see the other types of publications on this topic, follow the link: Enterprise architectures.
Dissertations / Theses on the topic 'Enterprise architectures'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Enterprise architectures.'
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.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
LladoÌ, Matas Catalina. "Performance evaluation of enterprise JavaBeans architectures." Thesis, Imperial College London, 2002. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.406582.
Full text
2
Mykityshyn, Mark. "Assessing the maturity of information architectures for complex dynamic enterprise systems." Diss., Atlanta, Ga. : Georgia Institute of Technology, 2007. http://hdl.handle.net/1853/26686.
Full textAbstract:
Thesis (Ph.D)--Industrial and Systems Engineering, Georgia Institute of Technology, 2008.Committee Chair: Dr. William B. Rouse; Committee Member: Dr. Amy Pritchett; Committee Member: Dr. Leon McGinnis; Committee Member: Dr. Mike Cummins; Committee Member: Dr. Steve Cross. Part of the SMARTech Electronic Thesis and Dissertation Collection.
3
Fradinho, Jorge Miguel dos Santos. "Towards high performing hospital enterprise architectures : elevating hospitals to lean enterprise thinking." Thesis, Massachusetts Institute of Technology, 2011. http://hdl.handle.net/1721.1/67757.
Full textAbstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Engineering Systems Division, 2011.Cataloged from PDF version of thesis.
Includes bibliographical references (p. 608-630).
This research is motivated by the National Academy of Engineering and the Institute of Medicine's joint call for research in healthcare, promoting the application of principles, tools, and research from engineering disciplines, and complex systems in particular. In 2005, the US healthcare expenditure represented 16% of its GDP, with hospitals representing the largest source of expenditure, as is the case in the United Kingdom. Consequently, the strategies and operations developed and implemented by hospitals have a significant impact on healthcare. Today, it would be hard to find a hospital that is not implementing a Lean initiative or who isn't familiar with its concepts. However, more often than not, their approach has narrowly focused at a process level and inside individual service units like an emergency department. This research seeks to elevate traditionally narrow hospital definitions of lean and explore the broader concepts of lean enterprise principles and Enterprise Architecture (EA) while enhancing our knowledge of hospitals' socio-technical complexity and enriching an emerging EA Framework (EAF) developed at the Massachusetts Institute of Technology (MIT). Following an extensive longitudinal multidisciplinary literature review, a number of expert interviews, and preliminary empirical findings, an exploratory inductive and deductive hybrid study was designed to collect and concurrently analyze both qualitative and quantitative empirical data from multiple hospital settings over two main phases: * The first phase consisted of recorded interviews with the Chief Executive Officers of seven leading Massachusetts hospitals, who also provided sensitive internal strategy and operations documents. We explored how hospitals currently measure their hospital performance and how their explicit and implicit practices may be improved using lean enterprise principles. e The second phase comprised two in-depth case studies of large leading multidisciplinary hospitals, one located in the US and other in the United Kingdom, and included a total of 13 embedded units of analysis. Multiple sources of evidence were collected including electronic medical records, 54 interviews, observation, and internal documents. Findings were categorized and sorted, as phenomena of interest consistently emerged from the data, and enriched both the EAF, and our understanding of hospitals' EA in particular. In both in-depth hospital cases we found that their EA consisted of multiple internal architectural configurations, and in particular, those with an enriched understanding of EA had made decisions which had improved not only their local performance, but also enhanced their interactions with other service units upstream and downstream. Conversely, worse performing configurations demonstrated a limited understanding of their hospital's EA. We conclude that hospital performance can be improved through an enriched understanding of hospital EA. Furthermore, whilst considering all hospitals included in this study, we propose general and specific recommendations, as well as diagnostic questions, performance dimensions, and metrics, to assist senior hospital leaders in architecting and managing their enterprise.
by Jorge Miguel dos Santos Fradinho.
Ph.D.
4
Ruyter, Masood. "The measurement of enterprise architecture to add value to small and medium enterprises." Thesis, Cape Peninsula University of Technology, 2012. http://hdl.handle.net/20.500.11838/2293.
Full textAbstract:
Thesis (MTech (Information Technology))--Cape Peninsula University of Technology, 2012.South Africa has a complex financial and retail service industry with high reliance on the use of IT systems to ensure effectiveness and maintainability. Decision making and improved outcomes may be done through an IT aligned enterprise architecture (EA) strategy. EA is a capability that contributes to the support and success of an organisations' IT. Organisations are currently using EA to better align IT and the business strategy which provides a comprehensive v.ew of the IT system. Thus, EA is increasing in organisations yet the measurement and value of EA is limited to organisations and enterprise architects. The discussions of the benefits and value of EA has been discussed for several years, however there are still no consensus about how the benefits and value of EA can be measured. The lack and clear understanding of the benefits and value of EA needs to consider different aspects of IT as well as the shareholders when measuring the benefits and value of EA to an organisation.
5
Qaddoura, Fareed. "Dynamic Website and Data Engine Generators for Distributed Enterprise/Business Architectures." ScholarWorks@UNO, 2004. http://scholarworks.uno.edu/td/195.
Full textAbstract:
Creating websites providing dynamic services is an extensive process. Intelligent systems are used to create websites with dynamic services. Current intelligent systems are hard to use and configure by the average user. The generated websites are usually custom built to solve one problem and cannot be fully customizable for users on different environments. This thesis presents a technological solution that enables the average user to create websites with dynamic services by providing a number of parameters. The website generator is a web-based application that generates all the components of the website. The components act as portlets and the generated website will be the portal application. The data engine generator creates the website's underlying database. To enable distributed enterprise/business architecture, the data engine generator records the metadata about the database and the website to be generated. The website generator is a cost effective, dynamic, secure, reliable, and scalable solution that outperforms current website generators and portal applications.
6
Zeito, Maurice. "Reference Architectures as Means to Aid in System Development." Thesis, KTH, Industriella informations- och styrsystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-120205.
Full textAbstract:
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.
7
Schlieter, Hannes, Martin Juhrisch, Stephan Bögel, and Werner Esswein. "Adapting Enterprise Architectures for Health-Care Networks – Field Report of an Implementation." Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2014. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-142820.
Full text
8
Schlieter, Hannes, Martin Juhrisch, Stephan Bögel, and Werner Esswein. "Adapting Enterprise Architectures for Health-Care Networks – Field Report of an Implementation." Technische Universität Dresden, 2010. https://tud.qucosa.de/id/qucosa%3A28019.
Full text
9
Tabatabaie, Malihe. "Towards process models for goal-based development of enterprise information systems architectures." Thesis, University of York, 2011. http://etheses.whiterose.ac.uk/2159/.
Full textAbstract:
Enterprises are organisations with multiple business processes; they often use Enterprise Information Systems (EIS) to support these business processes. The concept of an EIS has arisen from the need to deal with the increasingly volatile requirements of modern large{scale organisations. EIS are growing in use and are now being used to support government, health care, and non-profit / non-governmental organisations. The development of EIS has been affected significantly by the complexity and size of enterprises and their business processes, in addition to the influences of economical, social, and governmental factors. There are many challenges associated with building EIS. Three critical ones identied in the literature are: adequately satisfying organisational requirements; building valid and stakeholder-acceptable business processes; and providing repeatable and rigorous approaches to establish shared understanding of EIS goals. These challenges are difficult to cope with because of the need to deal with different goals, changes in goals, and the problem of how to transform these goals into system requirements and, ultimately, to an EIS architecture. This thesis contributes a rigorous approach for identifying and describing the enterprise-level requirements of IT developers, managers, and other stakeholders of an enterprise. The approach provides two modelling and tool-supported processes to help establish a rigorous model of EIS goals. It also provides support for transforming goals to a strategic EIS architecture. The approach presented in the thesis is based on the concepts of Goal-oriented software engineering. The thesis presents a novel Process Model, KAOS-B that extends goal-oriented software engineering approaches with new concepts and techniques for EIS. Further, to support the transition from requirements to an EIS architecture, an EIS Architecture Process Model (EAPM), is designed and evaluated. Using KAOS-B and EAPM in concert provides a rigorous, repeatable and tool-supported approach for analysing, and designing a strategic EIS architecture. The thesis illustrates the approach with two substantial examples from the health informatics and critical systems domain.
10
Montoya, Mario 1978. "On developing business architectures : a multi-framework evaluation of an early-stage enterprise." Thesis, Massachusetts Institute of Technology, 2010. http://hdl.handle.net/1721.1/59261.
Full textAbstract:
Thesis (S.M. in System Design and Management)--Massachusetts Institute of Technology, Engineering Systems Division, 2010.Cataloged from PDF version of thesis.
Includes bibliographical references (p. 193-196).
Early-stage enterprises are characterized by leveraging limited resources during periods of accelerating industry growth and relatively high uncertainty. This thesis is an examination of an early-stage enterprise within the medical technology industry using multiple frameworks. In addition to the standard Lean Advancement Initiative (LAI) suite of tools, the enterprise will be evaluated using Nightingale and Rhodes' eight Enterprise Architecture (EA) views, Kaplan's Balanced Scorecard (BSC), McKinsey's 7S framework, and Grave's Spiral Dynamics. Moreover, this thesis includes a practical examination of the current state using the framework developed by Piepenbrock's doctoral thesis that introduced the notion of modular versus integral enterprise architectures. A transformation plan is proposed based on the firm's current state and preferred future state based on insights from the various self-assessments and prevailing corporate strategy. The transformation plan is also informed by the author's perceived receptivity, commitment and need for change of the organization. The case organization's current state is described in general terms to protect the company's identity since the material presented includes portions of their corporate strategy and source of competitive advantage. Recognizing that all competitive advantage is temporary, considerable care has been exercised to balance the relevance of the research with the privacy needs of the organization.
by Mario Montoya, Jr..
S.M.in System Design and Management
11
Yates, James William. "MANAGING TELEMETRY AS AN ENTERPRISE SOLUTION LEVERAGING TECHNOLOGY INTO NEXT-GENERATION TELEMETRY ARCHITECTURES." International Foundation for Telemetering, 2000. http://hdl.handle.net/10150/607714.
Full textAbstract:
International Telemetering Conference Proceedings / October 23-26, 2000 / Town & Country Hotel and Conference Center, San Diego, CaliforniaWith today’s rapidly shifting technology in the areas of networking, the Web, platform-independent software, and component technology, a paradigm shift will allow us to treat our telemetry systems as enterprise-wide solutions in the future. These technologies will revolutionize how we support all phases of telemetry data acquisition, processing, archiving, distribution, and display. This paper will explain how these changes affect systems designers, operators, and users. Specific technical areas of discussion include: § Technology adoption cycles § Object-oriented environments and component technologies § Database interconnectivity § Web-enabling concepts and implementations § Application servers § Database replication § Data warehousing § Embedded Web servers
12
Grashoff, Henning. "A rational scheme for conflict detection and resolution in distributed collaborative environments for enterprise integration." Thesis, City University London, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.319671.
Full text
13
Holm, Hannes. "A Framework and Calculation Engine for Modeling and Predicting the Cyber Security of Enterprise Architectures." Doctoral thesis, KTH, Industriella informations- och styrsystem, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-140525.
Full textAbstract:
Information Technology (IT) is a cornerstone of our modern society and essential for governments' management of public services, economic growth and national security. Consequently, it is of importance that IT systems are kept in a dependable and secure state. Unfortunately, as modern IT systems typically are composed of numerous interconnected components, including personnel and processes that use or support it (often referred to as an enterprise architecture), this is not a simple endeavor. To make matters worse, there are malicious actors who seek to exploit vulnerabilities in the enterprise architecture to conduct unauthorized activity within it. Various models have been proposed by academia and industry to identify and mitigate vulnerabilities in enterprise architectures, however, so far none has provided a sufficiently comprehensive scope. The contribution of this thesis is a modeling framework and calculation engine that can be used as support by enterprise decision makers in regard to cyber security matters, e.g., chief information security officers. In summary, the contribution can be used to model and analyze the vulnerability of enterprise architectures, and provide mitigation suggestions based on the resulting estimates. The contribution has been tested in real-world cases and has been validated on both a component level and system level; the results of these studies show that it is adequate in terms of supporting enterprise decision making. This thesis is a composite thesis of eight papers. Paper 1 describes a method and dataset that can be used to validate the contribution described in this thesis and models similar to it. Paper 2 presents what statistical distributions that are best fit for modeling the time required to compromise computer systems. Paper 3 describes estimates on the effort required to discover novel web application vulnerabilities. Paper 4 describes estimates on the possibility of circumventing web application firewalls. Paper 5 describes a study of the time required by an attacker to obtain critical vulnerabilities and exploits for compiled software. Paper 6 presents the effectiveness of seven commonly used automated network vulnerability scanners. Paper 7 describes the ability of the signature-based intrusion detection system Snort at detecting attacks that are more novel, or older than its rule set. Finally, paper 8 describes a tool that can be used to estimate the vulnerability of enterprise architectures; this tool is founded upon the results presented in papers 1-7.Informationsteknik (IT) är en grundsten i vårt moderna samhälle och grundläggande för staters hantering av samhällstjänster, ekonomisk tillväxt och nationell säkerhet. Det är därför av vikt att IT-system hålls i ett tillförlitligt och säkert tillstånd. Då moderna IT-system vanligen består av en mångfald av olika integrerade komponenter, inklusive människor och processer som nyttjar eller stödjer systemet (ofta benämnd organisationsövergripande arkitektur, eller enterprise architecture), är detta tyvärr ingen enkel uppgift. För att förvärra det hela så finns det även illvilliga aktörer som ämnar utnyttja sårbarheter i den organisationsövergripande arkitekturen för att utföra obehörig aktivitet inom den. Olika modeller har föreslagits av den akademiska världen och näringslivet för att identifiera samt behandla sårbarheter i organisationsövergripande arkitekturer, men det finns ännu ingen modell som är tillräckligt omfattande. Bidraget presenterat i denna avhandling är ett modelleringsramverk och en beräkningsmotor som kan användas som stöd av organisatoriska beslutsfattare med avseende på säkerhetsärenden. Sammanfattningsvis kan bidraget användas för att modellera och analysera sårbarheten av organisationsövergripande arkitekturer, samt ge förbättringsförslag baserat på dess uppskattningar. Bidraget har testats i fallstudier och validerats på både komponentnivå och systemnivå; resultaten från dessa studier visar att det är lämpligt för att stödja organisatoriskt beslutsfattande. Avhandlingen är en sammanläggningsavhandling med åtta artiklar. Artikel 1 beskriver en metod och ett dataset som kan användas för att validera avhandlingens bidrag och andra modeller likt detta. Artikel 2 presenterar vilka statistiska fördelningar som är bäst lämpade för att beskriva tiden som krävs för att kompromettera en dator. Artikel 3 beskriver uppskattningar av tiden som krävs för att upptäcka nya sårbarheter i webbapplikationer. Artikel 4 beskriver uppskattningar för möjligheten att kringgå webbapplikationsbrandväggar. Artikel 5 beskriver en studie av den tid som krävs för att en angripare skall kunna anskaffa kritiska sårbarheter och program för att utnyttja dessa för kompilerad programvara. Artikel 6 presenterar effektiviteten av sju vanligt nyttjade verktyg som används för att automatiskt identifiera sårbarheter i nätverk. Artikel 7 beskriver förmågan av det signatur-baserade intrångsdetekteringssystemet Snort att upptäcka attacker som är nyare, eller äldre, än dess regeluppsättning. Slutligen beskriver artikel 8 ett verktyg som kan användas för att uppskatta sårbarheten av organisationsövergripande arkitekturer; grunden för detta verktyg är de resultat som presenteras i artikel 1-7.
QC 20140203
14
Piepenbrock, Theodore F. (Theodore Frederick) 1965. "Toward a theory of the evolution of business ecosystems : enterprise architectures, competitive dynamics, firm performance & industrial co-evolution." Thesis, Massachusetts Institute of Technology, 2009. http://hdl.handle.net/1721.1/57976.
Full textAbstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Engineering Systems Division, 2009.Cataloged from PDF version of thesis. Vita.
Includes bibliographical references (v. 4, p. 698-745).
This dissertation contributes toward the building of a theory of the evolution of business ecosystems. In the process, it addresses a question that has been posed by evolutionary theorists in the economics and sociology literatures for decades: "Why do firms in the same industry vary systematically in performance over time?" Seeking a systematic explanation of a longitudinal phenomenon inevitably requires characterizing the evolution of the industrial ecosystem, as both the organization (firm) and its environment (industry, markets and institutions) are co-evolving. This question is therefore explored via a theoretical sample in three industrial ecosystems covering manufacturing and service sectors, with competitors from the US, Europe and Japan: commercial airplanes, motor vehicles and airlines. The research is based primarily on an in depth seven-year, multi-level, multi-method, field-based case study of both firms in the large commercial airplanes industry mixed duopoly as well as the key stakeholders in their extended enterprises (i.e. customers, suppliers, investors and employees). This field work is supplemented with historical comparative analysis in all three industries, as well as nonlinear dynamic simulation models developed to capture the essential mechanisms governing the evolution of business ecosystems.
(cont.) A theoretical framework is developed which endogenously traces the co-evolution of firms and their industrial environments using their highest-level system properties of form, function and fitness (as reflected in the system sciences of morphology, physiology and ecology), and which embraces the evolutionary processes of variation, selection and retention. The framework captures the path-dependent evolution of heterogeneous populations of enterprise architectures engaged in symbiotic inter-species competition and posits the evolution of dominant designs in enterprise architectures that oscillate deterministically and chaotically between modular and integral states throughout an industry's life-cycle. Architectural innovation - at the extended enterprise level - is demonstrated to contribute to the failure of established firms, with causal mechanisms developed to explain tipping points.
by Theodore F. Piepenbrock.
Ph.D.
15
Sundar, Gayathri. "Design of a service-oriented dashboard." Birmingham, Ala. : University of Alabama at Birmingham, 2007. https://www.mhsl.uab.edu/dt/2007m/sundar.pdf.
Full textAbstract:
Thesis (M.S.)--University of Alabama at Birmingham, 2007.Additional advisors: David G. Green, Gary J. Grimes, John L. Hartman IV. Description based on contents viewed Feb. 5, 2008; title from title screen. Includes bibliographical references (p. 110-120).
16
Rifaie, Mohammad. "Strategy and methodology for enterprise data warehouse development : integrating data mining and social networking techniques for identifying different communities within the data warehouse." Thesis, University of Bradford, 2010. http://hdl.handle.net/10454/4416.
Full textAbstract:
Data warehouse technology has been successfully integrated into the information infrastructure of major organizations as potential solution for eliminating redundancy and providing for comprehensive data integration. Realizing the importance of a data warehouse as the main data repository within an organization, this dissertation addresses different aspects related to the data warehouse architecture and performance issues. Many data warehouse architectures have been presented by industry analysts and research organizations. These architectures vary from the independent and physical business unit centric data marts to the centralised two-tier hub-and-spoke data warehouse. The operational data store is a third tier which was offered later to address the business requirements for inter-day data loading. While the industry-available architectures are all valid, I found them to be suboptimal in efficiency (cost) and effectiveness (productivity). In this dissertation, I am advocating a new architecture (The Hybrid Architecture) which encompasses the industry advocated architecture. The hybrid architecture demands the acquisition, loading and consolidation of enterprise atomic and detailed data into a single integrated enterprise data store (The Enterprise Data Warehouse) where businessunit centric Data Marts and Operational Data Stores (ODS) are built in the same instance of the Enterprise Data Warehouse. For the purpose of highlighting the role of data warehouses for different applications, we describe an effort to develop a data warehouse for a geographical information system (GIS). We further study the importance of data practices, quality and governance for financial institutions by commenting on the RBC Financial Group case. v The development and deployment of the Enterprise Data Warehouse based on the Hybrid Architecture spawned its own issues and challenges. Organic data growth and business requirements to load additional new data significantly will increase the amount of stored data. Consequently, the number of users will increase significantly. Enterprise data warehouse obesity, performance degradation and navigation difficulties are chief amongst the issues and challenges. Association rules mining and social networks have been adopted in this thesis to address the above mentioned issues and challenges. We describe an approach that uses frequent pattern mining and social network techniques to discover different communities within the data warehouse. These communities include sets of tables frequently accessed together, sets of tables retrieved together most of the time and sets of attributes that mostly appear together in the queries. We concentrate on tables in the discussion; however, the model is general enough to discover other communities. We first build a frequent pattern mining model by considering each query as a transaction and the tables as items. Then, we mine closed frequent itemsets of tables; these itemsets include tables that are mostly accessed together and hence should be treated as one unit in storage and retrieval for better overall performance. We utilize social network construction and analysis to find maximum-sized sets of related tables; this is a more robust approach as opposed to a union of overlapping itemsets. We derive the Jaccard distance between the closed itemsets and construct the social network of tables by adding links that represent distance above a given threshold. The constructed network is analyzed to discover communities of tables that are mostly accessed together. The reported test results are promising and demonstrate the applicability and effectiveness of the developed approach.
17
Dimitrov, Dimitar. "Towards cloud application architectural patterns: transfer, evolution, innovation and oblivion." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-27643.
Full textAbstract:
Recently, cloud computing has been gaining more and more popularity. Misunderstanding, misusing and underutilizing the cloud offerings, though, both from business and technical perspective still poses a threat to the success of cloud projects. On the technical side, one of the main reasons for success or failure is often the architectural design of the system – if a system is not architected the “cloud way”, using cloud’s special characteristics, the business benefits of such a system are often questionable at best. Software architecture through architectural patterns – reusable generic solutions to classes of problems – has for long been a good way to overcome the challenges of software architecture. This paper focuses on establishing the grounds and highlighting the differences of the knowledge transfer regarding architectural patterns from building pre-cloud (“traditional”) software systems to building cloud-native systems. The following 3 research questions drive this research: RQ1. How does the existing knowledge on architectural patterns relate to the cloud computing environment? RQ2. Which characteristics of architectural patterns make them suitable for the cloud environment? RQ3. How can architectural pattern evolution be documented effectively for usage in the practice? In order to answer these 3 research questions and considering their focus is on utility i.e. creating a model which can be directly used in practice, the research uses design science research methodology (Peffers, et al., 2007-8). The emphasis in this methodology is iteratively building artefact(s) which can be improved and proven through practice that they actually help solving the problem at hand. This research contributes with building 4 inter-connected artefacts: a cloud applicability taxonomy of architectural patterns (CATAP) showing how applicable to a cloud environment an architectural pattern is and why; a pattern-to-characteristics mapping showing how using an architectural pattern affects the resulting system in traditional and cloud environments; a pattern form documenting the architectural patterns and the findings about them in the previous two artefacts; a wiki site, APE Wiki, which makes the results available to the public for reference and discussion and improvement. This research has a few interesting findings. First of all, the current architectural pattern knowledge seems to be very mature as no pattern has been found to have significantly evolved because of cloud – the architectural patterns are really generic and very flexible and only their effect on system characteristics has changed with the environment switch. On the other hand, a few new patterns were discovered and documented, which confirms the need for special attention to the new environment. Apart from that, the pattern-to-characteristics mapping provides interesting insights into which characteristics are most important for cloud and where there is a gap which may need to be filled. This paper presents both the process and the results of the research as equally important as replicating and extending this research could help in maturing the results and the knowledge about architecting systems for cloud thus increasing the chances of success of cloud projects.
18
Singh, Nisheet. "Sense Respond Environment for Adaptive Participatory Services." The Ohio State University, 2010. http://rave.ohiolink.edu/etdc/view?acc_num=osu1274975205.
Full text
19
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
20
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 textAbstract:
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.
21
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 textAbstract:
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.
22
Hloušek, Matouš. "MMDIS A ENTERPRISE ARCHITECTURE." Master's thesis, Vysoká škola ekonomická v Praze, 2008. http://www.nusl.cz/ntk/nusl-3369.
Full textAbstract:
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.
23
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 textAbstract:
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.
24
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 textAbstract:
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.
25
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 textAbstract:
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.
26
Joubert, Francois. "Knowledge assets in enterprise architecture." Thesis, Stellenbosch : University of Stellenbosch, 2010. http://hdl.handle.net/10019.1/5433.
Full textAbstract:
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.
27
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 textAbstract:
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.
28
Lee, Min-Wei. "Vacation system." CSUSB ScholarWorks, 2005. https://scholarworks.lib.csusb.edu/etd-project/2829.
Full textAbstract:
The purpose of this project was to explore the use of Web services to solve enterprise computing problems. XML-based Web services allow complex information systems to be subdivided. In order to explore this architectural paradigm, two systems were built: an employee records sytem, and a vacation system.
29
Iyamu, T. "The architecture of information in organisations." Open Journal Publishing, 2011. http://encore.tut.ac.za/iii/cpro/DigitalItemViewPage.external?sp=1000468.
Full textAbstract:
Over the last two decades competition amongst organisations including financial institutions
has increased tremendously. The value of information is critical to competition in different organisations. In addition, the management of cost of delivery and cohesiveness of information
flow and use in the organisations continue a challenge to information technology (IT). In an attempt to address these challenges, many organisations sought various solutions, including
enterprise information architecture (EIA). The EIA is intended to address the needs of the organisation for competitive advantage.
This research article focused on the role of principles in the development and implementation of EIA. The article aimed to investigate how EIA could be best leveraged, exploited, or otherwise used to provide business value. The research brings about a fresh perspective and
new methodological principles required in architecting the enterprise information.
30
Possne, Mathias. "Ramverk för Enterprise Architecture på SL." Thesis, KTH, Industriella informations- och styrsystem, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-102257.
Full textAbstract:
The concept of Enterprise Architecture (EA) has become increasingly common within enterprises today and aims to describe an enterprise’s structure in a standardized way. Implementing EA within an enterprise is a way to describe the how various domains affect each other and by defining uniform procedures and guidelines, particularly in the link between IT-activities and business activities, you can streamline you enterprise. An effective EA is a huge asset for an enterprise since it enables the full usage of the business potential of the IT-domain. However a malfunctioning EA can lead to an enormous drain of valuable organizational resources. The latter is too often more common. With EA, it is easier to understand how decisions made in one domain affects other domains, thereby increasing an enterprise's pro-activity and efficiency. By mapping the EA frameworks available on the market and how an implementation of an EA framework can affect how you work within SL, I give in this thesis a description of how an EA framework can be implemented in an enterprise regarding general needs and conditions. The framework which I think is best suited for SL to use in order to establish an EA within the enterprise is TOGAF. TOGAF is an established methodology framework, which also has a relatively well-defined ontology, i.e. a description of the components that a business should have and its relations. TOGAF is a generic framework intended to be used in a variety of environments, which enables the possibility for integration with other frameworks. TOGAF provides a flexible and extensible content which allows it to deliver a tailored approach that can be integrated into the processes and structures within the enterprise. The results of the requirement analysis carried out in the thesis shows that there is a great need and a great willingness to perform change management within SL. Of the surveyed respondents in the interview study, 83% answered that there are problem areas in SL that needs attention. The key problem area was considered by most of the respondents to be the lack of a link between the business domain and IT domains within SL, as well as who owns and manages information within the company. As for how these problem areas should be addressed most respondents (76%) answered that they agreed on Enterprise Architecture being a good tool for SL. Many also felt the need to clarify how the domains affect each other and clarify the benefits of implementing EA within SL.
31
Akhigbe, Okhaide Samson. "Business Intelligence - Enabled Adaptive Enterprise Architecture." Thèse, Université d'Ottawa / University of Ottawa, 2014. http://hdl.handle.net/10393/31012.
Full textAbstract:
The desire to obtain value and justify investments from the different Information Systems in place in organizations has been around for a long time. Organizations constantly theorize and implement different approaches that provide some sort of alignment between their different business objectives and Information Systems. Unfortunately, the environments in which these organizations operate are often dynamic, constantly changing with influence from external and internal factors that require continual realignment of the Information Systems with business objectives to provide value.
When businesses evolve, leading to changes in business requirements, it is hard to know what direct Information System changes are needed to respond to the new requirements. Similarly, when there are changes in the Information System, it is not often easy to discern which business objectives are directly affected. Whilst the different Enterprise Architecture frameworks available today provide and propose some form of alignment, in their implementation, they do not show links between business objectives and Information Systems, i.e., indicating what Information System is directly responsible for different business objectives thereby allowing for anticipation and support of changes as the business evolves.
This thesis utilizes insights from Business Intelligence and uses the User Requirements Notation (URN), which enables modeling of business processes and goals, to provide a framework that exploits links between business objectives and Information Systems. This Business Intelligence - Enabled Adaptive Enterprise Architecture framework allows for anticipating and supporting proactively the adaptation of Enterprise Architecture as and when the business evolves. The thesis also identifies and models levels within the enterprise where responses to change as the business evolves are needed and the ways the changes are presented. The tool-supported framework is evaluated against the different levels and types of changes on a realistic Enterprise Architecture at a Government of Canada department, with encouraging results.
32
Bhutkar, Arjun Vijay 1967. "Architecture for multi-enterprise E-business." Thesis, Massachusetts Institute of Technology, 2000. http://hdl.handle.net/1721.1/88324.
Full text
33
Larsson, Malin. "Defining Thresholds for Enterprise Architecture Debt." Thesis, KTH, Industriell ekonomi och organisation (Inst.), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-296936.
Full textAbstract:
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.
34
Vašíček, Václav. "Vztah Enterprise Architecture a strategického managementu." Master's thesis, Vysoká škola ekonomická v Praze, 2009. http://www.nusl.cz/ntk/nusl-17047.
Full textAbstract:
Enterprise Architecture is so far the highest development step in IT's architectural description of enterprises. At the beginning, just technological architecture existed. However, with the quickly growing complexity of IT other domains occurred, that had to be described. Information or application architectures can serve as examples. IT then realized, that it needed to add to its IT architectures a business view and consequently the discipline Enterprise Architecture came into being. Strategic management is crucial for the development of each enterprise. The thesis focuses on the strategic management of business and the strategic management of IT. The strategic management of business consists of a business strategy and an operating model. To the strategic management of IT then belongs an information strategy and IT governance. Business-IT alignment further explores and ensures the accord between the strategic management of business and the strategic management of IT. The aim of the thesis is to describe the relationship of Enterprise Architecture and the different forms of strategic management and to express to which rate Enterprise Architecture supports them. The explored relationships are: - The relationship of Enterprise Architecture and business strategy - The relationship of Enterprise Architecture and operating models - The relationship of Enterprise Architecture and information strategy - The relationship of Enterprise Architecture and IT governance - The relationship of Enterprise Architecture and business-IT alignment The goals of the thesis are reached via theoretical research and subsequent deduction. The author's personal asset consists of creating a hierarchical model of Enterprise Architecture, of defining Enterprise Architecture's reaction to business strategies, of modifying the methodology MMDIS in respect of information strategy, of depicting, how Enterprise Architecture can be used in IT governance, of illustrating, where Enterprise Architecture contributes to business-IT alignment and of assessing, to which rate Enterprise Architecture supports the different forms of strategic management.
35
Nosková, Michaela. "Aplikace projektového řízení v Enterprise Architecture." Master's thesis, Vysoká škola ekonomická v Praze, 2011. http://www.nusl.cz/ntk/nusl-124702.
Full textAbstract:
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.
36
Brown-Moorer, Charlotte A. "Traceable Enterprise Information Security Architecture Methodology." International Foundation for Telemetering, 2009. http://hdl.handle.net/10150/605972.
Full textAbstract:
ITC/USA 2009 Conference Proceedings / The Forty-Fifth Annual International Telemetering Conference and Technical Exhibition / October 26-29, 2009 / Riviera Hotel & Convention Center, Las Vegas, NevadaWith the introduction of networking into telemetry applications, these systems have become increasingly complex. This imposes significant strain on information security for architecture designs. It has been recognized that an organized or structured approach to developing security architectures is needed. Several enterprise architecture frameworks are available today that address system complexity. However they fall short of addressing security at a high enough level in the enterprise and address security too late in the design process. In this paper a methodology is proposed that bridges the gap between security requirements and architecture design development at the enterprise level. This approach is consistent with and traceable to the original needs of the customer. This paper introduces a systems engineering approach to develop an enterprise level methodology, and presents a worked example of this approach for the integrated Network Enhanced Telemetry system.
37
Rhodd, Easton B. "Enterprise Integration Modeling Linking Enterprise Integration Architecture With Business Strategy Planning." NSUWorks, 2002. http://nsuworks.nova.edu/gscis_etd/800.
Full textAbstract:
The goals for this study were twofold. The first goal was to identify planning variables for linking both organizational and architectural objectives for developing enterprise integration architecture. The second goal was to validate enterprise integration modeling methodology as a viable planning tool for the design, development, and maintenance of the enterprise integration architecture.
This lack of linkage at the intellectual dimension level can be characterized as having a dysfunctional effect on enterprise integration strategy formulation and infrastructure development. There is a disjoint between adoptions of appropriate information technology in relation to organizational objectives. This includes misapplication of investments in information technology selection and business systems development portfolio, failed information systems projects, architectures that do not support the strategic direction, and the organization's inability to manage change associated with environmental imperatives that impact the firm's ability to define information technology and systems requirements for competitive positioning.
In order to achieve the objectives the author in this research, developed a conceptual Enterprise Integration Architecture Planning Model and Methodology (EIAPMIM) model as the basis for linking enterprise integration architecture objectives and organizational objectives. Research data confirmed the need to effect linkages between organizational objectives and architectural objectives to achieve enterprise integration and validated enterprise integration modeling as the means by which enterprise integration architecture is developed.
38
Lagerström, Robert. "Enterprise Systems Modifiability Analysis : An Enterprise Architecture Modeling Approach for Decision Making." Doctoral thesis, KTH, Industriella informations- och styrsystem, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-12341.
Full textAbstract:
Contemporary enterprises depend to great extent on software systems. During the past decades the number of systems has been constantly increasing and these systems have become more integrated with one another. This has lead to a growing complexity in managing software systems and their environment. At the same time business environments today need to progress and change rapidly to keep up with evolving markets. As the business processes change, the systems need to be modified in order to continue supporting the processes. The complexity increase and growing demand for rapid change makes the management of enterprise systems a very important issue. In order to achieve effective and efficient management, it is essential to be able to analyze the system modifiability (i.e. estimate the future change cost). This is addressed in the thesis by employing architectural models. The contribution of this thesis is a method for software system modifiability analysis using enterprise architecture models. The contribution includes an enterprise architecture analysis formalism, a modifiability metamodel (i.e. a modeling language), and a method for creating metamodels. The proposed approach allows IT-decision makers to model and analyze change projects. By doing so, high-quality decision support regarding change project costs is received. This thesis is a composite thesis consisting of five papers and an introduction. Paper A evaluatesa number of analysis formalisms and proposes extended influence diagrams to be employed for enterprise architecture analysis. Paper B presents the first version of the modifiability metamodel. InPaper C, a method for creating enterprise architecture metamodels is proposed. This method aims to be general, i.e. can be employed for other IT-related quality analyses such as interoperability, security, and availability. The paper does however use modifiability as a running case. The second version of the modifiability metamodel for change project cost estimation is fully described in Paper D. Finally, Paper E validates the proposed method and metamodel by surveying 110 experts and studying 21 change projects at four large Nordic companies. The validation indicates that the method and metamodel are useful, contain the right set of elements and provide good estimation capabilities.QC20100716
39
Österlind, Magnus. "VALIDERING AV VERKTYGET "ENTERPRISE ARCHITECTURE ANALYSIS TOOL"." Thesis, KTH, Industriella informations- och styrsystem, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-81393.
Full textAbstract:
The Enterprise Architecture Analysis Tool, EAAT, is a software tool developed by the department of Industrial Information- and Control systems, ICS, at the Royal Institute of Technology, Stockholm, Sweden. EAAT is a modeling tool that combines Enterprise Architecture (EA) modeling with probabilistic relational modeling. Therefore EAAT makes it possible to design, describe and analyze the organizational structure, business processes, information systems and infrastructure within an enterprise. During this study EAAT has been validated in order to assess the usability of the tool and to provide suggestion of improvement. To reach conclusions EA models of IT systems out in the industry has been created in EAAT. A usability study has been performed in order to find weaknesses and strength in the tools user interface. The results of the study consist of a couple of scenarios of how the tool might be used by the industry. An important feature to improve is the possibility to easily find the weak parts of the system. The user interface should provide more feedback to the user. The modeling process could be improved by providing the user with suggestions on what to do next in order to reach a full and complete model.
40
Malhotra, Rajeev. "An architecture for an apparel manufacturing enterprise." Diss., Georgia Institute of Technology, 1991. http://hdl.handle.net/1853/9349.
Full text
41
Machisa, Musafare. "Object relational mapping for enterprise application architecture." [Denver, Colo.] : Regis University, 2005. http://165.236.235.140/lib/MMachisa2005.pdf.
Full text
42
Callegård, Christoffer, and Mikael Händling. "Enterprise Architecture : How does it support innovation?" Thesis, Högskolan i Borås, Institutionen Handels- och IT-högskolan, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-20591.
Full textAbstract:
We believe there to be a possible problem with Enterprise Architecture, in that in using standardizations such as frameworks stifles creativity and innovations, focusing on IT-environments. This assumption is not new as there already are thoughts in existence on this subject, each side discussing if there is a fault or not. Out of our own interest we delve deeper into the subject of Enterprise Architecture to see if there is any truth in our assumption and to see if there is anything anyone can do to compensate or solve this perceived problem. We look into what Enterprise Architecture consists of and examine four different popular frameworks associated with it: TOGAF, FEA, Gartner and Zachman. We learn about creativity in Information Systems organizations and its connection to IT. Our research strategy for this thesis is deduction together with two separate phases, one phase is exploratory and the other descriptive. We examine the nature of creativity and innovation, there too with an emphasis on IT. In order to find out if our assumption is correct we seek out literature, articles and other sources of information on innovations, creativity and frameworks. Armed with this information we seek out and perform interviews with people from large commercial organizations who have hands-on work experience working with Enterprise Architecture in order to see if our assumptions have any form of validity and to gain some insight into the subject matter. The method components for this thesis are literature review, document study and interviews. Analyzed with the help of SWOT we use the data gathered from the interviews to gain a visual representation of the results, to see the pros and cons of Enterprise Architecture. The results show that supplements or tools are used in order to produce or support business innovations, using departments, business related social networks or techniques to compensate. Hampering factors for business innovation can be internal conflicts, struggles between different groups for different EA solutions. Promoting business innovation through EA can come from mixing framework bits together, giving the result of a flexible and adaptive framework. It can also come from acting as a common language and a bridge between different hierarchies. EA aids with difficult decisions, evaluating which alternatives for realization and the order services are realized. Meetings can be used to compensate the lack of creativity and innovation rising from EA. A negative consequence of EA can occur during implementation of things related to EA in larger companies. No examples of companies that failed with creating business innovation in their IT with EA were found.Program: Kandidatutbildning i informatik
43
Wong, Ming Fai. "Enterprise architecture landscape in Singapore Government agencies." Thesis, Massachusetts Institute of Technology, 2013. http://hdl.handle.net/1721.1/83810.
Full textAbstract:
Thesis (S.M. in Engineering and Management)--Massachusetts Institute of Technology, Engineering Systems Division, 2013.Cataloged from PDF version of thesis.
Includes bibliographical references (pages 56-57).
This paper reports results of a study done to understand the Enterprise Architecture (EA) landscape in Singapore Government Agencies, to gather some best practices in doing EA in these agencies, and to postulate how the Singapore Government might get more value out of EA. Firstly, this paper reviews the EA field on why EA is important and what are some key challenges EA practitioners face. Secondly, this paper reviews and analyzes data from a EA survey of 18 Singapore Government Agencies. The analysis is done by comparing against data from a similar survey collected from over 100 organizations worldwide. In addition, the analysis also draws upon EA research done by MIT's Center for Information System Research. Thirdly, this paper reviews best practices and a case study collected from a subset of the studied Singapore Government Agencies. This paper concludes by rounding up the key findings and hypothesizing that there is a need for stronger inhouse design/architecting capabilities within the Singapore Government.
by Ming Fai Wong.
S.M.in Engineering and Management
44
Belfadel, Abdelhadi. "Enterprise Architecture Capability Profile for Software Reuse." Thesis, Lyon, 2019. http://www.theses.fr/2019LYSE2125.
Full textAbstract:
La plupart des projets de développement logiciel actuel dépendent de l'utilisation des solutions existantes pour gagner du temps et réduire les coûts de développement. Pour atteindre cet objectif, les entreprises doivent tirer parti des fonctionnalités offertes par les services techniques ou les interfaces de programmation applicatives exposées par les solutions existantes. La collecte et la qualification de ces composants ou services techniques permet de les réutiliser directement ou par orchestration. L'objectif de ce travail est double. Tout d'abord, nous visons la conception d'un conteneur de capacités logicielles qui offre une vision plus large des solutions applicatives internes ou externes d'une organisation. Le deuxième objectif est de définir un modèle d'exploitation de ces profils de capacités logicielles en adéquation avec l'ingénierie des besoins et l'architecture d'entreprise, afin de combler l'écart entre les objectifs des parties prenantes et ce qui peut être fourni comme solution pratique. Cependant, pour atteindre les objectifs susmentionnés, il y a de nombreux défis à relever pour gérer la complexité de l'exploitation des profils de capacités logicielles internes ou externes, afin de sélectionner les meilleurs composants candidats pour servir d'éléments constitutifs dans un nouveau système. Parmi ces défis, on peut citer l'identification des connaissances architecturales pour l'évaluation et la réutilisation des composants techniques, ou l'alignement des besoins et des artefacts d'architecture dans un cycle d'ingénierie pour la consolidation et le raffinement des exigences, afin de faciliter la découverte et la réutilisation des solutions applicatives existantes. A cet effet, nous définissons un Framework offrant un processus de qualification qui permet de recueillir les exigences initiales utilisées pour guider le développement des applications existantes et des services techniques exposés. Le processus de qualification est4basé sur un profil de capacité d'architecture d'entreprise proposé et de son ontologie associée. Cette dernière est utile pour spécifier formellement le profil de capacité produit qui offre une qualification couvrant les aspects organisationnels, opérationnels et techniques des applications orientées services. De plus, une méthodologie d'exploitation du conteneur conçu pour agréger ces profiles est proposée avec le Framework et basée sur l'alignement du processus d'ingénierie des besoins avec une méthode de développement d'architecture. Ces derniers évoluent ensemble pour étudier la plus grande compatibilité fonctionnelle et technique des fonctionnalités souhaitées et des contraintes associées, pour répondre aux besoins des utilisateurs finaux et réutiliser efficacement les solutions qualifiées.Notre contribution vise à améliorer l'évaluation, la découverte et la réutilisation des applications et des services techniques associés. Par ailleurs, l'originalité de ce travail de recherche consiste à mettre à niveau la recherche sur la consommation et l'orchestration des services au niveau des besoins des utilisateurs finaux, afin d'accélérer et de faciliter le développement d'applications métier futures. Une implémentation du Framework ainsi qu'une étude de cas industriels sont proposés pour valider et démontrer l'efficacité de cette approcheMost of today's software development projects depend on the usage of existing solutions to save time and development cost. To achieve this goal, companies should take advantage of the features provided by services or application programming interfaces exposed by existing solutions. Collecting and qualifying IT components and services helps to reuse them directly or via orchestration. The goal of this work is twofold. First, we target the design of a software capability container that provides a broader view of an organization’s internal and external software. The second objective is to define an exploitation model of the software capability profiles in line with requirements engineering and enterprise architecture, to fill the gap between the goals of the stakeholders and what can be delivered as a practical solution. However, to achieve the above-stated objectives, there are many challenges to manage the complexity of the exploitation of internal or external’s software capability profiles, to select the best candidate components to act as a building blocks in a new system. Among those challenges, one can mention the identification of architectural artifacts for the evaluation and reuse of software components. Adding to this challenge, the alignment of requirements and architectural artifacts in engineering cycle for requirements consolidation and refinement to facilitate the discovery and reuse of existing solutions.For this purpose, we define a Framework offering a qualification process that helps to retrieve and gather initial requirements used to guide the development of existing software and related services. The qualification process is based on a proposed Enterprise Architecture Capability Profile and its associated ontology. This latter is useful to formally specify and encode the produced capability2profile that offers a qualification and covers business, operational and technical aspects for service-oriented software. Furthermore, an exploitation methodology of the designed container is proposed along with the Framework and based on the alignment of requirements engineering process with an architecture development method. These latter evolve together to investigate the highest functional and technical compatibility of the desired functionalities and related constraints, to respond to end-user’s requirements and efficiently reuse the qualified solutions.Our contribution aims to improve the evaluation, discovery, and reuse of existing software and related services. Besides, the originality of this research work consists in upgrading research on services consumption and orchestration to the level of end-users’ requirements, mapped with advanced service assets as an enabler for accelerating business application development. An implementation of the Framework along with an industrial case study are proposed to validate and demonstrate the effectiveness of this approach
45
Oderinde, Dumebi O. "Understanding Enterprise Architecture in four UK universities." Thesis, University of Bolton, 2012. http://ubir.bolton.ac.uk/555/.
Full textAbstract:
This research examines the rationale and impact of Enterprise Architecture (EA) adoption in the UK Higher Educational (HE) sector. EA supports alignment of Information Systems (IS) capability and high-level Strategic Planning for organisations. Previous studies in HE sector show that IS planning difficulties are increasingly affecting required levels of effectiveness and future changes. Institutions identify the need for a business-like approach, to support senior managers in the decision-making in times of unprecedented economic and sector revolution. Adopters spearheading the process claim that EA concepts and tools will enable institutions capture IT resources, align administrative processes, leverage IS investments and coordinate information requirements and regulations effectively. This claim is supported by the identification of benefits of EA in other public and private sectors. Using 4 UK universities, this study reviews the practices and effects of EA in the larger but more traditional universities and medium-sized but newer universities. The institutions were investigated using interpretive research methods. Data was collected through semi-structured interviews and thematic analysis was used to analyse the data and interpret the findings based on a combination of existing and new theoretical constructs. A summary of the research findings states four key success factors for the adoption and institutionalisation of EA in HE institutions. They are: (i) Senior management support, appropriate organisational structures, actors and scope of EA work (ii) Key stakeholder buy-in and commitment (iii) Resources (iv) Evaluation metrics. HE institutions are not adverse to EA adoption; but are aware that institutional actors and cultures shape the adoption. There are necessary support structures that should be in place: (i) institutions need to have a formalised governance structure, which ensures proper planning procedures are enforced and change is monitored effectively, (ii) the right people skill and availability would ensure success, (iii) adopting a systematic and continuous approach to business process review (iv) institutions need to develop simple and flexible IT infrastructure to enable requirements for integration, accessibility, and agility.
46
Aririguzo, Julian Chika. "Fractal architecture for 'leagile' networked enterprises." Thesis, Sheffield Hallam University, 2009. http://shura.shu.ac.uk/19286/.
Full textAbstract:
The manufacturing environment and markets in recent times are becoming increasingly dynamic, diverse and unpredictable, due mainly to fast evolution of products and technology, erratic customer behaviour and high consumerism and an increasingly shorter lead-time. The burden of the impact falls on organisational structures built on centralized, rigid manufacturing architecture, because they cannot cope or adapt to the highly uncertain or unpredictable nature of the market. Enterprises who wish to survive these challenges need to rethink their business and manufacturing models, and most importantly reinvent their tactical, operational and organizational formulas to leverage their strategic long term visions. Newer manufacturing systems to curb the effects of this upheaval have to promote an entirely decentralised, flexible, distributed, configurable and adaptable architecture to ameliorate this condition. Many philosophies are proposed and studied towards planning, monitoring, and controlling the 21st century manufacturing system. These include - Bionic manufacturing system (BMS), Holonic manufacturing system (HMS), Fractal manufacturing system (FrMS), Responsive manufacturing etc. This research program focuses on the FrMS, which has vast conceptual advantageous features among these new philosophies, but its implementation has proved very difficult. FrMS is based on autonomous, cooperating, self-similar agent called fractal that has the capability of perceiving, adapting and evolving with respect to its partners and environment. The fractal manufacturing configuration uses self regulating, organisational work groups, each with identical goals and within its own area of competence to build up an integrated, holistic network system of companies. This network yields constant improvement as well as continuous checks and balances through self-organising control loops. The study investigates and identifies the nature, characteristic features and feasibility of this system in comparison to traditional approaches with a detailed view to maximising the logistical attribute of lean manufacturing system and building a framework for 'leagile' (an integration of lean and agile solutions) networked capabilities. It explores and establishes the structural characteristic potentials of Fractal Manufacturing Partnership (FMP), a hands-on collaboration between enterprises and their key suppliers, where the latter become assemblers of their components while co-owning the enterprise's facility, to create and achieve high level of responsiveness. It is hoped that this architecture will drive and harness the evolution from a vertically integrated company, to a network of integrated, leaner core competencies needed to tackle and weather the storm of the 21st century manufacturing system.
47
Kistasamy, Christopher. "The role of service-oriented architecture as an enabler for enterprise architecture." Thesis, Cape Peninsula University of Technology, 2011. http://hdl.handle.net/20.500.11838/2298.
Full textAbstract:
Thesis (MTech (Information Technology))--Cape Peninsula University of Technology, 2011.The adoption of Enterprise Architecture (EA) methodologies within organizations is causing an interest in the methodologies and supporting technologies available. Service Oriented Architecture (SOA) supports EA in many facets. However, there is much suspension with regard to the relationship between EA and SOA within organizations as well as the guidelines that organisations should follow in order for SOA to enable EA. There are potential problems that may arise if this relationship between SOA and EA is not agreed to at the outset of implementing an EA. The purpose of this research is to investigate the guidelines that are needed for SOA to enable EA, in order to provide practical steps that organisations can use to begin aligning SOA and EA, ensuring that these initiatives are driven from a business perspective. A qualitative approach using a case study was used as a methodology for this research. The data collection was conducted using semi-structured interviews, and the guidelines that were derived were validated through a survey that was distributed to industry architecture practitioners. The contribution of this research was a set of guidelines that can be used for SOA to enable EA. Further research areas were highlighted, including investigating the mapping of the guidelines that were derived from this research, into the EA frameworks that exist such as TOGAF and ZACHMAN.
48
Ahmad, Mahmood. "Semantic derivation of enterprise information architecture from Riva-based business process architecture." Thesis, University of the West of England, Bristol, 2015. http://eprints.uwe.ac.uk/25772/.
Full textAbstract:
Contemporary Enterprise Information Architecture (EIA) design practice in the industry still suffers from issues that hamper the investment in the EIA design. First and foremost of these issues is the shortcoming of EIA design research to bridge the gap between business and systems (or information) architectures. Secondly, contemporary developed business process architecture methods, and in particular object-based ones have not been fully exploited for EIA design and thus widening the gap between business processes and systems. In practice, knowledge-driven approaches have been thoroughly influencing EIA design. Thirdly, the lack of using knowledge representation methods adversely affected the automation (or semi-automation) of the EIA design process. Software Engineering (SE) technologies and Knowledge Representation using ontologies continue to prove instrumental in the design of domain knowledge. Finally, current EIA development methods have often resulted in complex designs that hampered both adopting and exploiting EIA in medium to large scale organisations. This research is aimed at investigating the derivation of the EIA from a given semantic representation of object-based Business Process Architecture (BPA), and in particular Riva-based BPA using the design science research-based methodology. The key design artefact of this research is the development of the BPAOntoEIA framework that semantically derives EIA from a semantic representation of Riva-based BPA of an enterprise. In this framework, EIA elements were derived from the semantic Riva BPA elements and associated business process models, with forward and backward traceability from/to the derived EIA to/from the original BPA. The BPAOntoEIA framework has been evaluated using the semantic Cancer Care and Registration BPA in Jordan. This framework has been validated using an authentic concern-based evaluation framework employing both static and dynamic validation approaches. The BPAOntoEIA framework contributes to bridging the gap between the business and systems world by providing a business/IT alignment through the EIA derivation process, and using the semantic knowledge of business processes within the resultant EIA. A major novel contribution is the introduction of new evaluation metrics for EIA design, which are quantitative, and are not only indicative of the quality of the semantic EIA derivation from the associated BPA but also the extent of utilising business process knowledge and traceability amongst EIA elements. Amongst other novel contributions is the semantic EIA derivation process that comprises a suite of the Semantic Web Rules Language (SWRL) rules applied on the semantic BPA elements. The derivation scheme utilises the generic EIA (gEIAOnt) ontology that was developed in this research and represents a semantic meta-model of EIA elements of a generic enterprise. The resultant EIA provides a highly coherent semantic information model that is in-line with the theory of EIA design, semantically enriched, and fully utilises the semantic knowledge of business processes. Benefits of this research to industry include the semantic EIA derivation process and a resultant information model that utilises the semantic information of business processes in the enterprise. Therefore, this enables the enterprise strategic management to plan for a single, secure and accessible information resource that is business process driven, and enabled in an agile environment. The semantic enrichment of the EIA is a starting point for a simplistic design of a domain-independent semantic enterprise architecture for the development of systems of systems in loosely coupled enterprises.
49
ARPINI, R. H. "A Framework to Support the Assignment of Active Structure and Behavior in Enterprise Modeling Approaches." Universidade Federal do Espírito Santo, 2012. http://repositorio.ufes.br/handle/10/4260.
Full textAbstract:
Made available in DSpace on 2016-08-29T15:33:18Z (GMT). No. of bitstreams: 1
tese_5494_.pdf: 2904195 bytes, checksum: c6fded7753ec6bae38735ba2962dbb09 (MD5)
Previous issue date: 2012-08-31The need to relate the various architectural domains captured in partial descriptions of an enterprise is addressed in virtually all enterprise modeling approaches. One of these domains, namely that of organizational behavior, has received significant attention in recent years in the context of business process modeling and management. Another important domain, that of organizational structure is strongly inter-related with the process domain. While the process domain focuses on how the business process activities are structured and performed, the organizational structure domain focuses on who performs these activities, i.e., which kinds of entities in an organization are capable of performing work. Given the strong connection between the organizational behavior and organizational resources, we argue that any comprehensive enterprise modeling technique should explicitly establish the relations between the modeling elements that represent organizational behavior, called here behavioral elements, and those used to represent the organizational resources (organizational actors) involved in these activities, called here active structure elements. Despite the importance of the relations between these architectural domains, many of the current enterprise architecture and business process modeling approaches lack support for the expressiveness of a number of important active structure allocation scenarios. This work aims to overcome these limitations by proposing a framework for active structure assignment that can be applied to enterprise architecture and business process modeling approaches. This framework enriches the expressiveness of existing techniques and supports the definition of precise active structure assignments. It is designed such that it should be applicable to a number of enterprise architecture and business process modeling languages, i.e., one should be able to use and apply different (enterprise and business process) modeling languages to the framework with minor changes.
50
Johnson, Pontus. "Enterprise Software System Integration : An Architectural Perspective." Doctoral thesis, KTH, Elektrotekniska system, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-3365.
Full text