Documenting SysML Blocks

[Paul Boxall]

I’m using edDocX to create documents from a SysML model. In SysML Blocks (basically stereotyped classes – <<Block>>) are used to represent all kinds of items relating to a system. I would like to be able to create a specific eaDocX profile for certain ‘types’ of block, but this doesn’t seem possible?
I have tried…
Adding a second stereotype to the element, but this is not recognised in eaDocX, it only sees the first one – <<Block>>.
Adding a tagged value to distinguish the different ‘types’ of block, but I can’t create a profile based on a tagged value.

Any ideas?

[Ian Mitchell]

Hi Paul,
No way will this ever be fixed using the main functions of eaDocX. Everything works using an (element type + element stereotype) combination, so the whole thing would explode.
But don’t dispair.
There was a feature in v5 which uses little bits of script to basically do anything: print any bit of a Word document, ijn any style, using any bit of EA data, and using any rules you can think of. I have not yet put this into eaTeamWorks (nobody needed it until now) but as you have asked so nicely, I’ll find the code and put it back.
I will also use your example of a secondary stereotype of a <>Class as a test case.
But will take a few days to implement, so go on your holidays, and it will be ready when you get back.

[Paul Boxall]

Sounds good, thanks!

[Ian Mitchell]

Change of plan.
I have spent a few days looking into re-implementing Scripting into eaDocX, but it is not possible.
The mechanism we used to use to do this used a 32-bit Microsoft Script Control, which does not work with 64 bit EA.
Sparx have confirmed this as an issue, but there is not out-of-the box fix.
I investigated a third-party solution, but it was very unreliable.
So sadly, there is no solution to this issue.
Sorry

[Paul Boxall]

OK, thanks for letting me know.

[Author]

Posts