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

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

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

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

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

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

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

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

1

PAHL, CLAUS, YAOLING ZHU, and VERONICA GACITUA-DECAR. "A TEMPLATE-DRIVEN APPROACH FOR MAINTAINABLE SERVICE-ORIENTED INFORMATION SYSTEMS INTEGRATION." International Journal of Software Engineering and Knowledge Engineering 19, no. 07 (November 2009): 889–912. http://dx.doi.org/10.1142/s0218194009004465.

Повний текст джерела
Анотація:
Service-oriented architecture (SOA) is currently the predominant software integration framework. Web services provide the predominant platform for SOA. SOA as an integration architecture solution supports a range of application scenarios. We present a solution for the integration of business information systems based on SOA and Web services. We discuss maintainability requirements in relation to information-specific integration and architecture aspects. A template-based approach based on modular and declarative transformation rules and architectural styles and patterns defines our solution to the maintainability problem of integration architectures.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Liu, Chang An. "Research on Eco-Architecture-Oriented Architectural Education." Applied Mechanics and Materials 357-360 (August 2013): 455–58. http://dx.doi.org/10.4028/www.scientific.net/amm.357-360.455.

Повний текст джерела
Анотація:
This paper analyses the status of the ecological architecture education nowadays and describes the necessity of embedding ecological and energy-saving technologies in traditional architectural education. Then the author introduces the teaching plan and practice in the newly started Building Integrated Solar System professional orientation in Shandong Jianzhu University and explores the possibility of establishing the ecological-featured architecture professional orientation in China.
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Neveu, Marc J. "Architecture Oriented Otherwise." Journal of Architectural Education 64, no. 1 (September 2010): 158–59. http://dx.doi.org/10.1111/j.1531-314x.2010.01116.x.

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

Sefika, Mohlalefi, Aamod Sane, and Roy H. Campbell. "Architecture-oriented visualization." ACM SIGPLAN Notices 31, no. 10 (October 1996): 389–405. http://dx.doi.org/10.1145/236338.236380.

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

Laskey, Kathryn B., and Kenneth Laskey. "Service oriented architecture." Wiley Interdisciplinary Reviews: Computational Statistics 1, no. 1 (July 2009): 101–5. http://dx.doi.org/10.1002/wics.8.

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

Jiang, Weiyu, Bingyang Liu, Chuang Wang, and Xue Yang. "Security-Oriented Network Architecture." Security and Communication Networks 2021 (May 26, 2021): 1–16. http://dx.doi.org/10.1155/2021/6694650.

Повний текст джерела
Анотація:
Internet benefits societies by constantly connecting devices and transmitting data across the world. However, due to the lack of architectural built-in security, the pervasive network attacks faced by the entire information technology are considered to be unending and inevitable. As Internet evolves, security issues are regularly fixed according to a patch-like strategy. Nevertheless, the patch-like strategy generally results in arms races and passive situations, leaving an endless lag in both existing and emerging attacking surface. In this paper, we present NAIS (Network Architecture with Intrinsic Security)—a network architecture towards trustworthiness and security. By solving stubborn security issues like IP spoofing, MITM (man-in-the-middle) attacks, and DDoS (distributed denial of service) attacks at architectural level, NAIS is envisioned to provide the most secure end-to-end communication in the network layer. This paper first presents a comprehensive analysis of network security at Internet range. Then, the system design of NAIS is elaborated with particular design philosophies and four security techniques. Such philosophies and techniques intertwine internally and contribute to a communication environment with authenticity, privacy, accountability, confidentiality, integrity, and availability. Finally, we evaluate the security functionalities on the packet forwarding performance, demonstrating that NAIS can efficiently provide security and trustworthiness in Internet end-to-end communication.
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Abusharekh, Ashraf M., Lawrence E. Gloss, and Alexander H. Levis. "Evaluation of Service Oriented Architecture-based federated architectures." Systems Engineering 14, no. 1 (January 21, 2011): 56–72. http://dx.doi.org/10.1002/sys.20162.

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

