What three (often conflicting) database requirements must be addressed in database design?
Database design must reconcile the following requirements:
• Design elegance requires that the design must adhere to design rules concerning nulls, derived
attributes, redundancies, relationship types, and so on.
• Information requirements are dictated by the end users
• Operational (transaction) speed requirements are also dictated by the end users.
Clearly, an elegant database design that fails to address end user information requirements or one that
forms the basis for an implementation whose use progresses at a snail's pace has little practical use.