Recent posts

#11
General Archi Discussion / Re: Open Exchange Import issue...
Last post by objective1 - September 15, 2022, 23:03:46 PM
In response to your question   yes i'm sure...

but...

I updated to the most recent version,  and it works as expected.   so  old version. 

 thanx for your response, and sorry to waste your time...

:-)
#12
General Archi Discussion / Re: Archi 4.10 Released
Last post by Xiaoqi - September 15, 2022, 22:04:46 PM
Thanks, understood, believe it will be quickly gain "reputation".
#13
General Archi Discussion / Re: Archi 4.10 Released
Last post by Phil Beauvoir - September 15, 2022, 20:03:55 PM
That's the way it is with MS Edge and Windows. Eventually that version will gain "reputation" and will be OK.

See https://www.archimatetool.com/faq/#winsign
#14
General Archi Discussion / Re: Archi 4.10 Released
Last post by Xiaoqi - September 15, 2022, 19:57:24 PM
Thanks Phil, have downloaded the released version and just done the upgrading.

Through comparing the version, the 4.10Beta2 is 202209050940, while your formal release is 202209150946, so far working fine.

While, when I download this time using Microsoft Edge, strangely it's reported in the Downloads section that "Archi-Win64-Setup-4.10.0.ext isn't commonly downloaded. Make sure you trust Anchi-Win64-Setup-4.10.0.ext before you open it."

Believe Windows treats the file is too new, however, I need to double confirm to "keep" it so that it can be shown in the explorer. At the same time, I've used its feedback form to report it's safety.

Before I communicate with our architect team to broader upgrade, it would be better such kind of download warning can be disappeared ;-)

I put some screenshots for your reference.

Regards, Xiaoqi

https://feedback.smartscreen.microsoft.com/feedback.aspx
#15
General Archi Discussion / Re: Hide/show objects on view ...
Last post by rchevallier - September 15, 2022, 18:37:27 PM
Not hiding/showing, but a script to colorize elements based on a property value.
#16
General Archi Discussion / Re: Data modelling in Archimat...
Last post by rchevallier - September 15, 2022, 18:26:30 PM
You can also use a specialization instead of a property to specify cardinality
#17
General Archi Discussion / Re: Archi 4.10 Released
Last post by Phil Beauvoir - September 15, 2022, 17:59:42 PM
Quote from: xiaoqi on September 15, 2022, 17:57:57 PMBy the way Phil, shall I still need to download and upgrade as I'm using the 4.10 beta 2?

It would be best to do that as there is a small change in the code.

Phil
#18
General Archi Discussion / Re: Archi 4.10 Released
Last post by Xiaoqi - September 15, 2022, 17:57:57 PM
By the way Phil, shall I still need to download and upgrade as I'm using the 4.10 beta 2?
#19
General Archi Discussion / Re: Archi 4.10 Released
Last post by Xiaoqi - September 15, 2022, 17:57:05 PM
congratulations!
#20
General Archi Discussion / Re: Data modelling in Archimat...
Last post by Jean-Baptiste Sarrodie - September 15, 2022, 14:21:14 PM
Hi,

Data modelling in ArchiMate is a long story and there's no standard way of doing it because several conventions might exist. That being said...

The typical relationships used are specialization, composition, aggregation and association. By definition:
- composition is a [0..1]:n relationship (maximum one parent, but potentially none)
- aggregation is a n:n relationship, but I wouldn't use it for all n:n relationship as it implies that one data somewhat contains the other, and this is not always wanted.
- association implied no specific cardinality, and can be use whenever neither composition and aggregation do the job. So association can be used for both 1:1 and n:n.

There's no standard way to define cardinality because this notion doesn't even really make sense in ArchiMate (a Business or Data Object is neither a class nor an instance as it all depends on the usage). My approach is simple: don't use cardinality, but instead use self explicit relationships' name wich include both the semantic of the relationship and some hint of the cardinality. This usually makes it easier to read for non architects because Object-Relationship-Object can then be read as a sentense (e.g. "Customer --Creates multiple--> Order", "Order --Leads to only one--> Invoice"...). Of course, make sure associations are directed so that people know which way it points. This works especially well with conceptual/business models.

If you really have to (or want to) use cardinality, then store it in a property, and define a custom (and dynamic) label to make it visible in a view (e.g. "${name} [${property:Cardinality}]").

Regards,

JB