LÓPEZ-SANZ, MARCOS, JUAN MANUEL VARA, ESPERANZA MARCOS, and CARLOS E. CUESTA. "A MODEL-DRIVEN APPROACH TO WEAVE ARCHITECTURAL STYLES INTO SERVICE-ORIENTED ARCHITECTURES." International Journal of Cooperative Information Systems 20, no. 02 (June 2011): 201–20. http://dx.doi.org/10.1142/s0218843011002201.

Повний текст джерела
Анотація:
Model-driven development is recognized as one of the most promising approaches in software engineering. Recent research in the area highlights the importance of using an explicit architectural model in this context. Since service-oriented architectures have also demonstrated to be adequate to overcome current software needs, the idea of using the model-driven approach to generate service-oriented architectural models has successfully flourished in the last years. However, the emphasis on the Service-Oriented Computing (SOC) paradigm has led to the design of architectures lacking some desirable features. Knowing the benefits provided by architectural styles, we have found that their use can help us to overcome those needs. Our goal is to obtain a service-oriented model which satisfies the requirements of the concrete architecture and complies with the constraints and vocabulary defined for a specific architectural style. To achieve this, here, we propose to use a weaving model which merges the concrete architectural model with a model of the architectural style of choice.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Bygstad, Bendik, Tor-Morten Grønli, Helge Bergh, and Gheorghita Ghinea. "Business Innovation and Service Oriented Architecture." International Journal of Information Technologies and Systems Approach 4, no. 1 (January 2011): 67–78. http://dx.doi.org/10.4018/jitsa.2011010105.

Повний текст джерела
Анотація:
Recent research suggests that a strong link exists between business innovation and service oriented IT architectures: modern IT architecture enables business to quickly create new services. However, the relationship between IT capabilities and business performance is not always straightforward. How does SOA support fast innovation in practice, and under which conditions is it effective? In this paper, the authors investigate these issues and ask: How can a SOA architecture like the Enterprise Service Bus support business innovation? This paper investigates this question through a case study at an airline company. Analyzing the relationship between innovation and IT architecture in the company over time, the authors offer the following conclusion: ESB gives strong support to business innovation, under two conditions. First, the implementation of ESB has to be comprehensive, that is, it should include the core processes of the business. Second, the top management (and partners) need to understand the principles of ESB.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Gebhard, Gernot, and Philipp Lucas. "OORS: An object-oriented rewrite system." Computer Science and Information Systems 4, no. 2 (2007): 2–26. http://dx.doi.org/10.2298/csis0702002g.

Повний текст джерела
Анотація:
Retargeting a compiler?s back end to a new architecture is a time-consuming process. This becomes an evident problem in the area of programmable graphics hardware (graphics processing units, GPUs) or embedded processors, where architectural changes are faster than elsewhere. We propose the object-oriented rewrite system OORS to overcome this problem. Using the OORS language, a compiler developer can express the code generation and optimization phase in terms of cost-annotated rewrite rules supporting complex non-linearmatching and replacing patterns. Retargetability is achieved by organizing rules into profiles, one for each supported target architecture. Featuring a rule and profile inheritance mechanism, OORS makes the reuse of existing specifications possible. This is an improvement regarding traditional approaches. Altogether OORS increases the maintainability of the compiler?s back end and thus both decreases the complexity and reduces the effort of the retargeting process. To show the potential of this approach, we have implemented a code generation and a code optimization pattern matcher supporting different target architectures using the OORS language and introduced them in a compiler of a programming language for CPUs and GPUs.
Стилі APA, Harvard, Vancouver, ISO та ін.
11

Al-Qaysi, Qoutaiba, Said M. Easa, and Nouman Ali. "Proposed Canadian automated highway system architecture: object-oriented approach." Canadian Journal of Civil Engineering 30, no. 6 (December 1, 2003): 955–69. http://dx.doi.org/10.1139/l03-043.

