Problem Statement: Your customer wants to get a software system for a simple electronic bookstore called EBook. EBook does not store any books itself. It just provides a large catalogue of the books it offers. The catalogue contains for each book the usual information like ISBN-number, title, authors, subtitles, publisher, typical shipping time, number of pages, hardcover/paperback, price. Furthermore, for some books, customer comments can be looked up (only by those customers accessing the system over the web). Order placement: A customer can order a book by mail, phone or wWw. He can pay either by credit card (Mastercard, Visa and American Express are accepted), or by check (only when he orders by mail). Customers and clerks can look up the catalogue on the WWW. Order processing: When a customer orders books, payment gets verified and the book is then ordered directly from the publisher (we assume that the money is credited or cashed at the time of ordering the book, not at delivery time). The communication with the publishers is by email, i.e. the system automatically sends out an email for each book that gets ordered. For the sake of simplicity, we assume that every book gets delivered eventually, and that there are no undeliverable books in the catalogue. When books arrive from a publisher, the books get shipped to those who ordered them. A customer can order one or several books per order, yet they will get shipped to the customer as they arrive at EBook, i.e. a single order can result in several shippings to the customer Order cancellation: A customer can cancel an order if it has not yet been sent out to him. In case of a cancellation, EBook either cancels the order at the publishers or returns the book(s) to them. Return of books: A customer can return a book within a week. The money will either be credited to his credit card, or he receives a check. Use cases: 1. 2. 3. 4. Order placement Order processing Order cancellation Return of books Domain analysis model: Provided on canvas Modules page. Refer to above problem statement and the provided domain analysis model to answer following questions. Question 1a (4*10=40 Points): For each use case, identify system operations and develop one or more interaction diagrams, as applicable. Apply GRASP/GoF design patterns, as appropriate. Question 1b (4*10=40 Points): Use at least ten different GRASP / GoF design patterns, to solve Question 1a. Provide a brief reasoning for applicability of each design pattern. Question 2 (20 Points): Develop the design class diagram. Problem Statement: Your customer wants to get a software system for a simple electronic bookstore called EBook. EBook does not store any books itself. It just provides a large catalogue of the books it offers. The catalogue contains for each book the usual information like ISBN-number, title, authors, subtitles, publisher, typical shipping time, number of pages, hardcover/paperback, price. Furthermore, for some books, customer comments can be looked up (only by those customers accessing the system over the web). Order placement: A customer can order a book by mail, phone or wWw. He can pay either by credit card (Mastercard, Visa and American Express are accepted), or by check (only when he orders by mail). Customers and clerks can look up the catalogue on the WWW. Order processing: When a customer orders books, payment gets verified and the book is then ordered directly from the publisher (we assume that the money is credited or cashed at the time of ordering the book, not at delivery time). The communication with the publishers is by email, i.e. the system automatically sends out an email for each book that gets ordered. For the sake of simplicity, we assume that every book gets delivered eventually, and that there are no undeliverable books in the catalogue. When books arrive from a publisher, the books get shipped to those who ordered them. A customer can order one or several books per order, yet they will get shipped to the customer as they arrive at EBook, i.e. a single order can result in several shippings to the customer Order cancellation: A customer can cancel an order if it has not yet been sent out to him. In case of a cancellation, EBook either cancels the order at the publishers or returns the book(s) to them. Return of books: A customer can return a book within a week. The money will either be credited to his credit card, or he receives a check. Use cases: 1. 2. 3. 4. Order placement Order processing Order cancellation Return of books Domain analysis model: Provided on canvas Modules page. Refer to above problem statement and the provided domain analysis model to answer following questions. Question 1a (4*10=40 Points): For each use case, identify system operations and develop one or more interaction diagrams, as applicable. Apply GRASP/GoF design patterns, as appropriate. Question 1b (4*10=40 Points): Use at least ten different GRASP / GoF design patterns, to solve Question 1a. Provide a brief reasoning for applicability of each design pattern. Question 2 (20 Points): Develop the design class diagram