Started by maksim aniskov, February 04, 2022, 13:52:17 PM
Quote from: maksim aniskov on February 04, 2022, 13:52:17 PMPlease help me to decide on how to approach the challenge. Do you think there is a better solution?
QuoteWell, Avoid 1 in all cases (raises lots of issues and make you rely on an internal format that change from time to time and will most certainly impact your work if any), try 2 because that's the easiest thing to work on and there's already a lot we can do with jArchi, but if it really doesn't work, then try 3.
Quote from: Alberto on February 04, 2022, 19:38:01 PMI haven't dealt with cloud yet as all my assets are on premise, but the problem is fairly similar... lots of assets, need to inventory them all, find the relationships, create views, keep the element in those views up-to-date. I usually leverage CSV imports only because I don't have the bandwidth to do jArchi or a plugin. What I've done so far:1) Create a reference model, keep track of how you define your real world assets/resources to archimate elements/specializations.2) Create properties to track data source, first created, last updated, etc. Leverage jArchi scripts to highlight in your views when elements are outdated or real world resource no longer exists.
Quote3) If you use multiple sources for your Archi model, define a strategy for element IDs and IDs for relationships that doesn't depend on ID is data sources. (e.g. ID for Node = device_OS_name+device_environment+"_node" guarantees me a unique ID that I can easily reuse when creating a relationship between nodes element and say communication_network or application_service element that are sourced from other places)
Quote4) Use jArchi script to remove all elements that don't exist on a view. This will keep the model lean and reduce the time of commits (if you are using a repo).