Статті в журналах з теми "Enterprise architectures"

Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Enterprise architectures.

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся з топ-50 статей у журналах для дослідження на тему "Enterprise architectures".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Переглядайте статті в журналах для різних дисциплін та оформлюйте правильно вашу бібліографію.

1

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

Повний текст джерела
Анотація:
There are two different enterprise IS architectures, older application architecture and younger service oriented architecture. The application architecture its structural element is a classical web-based application can accept a partial or complex solution of enterprise IS. The first has got problems with data-process-communication integrity disturbing among IS applications. The second is convenient for large enterprises not for small and intermediate. Classical web-based applications are too inflexible to accepted necessary changes concerning a progress in the enterprise market-production environment.The service oriented architecture of IS can be based on enterprise web-services. Computerization of such small and flexible units can be given by classical web-services. There is constructed a new web-based application that plays a structural unit role for service oriented architecture. This application consists of a sequence formed by enterprise web-services calling. Enterprise web-services can easily accept necessary changes concerning a progress in the enterprise market-production environment. That‘s why contemporary younger service oriented architecture seems to be more acceptable for any enterprise than older application architecture.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

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

Повний текст джерела
Анотація:
Several scholars have argued for the need to integrate both the IT perspective and the business perspective during development of enterprises and IS/IT architectures. In this process, it is necessary to be able to deal with a number of sub-areas to succeed with the transformation. One challenge is the need to move beyond a narrow focus on one tradition or technology, as well as to use and integrate different concepts within an enterprise. This integrated view also includes the use and development of guidelines (methods, tools, etc.), in addition to research methodologies and human aspects. Therefore, enterprise modeling and enterprise architecture must treat all slices in a comprehensive alignment context. In this paper, the author presents a conceptualization of the research area Enterprise Modeling and Enterprise Architecture with a focus on transformation and alignment of business and IT.
Стилі APA, Harvard, Vancouver, ISO та ін.
3

JONKERS, HENK, MARC LANKHORST, RENÉ VAN BUUREN, STIJN HOPPENBROUWERS, MARCELLO BONSANGUE, and LEENDERT VAN DER TORRE. "CONCEPTS FOR MODELING ENTERPRISE ARCHITECTURES." International Journal of Cooperative Information Systems 13, no. 03 (September 2004): 257–87. http://dx.doi.org/10.1142/s0218843004000985.

Повний текст джерела
Анотація:
A coherent description of enterprise architecture provides insight, enables communication among stakeholders and guides complicated change processes. Unfortunately, so far no enterprise architecture description language exists that fully enables integrated enterprise modeling, because for each architectural domain, architects use their own modeling techniques and concepts, tool support, visualization techniques, etc. In this paper, we outline such an integrated language and we identify and study concepts that relate architectural domains. In our language, concepts for describing the relationships between architecture descriptions at the business, application, and technology levels play a central role, related to the ubiquitous problem of business-ICT alignment, whereas for each architectural domain we conform to existing languages or standards such as UML. In particular, usage of services offered by one layer to another plays an important role in relating the behaviour aspects of the layers. The structural aspects of the layers are linked through the interface concept, and the information aspects through realization relations.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Wang, Heyong, Wu He, and Feng-Kwei Wang. "Enterprise cloud service architectures." Information Technology and Management 13, no. 4 (August 18, 2012): 445–54. http://dx.doi.org/10.1007/s10799-012-0139-4.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Geerts, Guido L., and Harry Jiannan Wang. "The Timeless Way of Building REA Enterprise Systems." Journal of Emerging Technologies in Accounting 4, no. 1 (January 1, 2007): 161–82. http://dx.doi.org/10.2308/jeta.2007.4.1.161.

Повний текст джерела
Анотація:
In a continuously changing business environment, the need for enterprise systems that are more adaptable has been recognized by many. Several solutions are being suggested to improve the adaptability of enterprise systems, including service-oriented architectures, model-driven architectures, and reflective architectures. In this paper, we propose a timeless way of building enterprise systems that employs a reflective architecture with integrated Resource-Event-Agent (REA) enterprise ontology specifications. We show how the explicit recording of enterprise schema descriptions results in enterprise systems with increased adaptability. In addition, we demonstrate how explicitly recorded ontological specifications can further increase application reusability. We validate our research with a prototype system.
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Roşu, Marius, and George Drăgoi. "VPN solutions and network monitoring to support virtual teams work in virtual enterprises." Computer Science and Information Systems 8, no. 1 (2011): 1–26. http://dx.doi.org/10.2298/csis100127033r.

