Deb has recently launched her Rain Caf in downtown Toronto. The Caf is a blast. Customers cannot get enough of Deb's coffee beverages and baked foods. To entice and retain customers, Deb is thinking of launching a loyalty membership app. She jots down what she has in mind of important features of the app. First and foremost, Deb wants an easy registration process for customers. In particular, a customer shall quickly create an account by simply entering his or her cell phone number. To ensure that the customer is the holder of the cell phone, the customer has to enter into the app a 6-digit confirmation code sent to the customer's phone to complete the registration process. At the end of the customer registration process, the customer is provided a unique membership ID. Deb also wants to reward customers who refer their friends and family members to her caf. A $5 voucher is added to the customer who has made a referral. So in creating an account, every new customer has the option of providing the cell phone number of the family member or the friend who has made a referral. Second, customers can use the app for ordering and payments. Customers shall be able to search all products using the app. Each product record shall contain the following information including regular price and promotion price (if applicable), award points, a general description, and images. The customer can add products to the shopping cart, and then proceed to check out to complete ordering. The app then generates an order number. The order, however, can be paid using the app or in store. If the payment is made using the app, the customer can pay by using a variety of methods including credit card, award points, and vouchers. To purchase by using award points (called BeanPoints), he or she has to select "purchase using BeanPoints." The app will calculate points to be deducted, and the amount that needs to be paid. If the BeanPoints is insufficient for a purchase, and if the customer decides to continue with using the points, the customer needs to pay the remaining amount by using his/her credit card. For purchases made by a credit card, Deb wants the app to reward the customer BeanPoints based on the dollar amount. In other words, no points are awarded if a purchase is made by using BeanPoints. Deb also wants the flexibility of adjusting BeanPoints for a purchase based on dates and times. For example, double BeanPoints could be awarded every Tuesday from 3-5pm. After completing the list, Deb feels pretty happy with what she's got. She is ready to talk to her business analyst to nail down details of the app requirements. The table below summarizes the number of diagrams needed for project phase I Domain class Use case Use case Activity diagram description diagram diagram 1 Diagrams No. of diagram that needs to be produced 1 21 2 Question: - System sequence diagram -Develop a system sequence diagram based on each fully detailed use case description - Design class diagram - Develop a design class diagram for the entire app. Include all classes of the system in the diagram. However, for the classes that are not involved in the use cases you've chosen, you should keep their methods blank. - Detailed system sequence diagram- Develop a first-cut sequence diagram for each use case description you've chosen for the project