Повний текст джерела
Анотація:
Recent advances in the fields of data communication and automated controls make the implementation of automated highway systems (AHSs) more possible. Currently, substantial research effort is being made on the design of intelligent transportation system (ITS) architectures in Europe, Japan, the United States, and Canada. These architectures, however, have major limitations inherit in the design methodology used. Most ITS developers use a process-oriented approach for the design of the architecture that reduces its quality attributes (stability and flexibility) to future changes. This paper presents an approach to implement object-oriented design methodology in the Canadian intelligent transportation system (C-ITS) architecture for AHS. It was also shown that the C-ITS architecture needs a backup communication system to be integrated within the C-ITS architecture. Such a backup system would aid the reliability of future transportation systems to be developed based on this architecture. The proposed C-ITS architecture promotes flexibility, stability, and communication and, as such, should be of interest to ITS developers and researchers.Key words: intelligent transportation systems, architecture, automated highways, object-oriented approach, backup communication.
Стилі APA, Harvard, Vancouver, ISO та ін.
12

Ciganek, Andrew P., and Marc N. Haines. "Service-Oriented Architecture Adoption." International Journal of Information Technology Project Management 1, no. 2 (April 2010): 1–15. http://dx.doi.org/10.4018/jitpm.2010040101.

Повний текст джерела
Анотація:
Service-oriented architecture (SOA) have been adopted by organizations in a wide variety of industries, however, best practices have still yet to mature. This article, which is part of a larger study on SOA, develops a normative decision model introducing key factors that influence the timing and approach of adopting a SOA. The decision model is based on the results of multiple case studies of organizations that had either employed or were considering implementing a service-oriented architecture project. The results indicate that there are four main areas an information technology (IT) manager needs to assess to determine when and how to move towards a SOA: the maturity of relevant standards, the technology gap, the organizational gap, and the nature of the benefits expected from a SOA. Analyzing these results suggest that differences in the business environment need to be considered in the decision of when and how an IT manager should pursue the move to a service-oriented architecture.
Стилі APA, Harvard, Vancouver, ISO та ін.
13

Hirayama, M. "VLSI oriented asynchronous architecture." ACM SIGARCH Computer Architecture News 14, no. 2 (May 1986): 290–96. http://dx.doi.org/10.1145/17356.17390.

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

Welke, R., R. Hirschheim, and A. Schwarz. "Service-Oriented Architecture Maturity." Computer 44, no. 2 (February 2011): 61–67. http://dx.doi.org/10.1109/mc.2011.56.

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

Hamada, Tomoyuki. "Human Oriented Production Architecture." Journal of the Society of Mechanical Engineers 95, no. 884 (1992): 620–23. http://dx.doi.org/10.1299/jsmemag.95.884_620.

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

Dally, William J., and James T. Kajiya. "An object oriented architecture." ACM SIGARCH Computer Architecture News 13, no. 3 (June 1985): 154–61. http://dx.doi.org/10.1145/327070.327151.

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

Francalanci, Chiara, and Vincenzo Piuri. "Designing Information Technology Architectures: A Cost-Oriented Methodology." Journal of Information Technology 14, no. 2 (June 1999): 181–92. http://dx.doi.org/10.1177/026839629901400207.

Повний текст джерела
Анотація:
This paper proposes a design methodology of information technology architectures tying organizational requirements to technical choices and costs. The primary goal is to provide a structured support for the selection of the minimum-cost architecture satisfying given organizational requirements. Previous empirical studies have attempted absolute cost comparisons of different architectural solutions, primarily relying on the expertise of practitioners and a priori beliefs, but have rarely taken into account the impact of organizational requirements on costs. Requirements are modelled as information processes, composed of tasks exchanging information and characterized by varying levels of computational complexity. Different architectural distributions of presentation, computation and data management applications are compared. The cost implications of organizational requirements for processing intensity, communication intensity and networking are analysed. The results show a relationship between structural features of information processes and architectural costs and indicate how architectural design should be based on organizational as well as technology considerations.
Стилі APA, Harvard, Vancouver, ISO та ін.
18

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 та ін.
19

