Добірка наукової літератури з теми "ORIENTED ARCHITECTURE"

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

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

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "ORIENTED ARCHITECTURE".

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

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

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

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

Дисертації з теми "ORIENTED ARCHITECTURE"

1

Martin, Kyle A. "Harmony oriented architecture." Master's thesis, University of Central Florida, 2011. http://digital.library.ucf.edu/cdm/ref/collection/ETD/id/4795.

Повний текст джерела
Анотація:
This thesis presents Harmony Oriented Architecture: a novel architectural paradigm that applies the principles of Harmony Oriented Programming to the architecture of scalable and evolvable distributed systems. It is motivated by research on Ultra Large Scale systems that has revealed inherent limitations in human ability to design large-scale software systems that can only be overcome through radical alternatives to traditional object-oriented software engineering practice that simplifies the construction of highly scalable and evolvable system. HOP eschews encapsulation and information hiding, the core principles of object-oriented design, in favor of exposure and information sharing through a spatial abstraction. This helps to avoid the brittle interface dependencies that impede the evolution of object-oriented software. HOA extends these concepts to distributed systems resulting in an architecture in which application components are represented by objects in a spatial database and executed in strict isolation using an embedded application server. Application components store their state entirely in the database and interact solely by diffusing data into a space for proximate components to observe. This architecture provides a high degree of decoupling, isolation, and state exposure allowing highly scalable and evolvable applications to be built. A proof-of-concept prototype of a non-distributed HOA middleware platform supporting JavaScript application components is implemented and evaluated. Results show remarkably good performance considering that little effort was made to optimize the implementation.
ID: 031001554; System requirements: World Wide Web browser and PDF reader.; Mode of access: World Wide Web.; Title from PDF title page (viewed August 26, 2013).; Thesis (M.S.)--University of Central Florida, 2011.; Includes bibliographical references (p. 79-84).
M.S.
Masters
Electrical Engineering and Computer Science
Engineering and Computer Science
Computer Science
Стилі APA, Harvard, Vancouver, ISO та ін.
2

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.

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

McClain, John W. F. (John Wesley Ferguson). "A lisp oriented architecture." Thesis, Massachusetts Institute of Technology, 1994. http://hdl.handle.net/1721.1/35999.

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

Zhang, Feng. "Secure Mobile Service-Oriented Architecture." Doctoral thesis, KTH, Kommunikation: Infrastruktur och tjänster, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-95328.

Повний текст джерела
Анотація:
Mobile transactions have been in development for around ten years. More and more initiatives and efforts are invested in this area resulting in dramatic and rapid development and deployment of mobile technologies and applications. However, there are still many issues that hinder wider deployment and acceptance of mobile systems, especially those handling serious and sensitive mobile transactions. One of the most important of them is security.This dissertation is focused on security architecture for mobile environments. Research issues addressed in this dissertation are based on three currently important groups of problems: a) lack of an open, comprehensive, adaptable and secure infrastructure for mobile services and applications; b) lack of standardized solutions for secure mobile transactions, compliant with various regulatory and user requirements and applicable to different types of popular mobile devices and hardware/software mobile platforms; and c) resource limitations of mobile devices and mobile networks.The main contribution of this dissertation is large-scale, secure service-oriented architecture for mobile environments. The architecture structures secure mobile transaction systems into seven layers, called trusted stack, which is equivalent to ISO/OSI layered networking model. These layers are, starting from the bottom: 1) secure element (chip) layer, 2) applets layer, 3) middleware layer, 4) mobile applications layer, 5) communication layer, 6) services broker layer, and 7) mobile service provider layer. These seven layers include all necessary components required for implementation and operations of secure mobile transaction systems and therefore provide a framework for designing and implementing such systems.Besides the architecture, four types of security services necessary and critical for serious mobile transactions, have also been designed and described in the dissertation. These services are: (1) mobile registration and identity management; (2) mobile PKI; (3) mobile authentication and authorization; and (4) secure messaging. These services are lightweight, therefore suitable for mobile environments, technologies and applications, and also compliant with existing Internet security standards.Finally, as the proof of correctness of the proposed concept and methodology, a prototype system was also developed based on the designed security architecture. The system provides comprehensive security services mentioned above to several types of mobile services providers: mobile banking, mobile commerce, mobile ticketing, and mobile parking. These types of providers have been selected only as currently the most popular and representative, since the architecture is applicable to any other type of mobile service providers.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Baggett, Neal Stuart. "Towards a phenomena-oriented architecture." Thesis, Montana State University, 2010. http://etd.lib.montana.edu/etd/2010/baggett/BaggettN0510.pdf.

