Question

Consider a book rental system in a comic store. When a customer borrows or returns a comic book, the shop- keeper needs to mark down the transaction or update the corresponding record on the transaction book.

a. Draw an enterprise data model for this book rental system.
b. Identify the type of relationship between the tables.
c. Design some attributes for these two tables.

Answer 1

An enterprise data model for a comic book rental system would involve entities such as Customer, Comic Book, and Transaction, with a one-to-many relationship between Customer and Transaction, and a many-to-many relationship between Comic Book and Transaction. Attributes for these entities would include unique identifiers, personal information for the Customer, and transaction details.

Step-by-step explanation:

The student's question pertains to creating a data model for a comic book rental system. For part (a), I would draw an enterprise data model which typically includes entities such as Customer, Comic Book, and Transaction, though it's not possible to draw in a text response.

In part (b), the type of relationship between Customer and Transaction would be one-to-many, indicating a customer can have multiple transactions, and between Comic Book and Transaction, it would likel

y be many-to-many as a comic book can be part of many transactions and a transaction can involve multiple comic books. For part (c), attributes for the Customer table could include CustomerID, Name, and ContactInfo, and for the Transaction table could include TransactionID, Date, CustomerID (foreign key), ComicBookIDs (foreign key), and Status (borrowed or returned).