Relevant bibliographies by topics / Service-oriented architectures

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Service-oriented architectures'

Author: Grafiati
Published: 4 June 2021
Last updated: 9 June 2025

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Service-oriented architectures.'

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

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

Journal articles on the topic "Service-oriented architectures"

1

Stantchev, V., and M. Malek. "Architectural translucency in service-oriented architectures." IEE Proceedings - Software 153, no. 1 (2006): 31. http://dx.doi.org/10.1049/ip-sen:20050017.

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

Soodeh, Pakari, Kheirkhah Esmaeel, and Jalali Mehrdad. "A Novel Approach: A Hybrid Semantic Matchmaker For Service Discovery In Service Oriented Architecture." International Journal of Network Security & Its Applications (IJNSA) 6, no. 1 (January 27, 2014): 37–48. https://doi.org/10.5281/zenodo.6339793.

Full text
Abstract:
Since service-oriented architectures make the commercial systems more reliable and reusable, they have gained more popularity in industry and scientific community in recent decades. Service-oriented architectures bring flexibility and reusability to software design. Due to the increasing number of services on the Web, finding a service which is suited to user requirements is crucial. The process of finding suitable services to user request is one of the main purposes of service-oriented architectures. Many methods have been proposed for service discovery in service-oriented architectures that try to fulfil user requirements and offer suitable services to user request; however the proposed methods do not have enough precision for discovering suitable services. In this paper, we propose a method for service discovery which offers more accurate services according to user request. The proposed method is a hybrid semantic matchmaker for service discovery in service oriented architecture. By providing accurate services suitable to user requests, we have greatly increased the reusability rate and reduced the time and cost of software development.
APA, Harvard, Vancouver, ISO, and other styles
3

Abuosba, Khalil A., and Asim A. El-Sheikh. "Formalizing Service-Oriented Architectures." IT Professional 10, no. 4 (July 2008): 34–38. http://dx.doi.org/10.1109/mitp.2008.70.

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

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.

Full text
Abstract:
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, and other styles
5

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.

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

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.

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

Dong, Jing, Raymond A. Paul, and Liang-Jie Zhang. "High-Assurance Service-Oriented Architectures." Computer 41, no. 8 (August 2008): 27–28. http://dx.doi.org/10.1109/mc.2008.298.

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

Reed, Barbara. "Service‐oriented architectures and recordkeeping." Records Management Journal 18, no. 1 (February 22, 2008): 7–20. http://dx.doi.org/10.1108/09565690810858488.

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

Reed, Barbara. "Service‐oriented architectures and recordkeeping." Records Management Journal 20, no. 1 (March 30, 2010): 124–37. http://dx.doi.org/10.1108/09565691011039898.

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

Liu, Lu, and Jie Xu. "Clouds and service-oriented architectures." Future Generation Computer Systems 29, no. 1 (January 2013): 271–72. http://dx.doi.org/10.1016/j.future.2012.05.002.

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

Dissertations / Theses on the topic "Service-oriented architectures"

1

Ramaratnam, Rajiv. "An analysis of service oriented architectures." Thesis, Massachusetts Institute of Technology, 2007. http://hdl.handle.net/1721.1/42372.

