Question

Use ONLY the classes in this list to draw a Class diagram. The diagram must show all the classes, their attributes, and the relationships between the classes. All the associations must have proper multiplicity constraints indicated. Note that class methods and attribute types are not required.                                                                                                              

Domain classes and their attributes
Order [date/time, total price, status] Account [full name, address, phone, email] SellerAccount (no attributes) BuyerAccount [credit card] Book [title, ISBN, author, publisher, asking price] BookOnOrder [quantity] Dispute [reason]

You are advised that the BookOnOrder class should be designed to help deal with the fact that an order may contain multiple copies of the same book and the same book can be purchased in different orders. Also, the SellerAccount and BuyerAccount classes should be designed to be specializations of the Account class.

TheEyesHaveIt.Com Book Exchange Case Study

TheEyesHaveIt Book Exchange is a type of e-business exchange that does business entirely on the Internet. The company acts as an exchange point for both buyers and sellers of used books.  

For a person to offer books for sale, he/she must register an account with TheEyesHaveIt. The person must provide their full name, current physical address, telephone number, and e-mail address.  

A seller may list as many books as desired through the system. Information required includes ISBN, title, author/s, publisher, and the asking price. The system maintains an index of all books in the system so that buyers can search for the books they want. Buyers can search by title or author. A seller may list multiple copies of the same book with the same information.

Likewise, the sellers, people who are buying books for the first time need to also register an account, but the buyers have to provide their credit card details. A buyer searches for a book and once a book is found, the buyer adds the book to an order. Each order contains information about the date and time of when the order is “created”, total price, and order status. After the first book has been added, the order is marked “open”. A buyer can add as many books as they want in a single order. After the buyer decides to finish their order, they submit the order and it is then marked “waiting for payment”. The buyer may not proceed directly to payment but return to their order to add/remove a book. Once the payment received, the system updates the status of the order to “paid”. Eventually, the seller will notify TheEyesHaveIt that the order has been “shipped”. Both buyers and sellers can view the status of their order via their account webpage on TheEyesHaveIt.com.

Buyers can open a dispute on their order based on two reasons as follows: if the shipment does not arrive within a 30-day and if the book arrived is not in the same condition as advertised. A dispute must be opened within 45 days after the order was shipped otherwise the order is considered “completed”. Each order that is “in dispute” will eventually be resolved by the sellers or TheEyesHaveIt. The order that has been successful or resolved will be marked “completed”.

Answer 1

Hi,

The class diagram is given below:

Here an order cannot placed without a user so it is represented as a filled diamond and it shows the composition.Here BookOnOrder is an aggregation to order that is order has a BookOnOrder.1 ...* represent one to many relationships.0 ..1 represent zero or one.That is if the shipment is not reached time a dispute is opened otherwise no dispute.

Thank you...