Wagenhals, Lee W., and Alexander H. Levis. "Service Oriented Architectures, the DoD Architecture Framework 1.5, and Executable Architectures." Systems Engineering 12, no. 4 (September 2009): 312–43. http://dx.doi.org/10.1002/sys.20125.

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

Stal, M. "Using architectural patterns and blueprints for service-oriented architecture." IEEE Software 23, no. 2 (March 2006): 54–61. http://dx.doi.org/10.1109/ms.2006.60.

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

Levina, A. I., and D. A. Serov. "Model of an Architectural Solution for a Value-Oriented Utility Company." Economics and Management 26, no. 6 (August 25, 2020): 606–12. http://dx.doi.org/10.35854/1998-1627-2020-6-606-612.

Повний текст джерела
Анотація:
Current trends in the housing and utilities sector are associated with a value-oriented approach, which implies that the key aspect in designing a product or service is the value received by the consumer.Aim. The presented study aims to develop a model of an architectural solution for a utility company that implements a value-oriented approach to services by using technologies for collecting and analyzing personalized data.Tasks. The authors form the value proposition of a utility company (through the example of a water supply and disposal company), determine the role of data collection, transmission, processing, and analysis technologies in the implementation of this value proposition, and develop a model for an architectural solution for a value-oriented utility company.Methods. This study uses an architectural approach to the design of enterprise management systems.Results. The study proposes a model of an architectural solution for a value-oriented utility company that describes the interaction between the user and corporate architecture of value proposition implementation. This model serves as a basis for creating detailed requirements for the services of application architecture, data architecture, and technological architecture of the utility system.Conclusions. The architectural model of a utility company should make allowance for the requirements of compliance with the principles of value-oriented activity - from business services to IT systems and technological architecture. Personalized data collection is one of the most important conditions for the implementation of a value-oriented approach. A model for integrating data processing technologies in the architectural solution of a utility company will allow it to develop and implement the services necessary for value proposition implementation.
Стилі APA, Harvard, Vancouver, ISO та ін.
22

Mutiah, Nurul, and Ferdy Febriyanto. "Perancangan Arsitektur Enterprise FMIPA UNTAN Menggunakan Kerangka Kerja TOGAF Berbasis SOA." JURNAL SISTEM INFORMASI BISNIS 12, no. 2 (December 20, 2022): 116–23. http://dx.doi.org/10.21456/vol12iss2pp116-123.

Повний текст джерела
Анотація:
The research aims to develop an Enterprise Architecture from FMIPA UNTAN, this is based on the many individual information systems that have been developed by FMIPA UNTAN which are not integrated in data and technology. This situation results in overlapping data that can affect the effectiveness of decision making within the organization. The designed Enterprise Architecture implements the concept of service-oriented architecture in order to support the integration between the business layer and the organization's technology layer. To support the research, several concepts are used, such as TOGAF as a framework for developing Enterprise Architecture, Service Oriented Architecture as a supporter for integration of architectural layers, and Archimate and Business Process Modeling Notation as a modeling language used to create architectural artifacts. The stages of the research included problem identification, the Enterprise Architecture development process followed the stages of TOGAF ADM namely the preliminary phase, architectural vision, business architecture, information system architecture, technology architecture, and making an architecture implementation roadmap. The results of the development of Enterprise Architecture are architectural artifacts consisting of catalogs, matrices, and diagrams of business, information system, and technology architecture. Based on the design results, it is found that the Enterprise Service Bus concept in Service Oriented Architecture can be used to support application and data integration in organization, as well as the concept of service access can bridge the gap between the business layer and the technology layer.
Стилі APA, Harvard, Vancouver, ISO та ін.
23

Lavendelis, Egons, and Janis Bicans. "Multi-Agent and Service Oriented Architectures for Intelligent Tutoring System Development." Scientific Journal of Riga Technical University. Computer Sciences 44, no. 1 (January 1, 2011): 11–20. http://dx.doi.org/10.2478/v10143-011-0017-2.

