![]() We propose an interprocedural dataflow analysis algorithm that determines precisely which objects are the receivers of certain messages, and assigns the appropriate diagram objects to represent them. A static analysis for such reverse engineering needs to map the interacting objects from the code to sequence diagram objects. This work considers the problem of extracting UML sequence diagrams from existing code for the purposes of software understanding and testing. UML sequence diagrams are commonly used to represent object interactions in software systems. One such technique that comes to mind is contained in the paper Object naming analysis for reverse-engineered sequence diagrams by Atanas Rountev and Beth Harkness Connell. If there is no plugin available, theoretically, one could follow the approach of such techniques to build one. I am not sure if there is a plugin for this but there are certainly techniques for doing this. In the preference one specify filters and filter the unwanted classes from the diagram.(repeat from How to Create Flowchart from java source code in Eclipse for completeness): These are not very useful in a sequence diagram. On very complex apps, especially those using JEE or Spring there are often quite a lot of layers and proxy classes. The entire stack frame will be put on the diagram. In a new sequence diagram right-click the debugger stack and select “add to sequence diagram”. Here’s where the sequence diagram shines. Once in the target class it can be tought to see the forest from the trees. From there stepping through the code dives deeper into the code. Quite often one know the entry point to a server call. The most useful to me is from the debugger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |