The type of Technical Documentation that Susan mentions is a part of DocuSys! Not only does DocuSys comb through basic code, and also the gamut of SB+ bits, but it sends it to MS Word - nicely formatted, with a table of contents, pagination, Styles, etc. Options include both User Documentation (for SB+ Apps) and Technical Documentation (SB+/Non-SB+).
This isn't really an ad, but DocuSys a really useful product/tool. If anyone would like more information, let me know! Laura Hirsh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn Sent: Thursday, June 28, 2007 7:59 AM To: [email protected] Subject: RE: [U2] Basic developments "reverse engineering" tool ? I was thinking of the sort of documentation that you could get from writing a utility to comb through code. I've written some (not for prime time) versions of this sort of thing. In particular whenever converting from one platform to another. The types of "technical documentation" that one can glean programmatically from an application are: What files are opened by what programs Where are records written What fields/amcs are read and written by what programs What subroutines are called by what programs What includes/inserts are in use, where In the case of SB+ (or any system where fields are referenced by name) - schemas can be built identifying field name across files and when and where these are updated What else? One thing that I have built into my application that I use rarely but when I need it I find it extremely handy - every one of my programs calls a subroutine at the beginning that just time-date stamps that it has been run. I think I keep the last five or ten runs in a Multivalue list. This helps when I want to clean up and find stuff that never gets run - or when I want to see the last time a customer ran something. I tiny little subroutine that you can stuff programmatically into a top line of all programs and let it go for awhile. Then come back and find interesting things. Susan ---------------- Date: Wed, 27 Jun 2007 11:33:17 -0700 From: "Tony Gravagno" <[EMAIL PROTECTED]> I don't believe there is a way to have a program read code and figure out what it does from a logical perspective. When you say "technical documentation", I'm not sure what sort of info you wish to extract from your code. If you mean file usage, common usage, etc, the only way to get a program to process such information is to make sure you have your code completely consistent - or you need to use meta data as described below. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
