I need the answers of these questions please

Petrie's Electronics Case, Chapter 7, I can't upload the scenario of these question

7-48. Review the data-flow diagrams given to you by your instructor. Study the data flows and data stored in these diagrams and decide whether you agree with the team's conclusion that the only six entity types needed are listed in the case and in PE Figure 7-1. If you disagree, define additional entity types, explain why they are necessary, and modify PE Figure 7-1 accordingly.

Entity is an object, concept, place, event, or person.

Type - a group of entities having common characteristics (like classes in Java).Only defined once

Instance - an instance of an entity type. (objects in java). Occur more than once

If an entity type is a collection of entities that have the same characteristics, then I do not believe that only 6 entity types displayed in figure 7-1, is sufficient and needs 2 more added.

Report - this is necessary since it doesn't share

Purchase - ( I can't submit the pic)

Entities

Coupon

Customer

Product

Promotion

Service

Transaction

Report

7-49. Again, review the DFDs you developed for the Petrie's Electronics case (or those given to you by your instructor). Use these DFDs to identify the attributes of each of the six entities listed in this case plus any additional entities identified in your answer to Case Question 7-48. Wri te an unambiguous definition for each attribute. Then, redraw PE Figure 7-1 by placing the six (and additional) entities in this case on the diagram along with their associated attributes.

Part 2:

Coupon

Customer

Product

Promotion

Service

Transaction

Report

7-50. Using your answer to Case Question 7-49, designate which attribute or attributes form the identifier for each entity type. Explain why you chose each identifier.

7-51. Using your answer to Case Question 7-50, draw the relationships between entity types needed by the system. Remember, a relationship is needed only if the system wants data about associated entity instances. Give a meaningful name to each relationship. Specify cardinalities for each relationship and explain how you decided on each minimum and maximum cardinality at each end of each relationship. State any assumptions you made if the Petrie's Electronics cases you have read so far and the answers to questions in these cases do not provide the evidence to justify the cardinalities you choose. Redraw your final E-R diagram in Microsoft Visio.

7-52. Now that you have developed in your answer to Case Question 7-51 a complete E-R diagram for the Petrie's Electronics database, what are the consequences of not having an employee entity type in this diagram? Assuming only the attributes you show on the E-R diagram, would any attribute be moved from the entity it is currently associated with to an employee entity type if it were in the diagram? Why or why not?

7-53. Write project dictionary entries (using standards given to you by your instructor) for all the entities, attributes, and relationships shown in the E-R diagram in your answer to Case Question 7-51. How detailed are these entries at this point? What other details still must be filled in? Are any of the entities on the E-R diagram in your answer to Case Question 7-51 weak entities? Why? In particular, is the SERVICE entity type a weak entity? If so, why? If not, why not?

7-54. What date-related attributes did you identify in each of the entity types in your answer to Case Question 7-51? Why are each of these needed? Can you make some observations about why date attributes must be kept in a database, based on your analysis of this database?