Full text
Abstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2007.<br>Leaf 96 blank.<br>Includes bibliographical references (leaves 88-95).<br>Introduction: Corporations all across the globe and of various sizes rely on their IT systems for business processes, reduction of process lifecycle and management of resources. These systems house several applications for internal sales, purchasing, finance, HR and so on. In any such typical organization, IT systems are a heterogeneous mix of hardware, operating systems and applications. Many of these applications run on different operating systems like Windows systems, Linux and Unix systems, etc. Oftentimes there is a need to consolidate data or access data from several such systems. The diversity among systems and applications makes these tasks difficult, time consuming and tedious. Furthermore, there is also a need for synchronization of data across systems and applications to ensure that the data is accurate and up-to-date. The heterogeneous nature of systems and applications lead to high levels of redundancy of data, making data maintenance a huge overhead for organizations. Today's organizations must also adapt to changes in environments both external and internal to them. Such changes could be changing market conditions, reorganization, change in business strategies within a company, addition or changing suppliers, partnerships, mergers and acquisitions and so on. There is also a growing need for integration across enterprise boundaries to facilitate fast and seamless collaboration between partners, customers and suppliers. All such needs entail changes to existing IT systems within an organization in a timely manner. There is thus a growing need for integration of such systems for consolidated decision making, accurate, up-to-date system information, better performance and system monitoring. IT Systems must also be flexible to respond to changes in the environments of their organization. Enterprise Application Integration is a process that aims to bring about such integration. The need for integration goes beyond the boundaries of an enterprise. Further, to successfully compete today, businesses need to be flexible. This means that their IT systems need to be able to keep pace with dynamic business conditions. It is evident that any solution for multiple IT systems to integrate with each other and to provide flexibility, they must be able to communicate and coordinate activities in a standard way. For almost two decades, many companies have tried to use CORBA, DCOM and similar technologies but have had little success. None of these technologies, for many reasons have become global technologies. The arrival of standards like HTTP and HTML helped linking together millions of humans across the internet but proved inadequate to link together computer systems. Moreover, internal and cross enterprise integration and coordination bring with them, security implications as both involve information exchange between organizational entities. As we will see later, the traditional methods of securing applications with firewalls prove inadequate for application security. One insight that has come from failed attempts to consolidate and coordinate IT systems is that such efforts cannot be limited to IT alone. Decision making on how interdepartmental and inter-enterprise data must data must be exchanged must be made by leaders and opinion shapers at each level or division of the organization. It is the goals of internal and external enterprise integration, flexibility of business processes, and enterprise data security that has led more and more organizations to adopt to Service Oriented Architectures (SOA). The adoption, implementation and running of a SOA does not simply involve IT department heads to design and create a new architecture for the enterprise. It involves a holistic understanding of the nature of the entire enterprise, its business and internal processes, the corporate strategy for the enterprise, an understanding of the business processes of the enterprise, its partners, suppliers, subsidiaries, etc. Such an undertaking is beyond the scope of a single department or division of the enterprise. The creation and running SOA architecture thus involves the coordination of all parts of the enterprise.<br>by Rajiv Ramaratnam.<br>S.M.
APA, Harvard, Vancouver, ISO, and other styles
2

Abeti, Luca. "Business-oriented model driven development of service oriented architectures." Thesis, IMT Alti Studi Lucca, 2009. http://e-theses.imtlucca.it/18/1/Abeti_phdthesis.pdf.

Full text
Abstract:
Context & motivation: The success in the adoption of innovative technologies and new software systems inside an organization is related not only to technical problems. Several authors pointed out the importance of business modelling in software development in order to understand for instance: how the organizational environment relates to its software infrastructure and how the development of a new software-intensive service for a company implies changes in the company business and in its processes. The growing complexity of organizations, such as: networked and information-dependent companies; globalization of the companies structures; evanescent services provided by companies, increase the uncertainty in software projects. Software engineering successes in turn became more and more bounded to the understanding of the organizational assets and their relation to the software. Question/problem: How can we model the business in requirements engineering phases and, at the same time, enable business-level concepts (such as strategies, goals, trust, etc.) to relate to system-level artifacts? Principal ideas/results: Our aim is to define a framework that helps software engineers to develop their systems in what we named the business-oriented approach. The business-oriented approach to software development has been defined as an approach that carefully consider the processes, actors and goal of the business in developing a software system and also analyzes the changes that the software will cause to the organization itself. In order to define such a framework we exploit model driven engineering that helps in managing high level abstractions for the software. In particular, our work relies on the service architectural paradigm that is particularly suitable in modeling socio-technical systems. Contribution: In order to define our framework we define: a method; a framework of technologies and a set of tools. Our method, named the Enterprise-Service-Implementation (ESI), starts from the requirements of the organization and the system, it derives a platform independent service model that can be in turn transformed into platform specific implementations. ESI exploits the service concept as an intermediate abstraction. Model driven technologies help us to translate concepts from the business domain, such as goals, into services concretely bounded to a specific implementation platform. A framework of technologies and languages helps us to implement the ESI method. We exploit and combine: a goaloriented language named Si*; UML Use Cases and a business process modeling language named Buiness Process Modeling Notation (BPMN), in order to model the business from different perspectives. We develop two tools to put into practice our framework. TheWiki Requirements tool (WikiReq) is a collaborative system and business requirements management Web application based on a wiki. WikiReq uses semantic wiki features for requirements gathering and management and is able to export semantically annotated knowledge to the Eclipse Integrated Development Environment (IDE). The Service Modeling Tool for Eclipse (SMOTE) is an Eclipse IDE application that exploits the Eclipse model driven architecture in order to perform the models transformations needed in our framework. We present a case studio where we experienced our framework in the challenging domain of Civil Protection. We present first results on the adoption of our approach concerning both the stakeholders experience and quantitative data.
APA, Harvard, Vancouver, ISO, and other styles
3

