The objective of Project #1 is to develop a relational data model describing the primary business...

   

Transcribed Image Text:

The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary. The objective of Project #1 is to develop a relational data model describing the primary business processes of Polytechnic Supply Corporation (PSC). PSC is in the business of Business-to-Business wholesale distribution, where they sell products to their customers who are retailers. Relevant business rules and a report that represents one user view are provided below. Business Rules: 1. Each customer may place multiple orders. Each order must be placed by one and only one customer. 2. Each order must contain one or many products. Each product may be requested by multiple orders. 3. There may be an order-level discount that is percentage based. For simplicity, we will ignore tax and shipping costs. 4. All products are purchased from suppliers - a product may be purchased from multiple suppliers at various unit costs; one supplier may provide multiple products. 5. 6. PSC sells the same product at the same unit price to all customers. PSC organizes their products into categories, such as books, food, appliances, electronics, sports, etc. A product can be in one and only one category, while one category contains one or more products. Sample Customer Order Report: Acme TNT 5460 Dusty Ln. Salt Lake City UT 84103 (800) 444-3876 Order Number 1515 Line Item 1 2 3 Discount: 10% off Total: $1,980 Customer Order Report Description Fire Alarm Security Alarm Blender Order Date 1/4/2022 Quantity 1 1 30 Customer # 2000 Ship Date 1/30/2022 Unit Price $500.00 $800.00 $30.00 Task 1: Create a data dictionary and a referential integrity table Create a project report in MS Word and name it "[Your Last Name] ProjectMilestone 1.doc". Based upon the business rules given above, complete the following Table 1 Data Dictionary. List entities (all letters in capitalization) and their attributes (capitalize first letter of each word), mark if Primary Keys (PK) and/or Foreign Keys (FK), and their data types, as the examples shown. . Then complete Table 2 Referential Integrity below, specify the relationships and their cardinalities, as the example shows. Make sure to maintain 3rd Normal Form for each relation, i.e. no repeating groups, partial dependencies or transitive dependencies. Table 1: Data Dictionary (to be completed by you) Entity Attribute CUSTOMER T ORDER_T [More tables to be completed by you...] CustomerID CustomerName to be completed by you... OrderID [More attributes to be completed by you...] [More attributes to be completed by you...] Key (mark if PK and/or FK) PK PK [primary keys and foreign keys to be completed by you...] Data Type* and field length in format of Domain/Category (length or precision) Number / Integer String/Varchar (100) to be completed by you... Number / Integer [data types to be completed by you...] [data types to be completed by you...] * When you create a new attribute you should assign its data type in Erwin: You can choose one from the four domains: Blob, Date/Time, Number, String. • Under each domain there are various categories, for example, Number can be Integer or Decimal. Use Number type only for attributes that are meaningful for arithmetic calculations, such as quantity or price. For Decimal (p.s), p is precision, s is scale. Precision refers to number of digits in a number, minimum 1, maximum 39. Scale refers to the number of digits to the right of the decimal point. The scale of a decimal value cannot exceed its precision. For example, Decimal (9,5) can store 1234.56789. https://docs.actian.com/ingres/10s/index.html#page/SQLRef/Decimal Data Type.htm Table 2: Referential Integrity (to be completed by you) Relationship CUSTOMER_T> ORDER_T ORDER T CUSTOMER T to be completed by you... ** Cardinality Constraints can be: Cardinality Constraints** Optional Many Mandatory One to be completed by you.... Optional Many - means 1 to many with the minimum 0. Mandatory Many - means 1 to many with the minimum 1. Optional One - means 1 to 1 with the minimum 0. Mandatory One - means 1 to 1 with the minimum 1. Task 2: Create a logical data model in Erwin Open Erwin, follow "Instructions on Initial ERwin Setup" below and set up your Erwin correctly. Instructions on Initial Erwin Setup: Set up Erwin with the following specifications: Model -> Model Properties -> Notations o Under both Logical and Physical notation, check "IE (Information Engineering)" Right click any spot on canvas and select "properties" o On the "Display" tab: ▪ Check mark "Display Parent to Child Verb Phrase" On the "Entity" tab: • . Based on the data dictionary and referential integrity in Task 1 Table 1 and Table 2, create a new Logical/Physical model in ERwin and name it "[FirstNameLastName] Project 1.erwin", including: Select "Attribute" from the drop-down for Logical Display Level Check mark all of the following Primary key designator Foreign Key designator Show Migrated Attributes o Create entities, their attributes, and relationships between the entities. Mark primary and foreign keys. Set the correct properties for each relationship (including Type properties, Relationship properties, and Cardinality properties). Make sure everything is consistent with the Table 1 Data Dictionary and Table 2 Referential Integrity in Task 1. o Assign data type and field length to each attribute as you defined in the data dictionary in Task 1. Make sure all entities, attributes, primary keys, and relationships are properly labeled following common practice as shown in textbook. 0 O • Double check the consistency between your Table 1 & 2 with your ERwin diagram, including details like cardinality constraints and data types. Make sure PK (marked with key icon and above the line inside its entity) and FK (marked with (FK) beside the attribute name) are correctly created. When in doubt create some fictitious data and enter into your table design and see if it makes sense. Capture a screenshot of the logical model in ERwin and insert into your Word project report. Make sure the screenshot is readable to the level of each relationship description and cardinality constraint. Use Horizontal layout if necessary.