Повний текст джерела
Анотація:
In order to be competitive enterprises continuously implement ICT strategies & architectures to improve manufacture, research, products quality, sales, services and costs control. All large enterprises have a local area network, a virtual private network, an Intranet and Internet, servers and workstations for operations, administration and management working together for the same objective: profits. The virtual enterprise and the virtual team?s concepts are discussed in this article. This work analyzes the network architecture for geographically dispersed enterprises (seen as virtual enterprises) as support for virtual project development by virtual teams work. In addition, the paper presents an enterprise networks monitoring solution using open source software (OSS).
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Lankhorst, M. M., H. A. Proper, and H. Jonkers. "The Anatomy of the ArchiMate Language." International Journal of Information System Modeling and Design 1, no. 1 (January 2010): 1–32. http://dx.doi.org/10.4018/jismd.2010092301.

Повний текст джерела
Анотація:
In current business practice, an integrated approach to business and IT is indispensable. In many enterprises, however, such an integrated view of the entire enterprise is still far from reality. To deal with these challenges, an integrated view of the enterprise is needed, enabling impact/change analysis covering all relevant aspects. This need sparked the development of the ArchiMate language, which was developed with the explicit intention of becoming an open standard, and as such has been designed such that it is extendable while still maintaining a clear and orthogonal structure. This article is concerned with documenting some of the key structures and design principles underlying the ArchiMate language. ArchiMate is designed as an architecture description language (ADL) for enterprise architectures. The authors will start by discussing the challenges facing the design of an architecture description language. Consequently we discuss how the design principles of the ArchiMate language aim to tackle these challenges. They then continue with a discussion of the modelling concepts needed. In this, we make a distinction between concepts needed to model domains in general, the modelling of dynamic systems, and the modelling of enterprise architectures.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Chalmeta, Ricardo, Christina Campos, and Reyes Grangel. "References architectures for enterprise integration." Journal of Systems and Software 57, no. 3 (July 2001): 175–91. http://dx.doi.org/10.1016/s0164-1212(01)00008-5.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Erder, M., and P. Pureur. "Transitional architectures for enterprise evolution." IT Professional 8, no. 3 (January 2006): 10–17. http://dx.doi.org/10.1109/mitp.2006.77.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

HOOGERVORST, JAN. "ENTERPRISE ARCHITECTURE: ENABLING INTEGRATION, AGILITY AND CHANGE." International Journal of Cooperative Information Systems 13, no. 03 (September 2004): 213–33. http://dx.doi.org/10.1142/s021884300400095x.

Повний текст джерела
Анотація:
Three core imperatives are essential for modern businesses and organizations: seamless integration of customer and operational processes, agility, and the ability to change. These imperatives are relevant in view of successfully executing strategic choices, but all too often not satisfied. Businesses and organizations are complex adaptive socio-technical systems and can be viewed from two fundamentally different perspectives: the functional (black-box) perspective and the constructional (white-box) perspective. Management and governance of businesses and organizations regard the functional, black-box perspective, which is inherently ill-suited for addressing the imperatives mentioned. It will be argued that establishing system integration, agility and change requires a focus on the system's design, hence necessitates the constructional perspective. The concept of architecture is considered fundamental for operationalizing the constructional perspective. Next to the more familiar notion of technology architecture, the concepts of business, organizational and information architecture are formally introduced and elucidated. Various domains within these architectures will be highlighted, whereby the importance of coherence and consistency is stressed, especially in view of the ability to change. Collectively, the four architectures are labeled Enterprise Architecture. Finally, enterprise architecture will be positioned as a crucial means for linking strategy development and execution.
Стилі APA, Harvard, Vancouver, ISO та ін.
11

Ilin, Igor V., Anastasia I. Levina, Alissa S. Dubgorn, and Alain Abran. "Investment Models for Enterprise Architecture (EA) and IT Architecture Projects within the Open Innovation Concept." Journal of Open Innovation: Technology, Market, and Complexity 7, no. 1 (February 20, 2021): 69. http://dx.doi.org/10.3390/joitmc7010069.

