scholarly journals Appendix C: Service-Oriented Architecture: Example of an Implementation with ADP Best Practices

2007 ◽  
pp. 369-389
Keyword(s):  
Best Practices ◽  
Service Oriented Architecture ◽  
Service Oriented

scholarly journals A Method for Service Agile Construction

2014 ◽  
Author(s):  
Felipe Carvalho ◽  
Leonardo Guerreiro Azevedo ◽  
Gleison Santos
Keyword(s):  
Best Practices ◽  
Systematic Approach ◽  
Service Oriented Architecture ◽  
Distributed Teams ◽  
Agile Methods ◽  
Service Development ◽  
Agile Practices ◽  
Core Practices ◽  
Service Oriented ◽  
Acceptance Tests

Service-Oriented Architecture (SOA) and agile methods share common drivers. However, there is a lack of guidelines a SOA team should pursue in order to develop services considering best practices, acceptance tests, distributed teams, contract refactoring, among other issues related to SOA principles and agile practices. This work presents a new method that addresses team concerns and needs aiming at a systematic approach for service development using XP's agile practices and SOA principles. We provide best practices, phases and activities that specifically address XP's core practices and service-oriented best practices. We also provide an example of our proposal in order to demonstrate its applicability.

Service-Oriented Architecture Adoption

2010 ◽  
Vol 1 (2) ◽  
pp. 1-15
Author(s):  
Andrew P. Ciganek ◽  
Marc N. Haines
Keyword(s):  
Information Technology ◽  
Best Practices ◽  
Case Studies ◽  
Decision Model ◽  
Service Oriented Architecture ◽  
Business Environment ◽  
Key Factors ◽  
Service Oriented ◽  
Multiple Case ◽  
Multiple Case Studies

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.

Service-Oriented Architecture Adoption

2012 ◽  
pp. 271-284
Author(s):  
Andrew P. Ciganek ◽  
Marc N. Haines ◽  
William (Dave) Haseman
Keyword(s):  
Information Technology ◽  
Best Practices ◽  
Case Studies ◽  
Decision Model ◽  
Service Oriented Architecture ◽  
Business Environment ◽  
Key Factors ◽  
Service Oriented ◽  
Multiple Case ◽  
Multiple Case Studies

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.

scholarly journals Best Practice Service-Oriented Architecture (SOA): Recommendation and Tips

2011 ◽  
Vol 2 (2) ◽  
pp. 783
Author(s):  
Maria Seraphina Astriani
Keyword(s):  
Best Practices ◽  
Best Practice ◽  
Service Oriented Architecture ◽  
Application Integration ◽  
Business Goals ◽  
Service Oriented ◽  
Business Functions ◽  
Integration Problems

Companies that have many applications always deal with application integration problems. For the of company necessity, they often yearn for information that an application can be used by other applications. Often a small portion of data from another application is needed in order to complete and support other business functions. They require an architectural approach that can bridge the information between applications. SOA (Service-Oriented Architecture) offers manufacturing services around existing business functions. Applications that wish to communicate with other applications can use the services to achieve business goals. This article will discuss recommendations and tips for implementing SOA best practices in banking. 

Service Evolution and Maintainability

2010 ◽  
pp. 321-341
Author(s):  
Bijoy Majumdar
Keyword(s):  
Best Practices ◽  
Service Oriented Architecture ◽  
It Service ◽  
Service Evolution ◽  
Service Oriented ◽  
Good For

Change is the only constant, and this concept holds good for services too. Service maintenance is the most tedious and longest phase of service lifecycle. The more complex the service, the more difficult it is to maintain it. Service maintenance and service evolution mandate a series of best practices and selective models to apply for better execution and administration. In this chapter we detail the challenges faced in service evolution management and the key activities involved, and their role in service-oriented architecture (SOA) quality.

Sign in / Sign up

Export Citation Format

Share Document