Questions to ask yourself to get started:
- What is the purpose of your db?
- What are the unique categories/tables/entities in your db?
- What fields/attributes does each table have?
- What are your key fields (primary & foreign)?
Create a Relational Database Logical Design to include:
Normalization (Justification as to how duplication was avoided),
Use any tool that you want for the ERD, but insert a .jpg (or equivalent file type) into your final document. One tool you might choose to use can be found in the “ER Diagram Templates” section at: http://creately.com/blog/diagrams/er-diagrams-tutorial/ . Another option that provides the ability to save your file as a jpg/gif and to use the Crow’s Foot Notation is: http://www.edrawsoft.com/entity-relationship-diagrams.php. In the reference section at the bottom of this document, other ERD tools and references are provided.
In your ERD, show entities, attributes, foreign key/primary key, relationships and cardinality. If any item needs further clarification, do this below the ERD.
Entities: Show entities in a rectangle. You must show >=3 entities.
Cardinality: use Crow’s Foot notation: http://www2.cs.uregina.ca/~bernatja/crowsfoot.html
Attributes: the cs.uregina site shows the attributes inside the entities. You can use this method, or show attributes in ovals as the creately.com site shows. You must have at least 3 attributes per entity
Foreign Key/Primary Key: below your ERD, provide a key to explain how you are notating foreign and primary keys.
Relationships: again, the two references show relationships differently. You may use either method. You must create >=2 relationships
Other: Remember, if any item in your ERD needs further clarification, do this below your diagram. Please provide a brief summary of what your ERD topic is and explain it to me like you did in class.
For each table provide table name, attribute name, contents, data type (use either notation: auto number/number/date/text or char/varchar/date/number), required (Y/N), Primary Key/Foreign Key, Foreign Key Referenced Table, specifics about the data
Write at least two paragraphs to justify how duplication was avoided.
I wanna my project to be about Pharmacy.
Employee, Customer, Physician, Customer has prescription, Prescription.