Get the most from Notes®

But how much is enough and when do you get to the point where you are simply documenting for the sake of documenting? Over documenting is all an extreme waste of time and money adding no value to the company. It’s difficult but you need to find the balance between business, technical and compliance requirements.

First thing to do is identify the type of documents that are required to support your application. It is divided into Master documents (updated with releases) and Release documents specific to each release. Once you are in agreement with the types of documents that need to be in your application suite, we can look at what content needs to be in each document. I'm going to throw out a list of the types of documents your application suite should consist of. Let me know what you think.

Application Master Documents

1. Security Document (Security management levels on the application.)
2. System Design (System architecture.)
3. Maintenance (Maintenance tasks associated with managing the application.)
4. Operational (Day-to-day operational activities that the application performs, agents, data transfers, etc.)
5. Version Management (How versions are managed in the application)
6. User Manual

Release Documents

1. Functional Changes
2. Test Plan and Test Scripts
3. Release Notes