Database Analysis

One of the great beauties of FileMaker is that it's very easy to just jump right in and start building things that work. And this is fine, as long as you can keep the whole plan in your head.

Earlier chapters have looked at some practical techniques for separating and organizing data in a FileMaker database system. This chapter takes that work another step. Here you'll learn some tools for analyzing database problems and translating them into buildable designs.

This chapter approaches the idea of things and their relationships somewhat abstractly. Your goal here won't be a finished FileMaker system, but rather a more general design document. You'll learn a simple but powerful design process to help you take a real-world problem description and translate it into a blueprint that a database designer could use to build the database in a real-world database development system. This design document is known as an entity-relationship diagram . The process for creating an entity-relationship diagram, somewhat simplified, looks like this:

1. Identify all the different types of things that are involved in the problem that's being modeled (customers and sales, for example, or trucks , drivers, and routes).

2. For each type of "thing," identify its attributes (customers have first and last names , truck routes have a beginning and an end).

3. Looking across all the different types of "things," determine the fundamental relationships between them (truck drivers have routes, trucks have drivers).

4. Draw up your findings into an entity-relationship diagram (ERD).

The ERD, again, is an abstract document, that you could implement (build) with FileMaker or some other database tool. The sections that follow examine each of the steps of this process in much more detail.