Instructions You must create a database design in MySQL Workbench and create a short PDF report presenting your design. Your design will contain the representation of a simple hierarchy for the provided specification. This is a CLOSED BOOK assignment, and you are not allowed to use any external information to solve it. Be sure that you use the description that was assigned to you. Solving a different version of the assignment will result in a grade of zero for this assignment and may result in honor committee referral. Database Conventions You must follow these conventions when you perform your homework. Failing to follow the conventions will be penalized per each mistake and may also constitute evidence of cheating. Entity names: singular nouns (or noun phrase) written in CAPITAL LETTERS, using _ instead of space, must start with a two letter sufix with your first name and last name initials (e.g. if your name is John Doe, an entity name will be PERSON_JD) Attribute names: singular nouns (or noun phrase) written in CAPITAL LETTERS, using _ instead of space, must start with a two-letter sufix with your first name and last name initials (e.g. if your name is John Doe, an attribute name will be FIRST_NAME_JD) Additional conventions might be specified by your instructor (e.g. prefix the attribute names with the entity name or abbreviation) Hierarchy Relationships: no name shown Hierarchy: Show the characteristics symbol, total/partial, disjoint/overlapping, type discriminator. Entity Diagram You must include all the following in your entity diagram (see rubric for a complete list of elements graded): All neded entities with names following conventions. All neded attributes with names following conventions. Mark if they are required or unique. Select the correct domain and size. The primary key for each entity. All needed foreign keys. Hierarchy: Show the characteristics symbol, total/partial, disjoint/overlapping, type discriminator.

Question 1 Requirements Specification (this is a fictional scenario) A large business, with several medical practices, contacted your company to create a database design. You received the task to investigate if there is a need for a hierarchy based on the specifications below, and to create the hierarchy analysis if needed. You must not create the entire analysis but only the aspects related to the hierarchy as described in the instructions, class lectures and sample examples. This is the relevant fragment from the requirements specification related to your task. In the practice we have only medical doctors, nurses and staff. For the doctors we keep the name (e.g. John Doe, having at most 20 characters for first or last name, no middle name is stored), SSN (with the format '999-99-9999'), phone (with format '999-999-9999'), email (having maximum 25 characters), main specialty (e.g. pediatrics, having at most 20 characters), medical school (having at most 30 characters). A doctor may have appointments and write prescripions. For nurses we keep the name (e.g. John Doe, having at most 20 characters for first or last name, no middle name is stored), SSN (with the format '999-99-9999'), phone (with format '999-999-9999'), and nurse program they completed (having at most 30 characters). A nurse will prepare the patient during the visit and may collect various data. A doctor is not allowed to perform nurse duties. F or staff we keep the (e.g. John Doe, having at most 20 characters for first or last name, no middle name is stored), SSN (with the format '999-99-9999'), phone (with format '999-999-9999'), and their role (e.g. receptionist, scheduler, accountant). Based on the practice policies, a nurse or a doctor will not be allowed to perform staff duties. The company wants to keep a log with who was working daily, between what hours and in which role. The company also wants to fast identify the role of a person in the organization (e.g. doctor, nurse, ...), based on the last name or id.