Gamble, Carl Jeffrey. "Design time detection of architectural mismatches in service oriented architectures." Thesis, University of Newcastle Upon Tyne, 2011. http://hdl.handle.net/10443/1241.

Full text
Abstract:
Service Oriented Architecture (SOA) is a software component paradigm that has the potential to allow for exible systems that are loosely coupled to each other. They are discoverable entities that may be bound to at run time by a client who is able to use the service correctly by referring to the service's description documents. Assumptions often have to be made in any design process if the problem domain is not fully speci ed. If those decisions are about the software architecture of that component and it is inserted into a system with di ering and incompatible assumptions then we say that an architectural mismatch exists. Architectural styles are a form of software reuse. They can simply be used by referring to a name such as \client-server" or \pipe and lter", where these names may conjure up topologies and expected properties in the architects mind. They can also however be more rigorously de ned given the right software environment. This can lead to a vocabulary of elements in the system, de ned properties of those elements along with rules and analysis to either show correctness of an implementation or reveal some emergent property of the whole. SOA includes a requirement that the service components make available descriptions of themselves, indicating how they are to be used. With this in mind and assuming we have a suitable description of the client application it should be the case that we can detect architectural mismatches when designing a new system. Here designing can range from organising a set of existing components into a novel con guration through to devising an entirely new set of components for an SOA. This work investigates the above statement using Web Services as the SOA implementation and found that, to a degree, the above statement is true. The only element of description required for a web service is the Web Service Description Language (WSDL) document and this does indeed allow the detection of a small number of mismatches when represented using our minimal web service architectural style. However from the literature we nd that the above mismatches are only a subset of those that we argue should be detectable. In response to this we produce an enhanced web service architectural style containing properties and analysis supporting the detection of this more complete set of mismatches and demonstrate its e ectiveness against a number of case studies.
APA, Harvard, Vancouver, ISO, and other styles
4

Al-Humam, Abdulaziz. "Service-oriented architectures for safety-critical systems." Thesis, University of York, 2015. http://etheses.whiterose.ac.uk/11823/.

Full text
Abstract:
Many organisations in the safety-critical domain are service-oriented, fundamentally centred on critical services provided by systems and operators. Increasingly, these services rely on software-intensive systems, e.g. medical health informatics and air traffic control, for improving the different aspects of industrial practice, e.g. enhancing efficiency through automation and safety through smart alarm systems. However, many services are categorised as high risk and as such it is vital to analyse the ways in which the software-based systems can contribute to unintentional harm and potentially compromise safety. This thesis defines an approach to modelling and analysing Service-Oriented Architectures (SOAs) used in the safety-critical domain, with emphasis on identifying and classifying potential hazardous behaviour. The approach also provides a systematic and reusable basis for defining how the safety case for these SOAs can be developed in a modular manner. The approach is tool-supported and is evaluated through two case studies, from the healthcare and oil and gas domains, and industrial review.
APA, Harvard, Vancouver, ISO, and other styles
5

Mayer, Philip. "MDD4SOA: Model-Driven Development for Service-Oriented Architectures." Diss., lmu, 2010. http://nbn-resolving.de/urn:nbn:de:bvb:19-124405.

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

Giese, Holger, and Basil Becker. "Modeling and verifying dynamic evolving service-oriented architectures." Universität Potsdam, 2013. http://opus.kobv.de/ubp/volltexte/2013/6511/.

