Note: This post was published in year 2013 Last month, the Revised Joint Submission SoaML for UPMS was submitted by several vendors to OMG. This was a highly anticipated submission for me, as I was eager to see what they were finally bringing to the table. The way they have approached modeling for SOA is particularly interesting. The submission defines a UML profile and metamodel for designing services in a Service-Oriented Architecture (SOA). The goal is to align it with a model-driven approach, and it is based on the UML 2.0 metamodel L2. Notably, they claim that it conforms to the OASIS SOA Reference Model. In this specification, services are represented using the "Package" notation. While all key aspects are covered, they have largely relied on existing UML symbols and notations to accommodate SOA concepts. Personally, this approach does not feel intuitive. The full specification can be found here: OMG Specification . I have doubts about whether this specification will t...