Model Language: SOAML (Service Oriented Architecture Modeling Language).
Overview:
SoaML is a standard profile introduced by OMG to extend UML with the ability to define the service structure and dependencies, to specify service capabilities and classification, and to define service consumers and providers. SoaML metamodel defines a Participant that can be a person, an organization, or a system in the business domain. It can be also an application or a component in the system domain. The role of the participant can be a consumer or a provider of a service. An Agent is specialized from a participant, which is an autonomous entity that is able to adapt with the environment. A Port is property of a Participant. It specifies the interaction point between the Participant, and the surrounded environment. A Port can be either a Service port when its participant offers a service or a Request port when its participant consumes a service. A Service interface specifies the interface of a participant to provide or consume a service. Collaboration describes the structure of the participant roles, and whether the bindings of the CollaboratioUse between the roles are enforced. Collaboration can be a ServiceContract which specify the agreement between the service providers, and service consumers, or a ServicesArchitecture which specifies how participants work together to provide or consume services using service contracts. A Service Channel is a communication path between service providers and service requests. A Property is structural feature that specifies an instance of a classifier to defined values. A MessageType specifies the information between the consumers and providers. An Attachment is a part of a message which is attached.
Target: Software
Sponsor: OMG (Object Management Group)
Website: http://www.omg.org/spec/SoaML/
Recommended Modeling Tools:
1. NetBeans SOA Project
2. IBM Rational Software Architecture (RSA).
Related topics:
Hi;
ReplyDeleteI don't see any advantage for SOAML with the UML. It is just using Composite structure diagram, component diagram, activity diagram and class diagram. So what is the point?
there isn't any additional views. All what they did is just introducing few stereotypes to the UML. Does any one agree with me?