Full text
Abstract:
The service-oriented architecture supports the dynamic assembly and runtime reconfiguration of complex open IT landscapes by means of runtime binding of service contracts, launching of new components and termination of outdated ones. Furthermore, the evolution of these IT landscapes is not restricted to exchanging components with other ones using the same service contracts, as new services contracts can be added as well. However, current approaches for modeling and verification of service-oriented architectures do not support these important capabilities to their full extend.In this report we present an extension of the current OMG proposal for service modeling with UML - SoaML - which overcomes these limitations. It permits modeling services and their service contracts at different levels of abstraction, provides a formal semantics for all modeling concepts, and enables verifying critical properties. Our compositional and incremental verification approach allows for complex properties including communication parameters and time and covers besides the dynamic binding of service contracts and the replacement of components also the evolution of the systems by means of new service contracts. The modeling as well as verification capabilities of the presented approach are demonstrated by means of a supply chain example and the verification results of a first prototype are shown.<br>Service-Orientierte Architekturen erlauben die dynamische Zusammensetzung und Rekonfiguration komplexer, offener IT Landschaften durch Bindung von Service Contracts zur Laufzeit, starten neuer Komponenten und beenden von veralteten. Die Evolution dieser Systeme ist nicht auf den Austausch von Komponenten-Implementierungen bei Beibehaltung der Service-Contracts beschränkt, sondern das Hinzufügen neuer Service-Contracts wird ebenfalls unterstützt. Aktuelle Ansätze zur Modellierung und Verifikation Service-Orientierter Architekturen unterstützen diese wichtigen Eigenschaften, wenn überhaupt, nur unvollständig. In diesem Bericht stellen wir eine Erweiterung des aktuellen OMG Vorschlags zur Service Modellierung mit UML - SoaML - vor, die diese Einschränkungen aufhebt. Unser Ansatz erlaubt die Modellierung von Service Contracts auf verschiedenen Abstraktionsniveaus, besitzt eine fundierte formale Semantik für alle eingeführten Modellierungskonzepte und erlaubt die Verifikation kritischer Eigenschaften. Unser kompositionaler und inkrementeller Verifikationsansatz erlaubt die Verifikation komplexer Eigenschaften einschließlich Kommunikationsparameter und Zeit und deckt neben der dynamischen Bindung von Service Contracts sowie dem Austausch von Komponenten auch die Evolution des gesamten Systems durch das Hinzufügen neuer Service Contracts ab. Die Modellierungs- als auch die Verifikationsfähigkeiten unseres vorgestellten Ansatzes werden durch ein Anwendungsbeispiel aus dem Bereich des Lieferkettenmanagements veranschaulicht.
APA, Harvard, Vancouver, ISO, and other styles
7

Thomas, Jamar. "Asynchronous instant messaging using service-oriented architectures (aimsoa)." DigitalCommons@Robert W. Woodruff Library, Atlanta University Center, 2005. http://digitalcommons.auctr.edu/dissertations/1251.

Full text
Abstract:
Instant messengers suffer from poor scalability, flexibility, security, and interoperability. This study attempts to solve these problems using the strengths of Service-Oriented Architectures. The key components to achieve these improvements include several Java related technologies such as JAX-RPC, JAXM, SOAP, WSDL, J2EE servlets and Enterprise Java Beans. SOAP provides a universal messaging protocol that heterogeneous parties can understand. JAX-RPC provides synchronous SOAP messaging, as well as a loosely coupled design that allows for a very flexible distributed architecture. JAXM provides asynchronous SOAP messaging. When used together, applications can implement robust instant messaging functionality. Registration, login, and other instant messaging configuration operations can be fulfilled through the use of JAX-RPC while JAXM can be used to fulfill requirements such as send and receive. Servlets and Enterprise Java Beans augment the benefits of Service-Oriented Architectures with the former being extremely scalable, portable, and modular. AIMSOA encapsulates these components to provide an instant messaging architecture solution that will augment the weaknesses of current instant messaging architectures by providing a solution for better scalability, flexibility, and interoperability.
APA, Harvard, Vancouver, ISO, and other styles
8

Norman, David. "The value proposition of service-oriented architecture." [Denver, Colo.] : Regis University, 2008. http://165.236.235.140/lib/DNorman2008.pdf.

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

Friesen, Andreas [Verfasser]. "Secure Subscription Management for Service-oriented Architectures / Andreas Friesen." Aachen : Shaker, 2004. http://d-nb.info/1170535038/34.

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