Повний текст джерела
Анотація:
Information technologies (IT) architecture and infrastructure is a significant cost item, especially for enterprises with complex production infrastructure and equipment that require automated and digital devices to collect and process primary data on technological and production processes. Most investment models for enterprise-wide development projects usually do not take into account the automation’s costs, including the design and implementation of information systems. The Enterprise Architecture (EA) paradigm has been proposed to bridge the gap between the business and the IT sector. The study aims to develop investment models for projects for the implementation and development of EA solutions, including IT architectures that eliminate the shortcomings of existing approaches. The research methodology is based on the analysis of published approaches to investment models for projects creating and developing EA, IT architectures with the identification of their advantages and limitations, and on the analysis of IT investment assessment practices in Russian infrastructure-intensive companies. As a result, investment and appraisal models are proposed that have advantages associated with the ability to calculate the effect of an integrated approach to the implementation of IT solutions, a more accurate calculation of an investment project cost by taking into account the IT system’s cost, a reduction in the investment cycle of development and implementation of architectural solutions, including physical and IT component.
Стилі APA, Harvard, Vancouver, ISO та ін.
12

Chung, Lawrence, and Nary Subramanian. "Bridging the gap between enterprise architectures and software architectures." Science of Computer Programming 66, no. 1 (April 2007): 1–3. http://dx.doi.org/10.1016/j.scico.2006.12.001.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
13

GOIKOETXEA, AMBROSE. "A MATHEMATICAL FRAMEWORK FOR ENTERPRISE ARCHITECTURE REPRESENTATION AND DESIGN." International Journal of Information Technology & Decision Making 03, no. 01 (March 2004): 5–32. http://dx.doi.org/10.1142/s0219622004000623.

Повний текст джерела
Анотація:
This paper presents a new mathematical framework for the representation and design of enterprise information architectures (EIA), also known as simply enterprise architectures (EA). Set theory is used to represent an EA as an 8-tuple consisting of a set of requirements, a set of business processes, a set of business systems, a set of data elements, a set of applications, a set of technologies, a set of constraints and business rules, and a set of architectural metrics and their values. These sets are then used to represent their respective architectural views, i.e. the Business Process Architectural View, the Business Systems Architectural View, etc. Next, it is shown that these multiple architectural views are all subsets of the same design point in the resource space. Design considerations leading to a Pareto efficient design point are discussed. Finally, the concept of Pareto design optimality is illustrated with one example in aircraft design and one example in database design.
Стилі APA, Harvard, Vancouver, ISO та ін.
14

Zhou, Zhengshu, Qiang Zhi, Shuji Morisaki, and Shuichiro Yamamoto. "IMAF." International Journal of Enterprise Information Systems 16, no. 1 (January 2020): 31–52. http://dx.doi.org/10.4018/ijeis.2020010102.

Повний текст джерела
Анотація:
Information technology has been used as a solution for improving productivity and service quality by enterprises, and software systematization supported by information technology has increasingly become the foundation for enterprise service. Innovation towards enterprise architecture improvement is usually necessary to provide high-quality service and create new value. This paper proposes a methodology aiming at stimulating innovation by evaluating the value provided by software system while visualizing the enterprise architectures. In this paper, the constituents of traditional business modeling methods are analyzed and integrated. Next, an innovation methodology based on ArchiMate framework is described and the detailed steps are defined. To evaluate the effectiveness of this proposed method, a case study on a Japanese convenience store information system is conducted and a controlled experiment is carried out.
Стилі APA, Harvard, Vancouver, ISO та ін.
15

Iliescu, Dragoș, Ion Diaconu, Ion Mateias, and Marian Gheorghe. "Organisational Architectures Modelling." Applied Mechanics and Materials 760 (May 2015): 665–70. http://dx.doi.org/10.4028/www.scientific.net/amm.760.665.

Повний текст джерела
Анотація:
The Virtual Organisation and Enterprise Modelling have become important topics starting with the mid 1990’s. This relevance comes from the positive combined effects expected by a business process reengineering and the particularities of the virtual organizations that fit very well to market challenges. A more advanced specialization, often found in the virtual organisations, gives a plus in terms of efficiency and productivity by an optimized business process. A particular well developed domain, for such type of organisations, is the informational system that can be seen as foundation for the business process reengineering. The paper presents relevant data and results for organisation architecture modelling. The architecture referred herein apply to enterprise and virtual organisation too, meaning that the improvements obtained by applying the business process reengineering for enterprise, can be foreseen, even with amplified effects, in the case of a virtual organisation.
Стилі APA, Harvard, Vancouver, ISO та ін.
16

Williams, Theodore J. "Development of Generic Enterprise Reference Architectures and Enterprise Integration Methodologies." IFAC Proceedings Volumes 27, no. 4 (June 1994): 27–30. http://dx.doi.org/10.1016/s1474-6670(17)45995-7.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
17

Pettersen, Lene. "Experiencing Virtual Social Enterprise Media Architectures." Nordic Journal of Science and Technology Studies 4, no. 2 (December 29, 2016): 29. http://dx.doi.org/10.5324/njsts.v4i2.2183.

