Model WSDL with UML

Ash Parikh snd Rajesh Pradhan from iopsis software discussing about the "Providing compelling system benefits by applying the concepts of UML modeling methodologies for WSDL."
WSDL is an Interface Definition Language (IDL). It needs to be the starting point in the Web services life cycle. Thus, it needs to be well crafted, designed, and implemented. It needs the same respect as the other artifacts within the software system.
JAX-RPC allows creation of the Java interfaces from extant WSDL—the first step toward an interface-centric design. However, creating WSDL from scratch does not go down well with most developers, and rightly so.

The solution is using Unified Modeling Language (UML) to make the WSDL more meaningful. As we know, UML is a graphical language for specifying, visualizing, constructing, and documenting the artifacts of software ssystems.
The WSDL profile comprises stereotypes, constraints, and tagged elements. The modeling experience can be divided broadly into creation of two WSDL partitions: Platform-Independent Model (PIM) and Platform-Specific Model (PSM).
The PIM view represents the abstract portion of the WSDL, and includes WSDL elements such as definitions, service, portType, message, part, and partType. This PSM view completes the bindings section of the WSDL. The elements modeled here include service, port, and binding. The necessary and sufficient UML diagrams required to represent the two WSDL partitions are Class view for the PIM view and Class, Component, and Deployment view for the PSM view.
we can apply the concepts of UML modeling methodologies for Web Services Interfaces or WSDL to provide compelling system benefits: dramatic productivity improvement for architects and programmers, lowering the cost of application development and integration, enhanced portability and interoperability, and reuse of architecture widgets and capture of intellectual property.

read more
Google It