Krähenbühl, Alexander. "Soability assessment, planning, and management of service oriented architectures." Saarbrücken VDM, Müller, 2006. http://d-nb.info/987710737/04.

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

Books on the topic "Service-oriented architectures"

1

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

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

Wieder, Philipp, Ramin Yahyapour, and Wolfgang Ziegler, eds. Grids and Service-Oriented Architectures for Service Level Agreements. Boston, MA: Springer US, 2010. http://dx.doi.org/10.1007/978-1-4419-7320-7.

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

Wieder, Philipp. Grids and Service-Oriented Architectures for Service Level Agreements. Boston, MA: Springer Science+Business Media, LLC, 2010.

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

Bell, Michael. Service-oriented modeling: Service analysis, design, and architecture. Hoboken, N.J: John Wiley & Sons, 2008.

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

Bertino, Elisa, Lorenzo Martino, Federica Paci, and Anna Squicciarini. Security for Web Services and Service-Oriented Architectures. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-540-87742-4.

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

Schillinger, Rolf. Semantic service oriented architectures in research and practice. Lohmar: J. Eul, 2011.

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

Lorenzo, Martino, Paci Federica, Squicciarini Anna, and SpringerLink (Online service), eds. Security for Web Services and Service-Oriented Architectures. Berlin, Heidelberg: Springer-Verlag Berlin Heidelberg, 2010.

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

Dovey, Matthew. Interoperable Web service standards for library systems: Service oriented architectures for libraries. Oxford: Chandos, 2006.

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

H, Howell-Barber, ed. Service-oriented architecture: Strategies, methodologies, and technologies. Boca Raton: Auerbach Publications, 2008.

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

Bell, Michael. SOA modeling patterns for service-oriented discovery and analysis. Hoboken, N.J: John Wiley & Sons, 2010.

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

Book chapters on the topic "Service-oriented architectures"

1

Lano, Kevin, and Sobhan Yassipour Tehrani. "Service-Oriented Architectures." In Introduction to Software Architecture, 177–90. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-44143-1_9.

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

Mahala, Geeta, Renuka Sindhgatta, Hoa Khanh Dam, and Aditya Ghose. "Designing Optimal Robotic Process Automation Architectures." In Service-Oriented Computing, 448–56. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-65310-1_32.

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

Hirzalla, Mamoun, Peter Bahrs, Jane Cleland-Huang, Craig S. Miller, and Rob High. "A Predictive Business Agility Model for Service Oriented Architectures." In Service-Oriented Computing, 653–60. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-25535-9_52.

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

Cantarutti, Michele, Pierluigi Plebani, and Mattia Salnitri. "Fast Replica of Polyglot Persistence in Microservice Architectures for Fog Computing." In Service-Oriented Computing, 45–55. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-65310-1_4.

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

Ntentos, Evangelos, Amirali Amiri, Stephen Warnett, and Uwe Zdun. "Decision-Making Support for Data Integration in Cyber-Physical-System Architectures." In Service-Oriented Computing, 137–52. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-48421-6_10.

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

Greenfield, Paul. "Service-Oriented Architectures and Technologies." In Essential Software Architecture, 65–80. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19176-3_5.

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

Eickhoff, Jens. "Service Oriented Simulator Kernel Architectures." In Simulating Spacecraft Systems, 271–80. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-01276-1_11.

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

van Gurp, Jilles, Anssi Karhinen, and Jan Bosch. "Mobile Service Oriented Architectures (MOSOA)." In Distributed Applications and Interoperable Systems, 1–15. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11773887_1.

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

Stollberg, Michael, and Dieter Fensel. "Semantics for Service-Oriented Architectures." In Advanced Information and Knowledge Processing, 113–39. London: Springer London, 2009. http://dx.doi.org/10.1007/978-1-84996-041-0_5.

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

Khondoker, Rahamatullah. "Background: Service Oriented Network Architectures." In Description and Selection of Communication Services for Service Oriented Network Architectures, 39–70. Wiesbaden: Springer Fachmedien Wiesbaden, 2016. http://dx.doi.org/10.1007/978-3-658-12742-8_2.

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

Conference papers on the topic "Service-oriented architectures"

1

"Service-oriented architectures." In 2010 8th IEEE International Conference on Industrial Informatics (INDIN). IEEE, 2010. http://dx.doi.org/10.1109/indin.2010.5549681.

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

