Thread: Execution Sequence in C

I have been assigned to a project where all the source code is in C.All though the business logic is well documented but how the same maps on to source code as which function gets called etc needs to be traced. While this tracing is easy is there a good way to document the same? Like for example after generating the sequence of execution(function calls) for a set of business rules is it possible to document in a comprehendible manner in say Rational or Star UML tools.Which would be the most professional way of doing it ?

I would say documenting your c code functionality as mapped against your business logic, or "use cases' would be ideally suited for UML. Perhaps something like below may help guide you:

Dr. Dobb's | UML for C Programmers | May 1, 2005

and this

Step-by-Step Guide to Reverse Engineering Code into UML Diagrams with Microsoft Visio 2000