Повний текст джерела
Анотація:
Multi-Agent and Service Oriented Architectures for Intelligent Tutoring System DevelopmentTraditional modular architecture of Intelligent Tutoring Systems (ITSs) does not provide sufficient modularity of complex ITSs. Distributed technologies like services and agents are used to increase modularity of ITSs by implementing traditional modules as sets of services or agents. The paper describes holonic agent architecture that implements each module as one or more holonic agents. It uses the lessons learned from the multi-agent architecture to propose service oriented ITS architecture.
Стилі APA, Harvard, Vancouver, ISO та ін.
24

Ferguson, D. F., and M. L. Stockton. "Service-oriented architecture: Programming model and product architecture." IBM Systems Journal 44, no. 4 (2005): 753–80. http://dx.doi.org/10.1147/sj.444.0753.

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

Bienvenu, Michael P., Insub Shin, and Alexander H. Levis. "C4ISR architectures: III. An object-oriented approach for architecture design." Systems Engineering 3, no. 4 (2000): 288–312. http://dx.doi.org/10.1002/1520-6858(2000)3:4<288::aid-sys6>3.0.co;2-f.

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

Ivanov, M. S. "Architecture of service-oriented applications." Automatic Documentation and Mathematical Linguistics 41, no. 6 (December 2007): 251–54. http://dx.doi.org/10.3103/s0005105507060039.

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

Diaconita, Vlad, Ana-Ramona Bologa, and Razvan Bologa. "Hadoop Oriented Smart Cities Architecture." Sensors 18, no. 4 (April 12, 2018): 1181. http://dx.doi.org/10.3390/s18041181.

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

Vengerov, Alexander. "Context-Oriented Learning Architecture (COLA)." International Journal of Technology, Knowledge, and Society 1, no. 3 (2006): 7–14. http://dx.doi.org/10.18848/1832-3669/cgp/v01i03/56032.

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

Rouached, Mohsen, Shafique Chaudhry, and Anis Koubaa. "LoWPANs Meet Service-Oriented-Architecture." Journal of Ubiquitous Systems and Pervasive Networks 1, no. 1 (December 30, 2010): 39–48. http://dx.doi.org/10.5383/juspn.01.01.005.

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

Singh, Munindar P., Amit K. Chopra, and Nirmit Desai. "Commitment-Based Service-Oriented Architecture." Computer 42, no. 11 (November 2009): 72–79. http://dx.doi.org/10.1109/mc.2009.347.

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

de Deugd, S., R. Carroll, K. Kelly, B. Millett, and J. Ricker. "SODA: Service Oriented Device Architecture." IEEE Pervasive Computing 5, no. 3 (July 2006): 94–96. http://dx.doi.org/10.1109/mprv.2006.59.

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

Safi Esfahani, Faramarz, Masrah Azrifah Azmi Murad, Md Nasir B. Sulaiman, and Nur Izura Udzir. "Adaptable Decentralized Service Oriented Architecture." Journal of Systems and Software 84, no. 10 (October 2011): 1591–617. http://dx.doi.org/10.1016/j.jss.2011.03.031.

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

Aljazzaf, Zainab M., Miriam A. M. Capretz, and Mark Perry. "Trust-based Service-Oriented Architecture." Journal of King Saud University - Computer and Information Sciences 28, no. 4 (October 2016): 470–80. http://dx.doi.org/10.1016/j.jksuci.2015.12.003.

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

Sacha, Jan, Bartosz Biskupski, Dominik Dahlem, Raymond Cunningham, René Meier, Jim Dowling, and Mads Haahr. "Decentralising a service-oriented architecture." Peer-to-Peer Networking and Applications 3, no. 4 (October 8, 2009): 323–50. http://dx.doi.org/10.1007/s12083-009-0062-6.

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

Yoon, Tom, and Bong-Keun Jeong. "Service Oriented Architecture (SOA) Implementation." International Journal of Information Systems in the Service Sector 10, no. 2 (April 2018): 1–21. http://dx.doi.org/10.4018/ijisss.2018040101.