Повний текст джерела
Анотація:
Architecture’s focus on the visual faculty omits potential dialogue with the tactile, auditory and proprioceptive ones. We have become a culture encouraged to live in that visual sense. The question is if Architecture can begin to engage the body and the sense for the user to have a more robust and fulfilling experience. This thesis rekindles dialogue with all sense perceptions with an architecture that engages the varying aspects of the built environment: texture, relationship and scale.
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Adepu, Sagarika. "Qos Aware Service Oriented Architecture." Thesis, University of North Texas, 2013. https://digital.library.unt.edu/ark:/67531/metadc500032/.

Повний текст джерела
Анотація:
Service-oriented architecture enables web services to operate in a loosely-coupled setting and provides an environment for dynamic discovery and use of services over a network using standards such as WSDL, SOAP, and UDDI. Web service has both functional and non-functional characteristics. This thesis work proposes to add QoS descriptions (non-functional properties) to WSDL and compose various services to form a business process. This composition of web services also considers QoS properties along with functional properties and the composed services can again be published as a new Web Service and can be part of any other composition using Composed WSDL.
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Ballapuram, Chinnakrishnan S. "Semantics-oriented low power architecture." Diss., Atlanta, Ga. : Georgia Institute of Technology, 2008. http://hdl.handle.net/1853/22567.

Повний текст джерела
Анотація:
Thesis (Ph. D.)--Electrical and Computer Engineering, Georgia Institute of Technology, 2008.
Committee Chair: Hsien-Hsin Sean Lee; Committee Member: Abhijit Chatterjee; Committee Member: Bernard Kippelen; Committee Member: Gabriel H. Loh; Committee Member: SungKyu Lim.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Kaliniak, Piotr. "Migration of a Chosen Architectural Pattern to Service Oriented Architecture." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4892.

Повний текст джерела
Анотація:
Context: Several examples of successful migrations of systems to Service Oriented Architecture (SOA) are presented in the literature. Some of the approaches also try to structure the process of migration to SOA. The reported migration attempts underline the role of architecture of migrated system, but they do not explore the architectural patterns applied in architecture of migrated systems while proper usage of patterns may simplify and improve quality of migration. Objectives: This work is aimed at elaborating guidelines that support migration from a system that is based on a chosen architectural pattern towards a system based on Service Oriented Architecture. Methods: Literature review is used as a basic method in the initial steps of the research, that is during investigation of existing techniques of migration to SOA, establishing procedure for selection of the migrated pattern and identifying building blocks of the target architecture. Results of the literature reviews are further analyzed in order to select the migrated architectural pattern and to elaborate the target architecture. The guidelines for migration are the result of the synthesis of the analyzed information. Results: The migration is realized as a translation between two pattern languages: the first pattern language describes the chosen architectural pattern–Model–View–Controller and the second pattern language describes SOA target architecture, expressed using SOA architectural patterns. The translation is defined by a set of migration guidelines. The approach is also illustrated with migrating an example student project. Conclusion: The study shows that the usage of an architectural pattern during migration allows to define the migration in a simple, structured and precise way using guidelines that represent a set of subsequent well defined steps that should be applied in order to migrate a specific type of legacy system.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Zimmermann, Olaf. "An architectural decision modeling framework for service oriented architecture design." Berlin dissertation.de, 2009. http://d-nb.info/994960557/04.

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

Rodem, Magne. "Security in a Service-Oriented Architecture." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2008. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9719.

Повний текст джерела
Анотація:

In a service-oriented architecture (SOA), parts of software applications are made available as services. These services can be combined across multiple applications, technologies, and organizations. As a result, functionality can be more easily reused, and new business processes can be assembled at a low cost. However, as more functionality is exposed outside of the traditional boundaries of applications, new approaches to security are needed. While SOA shares many of the security threats of traditional systems, the countermeasures to some of these threats may differ. Most notably, eavesdropping, data tampering, and replay attacks must be countered on the message level in a complex SOA environment. In addition, the open and distributed nature of SOA leads to new ways of handling authentication, authorization, logging, and monitoring. Web Services are the most popular way of realizing SOA in practice, and make use of a set of standards such as WS-Security, XML Encryption, XML Signature, and SAML for handling these new security approaches. Guidelines exist for development of secure software systems, and provide recommendations for things to do or to avoid. In this thesis, I use my findings with regard to security challenges, threats, and countermeasures to create a set of security guidelines that should be applied during requirements engineering and design of a SOA. Practical use of these guidelines is demonstrated by applying them during development of a SOA-based system. This system imports personal data into multiple administrative systems managed by UNINETT FAS, and is designed using Web Services and XML-based security standards. Through this practical demonstration, I show that my guidelines can be used as a reference for making appropriate security decisions during development of a SOA.

Стилі APA, Harvard, Vancouver, ISO та ін.

Книги з теми "ORIENTED ARCHITECTURE"

1

Judith, Hurwitz, Kaufman Marcia, and Halper Fern, eds. Service Oriented Architecture. 2nd ed. Hoboken: For Dummies [Imprint], 2009.

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

Hensel, Michael. Performance-Oriented Architecture. Chichester, UK: John Wiley & Sons Ltd, 2013. http://dx.doi.org/10.1002/9781118640630.

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

Marks, Eric A., and Michael Bell, eds. Service-Oriented Architecture. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2012. http://dx.doi.org/10.1002/9781119201700.

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

Architecture oriented otherwise. New York, NY: Princeton Architectural Press, 2009.

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

Sweeney, Rick, ed. Achieving Service-Oriented Architecture. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2012. http://dx.doi.org/10.1002/9781119200178.

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

C, Schmidt Douglas, ed. Pattern-oriented software architecture. Chichester [England]: Wiley, 2000.

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

1936-, Fernandez Eduardo B., and Lang Tomás, eds. Software-oriented computer architecture. Washington, D.C: IEEE Computer Society Press, 1986.

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

Simplified service oriented architecture. [Erscheinungsort nicht ermittelbar]: Felibr.com, 2010.

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

REKURSIV: Object-oriented computer architecture. Chichester [England]: E. Horwood, 1988.

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

Jones, William H. Project integration architecture: Architectural overview. [Cleveland, Ohio]: National Aeronautics and Space Administration, Glenn Research Center, 2001.

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

Частини книг з теми "ORIENTED ARCHITECTURE"

1

Draheim, Dirk. "Service-Oriented Architecture." In Business Process Technology, 221–41. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-01588-5_8.

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

Zaslavsky, Ilya. "Service-Oriented Architecture." In Encyclopedia of GIS, 1. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-23519-6_1199-2.

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

Mankovski, Serge. "Service Oriented Architecture." In Encyclopedia of Database Systems, 1–4. New York, NY: Springer New York, 2016. http://dx.doi.org/10.1007/978-1-4899-7993-3_1173-2.

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

Hazra, Tushar K. "Service-Oriented Architecture." In The Next Wave of Technologies, 115–29. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2015. http://dx.doi.org/10.1002/9781119199946.ch7.

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

Zaslavsky, Ilya. "Service-Oriented Architecture." In Encyclopedia of GIS, 1895–96. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-17885-1_1199.

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

Shekhar, Shashi, and Hui Xiong. "Service Oriented Architecture." In Encyclopedia of GIS, 1054. Boston, MA: Springer US, 2008. http://dx.doi.org/10.1007/978-0-387-35973-1_1198.

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

Zaslavsky, Ilya. "Service-Oriented Architecture." In Encyclopedia of GIS, 1054–55. Boston, MA: Springer US, 2008. http://dx.doi.org/10.1007/978-0-387-35973-1_1199.

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

Mankovski, Serge. "Service Oriented Architecture." In Encyclopedia of Database Systems, 2633–36. Boston, MA: Springer US, 2009. http://dx.doi.org/10.1007/978-0-387-39940-9_1173.

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

Mankovski, Serge. "Service-Oriented Architecture." In Encyclopedia of Database Systems, 3480–84. New York, NY: Springer New York, 2018. http://dx.doi.org/10.1007/978-1-4614-8265-9_1173.

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

Kühn, Christian. "User-Oriented Architecture." In Die Fakultät für Architektur und Raumplanung, 12–16. Wien: Böhlau Verlag, 2015. http://dx.doi.org/10.7767/9783205202271-003.

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

Тези доповідей конференцій з теми "ORIENTED ARCHITECTURE"

1

Sefika, Mohlalefi, Aamod Sane, and Roy H. Campbell. "Architecture-oriented visualization." In the 11th ACM SIGPLAN conference. New York, New York, USA: ACM Press, 1996. http://dx.doi.org/10.1145/236337.236380.

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

"Service-oriented architecture." In 2008 6th IEEE International Conference on Industrial Informatics. IEEE, 2008. http://dx.doi.org/10.1109/indin.2008.4618200.

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

Shan, Tony C., and Winnie W. Hua. "Service-Oriented Architecture Roadmapping." In 2009 IEEE Congress on Services (SERVICES). IEEE, 2009. http://dx.doi.org/10.1109/services-i.2009.117.

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

Overdick, Hagen. "The Resource-Oriented Architecture." In 2007 IEEE Congress on Services (Services 2007). IEEE, 2007. http://dx.doi.org/10.1109/services.2007.66.

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

Reza, H., and E. Grant. "Quality-oriented software architecture." In International Conference on Information Technology: Coding and Computing (ITCC'05) - Volume II. IEEE, 2005. http://dx.doi.org/10.1109/itcc.2005.237.

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

Sabucedo, Luis, and Luis Rifon. "Life Event Oriented Architecture." In 2006 IEEE Services Computing Workshops. IEEE, 2006. http://dx.doi.org/10.1109/scw.2006.26.

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

Spichkova, Maria, Huai Liu, and Heinz Schmidt. "Towards Quality-Oriented Architecture." In ECSAW '15: 2015 European Conference on Software Architecture Workshops. New York, NY, USA: ACM, 2015. http://dx.doi.org/10.1145/2797433.2797499.

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

Campbell, David. "Service Oriented Database Architecture." In the 2005 ACM SIGMOD international conference. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1066157.1066267.

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

Gohde, Johnathan, Peter Griffin, Brent Rickenbach, and Jason Rush. "Tactical service-oriented architecture." In SPIE Defense and Security Symposium, edited by Raja Suresh. SPIE, 2008. http://dx.doi.org/10.1117/12.784099.

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

Lotfallahtabrizi, Parisa, and Yasser Morgan. "Comparing autonomy and collaboration between agent-oriented architecture and service-oriented architecture." In 2017 8th IEEE Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON). IEEE, 2017. http://dx.doi.org/10.1109/iemcon.2017.8117134.

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

Звіти організацій з теми "ORIENTED ARCHITECTURE"

1

Aldrich, Susan. Service-Oriented Architecture FAQs. Boston, MA: Patricia Seybold Group, May 2003. http://dx.doi.org/10.1571/psgp5-9-03cc.

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

Eugene, Robert. Service-Oriented Architecture: Defining Granularity. Boston, MA: Patricia Seybold Group, July 2003. http://dx.doi.org/10.1571/bp7-17-03cc.

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

Eugene, Robert. Service-Oriented Architecture: Applying Granularity. Boston, MA: Patricia Seybold Group, July 2003. http://dx.doi.org/10.1571/bp7-24-03cc.

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

Eugene, Robert. Service-Oriented Architecture: Defining Services. Boston, MA: Patricia Seybold Group, August 2003. http://dx.doi.org/10.1571/bp8-7-03cc.

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

Blanco, Phil, Rick Kotermanski, and Paulo Merson. Evaluating a Service-Oriented Architecture. Fort Belvoir, VA: Defense Technical Information Center, September 2007. http://dx.doi.org/10.21236/ada475130.

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

Michelson, Brenda. The Evolution of Service-Oriented Architecture. Boston, MA: Patricia Seybold Group, January 2005. http://dx.doi.org/10.1571/soa1-6-05cc.

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

Bryant, J., V. Combs, J. Hanna, G. Hasseler, R. Hillman, B. Lipa, J. Reilly, and C. Vincelette. Phoenix: Service Oriented Architecture for Information Management - Abstract Architecture Document. Fort Belvoir, VA: Defense Technical Information Center, September 2011. http://dx.doi.org/10.21236/ada549855.

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

Michelson, Brenda. A New Service-Oriented Architecture Maturity Model. Boston, MA: Patricia Seybold Group, November 2005. http://dx.doi.org/10.1571/psgp11-3-05cc.

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

Merson, Paulo. Using Aspect-Oriented Programming to Enforce Architecture. Fort Belvoir, VA: Defense Technical Information Center, September 2007. http://dx.doi.org/10.21236/ada479322.

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

Hamlet, Benjamin R., Andre Villanova Encarnacao, James M. Harris, and Christopher J. Young. US NDC Modernization: Service Oriented Architecture Study Status. Office of Scientific and Technical Information (OSTI), December 2014. http://dx.doi.org/10.2172/1173201.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

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