1. Guidelines Towards Good Design
Convey “real” application requirements
Utilize meaningful names
Try simpler construct first
Avoid redundancy
Be as precise as possible (constraints)
Don’t over specify (limits input)
CS542

2. Coming up with a good design for your application
Give good names to entity types, relationship types, attributes and roles
CS542

3. Good Design: Attribute or entity type?
Should we represent something as an attribute or entity type?
(or)
How should dept be represented?
CS542

4. KISS Principle: Keep It Simple Stupid
Do not introduce unnecessary entity types
(or)
Is Entity type Contract
Un-necessary ??
CS542

5. Good Design: Determine correct cardinality constraints
CS542

6. Good Design: Try to avoid redundancy
Any Redundant attribute ?
Attribute dNum is redundant
CS542

7. Good Design: Try to Avoid redundancy
Any Redundant relationship type ?
Relationship Type IsObtainedBy is redundant
CS542

8. Towards a Good Design Convey “real” application requirements
Utilize meaningful names
Try simpler construct first
Avoid redundancy
Be as precise as possible (constraints)
Don’t over specify (limits input)
CS542