Повний текст джерела
Анотація:
Using a multiple case studies and surveys, this article finds that factors essential to successful Service Oriented Architecture (SOA) implementations include establishing effective SOA governance, establishing SOA registries, starting with a small project, collaboration between business and IT units, strengthening trust among business units, and training. This article also explores business and IT motivations for SOA implementation and the benefits realized from this implementation. The findings from this article can provide a guidance for practitioners on the successful implementation of SOA.
Стилі APA, Harvard, Vancouver, ISO та ін.
36

Young, Ed. "Service Oriented Architecture Conceptual Landscape." International Journal of Web Portals 1, no. 3 (July 2009): 1–14. http://dx.doi.org/10.4018/jwp.2009070101.

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

Young, Ed. "Service Oriented Architecture Conceptual Landscape." International Journal of Web Portals 1, no. 3 (July 2009): 15–43. http://dx.doi.org/10.4018/jwp.2009070102.

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

Arai, Eiji, Hidefumi Wakamatsu, Masayuki Takata, and Keiichi Shirase. "Human oriented production system architecture." International Journal of Human Resources Development and Management 1, no. 1 (2000): 90. http://dx.doi.org/10.1504/ijhrdm.2000.000996.

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

Suzuki, Hiroshi, Atsushi Iwata, Chinatsu Ikeda, and Naoki Mori. "ATM-oriented multimedia LAN architecture." Electronics and Communications in Japan (Part III: Fundamental Electronic Science) 77, no. 8 (1994): 69–83. http://dx.doi.org/10.1002/ecjc.4430770807.

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

Balabanova, L. V., and L. A. Yuzyk. "SOCIALLY ORIENTED MARKETING ARCHITECTURE FORMATION." Herald of the Belgorod University of Cooperation, Economics and Law 3, no. 100 (2023): 216–23. http://dx.doi.org/10.21295/2223-5639-2023-3-216-223.

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

Wu, Qing, Shi Ying, You Cong Ni, and Hua Cui. "The Architecture Framework with Exception Handing in SOA." Applied Mechanics and Materials 20-23 (January 2010): 992–97. http://dx.doi.org/10.4028/www.scientific.net/amm.20-23.992.

Повний текст джерела
Анотація:
Service-oriented software systems are inherently complex and have to cope with an increasing number of exceptional conditions in order to meet the system’s dynamic requirements. This work proposes an architecture framework which has exception handling capability. This framework ensures the credibility of service-oriented software, during the architectural stage, by adding exception handling-related architecture elements and modeling exception handling process. It allows a clear separation of concerns between the business function and the exception handling unit, using reflection mechanism. It plays an important guiding role for achieving reliable service-oriented system.
Стилі APA, Harvard, Vancouver, ISO та ін.
42

Khumaidi, Ahmad, and Eka Ridhawati. "DEVELOPMENT OF INFORMATION SYSTEM STRATEGIES AND INFORMATION TECHNOLOGY AT PRIVATE UNIVERSITIES IN PRINGSEWU BY USING METHODOLOGY ENTERPRISE ARCHITECTURE PLANNING (EAP)." IJISCS (International Journal of Information System and Computer Science) 1, no. 2 (August 15, 2017): 38. http://dx.doi.org/10.56327/ijiscs.v1i2.503.

Повний текст джерела
Анотація:
The development of information systems and information technology requires planning to complement the direction of the college strategy. Planning is constructed by defining data, application and technology architectures in the use of information to support business processes and then architectural design to identify needs and create architectural schemes and make plans for their implementation. Enterprise Architecture Planning (EAP) is a method of data quality planning approach oriented to business needs and how the implementation of the architecture is done in such a way in an effort to support business turnover and achievement of Vision and Mission and the goal of strategic development of SI and IT at college private high. The result of this research is to get the blueprint resulting from Enterprise Architecture Planning (EAP) methodology which will be used as a guide for making blueprint in the form of data architecture, application architecture and technology architecture in strategy development Information system and information technology as a whole on High private sector especially in Pringsewu
Стилі APA, Harvard, Vancouver, ISO та ін.
43

Erickson, John, and Keng Siau. "Web Services, Service-Oriented Computing, and Service-Oriented Architecture." Journal of Database Management 19, no. 3 (July 2008): 42–54. http://dx.doi.org/10.4018/jdm.2008070103.

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

