You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't recall any Archimate language semantics forbidding the use of dotted or dashed borders on elements (See 3.9 Use of Colors and Notational Cues). Grouping notation could be the closest possible conflict, but I don't believe this is a mandatory constraint of the language.
Adding border styles could help to express considerations more intuitively to various stakeholder groups, like how the Salesforce Diagram Framework uses to differentiate between conceptual vs. concrete elements.
(NOTE: The SF Diagramming Framework uses rounded edges on everything, even structural elements. I'm NOT interested in changing that, just noting the use of color and border styles to help create visual distinction).
The text was updated successfully, but these errors were encountered:
I don't recall any Archimate language semantics forbidding the use of dotted or dashed borders on elements (See 3.9 Use of Colors and Notational Cues). Grouping notation could be the closest possible conflict, but I don't believe this is a mandatory constraint of the language.
Adding border styles could help to express considerations more intuitively to various stakeholder groups, like how the Salesforce Diagram Framework uses to differentiate between conceptual vs. concrete elements.
(NOTE: The SF Diagramming Framework uses rounded edges on everything, even structural elements. I'm NOT interested in changing that, just noting the use of color and border styles to help create visual distinction).
The text was updated successfully, but these errors were encountered: