Convert the following textual description to an entity$-$relationship diagram in UML notation. Please spend time differentiating between entities, attributes, relationships and values of attributes. If you are identifying a strong entity $-$ make sure you identify a primary key for it$.$ You are not required to use superclass$/$subclass hierarchy for any of these problems, but may choose to do so if you wish. Remember, weak entities do not have a primary key. You are not required to use superclass$/$subclass hierarchy for any of these problems, but may choose to do so if you wish.Convert the following textual description to an entity$-$relationship diagram in UML notation. Please spend time differentiating between entities, attributes, relationships and values of attributes. If you are identifying a strong entity $-$ make sure you identify a primary key for it$.$ You are not required to use superclass$/$subclass hierarchy for any of these problems, but may choose to do so if you wish. Remember, weak entities do not have a primary key. You are not required to use superclass$/$subclass hierarchy for any of these problems, but may choose to do so if you wish.

A laptop has a unique serial number and is associated with a specific manufacturer and a model for that manufacturer. Each laptop is associated with exactly $1$ manufacturer and $1$ model for that manufacturer. A manufacturer has a unique name. A manufacturer can produce $1$ to many laptop models. A model does not have a unique name but is associated with at least $1$ manufacturer. An electronic store has a unique name and a unique address that consists of a street number, street address, town, state and zip code. An electronic store stocks $1$ to many laptops but a laptop can only be found at $1$ and only $1$ store. A customer consists of a name, and a unique credit card number. A customer buys a laptop at a store. A laptop can be bought by at most one customer but a customer may buy $0$ to many laptops.