Повний текст джерела
Анотація:
<p>This article addresses knowledge professionals’ experiences of being in and using social enterprise media, which is characterized by a social, people-centric, dynamic and non-hierarchical information architecture. Rather than studying the social enterprise media from a typical STS-perspective in terms of ‘scripts’, ‘antiprogram’, or as ‘configuring design processes based on the user’, the paper direct its analytical lens to the users’ experiences, practices and routines when they are making sense of the virtual space in social enterprise media. As theoretical framework, unexplored corners of structuration theory where Giddens (1979, 1984) discusses spatiality (place) and temporality (time), where Giddens is inspired by the philosopher Wittgenstein (1972), the micro-sociologist Goffman (1959), and the time-geographer Hägerstrand (1975, 1978) are employed. With this approach, dynamic social processes are included in our studies of technology. Qualitative insights from a comprehensive and longitudinal case study of a multinational organization with entities in Europe, North Africa and the Middle East were used in order to get an in-depth understanding of how people experienced using virtual and social architectural spaces. The findings show that the social architecture and people-centric model in the virtual space in social enterprise media does not provide an intuitive spatial sense, nor does it provide logics that correspond with known and familiar logics or established communication and interaction practices among employees. Key features in social enterprise media (e.g., transparency) collide with how space is constructed in the physical world and with the logics at play in offline conversations and social interactions (e.g. turn-taking in conversations or the opportunity to withdraw from conversations). </p>
Стилі APA, Harvard, Vancouver, ISO та ін.
18

Dube, Mahesh R., and Shantanu K. Dixit. "Comprehensive Measurement Framework for Enterprise Architectures." International Journal of Computer Science and Information Technology 3, no. 4 (August 30, 2011): 71–92. http://dx.doi.org/10.5121/ijcsit.2011.3406.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
19

Melling, Wesley P. "Enterprise information architectures—they're finally changing." ACM SIGMOD Record 23, no. 2 (June 1994): 493–504. http://dx.doi.org/10.1145/191843.191948.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
20

Vernadat, F. B. "INTEROPERABLE ENTERPRISE SYSTEMS: ARCHITECTURES AND METHODS." IFAC Proceedings Volumes 39, no. 3 (2006): 13–20. http://dx.doi.org/10.3182/20060517-3-fr-2903.00010.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
21

Astri, Lola Yorita, and Ford Lumban Gaol. "INFORMATION SYSTEM STRATEGIC PLANNING WITH ENTERPRISE ARCHITECTURE PLANNING." CommIT (Communication and Information Technology) Journal 7, no. 1 (May 30, 2013): 23. http://dx.doi.org/10.21512/commit.v7i1.580.

Повний текст джерела
Анотація:
An integrated information system is needed in an enterprise to support businessprocesses run by an enterprise. Therefore, to develop information system can use enterprisearchitecture approach which can define strategic planning of enterprise information system. SMPNegeri 1 Jambi can be viewed as an enterprise because there are entities that should be managedthrough an integrated information system. Since there has been no unification of different elementsin a unity yet, enterprise architecture model using Enterprise Architecture Planning (EAP) isneeded which will obtain strategic planning of enterprise information system in SMP Negeri 1Jambi. The goal of strategic planning of information system with Enterprise Architecture Planning(EAP) is to define primary activities run by SMP Negeri 1 Jambi and support activities supportingprimary activities. They can be used as a basis for making data architecture which is the entities ofapplication architecture. At last, technology architecture is designed to describe technology neededto provide environment for data application. The plan of implementation is the activity plan madeto implemented architectures by enterprise.
Стилі APA, Harvard, Vancouver, ISO та ін.
22

Saluky, Saluky. "Pengembangan Blueprint Sistem Informasi Akademik Terintegrasi (Studi Kasus : IAIN Syekh Nurjati Cirebon)." ITEJ (Information Technology Engineering Journals) 1, no. 2 (December 5, 2016): 19–33. http://dx.doi.org/10.24235/itej.v1i2.8.

Повний текст джерела
Анотація:
The information system is used to present information for management decision making and running the activities involved in an organization. Blue Print of information technology essentially provides college's strategic plan to implement and build information systems in college which is a derivative of the Business Plan colleges where individual companies generally have a strategic plan. This study aims to create an enterprise architecture for IAIN Syekh Nurjati Cirebon, in the form of IT blueprint that could later be used by the enterprise to achieve its vision and mission. The planning is done by utilizing EAP methodology (Enterprise Architecture Planning). The means used is through the process of defining the enterprise architecture in the form of data architecture, application architecture, technology architecture, business architecture, as well as integration architecture. Once the rest of the enterprise architecture is defined, the result made implementation plan is a plan for the implementation of enterprise architectures in the future as a blueprint for the information technology IAIN Sheikh Nurjati Cirebon.
Стилі APA, Harvard, Vancouver, ISO та ін.
23