Bierhoff, Kevin, Mark Grechanik, and Edy S. Liongosari. "Architectural Mismatch in Service-Oriented Architectures." In International Workshop on Systems Development in SOA Environments (SDSOA'07: ICSE Workshops 2007). IEEE, 2007. http://dx.doi.org/10.1109/sdsoa.2007.2.

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

Baresi, Luciano, Carlo Ghezzi, Antonio Miele, Matteo Miraz, Andrea Naggi, and Filippo Pacifici. "Hybrid service-oriented architectures." In the 5th international workshop. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1108473.1108487.

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

Bonetta, Daniele, and Cesare Pautasso. "Towards liquid service oriented architectures." In the 20th international conference companion. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/1963192.1963340.

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

Gkioulos, Vasileios, and Stephen D. Wolthusen. "Securing tactical service oriented architectures." In 2016 International Conference on Security of Smart cities, Industrial Control System and Communications (SSIC). IEEE, 2016. http://dx.doi.org/10.1109/ssic.2016.7571813.

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

"REPLICATION IN SERVICE ORIENTED ARCHITECTURES." In 3rd International Conference on Software and Data Technologies. SciTePress - Science and and Technology Publications, 2008. http://dx.doi.org/10.5220/0001874701030110.

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

Fredj, Manel, Nikolaos Georgantas, Valerie Issarny, and Apostolos Zarras. "Dynamic Service Substitution in Service-Oriented Architectures." In 2008 IEEE Congress on Services Part 1 (SERVICES-1). IEEE, 2008. http://dx.doi.org/10.1109/services-1.2008.52.

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

May, Nicholas R., Heinz W. Schmidt, and Ian E. Thomas. "Service Redundancy Strategies in Service-Oriented Architectures." In 2009 35th Euromicro Conference on Software Engineering and Advanced Applications. IEEE, 2009. http://dx.doi.org/10.1109/seaa.2009.59.

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

Street, Julie, and Hassan Gomaa. "Software Architectural Reuse Issues in Service-Oriented Architectures." In 2008 41st Annual Hawaii International Conference on System Sciences. IEEE, 2008. http://dx.doi.org/10.1109/hicss.2008.406.

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

Zhang, Xianan, Matti Hiltunen, Keith Marzullo, and Richard Schlichting. "Customizable Service State Durability for Service Oriented Architectures." In 2006 Sixth European Dependable Computing Conference. IEEE, 2006. http://dx.doi.org/10.1109/edcc.2006.8.

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

Reports on the topic "Service-oriented architectures"

1

O'Brien, Liam, Len Bass, and Paulo Merson. Quality Attributes and Service-Oriented Architectures. Fort Belvoir, VA: Defense Technical Information Center, September 2005. http://dx.doi.org/10.21236/ada441830.

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

Eugene, Robert. Retrofitting Applications Using Service-Oriented Architectures. Boston, MA: Patricia Seybold Group, October 2003. http://dx.doi.org/10.1571/bp10-16-03cc.

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

Eugene, Robert. Retrofitting Applications with Service-Oriented Architectures. Boston, MA: Patricia Seybold Group, October 2003. http://dx.doi.org/10.1571/bp10-2-03cc.

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

Michael, J. B., M. Shing, and D. Wijesekera. Forensic Capabilities For Service-Oriented Architectures. Fort Belvoir, VA: Defense Technical Information Center, February 2008. http://dx.doi.org/10.21236/ada477370.

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

Eugene, Robert. Building New Applications Using Service-Oriented Architectures. Boston, MA: Patricia Seybold Group, November 2003. http://dx.doi.org/10.1571/bp11-6-03cc.

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

Lenahan, Jack. The Data Warehouse in Service Oriented Architectures and Network Centric Warfare (Briefing Charts). Fort Belvoir, VA: Defense Technical Information Center, June 2004. http://dx.doi.org/10.21236/ada464283.

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

Lenahan, Jack. Are Service Oriented Architectures the Only Valid Architectural Approach for the Transformation to Network Centric Warfare? (Briefing Charts). Fort Belvoir, VA: Defense Technical Information Center, June 2004. http://dx.doi.org/10.21236/ada462299.

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

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

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

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

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

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

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Service-oriented architectures' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography