Started by Manj75, November 01, 2019, 14:01:50 PM
QuoteAn element in a View is nested inside of another element. However, this is only visual as the two elements do not have a semantic relationship in the model.The relationship between the elements should be either Composition, Aggregation, Assignment, Access, Realization, or Specialization.
Quote from: Phil Beauvoir on November 15, 2019, 10:25:14 AMSpecialization and Access were included in the Validator rules for reasons I can't remember.
Quote from: Manj75 on November 15, 2019, 07:50:10 AMBusiness Actor -> Assignment -> Business Role | Actor nested in RoleBusiness Function -> Triggering -> Business Event | Event nested in Function (I got it wrong in my first post when I stated Assignment)Business Function -> Serving -> Buisness Interface | Interface nested in FunctionApplication Function -> Triggering -> Application Event
Quote from: Phil Beauvoir on November 15, 2019, 11:37:55 AMI'm happy to make changes to the Visualiser rules, as long as there's consensus among users, and as long as things don't get too complicated.
Quote from: Manj75 on November 18, 2019, 11:03:35 AMOn the basis that my understanding above is now correct,
Quote from: Manj75 on November 18, 2019, 11:03:35 AMI believe that these should not be flagged up as Advisories in Archi, but instead should be Errors, following the specification strictly. Archi, itself would help to teach and consolidate the ArchiMate specification. If these were raised as errors then it would prompt to correct and if these are to be accepted then they could be configured to be ignored as per feature request stated by JB on github.
Quote from: Manj75 on November 18, 2019, 11:03:35 AMAlso, If the ARM feature request issue is to be developed - it would be ideal to have it configure on a per View basis rather than a global configuration, this will better fit with Archi being used Collaboratively.
Quote from: Manj75 on November 18, 2019, 11:03:35 AMBTW - can you tell me what ARM stands for (sorry if this should be obvious)