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

Mastering Trade-Off Analysis in System Architecture: A Strategic Guide for Architects

 In system architecture and design, balancing conflicting system qualities is both an art and a science. Trade-off analysis is a strategic evaluation process that enables architects to make informed decisions that align with business goals and technical constraints. By prioritizing essential system attributes while acknowledging inevitable compromises, architects can craft resilient and efficient solutions. This enhanced guide provides actionable insights and recommendations for architects aiming to master trade-off analysis for impactful architectural decisions. 1. Understanding Trade-Off Analysis Trade-off analysis involves identifying and evaluating the conflicting requirements and design decisions within a system. Architects must balance critical aspects like performance, scalability, cost, security, and maintainability. Since no system can be optimized for every quality simultaneously, prioritization based on project goals is essential. Actionable Insights: Define key quality ...
Post a Comment
Read more

Virtual environments in python

 Creating virtual environments is essential for isolating dependencies and ensuring consistency across different projects. Here are the main methods and tools available, along with their pros, cons, and recommendations : 1. venv (Built-in Python Virtual Environment) Overview: venv is a lightweight virtual environment module included in Python (since Python 3.3). It allows you to create isolated environments without additional dependencies. How to Use: python -m venv myenv source myenv/bin/activate # On macOS/Linux myenv\Scripts\activate # On Windows Pros: ✅ Built-in – No need to install anything extra. ✅ Lightweight – Minimal overhead compared to other tools. ✅ Works across all platforms . ✅ Good for simple projects . Cons: ❌ No dependency management – You still need pip and requirements.txt . ❌ Not as feature-rich as other tools . ❌ No package isolation per project directory (requires manual activation). Recommendation: Use venv if you need a simple, lightweight solut...
Post a Comment
Read more