A framework for information systems architecture
IBM Systems Journal
Computer
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Managing ontologies: a comparative study of ontology servers
ADC '07 Proceedings of the eighteenth conference on Australasian database - Volume 63
Patterns and technologies for enabling supply chain traceability through collaborative e-business
Information and Software Technology
A SOA-based embedded systems development environment for industrial automation
EURASIP Journal on Embedded Systems - Embedded System Design in Intelligent Industrial Automation
Refactoring J2EE application for JBI-based ESB: a case study
EDOC'09 Proceedings of the 13th IEEE international conference on Enterprise Distributed Object Computing
Towards a service-oriented methodology: business-driven guidelines for service identification
OTM'07 Proceedings of the 2007 OTM confederated international conference on On the move to meaningful internet systems - Volume Part I
Software characteristics of SOA projects
Proceedings of the 11th International Conference on Product Focused Software
A Scalable Healthcare Information System Based on a Service-oriented Architecture
Journal of Medical Systems
Applying an ontology approach to IT service management for business-IT integration
Knowledge-Based Systems
Design of service-based systems with adaptive tradeoff between security and service delay
ATC'07 Proceedings of the 4th international conference on Autonomic and Trusted Computing
| Hi-index | 0.00 |
One of the year's biggest buzzwords is service-oriented architecture. An introduction to SOA's concepts can help answer one of its biggest questions-"What is a service?" When architects, developers, designers, and clients agree on a definition of service, the question is then how to define the service. Commercial developers have many available options, and the rapidly evolving Web Services standards are giving service definition a structure. However, challenges remain in defining services beyond simple interface and data types, and tool vendors need to solve problems. If a service canýt define its security, availability, integrity, and environment, we're no nearer an acceptable definition of service than we were 10 years ago. Without a true service-level agreement, how can we measure quality?