1
Bugs and Issues / Re: Archimate Derived Relationships
« on: January 16, 2019, 05:11:21 pm »I seem to remember discussions in other threads about derived relationships and the many pragmatic challenges. Whilst other tools do attempt to support automatic derived relationships I can understand that the ambiguities of the spec and vagaries of different peoples' intentions would make such a feature extremely difficult to implement successfully.Yes, we need an easily referencable property to indicate a derived relationship (We hijacked the isLeaf field for a connector to do that - and also created some tagged values {for defining the type of derivation and other information))
What I think would be useful however would be for Sparx to be aware of 'manually' created derived relationships. As a modeler I could explicitly create the 'derived' relationships that I care about so that I can create simplified diagrams by excluding some intermediate elements. If those intermediate elements are shown however, the connector for the direct 'derived' relationships would be hidden (automatically, or perhaps by use of a filter).
This would require Sparx to:
- Understand when a connector is 'derived' (@Paolo - is that what you had in mind wrt the 'universal "derivation" indicator' ?)
- Be able to determine when there is an alternative (non-'derived') path between elements connected by such a 'derived' connector so that the derived path can be hidden
- Allow 'derived' connectors to be created within the strict connector syntax/model validation rules
We also use the new arc-to-arc relationships to indicate explicitly which relationships are derived by what means.
We assume that "all bets are off" with derived connectors - that is we don't implement strict syntax for them. As I said, the derivation rules are quite complex and a derived relationship that is valid at creation time may become invalid if one of the traversals is changed.
BTW, we sometimes show BOTH the derived and derivation paths on the same diagram. It's not a given that the derived arc should be hidden if the alternate path is available.
Paolo
Are Archimate derived relationships a property of the instances or a property of the class? I have element instances with derived relationships with no intervening instance. This is useful because sometimes I don't care about the application functions/processes for COTS applications but I do care about the application components (which will be deployed) and the application services (which will be used by business processes).
In terms of the tool I'd like to be able to manually add derived relationships that I care about with checking turned on. Bonus points for being able to create an automatic style for their display such as colouring them red.
I believe that there is a version of a fixed matrix floating around done by someone outside the committee but I couldn't find it just now. I'll have to have a look tomorrow and see if I can edit this post with a link to it.