|
Amarco as an UML extension for high
level SOA analysis
Amarco can be seen as an UML extension enabling high level service
oriented analysis for information systems:
- There is a definite compatibility between UML models and that
supported by Amarco
- There are some additions that bring an exclusive added value
enabling complex system analysis
Amarco Tools does not target object oriented code generation.
Accordingly it makes use of a limited set of diagrams, but enforces the
cross relationship between them
Model compatibility
| Activity diagram |
The activity diagram shows the services exchanged between
the systems |
| Sequence diagram |
This diagram is automatically derived from the activity
diagram |
| Deployment diagram |
In Amarco, this diagram relates to a system organization. It
shows how various components exchange services |
| Component diagram |
The component are "systems" linked with "service points" |
This models are enforced in Amarco Tools by storing the information
in a database and produced by automatic diagramming using Visio.
The other UML diagrams can be produced using the Visio integrated
features, if required.
Added value in Amarco
Amarco targets high level system architecture for complex systems. It
extends the current analysis tools and concepts with:
| The composition model supported in Amarco is quite similar
in functionality to the composition model that will be available
in UML 2.0. Also the notion of ports (alias "service points" in
Amarco) is equally introduced. You may see an interesting
article about this in this reference: Conrad Bock: "UML 2
Composition Model", in Journal of Object Technology,
vol. 3, no. 10, November-December 2004, pp. 47-73,
http://www.jot.fm/issues/issue_2004_11/column5 |
- It introduces the notion of "service point" that gathers related
services. This information chunk simplifies system analysis and
visualization
- It used the notion of "requested service" and "rendered service"
when analyzing the interaction between systems
- A recursive decomposition / assembly enables the definition of
high level components and readies them for reuse
- The "external architecture" and "internal architecture" views of
a system shows the system static organization
- The services show the system behavior. They are used as
component parts for processes.
|
 |
|
