Abstract
Useful systems depend on requirements analysis, of which data modeling is an essential part. Yet data modeling is often abandoned as a cumbersome and ineffective technique that cannot be understood by potential system users. Because the fault lies with the way the models are designed and not with the underlying complexity of what is being represented, guidelines regarding the way the models are constructed and their components named help ensure the creation of accessible models that are useful for both understanding a business and data base design.