INTERPRETING REQUIREMENTS - A Developer's Guide to Data Modeling for SQL Server - page 142

Attribute List
Each item on your entity list should have a corresponding attribute list.
Again, this may not be a complete list because you may still discover new
information or need to rearrange things as you implement your model.
This list should contain these items:

The name of the attribute

■

The attribute's data type and the data type length, precision, and
scale when applicable

■

The nullability of the attribute

■

A description of the data that will be stored in the attribute

■

Relationship List
You should also produce a relationship list that documents all the relation-
ships between all your entities. This list should include the following
information:

The parent entity of the relationship

■

The child entity of the relationship

■

The type of relationship (1:1, 1:M, M:M, etc.)

■

Any special cardinality rules

■

A description of the relationship

■

Business Rules List
Finally, you should include a list of the business rules you have determined
up to this point. As we discussed earlier, many of the business rules will be
implemented in the model, and some will be physically implemented only
in SQL Server 2008. This list should contain some notation as to whether
the business rule is a “modeling” rule. The list should contain these items:

The purpose of the business rule (e.g., encrypt credit card numbers)

■

A description of how the business rule will be implemented

■

An example of the business rule in practice

■

A flag as to whether the rule can be implemented in the model

■