How to document procedural programming?

Ended up going this route. – jrm82 Apr 1 '10 at 4:45.

You could use PSD(process structure diagrams) or NSD (Nassi Schneiderman Diagrams). I had to learn it for my first lessons of programming, before diving into OO and Java. It doesn't cover different aspects as UML, but it's starting point to visualize a procedural program.

Remember what UML stands for Unified Modeling Language. It's not just for modeling Object Relations, which I believe is a common misconception of UML. It can also be used for state diagrams, business processes, database schemas, ... See : en.wikipedia.org/wiki/Unified_Modeling_L... .

I recently used IBM's Rational Software Architect to convert State Diagrams into Perl. But for Perl we had to write our own translation files since Architect didn't include them for Perl. But if you are talking about C code, Architect has a built in feature to reverse engineer written code into a UML diagram.

I've used that feature for Java and it works pretty well and creates a Object Diagram. I haven't used it for C before, so I don't know if it will turn it into a Sequence, Activity or State Diagram. You can download the trial version of Software Architect and see if it works for your code.

1 ...and there are a number of other UML tools out there with free 'community' editions that might give you a taste. I've used the free version of Poseidon for this specific purpose several times. – DaveE Jan 22 '10 at 23:55.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.