Why Or Why Not Service Oriented Architecture

[[abstract]]Service Oriented Architecture (SOA) is a new computation technology in these years. Though this architecture, business application can be wrapped as loosely-coupled component. Base on business needs, connecting different component into necessary services of real process, enterprise can utilize existing applications repeatedly, then integrate the independent applications into new services. This paper focused on the issues on which enterprise needs to consider before implementation of SOA. We have a further discussion on advantages and disadvantages for adopting SOA. Once SOA is implemented what we need to care about? It is helpful on your long term success if you can thoroughly understand the key points of this paper, then the enterprise can well evaluate if its information system needs to adopt SOA.[[conferencetype]]國際[[conferencelocation]]Zhangjiajie, Chin

The Influence of Green Strategies Design onto Quality Requirements Prioritization

[Context and Motivation] Modern society is facing important challenges that are critical to improve its environmental performance. The literature reports on many green strategies aimed at reducing energy consumption. However, little research has been carried out so far on including green strategies in software design. [Question/problem] In this paper, we investigate how green software strategies can contribute to, and influence, quality requirements prioritization performed iteratively throughout a service-oriented software design process. [Methodology] In collaboration with a Dutch industry partner, an empirical study was carried out with 19 student teams playing the role of software designers, who completed the design of a real-life project through 7 weekly deliverables. [Principle ideas/results] We identified a list of quality requirements (QRs) that were considered by the teams as part of their architectural decisions when green strategies were introduced. By analyzing relations between QRs and green strategies, our study confirms usability as the most used QR for addressing green strategies that allow to create people awareness. Qualities like reliability, performance, interoperability, scalability and availability emerged as the most relevant for addressing service-awareness green strategies. [Contribution] If used at the beginning of a green software project, our results help including the most relevant QRs for addressing those green software strategies that are e.g. the most domain-generic (like increase carbon footprint awareness, paperless service provisioning, virtualization)

The Impact of Service Oriented Architecture (SOA) on IT Auditing

Executive Summary This study investigates the impact that SOA has on IT Auditing. Service-oriented architecture emerged as new technology in literature since 1996 and it has been a hype in the Netherlands between 2006 and 2007. The development of new technologies is faster than the developments in IT auditing profession. IT auditors have stated in interviews that they are aware of the impact that SOA has on their profession and that SOA will need another audit approach, because the environment is different than the traditional IT environments on which audit programs are based on. Auditing SOA is a complex process, but by approaching it from the business processes and stages in the Software Development Life Cycle process, the auditor can gain more insights to audit this complex environment

Factors Affecting The Organizational Adoption Of Service-Oriented Architecture (Soa)

Service-oriented computing is an emerging IT innovation. Among its manifestations is service-oriented architecture (SOA), an architectural approach to designing and implementing IT solutions. Academic empirical research on SOA adoption is scarce, with many studies focussing on qualitative analysis. The purpose of this study is to explore SOA adoption using a quantitative approach. This study investigates organizational SOA adoption in South Africa from DOI theory and TOE framework perspectives. A comprehensive model of SOA adoption is presented along with an associated research instrument. In order to validate the instrument and to gauge the state of SOA adoption, an online survey was conducted among South African organizations. The results of the survey highlight a number of factors influencing SOA adoption. Use of multiple standards and platforms, complexity, compatibility, cost, top management support, good governance and strategy, adequate human and financial resources, vendor support for integration and development tools are all significant factors for a fruitful SOA implementation. The findings of this study can contribute to the body of knowledge on organizational SOA adoption and create opportunities for future related research in this field

Balancing between Local Requirements, Interoperability Standards, and SOA principles ‐ Case eBooking of Health Services

Service‐oriented architecture is an attractive development approach for flexible and reusable healthcare IT solutions. However, there are many practical architectural challenges in developing Service‐Oriented Architectures (SOA) in organizations. In practice, not all basic SOA principles can be easily followed using vertical standards and local adaptation is typically needed. In this paper, we discuss balancing between vertical interoperability standards, local requirements and SOA principles. We classify different types of conflicts between these elements and analyze healthcare electronic booking solutions as a case example. The establishment of inter‐organizational interoperability solutions requires agreements on many levels, and open vertical standards such as HL7 combined with horizontal industry standards provide solutions to many of these levels. SOA based interfaces using vertical industry standards and models are good starting points, but they must be further refined to guarantee interoperability and fit for local requirements

Participant Domain Name Token Profile for security enhancements supporting service oriented architecture

This research proposes a new secure token profile for improving the existing Web Services security standards. It provides a new authentication mechanism. This additional level of security is important for the Service-Oriented Architecture (SOA), which is an architectural style that uses a set of principles and design rules to shape interacting applications and maintain interoperability. Currently, the market push is towards SOA, which provides several advantages, for instance: integration with heterogeneous systems, services reuse, standardization of data exchange, etc. Web Services is one of the technologies to implement SOA and it can be implemented using Simple Object Access Protocol (SOAP). A SOAP-based Web Service relies on XML for its message format and common application layer protocols for message negotiation and transmission. However, it is a security challenge when a message is transmitted over the network, especially on the Internet. The Organization for Advancement of Structured Information Standards (OASIS) announced a set of Web Services Security standards that focus on two major areas. “Who” can use the Web Service and “What” are the permissions. However, the location or domain of the message sender is not authenticated. Therefore, a new secure token profile called: Participant Domain Name Token Profile (PDNT) is created to tackle this issue. The PDNT provides a new security feature, which the existing token profiles do not address. Location-based authentication is achieved if adopting the PDNT when using Web Services. In the performance evaluation, PDNT is demonstrated to be significantly faster than other secure token profiles. The processing overhead of using the PDNT with other secure token profiles is very small given the additional security provided. Therefore all the participants can acquire the benefits of increased security and performance at low cost

A Governance Reference Model For Service-oriented Architecture-based Common Data Initialization A Case Study Of Military Simulation Federation Systems

Military simulation and command and control federations have become large, complex distributed systems that integrate with a variety of legacy and current simulations, and real command and control systems locally as well as globally. As these systems continue to become increasingly more complex so does the data that initializes them. This increased complexity has introduced a major problem in data initialization coordination which has been handled by many organizations in various ways. Serviceoriented architecture (SOA) solutions have been introduced to promote easier data interoperability through the use of standards-based reusable services and common infrastructure. However, current SOA-based solutions do not incorporate formal governance techniques to drive the architecture in providing reliable, consistent, and timely information exchange. This dissertation identifies the need to establish governance for common data initialization service development oversight, presents current research and applicable solutions that address some aspects of SOA-based federation data service governance, and proposes a governance reference model for development of SOA-based common data initialization services in military simulation and command and control federations