A Service-Oriented Architecture for Web Applications in e-Mental Health: Two Case Studies

Author(s):  
Frank J. Blaauw ◽  
Ando Emerencia
Author(s):  
Tom Yoon ◽  
Bong-Keun Jeong

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.


2002 ◽  
Vol 39 (5) ◽  
pp. 523-539 ◽  
Author(s):  
Rakesh Agrawal ◽  
Roberto J. Bayardo ◽  
Daniel Gruhl ◽  
Spiros Papadimitriou

Author(s):  
Yusuf Lateef Oladimejia

The realisation of Service-Oriented Architecture (SOA) to communicate data between systems running on different platforms lack an organised framework to capture the essential elements required for successful interoperability between web applications and their services. In this work, a SOA for Data Interoperability in Web Applications (SOADIWA) was designed. The architecture of SOADIWA was based on five layers, namely Web Application Layer (WAL), Quality of Service Assurance Certifier Layer (QoSACL), Web Service Layer (WSL), Visualization Input Layer (VIL) and Visualization Output Layer (VOL). In WAL, the Service Requester (SR) initiates a request for data from the Service Provider (SP) through the QoSACL to provide appropriate website via WSL for rendering of services which must be accepted, processed and returned for a particular need in VIL. The requested data is filtered in VIL for data exploration and analysis in VOL using context-sensitive visualization techniques. The purpose of QoSACL is to check and verify the claims made by the SP about its quality of service. This enabled the SR to choose the service that satisfied its needs. The implementation comprised of Java Script, Microsoft Visual Studio 2017 and NuGet packages; while the experiment was simulated on LoadUI pro application. Standard metrics such as Optimal Performance (OP) and Phased Effort Distribution (PED) were developed to test SOADIWA. These results conformed to basic web service interoperability. The work led to the integration of a host of techniques towards the creation of a novel tool that is useful in web domain using SOA approach.


Author(s):  
Karyn Welsh ◽  
Kim Hassall

Businesses use many portals and for a variety of reasons. Some portals are used for inter-organisational collaboration between suppliers, buyers, and customers or as electronic marketplaces for users to browse and search for genuine savings in the purchase of goods or services. Portals support interorganisational networks by defining function and content on the basis of the customer process, and provides availability to the user via role-based and personalised interface while e-markets offer to the user a restricted or open view of the products and services on offer. Each profile is determined by the participant or its administrator. Today’s portal technology, paired tightly with tools and services, support user activity in an integrated way. The use of portals is still in its infancy among a number of organisations while early adopters are at the point of experiencing some genuine rewards. Portal technology provides a modular service-oriented architecture for integrating content and services and for managing user profiles and security settings from other systems. Portal technology provides customers the basis for constructing, building, and deploying a variety of Web applications designed to meet the changing business requirements.


Author(s):  
Andrew P. Ciganek ◽  
Marc N. Haines

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.


Author(s):  
Naijun Zhou

A geospatial portal is a repository of distributed geospatial data, tools and services, and supports the publishing, management, search, use and sharing of the resources. Geospatial portals have been developed as clearinghouses, metadata portals, data warehousing, and recently geospatial portals incorporated the Service Oriented Architecture and distributed computing to make service-oriented portals. In addition to software and computational challenges, ontology and semantics play an increasingly important role in geospatial portals due to the demand of interoperability. The interoperation and communication of data, tools and services become critical when heterogeneous resources are consolidated and exchanged on geospatial portals. This chapter provides an updated overview of geospatial portals followed by detailed discussion on how the ontological and semantic technologies are incorporated into geospatial portals. Three recent research and practice of geospatial portals are briefly introduced as the case studies of service-oriented portals.


2016 ◽  
pp. 277-298
Author(s):  
One-Ki (Daniel) Lee ◽  
Roger Blake ◽  
Deepa Varghese Baby

Global Information Technology (IT) projects span multiple locations that are typically employing different practices, adhering to different standards, and using different technologies – at the same time operating in highly diverse cultures. Differences such as these are prevalent factors that increase risk on global IT projects. Further, they are prone to changing continuously over the course of a project, with the consequence that risk becomes highly unpredictable and dynamic. This chapter proposes a framework to characterize risks within the people-process-technology-external elements of a global IT project. The framework gives particular consideration to risks that arise from interactions of multiplicities within and between those elements (i.e. dynamic risks). The principles of Service-Oriented Architecture (SOA) are adopted to propose specific strategies for mitigation of these dynamic risks. Two case studies further illustrate how those strategies can mitigate the risks.


Author(s):  
One-Ki (Daniel) Lee ◽  
Roger Blake ◽  
Deepa Varghese Baby

Global Information Technology (IT) projects span multiple locations that are typically employing different practices, adhering to different standards, and using different technologies – at the same time operating in highly diverse cultures. Differences such as these are prevalent factors that increase risk on global IT projects. Further, they are prone to changing continuously over the course of a project, with the consequence that risk becomes highly unpredictable and dynamic. This chapter proposes a framework to characterize risks within the people-process-technology-external elements of a global IT project. The framework gives particular consideration to risks that arise from interactions of multiplicities within and between those elements (i.e. dynamic risks). The principles of Service-Oriented Architecture (SOA) are adopted to propose specific strategies for mitigation of these dynamic risks. Two case studies further illustrate how those strategies can mitigate the risks.


Author(s):  
Andrew P. Ciganek ◽  
Marc N. Haines ◽  
William (Dave) Haseman

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.


Sign in / Sign up

Export Citation Format

Share Document