Assimakopoulos, Nikitas A., and Anastasios N. Riggas. "Designing a Virtual Enterprise Architecture using Structured System Dynamics." Human Systems Management 25, no. 1 (March 6, 2006): 13–29. http://dx.doi.org/10.3233/hsm-2006-25102.

Повний текст джерела
Анотація:
The starting point for establishing a Virtual Enterprise is a set of existing enterprises which might contribute with some of their functionalities (core competencies) to the formation of the virtual entity. The most important issue, in this formation, is the rapid integration of the business processes of the participating companies. The architecture of the VE must assist companies desiring to enter into a virtual relationship by defining the functions and interfaces of critical business processes, thus allowing for a more rapid and efficient integration of the expertise which will be contributed by each partner in the virtual enterprise. While the integration of computer and communication technologies are no doubt critical issues, the successful attainment of the business goals of the virtual enterprise often depends on its ability to align the business processes and practices of partner enterprises. Focus of this paper, is the presentation of Structured System Dynamics (SSPS) multi-methodology for the design and the evaluation of a Virtual Enterprise Architecture. SSPS uses Systems Thinking and System Dynamics principles as launch pad for its approach. The Systemic Methodologies of Problem Structuring Methodology (PSM) and SAST are also integrated in this new Multi-Methodology. SSPS is a new practical and scientific tool in designing and evaluating a VE architecture providing the ability to determine the impact, reliability, success of the Architectures' models created, refine them and identify potential process improvements. A framework for the rapid and efficient integration of the business processes of the participating companies in the virtual enterprise is provided. For this multi-methodology, a real-life application is also presented for a Virtual Enterprise that constructs Wireless Payment Mechanisms.
Стилі APA, Harvard, Vancouver, ISO та ін.
24

Goerzig, David, and Thomas Bauernhansl. "Enterprise Architectures for the Digital Transformation in Small and Medium-sized Enterprises." Procedia CIRP 67 (2018): 540–45. http://dx.doi.org/10.1016/j.procir.2017.12.257.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
25

Kotusev, Svyatoslav. "Enterprise architecture and enterprise architecture artifacts: Questioning the old concept in light of new findings." Journal of Information Technology 34, no. 2 (February 6, 2019): 102–28. http://dx.doi.org/10.1177/0268396218816273.

Повний текст джерела
Анотація:
Enterprise architecture is a description of an enterprise from an integrated business and IT perspective intended to bridge the communication gap between business and IT stakeholders and improve business and IT alignment. Enterprise architecture consists of multiple different artifacts providing certain views of an organization and the available enterprise architecture literature offers a number of comprehensive lists of artifacts that can be used as part of an enterprise architecture practice. However, these lists of enterprise architecture artifacts were never validated empirically and the practical usage of different artifacts still remains largely unexplored. Based on a comprehensive empirical analysis of enterprise architecture artifacts used in 27 diverse organizations, this study identifies the list of 24 common artifacts that proved useful in practice and describes in detail their usage and purpose. Although this study does not attempt to theorize on the findings, it makes a significant empirical contribution to the enterprise architecture discipline. In particular, this study (1) provides the first consistent list of enterprise architecture artifacts that actually proved useful in organizations, (2) offers the first available systematic description of their usage, (3) questions the common view of enterprise architecture as a set of business, information, applications and technology architectures and (4) questions the widely accepted conceptualization of enterprise architecture as a set of the current state, future state and transition roadmap. This study provides compelling empirical evidence in favor of reconceptualizing enterprise architecture and calls for further research in this direction.
Стилі APA, Harvard, Vancouver, ISO та ін.
26

Mertins, K., and R. Jochem. "Architectures, methods and tools for enterprise engineering." International Journal of Production Economics 98, no. 2 (November 2005): 179–88. http://dx.doi.org/10.1016/j.ijpe.2004.05.024.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
27

Nezlek, George S., Hemant K. Jain, and Derek L. Nazareth. "An integrated approach to enterprise computing architectures." Communications of the ACM 42, no. 11 (November 1999): 82–90. http://dx.doi.org/10.1145/319382.319399.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
28

Handley, Holly A. H., Evelyn Vance, and Daniel Heimerdinger. "A Human Resource Framework for Enterprise Architectures." IEEE Engineering Management Review 47, no. 1 (March 2019): 86–93. http://dx.doi.org/10.1109/emr.2019.2898629.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
29

Armour, F. J., S. H. Kaisler, and S. Y. Liu. "A big-picture look at enterprise architectures." IT Professional 1, no. 1 (January 1999): 35–42. http://dx.doi.org/10.1109/6294.774792.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
30

Hussain, Tahani H., Paulvanna N. Marimuthu, and Sami J. Habib. "Exploration of Storage Architectures for Enterprise Network." Computer Journal 61, no. 2 (May 24, 2017): 233–47. http://dx.doi.org/10.1093/comjnl/bxx054.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
31

Toh, K. T. K. "The realization of reference enterprise modelling architectures." International Journal of Computer Integrated Manufacturing 12, no. 5 (January 1999): 403–17. http://dx.doi.org/10.1080/095119299130146.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
32

Kim, J. H., and E. ‐S Ryu. "Distributed stochastic buffering for enterprise WLAN architectures." Electronics Letters 49, no. 4 (February 2013): 302–4. http://dx.doi.org/10.1049/el.2012.3837.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
33

Gonzalez-Lopez, Fernanda, and Guillermo Bustos. "Integration of Business Process Architectures within Enterprise Architecture Approaches: A Literature Review." Engineering Management Journal 31, no. 2 (January 24, 2019): 127–40. http://dx.doi.org/10.1080/10429247.2018.1522565.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
34

Simpson, William R., and Kevin E. Foltz. "Maintaining Zero Trust With Federation." International Journal of Emerging Technology and Advanced Engineering 11, no. 5 (May 20, 2021): 17–32. http://dx.doi.org/10.46338/ijetae0521_03.

Повний текст джерела
Анотація:
Federated activity presents a challenge for enterprises with high-level security architectures. Federation involves information sharing among services and with working partners, coalition partners, first responders, and other organizations. Federation may be unilateral or bilateral with similar or dissimilar information-sharing goals. Strong internal security, including zero trust controls, often do not extend cleanly across enterprise boundaries, potentially leading to insecure shortcuts and workarounds that can become the rule instead of the exception. This paper presents methods for an enterprise to extend its zero trust security policies to include federation partners. It applies to federation partners that support the same security policies with compatible standards and services and to partners that provide a similar but incompatible security framework, a subset of required security services, or no security services. The partner organization may be fully trusted, partially trusted, or untrusted. Even for trusted partners, the services may not meet required security standards. Our solution combines selected partner security services, internal services, derived credentials, delegated authorities, and supplemental services to form the federation security architecture based on zero trust premises to the maximum extent. This paper uses the Zero Trust for Enterprise (ZTE) architecture as the starting point for a secure enterprise and addresses the challenge of extending this model to federate with different types of partners. We review the security approach, the security properties, and several options for an enterprise to maintain the ZTE security properties while enabling federated sharing with other enterprises that have different capabilities and levels of trust
Стилі APA, Harvard, Vancouver, ISO та ін.
35

Pisoni, Galena, Bálint Molnár, and Ádám Tarcsi. "Data Science for Finance: Best-Suited Methods and Enterprise Architectures." Applied System Innovation 4, no. 3 (September 18, 2021): 69. http://dx.doi.org/10.3390/asi4030069.

Повний текст джерела
Анотація:
We live in an era of big data. Large volumes of complex and difficult-to-analyze data exist in a variety of industries, including the financial sector. In this paper, we investigate the role of big data in enterprise and technology architectures for financial services. We followed a two-step qualitative process for this. First, using a qualitative literature review and desk research, we analyzed and present the data science tools and methods financial companies use; second, we used case studies to showcase the de facto standard enterprise architecture for financial companies and examined how the data lakes and data warehouses play a central role in a data-driven financial company. We additionally discuss the role of knowledge management and the customer in the implementation of such an enterprise architecture in a financial company. The emerging technological approaches offer opportunities for finance companies to plan and develop additional services as presented in this paper.
Стилі APA, Harvard, Vancouver, ISO та ін.
36

Alshammari, Bandar M. "Security Assessment Model for Database Relational Designs." Journal of Medical Imaging and Health Informatics 9, no. 6 (August 1, 2019): 1171–80. http://dx.doi.org/10.1166/jmihi.2019.2715.

