Code to Diagram

In context of computer programming, code instrumentation refers to an ability to monitor or measure the level of a product's performance, to diagnose errors and writing trace information. Instrumentation is in the form of code instructions that monitor specific components in a system (for example, instructions that output logging information appear on screen). When an application contains instrumentation code, it can be managed using a management tool. Instrumentation is necessary to review the performance of the application. Instrumentation approaches can be of two types, source instrumentation and binary instrumentation from Wikipedia, 2010

Code to Diagram it is a project what intent to use code instrumentation and rich internet applications to improve the use of diagrams into projects and make easy keep them sync with the real code execution. To do that it is possible to create diagrams based on code executions, unitary tests, code files, xmls files, text files, etc.

To generate diagrams based on code executions it is necessary to make a call to a bootstrap file of the code to diagram engine, what will sniffer all the execution and based on the objects interactions will generate a diagram. But, to config more detail the diagram, changing the user-agent order, the user-agent type, append some note object, change style properties, etc. the user will need to deal with the code to diagram objects. In this page we will explain to you how to do it.

This tool is for the automatic generation of class diagrams based on the PHP code execution or recursive analysis of the PHP project folder. In the first case, just like the Sequence Diagram Generation, one full code execution or some stretch of execution it is monitored by classes of Code Instrumentation what, based on the in formations received, creating the diagram of that code execution. This diagram can be seen in browser and edited in browser, and also to be saved as XML, as a jpeg image and as XMI UML file.

With the recent changes into the PHP, as namespaces, the code instrumentation need to be updated. Maybe this will take a big time because. Until then, try generate diagrams of projects what use this new features probably will fail. Another option more trustable, simple and fast it is the creation of diagrams based on the results of the XDebug. That is the reason because the creation of diagrams based on XDebug become one of the priority features.

The Diagram Generation With XDebug still is in working progress. You can help to accelerate it making a donation.

While still not fully working on Internet Explorer, the generator already makes life easier for those responsible in maintaining this kind of diagrams. We welcome anyone with the patience and desire to make the CSS changes need for it to work on Internet Explorer.

Also, fully compliance with UML 2.0 is still under development. Anyone interested in working in these fields is more than welcome to join the team. And if you have a patch on add-on to send, feel free to do so. Just send an e-mail to me thiago.henrique.mata@gmail.com . And remember, this is free software, in development, and as such, I can give you no warranty. Use it at your own risk. It's not for the faint of heart. Tag names can and should change. New tags can be add anytime. Stay tunned for more news.