- #EASY UML SEQUENCE DIAGRAM GENERATOR HOW TO#
- #EASY UML SEQUENCE DIAGRAM GENERATOR FULL#
- #EASY UML SEQUENCE DIAGRAM GENERATOR CODE#
- #EASY UML SEQUENCE DIAGRAM GENERATOR FREE#
I overrode this method to use my particular extractor if it was me running the code. There is a factory class/method CL_ATRA_UML_FACTORY that creates an instance of a class implementing the interface.
#EASY UML SEQUENCE DIAGRAM GENERATOR FREE#
Now, I’m sure that Borland and Altova have good products, it’s just that I don’t really want to spend money on then when there are perfectly good (for my tasks) free and open source products out there. There are classes for extracting to JNet, Borland Together and Altova. All of these routines implement the IF_ATRA_UML_TOOL interface. It allows the user to chose from a list of potential UML extraction routines. One does have to wonder why this has been done, but nevertheless it has. In customer systems there is a function module ATRA_UML_DECIDER that has been purposely handicapped. Only about 400 of those calls involved my code, so you can imagine generating a UML diagram for the whole 100,000 calls would be a bit of overkill (not to mention an impossible to read diagram).
#EASY UML SEQUENCE DIAGRAM GENERATOR HOW TO#
However, it does not allow you to do things like filter out standard SAP routines (as far as I know! If anyone can tell me how to do this (without needing to list every method I call, please let me know!) When I was looking at one of my examples, where I ran a program to generate a performance review document for an employee, there were over 100,000 different routines called. So in transaction SAT there is the possibility to generate your own JNet UML sequence diagram (this exists as standard.)
If you’re interested check out their website: Intercepting the SAP standard UML generation There are a bunch of other formatting features that can be used too. This feature I didn’t find on the other free UML tools that I looked at. See how it’s quite possible to show “internal” calls of an instance and also show the life time of those calls.
It has some awesome functionality for creating sequence diagrams, actually, most UML diagrams it seems, but it was the sequence diagrams that I was interested in. So a bit of browsing later and I found PlantUML. Given that interaction diagrams are only supposed to show external interaction it’s not surprising that most of the tools for creating the diagrams don’t really support this idea of internal object calls. if I make a call to a private method of my class, I’d really like that to show up in my diagram. However, the thing is, if I’m documenting my code, I’d really like to show the interaction within my objects too. Basically, interaction diagrams are supposed to show interaction between objects. There were loads there, and I’d pretty much decided on UMLet when I discovered something about interaction diagrams. Having had lots of fun in Sydney trying to make Gravity do something it really wasn’t designed for I thought I’d research how else I could get my interaction diagrams created. The first thing I decided, was that I was NOT going to try to build the graphical output myself. So in my “free time” in the evening I decided to see if I could recreate the solution that we’d built in Sydney, and perhaps make it a little nicer.
#EASY UML SEQUENCE DIAGRAM GENERATOR FULL#
So I now have a whiteboard full of post-it notes that represent potentially weeks of doco hell for me. Then the poo hit the fan, and everyone wanted everything done yesterday, and didn’t care about doco. At the beginning of the project, I was very good, and did all my doco as I went along. They all represent at least one development that I’ve done for the current project I’m working on. I have a whiteboard in the office covered in post-it notes.
#EASY UML SEQUENCE DIAGRAM GENERATOR CODE#
Here’s a link to the Prezi that I presented in that video:īut it was long time ago and the move to a new version of SCN has kinda buggered it up.Īnyway, in short – Rui Nogueira never managed to get the terms and conditions of CodeExchange changed to a level where I’m happy to support it and put code in there. Here’s a video of the solution we came up with: In staying true to my aversion for writing doco, I came up with an idea about auto-generation UML diagrams from SAP code. It was good fun, and people could build whatever the heck they wanted. InnoJam Sydney 2011īefore InnoJam had any of that fun fluffy design thinking aspect to it, we ran one in Sydney. And occasionally by doing the doco, I even find some small errors in my code that I hadn’t seen before. Most of them are supposed to save the customer money in the long run.
I think the above image is a not unjustifiable representation of my feelings about documentation:īut there are many good reasons that I should be doing doco. It’s kinda a mantra that I live a reasonable part of my life to.
0 kommentar(er)
