Join GitHub today
Archimate 3 Specifications #61
So the last beta https://www.dropbox.com/s/koo42q3d9gxw288/plantuml.jar?dl=0
allows now this:
This will be released in next official release.
That's great. However, some icons are misaligned.
As an added note, I have a massive definitions file I include with every diagram that aligns the icons to the correct scope and colorizes the artifacts to match. There are 2 scopes commented out due to the missing icons. Is there any way you could make it more official as part of the PlantUml build (exact naming conventions not withstanding). Also feel free to ignore the macros.
I love the archimate notation, but not the official tools -- and have been writing a plantuml plugin for visio to help avoid having to use them. This update will help greatly in achieving that.
For renaming the icons:
archimate/strategy-capability --> OK
Does that make sense?
In terms of a change to syntax, it would be nice if I could type something like:
and that would produce the same result as:
I attached my definitions file a few posts up to give an indication of what I'm using to simplify my usage.
Example syntax could be:
Or simpler (but possibly too abstracted):
to give the same result as currently:
I hope that clarifies a few things.
Yes, that's perfect, thanks!
So in last beta https://www.dropbox.com/s/koo42q3d9gxw288/plantuml.jar?dl=0
Note that we treat #BUSINESS / #APPLICATION / ... as regular colors (it's just new color names to us).
So now the following examples are working:
Thanks for your tests, it really helps!
There are probably some other issues, so do not hesitate to post again here!
@arnaudroques Any chance committing (those) changes to GitHub instead of just providing binaries from a private DropBox?
https://github.com/plantuml/plantuml/commits/master does not seems to contain "individual commits" but "source backups" on each release :(.
Also the https://github.com/plantuml/plantuml/pulls seems to be totally ignored :( .
That's working great now. I also have some other suggestions.
2 important and useful features of Archimate are grouping and junctions.
The group should be handled the same way as an individual artifact with the arrow centered on the side it comes from rather than being constrained to the corners. Also, aggregate groups should have a dashed outline, composition groups a full line.
It would be nice if I could have the syntax to specify.
Junctions indicate decisions and parallel conditions and I would normally implement as below:
The problem with the new Archimate command is that it produces an error if I mix with Circle.
It would also be nice if we could have an Archimate specific syntax to create the Junctions:
Also that the border colour defaults to black in both cases.
I hope that explains the requirement adequately and is not too much of an ask.
@aadrian Yes, those changes will be committed in next release in GitHub. I understand that this way of working is strange, but right now, we are sticking to this. Sorry about that
About function, we are trying to minimize the number of keywords. For "archimate" keyword, there was no other option than adding a new keyword.
So now, you can have with last beta
Even if we focus on UML, we are happy to help Archimate users, as long as we can keep this consistent with UML diagrams.
That's great. I can live with using a macro for junctions now that allow_mixing is no longer necessary.
As a solution architect, my primary domain is software/data, and so most of my product specific design work is in UML--but I do often have to branch into TOGAF/archimate territory for integration designs or mapping and modelling boundaries between systems and concerns. This has always meant relying on multiple toolsets. Having always been a software engineer, code is where my strengths are (and a more native mindset) rather than drag and drop interfaces. As such, I really appreciate this project in how it allows me to 'code up' my diagrams and mix disciplines.
Thanks for this awesome service.