TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I'm currently working on a project using SharePoint as a platform to customize a web app as a document repository and automated workflow processes. With other applications, we normally build out a full technical specification; however, with this project, we're performing mostly (or completely) out-of-the-box configurations to SharePoint. Our QA process requires this configuration changes to be documented in some manner. This will serve as a reference for future developers to understand what was done to the system. Does anyone here have any experience with documenting configuration-only changes into a technical document? How would you outline such a document?
Thanks!
Andy Tran
Associate Management Consultant
Blackstone Technology Group
Mobile: 571-451-4780
atran -at- bstonetech -dot- com <mailto:atran -at- bstonetech -dot- com>
www.bstonetech.com <http://www.bstonetech.com/>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Writer Tip: Create 10 different outputs with Doc-To-Help -- including Mobile and EPUB.