https://training-course-material.com/index.php?action=history&feed=atom&title=SoaML_-_ExtrasSoaML - Extras - Revision history2026-04-22T22:13:26ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=SoaML_-_Extras&diff=21410&oldid=prevBernard Szlachta at 14:56, 28 August 20142014-08-28T14:56:05Z<p></p>
<p><b>New page</b></p><div>{{Cat|SoaML|SoaML4}}<br />
<br />
== Connecting Services ==<br />
TODO: ServiceChannel, Assemply<br />
<br />
== Quiz ==<br />
A request:<br />
# is logically the ''conjugate type'' of the provider<br />
# is logically the ''conjugate type'' of the consumer<br />
<br />
A request:<br />
# is the ''use of'' the service interface<br />
# is the ''use of'' the request interface<br />
<br />
<br />
A ServiceInterface can be used to type:<br />
# only service port<br />
# only request port<br />
# both if used a conjugated type<br />
<br />
The <<Provider>> and <<Consumer>> stereotypes are used on:<br />
# Classes<br />
# Interfaces<br />
# Ports<br />
# CollaborationUse<br />
<br />
The isConjugated property must be set to true for which element:<br />
# Every Port<br />
# Service Port<br />
# ServiceInterface<br />
# Request Port<br />
<br />
Which of the elements below can type a port in SoaML?<br />
# Consumer<br />
# Milestone<br />
# Provider<br />
# Interface<br />
# ServiceInterface<br />
# Participant<br />
<br />
=== Further Questions ===<br />
* What kind of elements can appear on ServiceArchitecture?<br />
* What kind of elements can appear on ServiceContracts?<br />
* What kind of types a Service or Request can have?<br />
<br />
== Extra Exercises ==<br />
* Design a payment scheduling system (i.e. a person can schedule a payment for a specific date)<br />
** used vocabulary: payment, notification<br />
** Design Service Architecture<br />
** Design Contracts<br />
** Design interfaces<br />
** Design service choreography using:<br />
*** state machine<br />
*** activity diagram<br />
*** sequence diagram<br />
<br />
== Exercises ==<br />
# Design an ATM withdrawal:<br />
## service interfaces<br />
## ports<br />
## service contract<br />
## collaboration<br />
<br />
Vocabulary you can use:<br />
* Withdraw<br />
* Authorize<br />
* Validate Pin<br />
* Reject<br />
* Customer<br />
* ATM<br />
* Bank<br />
* Visa<br />
<br />
<br />
== Further Reading ==<br />
* http://www.omg.org/news/whitepapers/EnterpriseSoaML.pdf<br />
* http://www.omg.org/spec/SoaML/<br />
<br />
== Icons Cheat-sheet ==<br />
[[File:Soaml icons.png]]<br />
<br />
<br />
== Compound service contract ==<br />
<br />
[[File:Compound Services.png|300px]]<br />
<br />
<br />
Create a compund contract Purchasing Service.<br />
<br />
Vocabulary: Seller, Buyer, Place Order, Returns Service<br />
<br />
Show the ports on the consumers and the provider.</div>Bernard Szlachta