Checklist: Data Model
This checklist helps make sure that the Data Model is correct and complete.
CollapseRelationships  
Related Elements
CollapseMain Description  


CollapseCheck Items  
Expand All persistent classes that use the database for persistency have been mapped to database structures  
Expand Many-to-many relationships have an intersecting table  
Expand Primary keys have been defined for each table, unless there is a performance reason not to define a primary key  
Expand The storage and retrieval of data has been optimized  
If a relational database is used, tables have been denormalized (where necessary) to improve performance.
Where denormalization has been used, all update, insert and delete scenarios have been considered to ensure the denormalization does not degrade performance for those operations.
Expand Indexes have been defined to optimize access  
Expand The impact of index updates has been considered in the other table operations  
Expand The distribution of data has been planned  
Expand Data and referential integrity constraints have been defined  
Expand A plan exists for maintaining validation constraints when the data rules change  
Expand Stored procedures and triggers have been defined  
Expand The persistence mechanism uses stored procedures and database triggers consistently