Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Yeah maybe but if you look at all the ArchiMate element options its looks like the best fit. Could have put CLR to be more equivalent to JVM I guess.
You can put the versions in either the name such as ".Net Framework V.4.7.1" or in the version field of the element.
Draw up some diagrams that show the that Application A consists of .Net Framework connected via a link. The valid relationships can be found in B5 of archimate spec V3.1. between Application Component and System software are limited to vtfo or the other way its rvtfo. So out of those choices you could use association.
From https://www.omg.org/ocup-2/documents/Meta-ModelingAndtheMOF.pdf: "any UML modeling tool can be used to model metadata more easily".
I wonder, why these tools are not able to import mof-files and create the corresponding viewpoints.
Sure. It's just me... I'd ask for change. A tool should be right from the beginning. A car dealer would not sell cars with handbrakes stripped down by cable ties so you have to cut them before driving. Why is Ian asking "Make EA user friendly"? Because it is not user friendly. Simple, isn't it?
Any hint when the forum server will respond in non snail mode again?
Have a look at Labnaf: www.labnaf.one
If I keep spruiking new EA features maybe over time you'll have sufficient evidence to convince someone you do need the upgrade.
Yes, it does. In the new diagram dialog the viewpoints are available as nodes under the base diagram types. By default EA comes with all the viewpoints that the ArchiMate specification defines in Appendix C. Custom metamodel views allow you to define any of your own. They limit the toolbox to the specified types and optionally allow filtering the diagram to only show matching elements (if you've added them before or dropped them from somewhere else)
By default the ArchiMate technology offers 5 diagram types corresponding to each layer. If you don't select a view (expanding the diagram node in the diagram dialog) the toolbox will offer all the elements and relationships in that layer. If you select a view all it's doing is clearing the clutter to help express a limited aspect of the model. On top of the default views that ArchiMate describes you can also create your own views to assist in expressing the architecture in ways not covered by the default views.
What "standard folder structure" are you referring to? From my reading of the specification there is no description of folder structure. EA is much more flexible in that regard because it supports arbitrary structure. If you're just looking for a list of your elements by type, maybe the Model Views window (in the Portals in 15) will help. With that you can have folders that perform searches on your model. One possible use of that would be to list all ArchiMate elements in your model by type.
I cannot see there is linked information behind an element unless i select the element, and it shows the 'eye'. This will not work for me, which is why we have been thinking about hyperlinks.
