<<As development teams strive to find the best way to construct an SOA, a model-driven approach must be considered. Long regarded as an effective means for raising the level of abstraction in software development, modeling is extremely useful for the creation of service-oriented solutions, which rely on a variety of underlying implementation technologies and standards.
The following article presents a framework for a model that allows designers and architects to specify the right services with the right capabilities, and thereby realize the potential benefits of a Service Oriented Architecture (SOA). Specifically, we will look at the importance of service identification and specification, managing a service portfolio, and partitioning service-oriented solutions as necessary elements for any SOA development. We will then look at three different approaches to the development of services when using modeling, with hopes of providing readers with a practical guide for leveraging the power of modeling for service-oriented solutions. Service identification and specification First of all, key SOA concepts must be presented through the model as first class elements. Although one of the key concepts is the service itself, it actually becomes a secondary element in the model. To construct a model that reflects a WSDL (Web Services Description Language)-defined service, we have to first develop a a set of service specification elements –structural, behavioral and policy. For example, an order management service might include structural specifications that list "place order," "cancel order," and "update order," as available operations. The behavioral specification for this ordering service might then describe how you cannot update or cancel an order you did not place. A policy specification may require that certain elements of the order are to be encrypted, denoting the encryption techniques to be used, certificates to use, etc. Another important aspect for the development of an SOA model is the identification of services.. This allows architects and designers to produce a model of specifications that describe "idealized" services, which would realize either a process or set of requirements. These services are then refactored to 1) fit with existing services, 2) fit within the framework of an existing functional architecture, or 3) be separated out to allow for more fine-grained or parallel development.>> You can read this at: <http://searchwebservices.techtarget.com/tip/1,289483,sid26_gci1168687,00.html?track=NL-110&ad=543674> Gervas Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