Mu, Yan Hua. "Task-Oriented Architecture for a Humanoid Robot." Applied Mechanics and Materials 40-41 (November 2010): 228–34. http://dx.doi.org/10.4028/www.scientific.net/amm.40-41.228.

Повний текст джерела
Анотація:
A humanoid robot is developed to perform various kinds of tasks in human daily environments. In this paper, three advanced capabilities which are indispensable for a humanoid robot to perform tasks, namely, natural human-humanoid robot interaction based on spoken dialogue and vision, vision-based navigation in complex and dynamic environments, object grasp and manipulation with hand-eye coordination, are discussed firstly. Then, a biologically-inspired system structure for a humanoid robot is presented. Based on this system structure, a task-oriented layered architecture for a humanoid robot is proposed, and the architectures of the three advanced capabilities are presented, respectively.
Стилі APA, Harvard, Vancouver, ISO та ін.
45

Neumann, B., T. von Sydow, H. Blume, and T. G. Noll. "Design and quantitative analysis of parametrisable eFPGA-architectures for arithmetic." Advances in Radio Science 4 (September 6, 2006): 251–57. http://dx.doi.org/10.5194/ars-4-251-2006.

Повний текст джерела
Анотація:
Abstract. Future SoCs will feature embedded FPGAs (eFPGAs) to enable flexible and efficient implementations of high-throughput digital signal processing applications. Current research projects on and emerging products containing FPGAs are mainly based on "standard FPGA"-architectures that are optimised for a very wide range of applications. The implementation costs of these FPGAs are dominated by a very complex interconnect network. This paper presents a method to improve the efficiency of eFPGAs by tailoring them for a certain application domain using a parametrisable architecture template derived from the results of a systematic evaluation of the requirements of the application domain. Two different architectures are discussed, a reference architecture to illustrate the methodology and possible optimisation measures as well as a specialised arithmetic-oriented eFPGA for applications like correlators, decoders, and filters. For the arithmetic-oriented architecture, a novel logic element (LE) and a special interconnect architecture that was designed with respect to the connectivity characteristics of regular datapaths, are presented. For both architecture templates, physically optimised implementations based on an automatic design approach have been created. As a first cost comparison of these implementations with standard FPGAs, the LE-density (number of logic elements per mm2) is evaluated. For the arithmetic-oriented architecture, the LE-density could be increased by an order of magnitude compared to standard architectures.
Стилі APA, Harvard, Vancouver, ISO та ін.
46

Festus O Oliha. "Guaranteeing Performance in a Fault Tolerant Architecture Solution using Software Agent’s Coordination." Journal of Information and Communication Technology 21, no. 4 (October 19, 2022): 595–625. http://dx.doi.org/10.32890/jict2022.21.4.6.

Повний текст джерела
Анотація:
Performance is a critical attribute in evaluating the quality and dependability of service-oriented systems dependent on fault-tolerantarchitectures. Fault-tolerant architectures have been implemented with redundant techniques to ensure fault-tolerant services. However, replica-related overhead burdens fault-tolerant techniques with associated performance degradation in service delivery, and this consequentially discourages service consumers with discredits for service providers. In this paper, a fault-tolerant approach thatadopts replication and diversity was employed on agent-oriented coordination toward guaranteeing the performance of the proposedfault-tolerant architecture solution under a large-scale service request load. In addition, the resultant architecture solution was simulated with Apache JMeter for performance evaluation considering the performability in the absence and presence of a fault load. The simulation experiments and results revealed the architecture’s efficiency in fault tolerance via the timely coordination of logicaland replica-related activities by software agents. Noteworthily, the continued service availability and performance were guaranteed for the architecture solution with a significant rate of regularity in the absence and presence of a replica-related fault. Therefore, this study’s performance evaluation methods and results could serve as a veritable milestone for building fault-tolerant service systems with appreciable performability and contribute to the service-oriented fields where performance is inevitable.
Стилі APA, Harvard, Vancouver, ISO та ін.
47

