Question

Based on the business you proposed in deliverable 1, please submit

1. A detailed ER diagram
2. Definitions of entities (include strong, weak, associative, supertype, subtype etc.) – minimum # of entities 4
3. Definitions of relationships
4. For each relationship, specify whether it is
   1. Required vs. optional
   2. Simple vs. composite
   3. Single-valued vs. multi-valued
   4. Also specify key identifier

Project Deliverable 2 (should have)

Attributes ◦ Customer ◦ Cust_ID: Customer ID; Key identifier; required; simple; single-valued ◦ Cust_Name: Customer name; Key identifier; required; simple; single-valued ◦ Address (street, city, zip, state): Customer address; required, composite; single-valued; state and city can be derived from zip ◦ Balance: Customer’s balance; optional; simple; single-valued ◦ For each entity, specify the attribute with ◦ Brief description (data definition) ◦ Classifications

IS 410 Project 1 Deliverable

Team Name: A-Team - Patricia Balram, David Seo, Dennis Kim, Ethan Lai

Responsibilities: No one is in charge of one specific task, we are all going to be working together collectively as a team for each part of the project.

Business Situation: The business problem we want to solve is finding the right staff for certain technology positions, when you go on a hiring website and look for people for a specific position you are loaded with resumes and people from different positional backgrounds, you don’t want to look through all of them. You want to be able to see people who have the most experience and what they are able to offer your company. People who will use it will be from Indeed.com, and other hiring websites.

Business Rules: Applicants will add their information such as years of work experience, certifications, gpa/where they graduated, etc onto hiring websites like Indeed.com. This information will then be stored into a database where it ranks the applicants in order from best to worst based on their attributes (example: a person with 10 years of work experience will be ranked higher than someone with 5). The employer will then use this information to schedule interviews with the top candidates instead of having to sort through every application one by one to find the right person.

Stored Data: Names, Work Experience, Qualifications/Certifications, Major from school along with GPA, Where they graduated from, and Level of Degree.

Assumptions: Only employers will be able to use this, people who are applying will not be able to use this feature

Answer 1

ERD for given database:

Entity	Definitions of entity	Relationships	Required VS Optional attributes	Simple Vs. Composite attributes	Single_valued Vs Multi-valued	Key Identifier
Applicants	Strong entity	has relationship with Rank entity	1) Applicant_ID : Required 2)Applicant_name: Required 3) GPA : Required 4)Experience_year : Required 5) graduatedFrom : optional 6) DegreeLevel : Required	1) Applicant_ID: Simple 2)Applicant_name:Composite 3) GPA: Simple 4) Experience : Simple 5) DegreeLevel:Composite	1)Applicant_ID: Single-valued 2)Applicant_name:Single-valued 3) GPA: Single_value 4) Experience : Single-Value 5)DegreeLevel:Multi-valued	Applicant_ID
Ranks	SuperType entity	Disjoint relationship with Best_rank entity and Worst_rank entity	1) Rank_No : Required 2) Rank_Type : Required 3)Experience_year : Required	1) Rank_No : Simple 2) Rank_Type : Simple 3)Experience_year:Simple	1) Rank_No : Single-valued 2) Rank_Type : Single_valued 3)Experience_year:Single-valued	Rank_No
Best_Rank	SubType entity	Disjoint relationship with Best_rank entity and Worst_rank entity	1) Rank_no : Required	1) Rank_no : Simple	1) Rank_No : Single-valued	Rank_No
Worst_Rank	SubType entity	Disjoint relationship with Best_rank entity and Worst_rank entity	1) Rank_no : Required	1) Rank_no : Simple	1) Rank_No : Single-valued	Rank_No
Employee	Strong entity	Use relationship with Ranks entity	1) Employee_ID : Required 2) name : Required 3) Address: Optional	1) Employee_ID : Simple 2) name : Composite 3) Address: Composite	1)Employee_ID : Single-valued 2) name : Single_valued 3) Address: Multi-Valued	Employee_ID
Interview	Strong entity	Schedule relationship with Employee class	1) Interview_Date: Required 2) Interview_Day : Required 3) Interview_Time: Required 4) Location : Required	1) Interview_Date: Simple 2) Interview_Day : Simple 3) Interview_Time: Simple 4) Location : Composite	1) Interview_Date: Single-valued 2) Interview_Day : Single-valued 3) Interview_Time: Single-valued 4) Location : Multi-Valued	Interview_Date

ERD Diagram :

Thank you................