Повний текст джерела
Анотація:
The increasing number of data breaches has led many organizations to focus on securing their IT infrastructures and application architectures. However, the main causes of many of the latest attacks are not associated with these two architectures. The damage caused by most of the recent attacks could have been minimized if more attention was given to enhancing the security of all components of the database architecture. The existing enterprise database architecture frameworks do not consider this issue a priority; hence, it has received minimal attention. The enterprise database architecture is the most important architecture because it is responsible for defining how all types of data, whether security-critical or not, are stored and accessed. This paper focuses on addressing the lack of a complete solution to help enterprise system architects to address the security of their organizations from early stages. The novelty of this approach is that it specifies how to modify the required artifacts by the enterprise database architecture to address security-critical data. The approach also defines a number of security measurements that help enterprise architects in measuring the security of the organization database based on those artifacts. These metrics are developed based on the results of a cybersecurity experiment conducted on 100 randomly selected open-source websites. The paper's contributions also consist of the definition of a number of security refactoring rules that specify how to modify current enterprise databases to make them more secure. This paper uses an existing relational diagram for a health clinic database to illustrate the application of the model to an existing database. The validity and applicability of these metrics and refactoring rules are proved using an experiment conducted on a number of security-related databases.
Стилі APA, Harvard, Vancouver, ISO та ін.
37

Lee, G. J., R. Venter, and B. Bates. "Enterprise-based HIV/AIDS strategies: Integration through organisational architecture." South African Journal of Business Management 35, no. 3 (September 30, 2004): 13–22. http://dx.doi.org/10.4102/sajbm.v35i3.658.

Повний текст джерела
Анотація:
The management of the HIV/AIDS pandemic has clearly become a core strategic issue for many organisations, especially in the developing world. However the policies and practices of an HIV/AIDS programme are often less than integrated and strategic in nature, with organisations frequently subscribing to discrete and isolated interventions in imitation of others, or at best instituting a stand-alone policy. One management tool that may serve to help in drawing together and focusing efforts in this regard is an organisational architecture. Organisational architecture has been suggested as an holistic management tool for the delivery of organisational strategies. This article accordingly reviews varied literature on organisational architectures, and then shows how various HIV/AIDS policies and practices might fit into such an architecture. Organisational architecture could be used effectively to organise, integrate and focus the information and efforts connected to the policies and practices surrounding a corporate HIV/AIDS effort.
Стилі APA, Harvard, Vancouver, ISO та ін.
38

R. Simpson, William, and Kevin E. Foltz. "Resolving Network Defense Conflicts with Zero Trust Architectures and Other End-to-End Paradigms." International Journal of Network Security & Its Applications 13, no. 1 (January 31, 2021): 1–20. http://dx.doi.org/10.5121/ijnsa.2021.13101.

Повний текст джерела
Анотація:
Network defense implies a comprehensive set of software tools to preclude malicious entities from conducting activities such as exfiltration of data, theft of credentials, blocking of services and other nefarious activities. For most enterprises at this time, that defense builds upon a clear concept of the fortress approach. Many of the requirements are based on inspection and reporting prior to delivery of the communication to the intended target. These inspections require decryption of packets and this implies that the defensive suite either impersonates the requestor, or has access to the private cryptographic keysof the servers that are the target of communication. This is in contrast to an end-to-end paradigm where known good entities can communicate directly and no other entity has access to the content unless that content is provided to them. There are many new processes that require end-to-end encrypted communication, including distributed computing, endpoint architectures, and zero trust architectures and enterprise level security. In an end-to-end paradigm, the keys used for authentication, confidentiality, and integrity reside only with the endpoints. This paper examines a formulation that allows unbroken communication, while meeting the inspection and reporting requirements of a network defense. This work is part of a broader security architecture termed Enterprise Level Security (ELS)framework.
Стилі APA, Harvard, Vancouver, ISO та ін.
39

Janssen, Marijn, and Bram Klievink. "Can enterprise architectures reduce failure in development projects?" Transforming Government: People, Process and Policy 6, no. 1 (March 16, 2012): 27–40. http://dx.doi.org/10.1108/17506161211214804.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
40

Veasey, Philip W. "Use of enterprise architectures in managing strategic change." Business Process Management Journal 7, no. 5 (December 2001): 420–36. http://dx.doi.org/10.1108/14637150110406803.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
41

Soegoto, E. S., S. I. Fauzi, and T. Valentina. "Relationship between enterprise architectures planning and information system." Journal of Physics: Conference Series 1402 (December 2019): 066078. http://dx.doi.org/10.1088/1742-6596/1402/6/066078.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
42

Black, J., R. Gottschalk, T. Lococo, and D. Moore. "Architectures and technologies for the globally integrated enterprise." IBM Journal of Research and Development 53, no. 6 (November 2009): 1:1–1:14. http://dx.doi.org/10.1147/jrd.2009.5429029.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
43

Schwer, Karlheinz, Christian Hitz, Robin Wyss, Dominik Wirz, and Clemente Minonne. "Digital maturity variables and their impact on the enterprise architecture layers." Problems and Perspectives in Management 16, no. 4 (November 2, 2018): 141–54. http://dx.doi.org/10.21511/ppm.16(4).2018.13.

Повний текст джерела
Анотація:
This study examines the variables of digital maturity of companies. The framework for enterprise architectures Archimate 3.0 is used to compare the variables. The vari¬ables are assigned to the six layers of architecture: Strategy, Business Environment, Applications, Technology, Physical and Implementation and Migration. On the basis of a literature overview, 15 “digital maturity models” with a total of 147 variables are analyzed. The databases Scopus, EBSCO – Business Source Premier and ProQuest are used for this purpose.The results of the work will help researchers and managers to identify which digitiza¬tion variables affect the different layers of the company. This enables researchers or managers to use the right model for a specific purpose or to create a new model from a combination of existing models for the entire company or just one architectural layer.On the basis of a more precise assessment of the digital maturity of a company, better actions can be derived. This work is important for companies, as the digitization of enterprises and markets changed similarly to the invention of the steam engine did. Websites, sensors, mobile devices, apps, etc. are combined into new digital products and services. The competitors in the market have to adapt. If this is not done, they will increasingly disappear.Finally, the authors suggests a conclusion about the current situation regarding the measurement of digital maturity in companies and show in which areas further studies could be carried out.
Стилі APA, Harvard, Vancouver, ISO та ін.
44

Carl, Joseph W., and John M. Colombi. "5.1.2 SEVEN SECRET TIPS TO BUILD INTELLIGENT ENTERPRISE ARCHITECTURES." INCOSE International Symposium 17, no. 1 (June 2007): 803–14. http://dx.doi.org/10.1002/j.2334-5837.2007.tb02913.x.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
45

Baghdadi, Youcef. "Enterprise interactions: conceptualisation, ontology, and standard architectures and services." International Journal of Services and Standards 12, no. 2 (2018): 104. http://dx.doi.org/10.1504/ijss.2018.091841.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
46

Baghdadi, Youcef. "Enterprise interactions: conceptualisation, ontology, and standard architectures and services." International Journal of Services and Standards 12, no. 2 (2018): 104. http://dx.doi.org/10.1504/ijss.2018.10012981.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
47

Brebner, Paul C. "Real-world performance modelling of enterprise service oriented architectures." ACM SIGMETRICS Performance Evaluation Review 39, no. 3 (December 21, 2011): 12. http://dx.doi.org/10.1145/2160803.2160813.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
48

Chae, Heekwon, Younghwan Choi, and Kwangsoo Kim. "Component-based modeling of enterprise architectures for collaborative manufacturing." International Journal of Advanced Manufacturing Technology 34, no. 5-6 (May 30, 2006): 605–16. http://dx.doi.org/10.1007/s00170-006-0620-5.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
49

Kang, Dongwoo, Jeongsoo Lee, and Kwangsoo Kim. "Alignment of Business Enterprise Architectures using fact-based ontologies." Expert Systems with Applications 37, no. 4 (April 2010): 3274–83. http://dx.doi.org/10.1016/j.eswa.2009.09.052.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
50

Dumitrache, Caramihai, Moisescu, Sacala, Vladareanu, and Repta. "A Perceptive Interface for Intelligent Cyber Enterprises." Sensors 19, no. 20 (October 12, 2019): 4422. http://dx.doi.org/10.3390/s19204422.

Повний текст джерела
Анотація:
Large scale, complex, networked enterprises, as may be considered (trans)national energy systems, multi-national manufacturing enterprises, smart cities a.s.o. are structures that can be characterized as systems of systems (SoS) and, as such, require specific modelling paradigms and control architectures to ensure their successful running. Their main characteristic is the necessity of solving practically one-of-a-kind problems with respect to the external context and internal configuration, thus dealing with dynamically evolving flows of data and information. The paper introduces the concept of intelligent cyber-enterprise, as an integrating paradigm that uses information and knowledge dynamics, in order to model and control SoS, especially focusing on the importance of appropriately adapt external and internal perception of an enterprise through a new generation of sensorial systems—the perceptive interfaces. The authors analyze sensing and perception in relation to intelligent cyber enterprise model and propose an implementation for a perceptive system interface.
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

До бібліографії