Suppose you want to implement an online bookstore. In this system the user can browse the website to review the list of available books but can only purchase books after registration. The user can also cancel the order or request return after placing the order. The site admin's tasks include validating the user, updating the list of available books, processing orders and return requests. The first step for implementing this system is to conceptually model it. For this purpose, do the following: A. Write the use cases for the purchase process. (at least 5 use cases) - 15 points You can choose any type of use cases (i.e. brief, casual, fully dressed, etc.) and need to explain your rationale for choosing that type. B. Draw the use case diagram based on the generated use cases 15 points C. Draw the UML Domain Model of the purchase process - 20 points Identify the conceptual classes and draw them as classes in a UML class diagram with their relationships, attributes and methods. At this phase you don't have to focus on the payment authentication process. Additional notes to consider: The name of the conceptual classes should be meaningful to describe the role of each component. - For each class, minimum number of properties should be specified, as unnecessary properties will make the diagram complicated. Use notes whenever required to describe some aspect of the diagram. At the end of the drawing, it should be understandable to the developer/coder. You can draw the diagrams on paper or use the existing tools. In designing your class diagram be mindful of cohesion and coupling in system components. Suppose you want to implement an online bookstore. In this system the user can browse the website to review the list of available books but can only purchase books after registration. The user can also cancel the order or request return after placing the order. The site admin's tasks include validating the user, updating the list of available books, processing orders and return requests. The first step for implementing this system is to conceptually model it. For this purpose, do the following: A. Write the use cases for the purchase process. (at least 5 use cases) - 15 points You can choose any type of use cases (i.e. brief, casual, fully dressed, etc.) and need to explain your rationale for choosing that type. B. Draw the use case diagram based on the generated use cases 15 points C. Draw the UML Domain Model of the purchase process - 20 points Identify the conceptual classes and draw them as classes in a UML class diagram with their relationships, attributes and methods. At this phase you don't have to focus on the payment authentication process. Additional notes to consider: The name of the conceptual classes should be meaningful to describe the role of each component. - For each class, minimum number of properties should be specified, as unnecessary properties will make the diagram complicated. Use notes whenever required to describe some aspect of the diagram. At the end of the drawing, it should be understandable to the developer/coder. You can draw the diagrams on paper or use the existing tools. In designing your class diagram be mindful of cohesion and coupling in system components
