association class - reference many associations

[volenin]

Hi,

I'm trying to find a way to reference or attach an element (eg, association class) to more than one association. Couldn't find a way so far... Is this support in EA Sparx?

To clarify, here is a sample model I'm looking at:

Code: [Select]

CompositeA:
  ClassA1
  ClassA2
  ClassA3

CompositeB:
  ClassB1
  ClassB2
  ClassB3

Associations:
  L1: ClassA1 - ClassB1
  L2: ClassA2 - ClassB2
  L3: ClassA3 - ClassB3
  L0: CompositeA - CompositeB

I need to somehow be able to trace that L0 association on the level of composites can be 'split' or 'mapped' into L1, L2, L3 associations on the level of composite members. The model I'm looking at is much more complex and deals with traceability between composites and members, but the example above seems to be the 'least common denominator' for my problem. Any insight or approach would be highly appreciated.

Thanks,

Vlad

[Geert Bellekens]

Vlad,

I don't think an association class can be be linked to more then one association because in UML an association class IS an association (and it IS a class as well -> multiple inheritance)

What this sort-of looks like is association refinement/redefinition.
Or at leas that would be it if CompositeA would be a superclass of all your ClassA classes and CompositeB would be a superclass of all your ClassB classes.

Maybe you can use a constraint or a note to visualize the relation between the different associations.

Geert

[volenin]

It's not really quite for the purpose of visualization... The idea is to have an effective way to cross reference 'aggregate' relationships with 'more granular' relationships for the purpose of searching the model and 'walking' the model graph through scripts.

To elaborate, if you have a complex system, you'll describe the relationship (L0) between major systems ('CompositeA and CompositeB' in the example). Then when you go to more granular level, you'll elaborate how that relationship between major systems is realized through other relationships (L1-3) defined between the 'subsystems' (ClassA1-3 and ClassB1-3 in the example).

Eg, L0 may represent 3 various ways CompositeA and CompositeB systems can exchange the information - through SOAP interface, REST and raw TCP/IP socket. L1-3 would actually show the 'Point to Point' connections to the subsystems which realize this particular ways of communication. The example above does resemble composite elements, with ports & parts defined as part of the composite, but that approach doesn't exactly match my needs... So, looking for the alternative.

Vlad