This kind of the table is also called Function-Entity Matrix in [18]. According to this modeling technique, the entries in row 0 contain transaction names. The entries in column 0 contain object class (or entity type) names. The other entries contain CRUD strings: a string containing zero or one occurrences of the characters C, R, U and D, and that does not contain any other character. To separate row 0 and column 0 from the rest, the initial table separates them from the rest by a dual line. The editor does not check for that layout, however.
In [18] it is shown how you can define business areas in a function-entity type table. To draw business areas in TFET you could use the Update Surrounding Lines in the Table menu. See figure 7.8 for an example table. Currently, the editor checks the constraints in figure 7.7.
