Skip to main content

SOA - SoaML

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 truly simplify SOA implementation. Even if it is adopted, I question whether it will genuinely help practitioners. From what I have seen, the specification does not introduce anything beyond the traditional object-oriented paradigm. It seems to have been designed primarily to work within the constraints of existing modeling tools, minimizing the need for tool vendors to make significant changes.

In my view, SOA is fundamentally different from the traditional OO paradigm. Its architecture and modeling approach should be designed in a way that is more accessible to business users, rather than being overly tied to existing object-oriented methodologies.

Labels:

Comments

Post a Comment

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...
Post a Comment
Read more

Examples 7: ArchiMate flow relationship between elements in layers

Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 20 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > title "ArchiMate 3.2 Valid Flow Relationships" left to right direction ' Business Layer Flow Relationships rectangle "Business Layer Flows" {     Business_Process ( bp1 , "Order Process" )     Business_Process ( bp2 , "Payment Process" )     Rel_Flow ( bp1 , bp2 , "Order data" )     note on link         Flow between Business Processes     end note         Business_Function ( bf1 , "Sales Function" )     Business_Function ( bf2 , "Delivery Function" )     Rel_Flow ( bf1 , bf2 , "Sales information" )     note on link     ...
Post a Comment
Read more

SmartSimpleTextGenerator: A Smarter Way to Generate Text

  Introduction In the world of text generation, simple n-gram models can produce decent results, but they often lack context-awareness and coherence. To address these limitations, I have developed SmartSimpleTextGenerator , an improved version of my previous project, ImprovedSimpleTextGenerator . This new version enhances the text generation process by integrating Part-of-Speech (POS) tagging , n-gram models , and a back-off strategy , making the generated text more meaningful and contextually relevant. Key Features of SmartSimpleTextGenerator ✅ N-Gram Model with POS Tagging – Uses trigrams (default n=3) and applies POS tagging for better word prediction. ✅ Back-off Strategy – If a trigram sequence is unavailable, it falls back to bigrams and unigrams to ensure smooth text generation. ✅ Sentence Tokenization & Structure Preservation – Tokenizes input text properly while maintaining sentence integrity. ✅ Randomized Word Selection – Generates diverse outputs rather ...
Post a Comment
Read more