Service-Oriented Computing Track

Traditional approaches to software development — the ones embodied in CASE tools and modeling frameworks — are appropriate for building individual software components, but they are not designed to face the challenges of open environments. Service-oriented computing provides a way to create a new architecture that reflects components ’ trends toward autonomy and heterogeneity. Although the Web was initially intended for human use, most experts agree that it will have to evolve — probably through the design and deployment of modular services — to better support automated use. Services provide higher-level abstractions for organizing applications for large-scale, open environments. Thus, they help us implement and configure software applications in a manner that improves productivity and application quality. Because services are simply a means for building distributed applications, we cannot talk about them without talking about service-based applications — specifically, how these applications are built and how services should function together within them. The applications will use services by composing or putting them together. An architecture for service-based applications has three main parts: a provider, a consumer, and a registry. Providers publish or announce their services on registries, where consumer