Use of new Connector

[Oliver Michalski]

Hi all,
I develop a UML profile for SOA.Some components of the Profile are ServiceProvider, ServiceConsumer,
Service(a Port), ServiceGateway(a Port) and ServiceChannel (a new Connector)

ServiceChannel should be used only between elements of Type Services or ServiceGateway

My question is whether I can limit the use of a connector ?

Any Suggestions

Thanks
Oliver  

[Paolo F Cantoni]

Hi all,
I develop a UML profile for SOA.Some components of the Profile are ServiceProvider, ServiceConsumer,
Service(a Port), ServiceGateway(a Port) and ServiceChannel (a new Connector)

ServiceChannel should be used only between elements of Type Services or ServiceGateway

My question is whether I can limit the use of a connector ?

Any Suggestions

Thanks
Oliver  

Oliver, your profile looks very interesting.  But to answer your question, no, not directly.  

I had also intended to apply some similar rules.  However, I would do it via a MS-Access connection to the database and find those that didn't fit the rules (via queries) and highlight them (by changing their adornments - such as colour and thickness).

HTH,
Paolo

[Oliver Michalski]

Hi Paolo,

thanks  for the fast answer.  I will try it.

The profile has at present beta status.  After completion I will share the result with everybody interested person


Oliver

[Eve]

It's possible to limit the use of a connector using an add-in.

There is EA_OnPreNewConnector that allows you to disallow creation. http://sparxsystems.com.au/EAUserGuide/index.html?broadcastprenewconnector.htm

There is also EA_OnPostNewConnector that allows you to modify a created connector.

Simon

[Oliver Michalski]

Hi Simon,

thanks  for the good reference

Oliver  

[Paolo F Cantoni]

Oliver,

Don't forget that these methods are only part of the story.

You have established rules for what a connector may connect from and connect to.  These are, essentially, declarative - that is, they don't (or shouldn't) rely on any particular process.  Thus, as the connector and the end objects change, they may invalidate themselves.

A viable approach is to place the rules in a data structure and interrogate the rules whenever any of the component objects changes.  You can apply these rules at connector creation time as Simon says, but you'll also need to apply them at other times.  You need a consistent mechanism to apply the rules...

Consistency, Consistency, Consistency! ^TM

HTH,
Paolo

[Oliver Michalski]

Hi Paolo,

good objection

Thanks
Oliver  

[mikewhit]

A year ago I put in a Feature Request about model validation rules, but did not get a reply (or if I did and deleted it, it was "no plans for this").

[jeshaw2]

You might find this article helpful.

http://www.jot.fm/issues/issue_2004_11/column5

Cheers