I have found a multi-part documentation process very useful. First, for every change, we keep a record of the changes made with their purpose and details in a word document. We also keep copies of the definition files and any requirements documentation, and store the documentation in folders organized by date and/or project.
Second, we keep a master list of all changes as a quick reference so when the time comes to upgrade or research a previous change, we can quickly find the information we're searching for. Lastly, some people like to keep records of Remedy changes in the Change Request form, which is an excellent opportunity to utilize the functions for which Change is designed, however, the other forms of documentation kept on a separate system are essential in case you should lose your Remedy server for some reason. Jennifer Meyer From: T. Dee Sent: Thu 20-Mar-08 09:19 To: [email protected] Subject: OT: Documentation - Workflow, etc. I was wondering for those of you who do customizations, modifications, etc., how do you document your changes / workflow, etc. Thanks! _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
