• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Q&A

Q1:What is the best way to document a FileMaker solution?
A1: There are several ways to document a solution. The first and most basic way is to keep the specification document along with any revisions to it that have been made along the way. In large installations, there is a formal process for maintaining this documentation. In smaller environments, it's often a problem to find the time to do this sort of clean up. One way to handle it is to simply save all the documents and email messages that surround development. At some time, you can organize them into a coherent report. If you don't have the time, when you need to refer to them, you'll at least have the raw material.

Another excellent way of documenting a solution is to use the reports in FileMaker Developer, which is described in Hour 20, “Creating Solutions with FileMaker Developer.”

Q2:How important is it to have a test suite of data?
A2: For most FileMaker solutions, it's critical to create this body of data that you can use to validate the solution. If you have several people working on the project, the end-user is often a good candidate for someone to create the test data. Remember that you want a lot of data (for stress testing), common data conditions, and exceptional data. Often, preparing the test data results in modifications to the system specifications as people start to understand special cases that the software needs to address.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint