Originally posted by Satya
I've used this tool earlier.
thanks for the quick reply,
but I have to write in details about the use of the table and the logic used in the stored procs also.
I'll go thru the software, is there any specific format for documenting?
documentation is already there, basic, maybe even primitive, but is there, in diagrams. if one was too lazy to write it as the app was being developed, doing it when everything else is done is going to be a project in itself. when this is the situation, you can use something as simple as copy con from dos prompt, or as sophisticated as robohelp office or er/studio or visio. the tool does not make any difference for as long as features of the tool will adequately describe what you got.
Originally posted by Brett Kaiser
Documentation, is documentation.
It is painful.
If the code's not clean, it's even more painful.
Sorry...been there, done that.
And that's just the sprocs...
Do you need to a data model as well?
What about an application process model?
And what did you do wrong to get this assignment?
yeah the format is jsut similar to what i am currently using.
The real thing is in the process flow at places the code is worst this part is driving me crazy.
The application process model is to be documented by another guy
but yeah i do have to have the data flow diagrams
what i do wrong???
well that is a question i am been thinking of since yesterday