All base elements must be stored in the system. Derived elements, such as the employee year-to-date gross pay, may also be stored in the system. Data stores are created for each different data entity being stored. That is, when data flow base elements are grouped together to form a structural record, a data store is created for each unique structural record.
Because a given data flow may only show part of the collective data that a structural record contains, you may have to examine many different data flow structures to arrive at a complete data store description.
Figure illustrated below is a typical form used to describe a data store.
The information included on the form is as follows:
- The data store ID. The ID is often a mandatory entry to prevent the analyst from storing redundant information. An example would be D1 for the CUSTOMER MASTER.
- The data store name, which is descriptive and unique.
- An alias for the table, such as CLIENT MASTER for the CUSTOMER MASTER.
- A short description of the data store.
- The file type, either computer or manual.
- The format designates whether the file is a database table or if it has the format of a simple flat file. (File formats are detailed in Chapter 13.)
- The maximum and average number of records on the file as well as the growth per year. This information helps the analyst to predict the amount of disk space required for the application and is necessary for hardware acquisition planning.
- The file or data set name specifies the file name, if known. In the initial design stages, this item may be left blank. An electronic form produced using Visible Analyst is shown in the figure below. This example shows that the CUSTOMER MASTER is stored on a computer in the form of a database with a maximum number of 45,000 records. (Records and the keys used to sort the database are explained in Chapter 13.)