What Should Be on Each Form

Look at each form in the application as having a distinct job to do. Most applications have many different types of forms. All applications have a main form (also called a parent form), which comprises the application's frame. All other objects and forms are selected and displayed from the main form.

Again, VBScheduler is fairly simple, so it has only one form (the main form). If you create a multiform project, however, keep track of the forms you add to the project and document each form's purpose and contents as you go along.

Updating Documentation

As you create your application, update your documentation. Your application might contain different kinds of documentation. You might want to document the application internally with remarks so that you can more easily maintain the project later. Also, you might want to keep a notebook handy with form and control names and their descriptions so that you have a system documentation paper for the project.

End users need documentation as well. You should supply online help and ToolTips where appropriate. Also, write a user manual so that users can learn the program without your help. The best time to write the system and user documentation is during the design and development of the project.

Therefore, documentation is an ongoing task that isn't over until you finish the project. Even then, your users will suggest improvements that you'll want to track so that you can offer updated software and documentation periodically.