XU, KUANG, and JEFFREY J. P. TSAI. "SPECIFICATION OF MULTIMEDIA SOFTWARE SYSTEMS USING AN OBJECT ORIENTED ARCHITECTURE DESCRIPTION LANGUAGE." International Journal of Software Engineering and Knowledge Engineering 09, no. 06 (December 1999): 767–800. http://dx.doi.org/10.1142/s0218194099000401.

Повний текст джерела
Анотація:
Despite the growing importance of multimedia applications, we still know relatively little about how to specify, design, and maintain this class of complex applications in a systematic manner. The concept of software architecture has recently emerged as a way to improve our ability to effectively construct and maintain large-scale complex software systems. Under this new paradigm, software engineers are able to do evolutionary design of complex systems through architecture specification, design rationale capture, architecture validation and verification, and architecture transformation. Several architecture description languages (ADLs), such as Wright, Rapide, UniCon, ACME, etc. have been proposed to support the architecture development under this new software paradigm. Although current ADLs more or less support certain features of object-oriented design approach, few of them are purely based on object-oriented paradigm. In this paper, we present an architecture description language — OOADL (Object-Oriented Architecture Description Language) to facilitate the architecture specification of multimedia software systems. This language takes object-oriented paradigm as its backbone, and provides formal semantics for modeling architectures of software systems. It also aims at other goals such as, support for hierarchical refinement, support for reuse of architecture styles, support for analysis, and support for exception handling. We also introduce the default architecture style which brings the features of extensibility and re-usability into the language. Finally, we use OOADL to construct part of the architecture framework of a multimedia system to illustrate the usage and modeling capability of OOADL.
Стилі APA, Harvard, Vancouver, ISO та ін.
48

Al-Rashedi, Abdulelah Awadh. "E-Government Based on Cloud Computing and Service-Oriented Architecture." International Journal of Computer and Electrical Engineering 6, no. 3 (2014): 201–6. http://dx.doi.org/10.7763/ijcee.2014.v6.822.

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

K.Sai Manoj, Dr, Ms K.Mrudula, G. Maanasa, and K. Phani Srinivas. "Conceptual oriented study on the cloud computing architecture for the full-security." International Journal of Engineering & Technology 7, no. 4 (September 24, 2018): 2491. http://dx.doi.org/10.14419/ijet.v7i4.11654.

Повний текст джерела
Анотація:
Many developers have designed their own architecture for installing the cloud computing infrastructure. The existing cloud computing architectures differs in many ways. Security has been the serious issue as client related data and processing is un-dertaken using the infrastructure provided by third party service providers varies greatly. It is necessary to know the extent of inclusion of security into the cloud computing system and then find the best architecture that includes best and tight security system.In this paper, a comparison of existing architectures from the perspective of inclusion of security infrastructure within cloud computing system is presented along with a comprehensive architecture that is included with every aspect of security taking into account the most of the vulnerabilities
Стилі APA, Harvard, Vancouver, ISO та ін.
50

Hensel, Michael, and Søren Sørensen. "En route to performance-oriented architecture: The research centre for architecture and tectonics: Integrating architectural education with research by design along a practice-oriented perspective." SAJ - Serbian Architectural Journal 5, no. 2 (2013): 106–31. http://dx.doi.org/10.5937/saj1302106h.

Повний текст джерела
Анотація:
This article examines the development of the integrative and interdisciplinary approach to research by design in architecture pursued at the Research Centre for Architecture and Tectonics (RCAT). RCAT constitutes the primary research environment of the Institute of Architecture at the Oslo School of Architecture and Design and focuses on an extensive scope of research activities related to architecture and the built environment that are geared towards the development of a comprehensive approach to performance-oriented architecture. This involves specific ways of integrating architectural education and research, in particular research by design, to support the development of related knowledge, concepts, methods and frequently also the production of reliable empirical data, engaging real-life design problems and seeking interaction with practice. Advanced computational design underpins a lot of the research, as well as scaled and full-scale construction.
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

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