Documenting interconnected systems

[Peter Kleczka <pkleczka -at- yahoo -dot- com>]

Techwrlers

I'm trying to figure out how to make 
a project easy to maintain/update.
The project involves creating documentation
that describes *all* the computer systems 
where I work. The systems range from 
legacy DOS applications, to mainframe, 
AS/400, Unix, NT Servers, and web-based 
applications. The documentation needs 
to describe the existing systems, 
how these systems interoperate, 
*and* how future proposed systems (that 
will be replacing some of the legacy 
systems) interoperate with all the 
other systems.

If you've worked on a project like this, 
how have you structured it so that its 
easy to maintain.  Is there perhaps a 
standard XML structure used for this 
type of thing?

TIA for your suggestions,
Pete (pkleczka -at- yahoo -dot- com)




__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems 
Available 4/30/01 at http://www.devahelp.com or info -at- devahelp -dot- com

Sponsored by DigiPub Solutions Corp, producers of PDF 2001 Conference East, 
June 4-6, Baltimore, MD. Now covering Acrobat 5. Early registration deadline 
April 27. http://www.pdfconference.com. 

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.