I was playing with the tool in a sample project to see what the actual,
concrete realization would be in code, and I found that StarUML (with Java
selected as my preferred language) only generates code for class diagrams,
and nothing else, and furthermore, many of the model objects available
visually have no code counterpart. Is this a true limitation of the tool, or
is it because I'm working in the Design Model instead of the implementation
model?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently the language handling modules generate code for specified classes.
However as those modules are separate DLLs they can be modified, extended or
even completely replaced to meet concrete needs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was playing with the tool in a sample project to see what the actual,
concrete realization would be in code, and I found that StarUML (with Java
selected as my preferred language) only generates code for class diagrams,
and nothing else, and furthermore, many of the model objects available
visually have no code counterpart. Is this a true limitation of the tool, or
is it because I'm working in the Design Model instead of the implementation
model?
Currently the language handling modules generate code for specified classes.
However as those modules are separate DLLs they can be modified, extended or
even completely replaced to meet concrete needs.