Based on the table structure and buisness rules, match the following attributes or phrases with terms definitions or concepts discussed in chapter 4.

at the bottom theres 10 blue boxes with terms that need to be match with there definitions/concept.

3 Search this cour Role table Structure: Attribute (Field) Data Type Example Required Role ID Character DB294 Y Role. Description Character Database Programmer job Responsibilities include, but not limited to DDL DML programming SQL Coding. Developing Checking DB Security Scripts. Establishing DB connections through ODBC and other technologies, updating Data Dictionaries Y Employee table structure: Attribute (Field) Data Type Example Required Employee-ED Character 112-632-294 Role-ID Character DB294 First Name Character JoAnn Middle initial Character K Last Name Character Hansen Y Reports To Character 112-532-111 Y office Character South Tower: 1128 Y Office Phone Character 511-788-7788 Y 10 TPU k #3 office Character South Tower: 1128 Y Office Phone Character 511-788-7788 Y Start Date in Role Date 12/30/2011 Y End Date in Role Date N Number of assigned projects Integer Y Project table structure: Attribute Data (Field) Type Example Required Project ID Character DB-201215 Y Description Text Y An IT team is assigned to expand the Electronic Health Record database patient data fields and clinical documentation capabilities. The objective is to support the specific needs of physicians in the ER area to expand the transfer protocol documentation scope, based on ICD-10 codes Project Leader Character 112-732-109 Date 01/15/2018 Project Start Date Project-End Date Date SUCC Attribute (Field) Data Type Example Required Character DB-201215-112-632-294 Y Project-Assigned-ID Employee-ID Character 112-632-294 Project-ID Character DB-201215 Y Assignment-Start Date Date 02/15/2018 Y N Assignment-End Date Date Business Rules 1. All fields in all tables which are required (Y), cannot be blank. 2. Employees cannot assume multiple roles. Employees must be assigned a singular role. 3. Same Role can be assigned to zero - multiple Employees. 4. Employees can be assigned zero through 2 projects maximum, simultaneously. 5. Employees can be assigned to multiple projects, during a cycle (year), provided it meets the rule 4. 6. Number-of-assigned projects in the Employee table can be o, but not blank. 7. Number-of-assigned projects in the Employee table is automatically updated when a project is assigned. 8. The Project-assigned-ID. uses a combination of Project ID and Employee ID. Based on the table structure and business rules, match the following attributes or phrases with terms, definitions or concepts discussed in Chapter 4 9102 GAGE MINDTAP Q Search ork #3 Based on the table structure and business rules, match the following attributes or phrases with terms, definitions or concepts discussed in Chapter 4 Relation between Role and Employee entities 1:M Minimum and Maximum allotted-projects (0.2) Entity to support Multivalued Attribute Model Relation between Employee and Role entities Existence-dependent Project Assigned entity Single-Valued Attribute Project Assigned.ID Composite key Middle initial Optional Attribute Hash mark across the relationship line (#) Cardinality Employee entity 1:1 Number-of-assigned- projects Mandatory relationship Project Leader Derived Attribute 3 Search this cour Role table Structure: Attribute (Field) Data Type Example Required Role ID Character DB294 Y Role. Description Character Database Programmer job Responsibilities include, but not limited to DDL DML programming SQL Coding. Developing Checking DB Security Scripts. Establishing DB connections through ODBC and other technologies, updating Data Dictionaries Y Employee table structure: Attribute (Field) Data Type Example Required Employee-ED Character 112-632-294 Role-ID Character DB294 First Name Character JoAnn Middle initial Character K Last Name Character Hansen Y Reports To Character 112-532-111 Y office Character South Tower: 1128 Y Office Phone Character 511-788-7788 Y 10 TPU k #3 office Character South Tower: 1128 Y Office Phone Character 511-788-7788 Y Start Date in Role Date 12/30/2011 Y End Date in Role Date N Number of assigned projects Integer Y Project table structure: Attribute Data (Field) Type Example Required Project ID Character DB-201215 Y Description Text Y An IT team is assigned to expand the Electronic Health Record database patient data fields and clinical documentation capabilities. The objective is to support the specific needs of physicians in the ER area to expand the transfer protocol documentation scope, based on ICD-10 codes Project Leader Character 112-732-109 Date 01/15/2018 Project Start Date Project-End Date Date SUCC Attribute (Field) Data Type Example Required Character DB-201215-112-632-294 Y Project-Assigned-ID Employee-ID Character 112-632-294 Project-ID Character DB-201215 Y Assignment-Start Date Date 02/15/2018 Y N Assignment-End Date Date Business Rules 1. All fields in all tables which are required (Y), cannot be blank. 2. Employees cannot assume multiple roles. Employees must be assigned a singular role. 3. Same Role can be assigned to zero - multiple Employees. 4. Employees can be assigned zero through 2 projects maximum, simultaneously. 5. Employees can be assigned to multiple projects, during a cycle (year), provided it meets the rule 4. 6. Number-of-assigned projects in the Employee table can be o, but not blank. 7. Number-of-assigned projects in the Employee table is automatically updated when a project is assigned. 8. The Project-assigned-ID. uses a combination of Project ID and Employee ID. Based on the table structure and business rules, match the following attributes or phrases with terms, definitions or concepts discussed in Chapter 4 9102 GAGE MINDTAP Q Search ork #3 Based on the table structure and business rules, match the following attributes or phrases with terms, definitions or concepts discussed in Chapter 4 Relation between Role and Employee entities 1:M Minimum and Maximum allotted-projects (0.2) Entity to support Multivalued Attribute Model Relation between Employee and Role entities Existence-dependent Project Assigned entity Single-Valued Attribute Project Assigned.ID Composite key Middle initial Optional Attribute Hash mark across the relationship line (#) Cardinality Employee entity 1:1 Number-of-assigned- projects Mandatory relationship Project Leader Derived Attribute