A simple architecture for the database design is to make a one to one correspondence between classes and files, i.e., each file represents a class in the object analysis. For example, the robot file represents the robot class and each of the robot subclasses has a corresponding file. This design facilitates data transfer between the files and the system (the memory). On the other hand, this strong coupling between the database design and the system classes violates the database design rule of trying to make the design independent of the application; however, if the object analysis is done independently of the application intended, then this coupling is not a problem.
Now, we need to determine the format to be used to represent the database contents and the relations between the files in this database. Figure 37 shows the suggested data files that constitute the database for the system, and the data items in each file. The figure also shows the relations between the files. The single arrow arcs represent a one-to-one relation, and the double arrow arcs represent a one-to-many relation.
Figure 37: Database design for the system.