>>>>>
>>>>
>>>>How about Functional Description? That's what I'm using in a current project.
>>>>
>>>>Tamar
>>>
>>>If it is good enough for you, it should work for me too. And I like the way it sounds too. Thank you very much.
>>
>>I am going to disagree with Tamar, which I don't do very often. To me Functional Description implies a description of a system from the user's POV -- what it is supposed to
do. Screens, reports, menus, updates, etc. When you document a system's classes, methods, and properties you are describing the system's technical internals. It would be of no interest to end users or managers, only to developers.
>>
>>I don't know a better term for your document. Technical Documentation maybe?
>>
>>On your follow-up question about embedding flow charts and the like in a Word document, have you looked at Visio? It comes with some versions of Office as well as being for sale on its own. The last I knew there was a free 60 day trial version.
>
>The Technical Documentation is what I call the entire Word file that documents classes, methods, features, etc. Therefore, so far, I can't think of better term that what Tamar suggested.
>
>I think I did try Visio about 10 years ago. It was too complicated to learn. So I never went back. I am trying to cut down on my learning time <g>, so I was hoping something simpler and easier to learn.
Have you looked at download#
9428 ? It seems to be well-regarded - lots of positive comments.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up