The goal of this assignment is to implement a use case as specified. Homework Description: Implement the main sequence for Make Order Request use case using an object-oriented programming language (such as Java, C++ or C#) as specified in the communication diagram (Fig. 1). The classes and their operations are given below and the sample data for entity objects are also given. The pseudocode for operations provided by Customer Interface and Purchase Order Manager classes are specified. A customer makes an order request with the order contents and account ID. Assume that the customer account data are stored in the system (see table below) and three order requests had been made (see table below). When the system request authorization from a bank, you need to enter an approval number to the system via the bank interface object. For email confirmation, the system needs to display an email address via the email system interface object. Fig. 1 Main Sequence for Make Order Request use casee request(in item, in quantity, in totalPrice, in AccountID, out Result) M1: Order Request user interaction Customer aCustomer M13: Customer Output requestOrder in item, in quantity, inM2: totalPrice in AccountID, out R esult) Order Request M12: Order Confirmation readAccountInfo(in AccountID out CardNo, out CustEmail) authorize(in CardNo, out Result) M5: Authorize Credit Card Request M3: Account system business logic centity Customer Account M8: Credit Card M4 [Available] Account Info M7: [Approval] Approved Authorization M6: Authorize M11: Send Order Confirmation Email Number M9: Create Order createOrder in item, in quantity, in totalPrice, M10 Order Confirmation emailConfirmation( in CustEmail) entity Delivery Order system interface Email aBank AuthorizationNo, out OrderConfirmation) The goal of this assignment is to implement a use case as specified. Homework Description: Implement the main sequence for Make Order Request use case using an object-oriented programming language (such as Java, C++ or C#) as specified in the communication diagram (Fig. 1). The classes and their operations are given below and the sample data for entity objects are also given. The pseudocode for operations provided by Customer Interface and Purchase Order Manager classes are specified. A customer makes an order request with the order contents and account ID. Assume that the customer account data are stored in the system (see table below) and three order requests had been made (see table below). When the system request authorization from a bank, you need to enter an approval number to the system via the bank interface object. For email confirmation, the system needs to display an email address via the email system interface object. Fig. 1 Main Sequence for Make Order Request use casee request(in item, in quantity, in totalPrice, in AccountID, out Result) M1: Order Request user interaction Customer aCustomer M13: Customer Output requestOrder in item, in quantity, inM2: totalPrice in AccountID, out R esult) Order Request M12: Order Confirmation readAccountInfo(in AccountID out CardNo, out CustEmail) authorize(in CardNo, out Result) M5: Authorize Credit Card Request M3: Account system business logic centity Customer Account M8: Credit Card M4 [Available] Account Info M7: [Approval] Approved Authorization M6: Authorize M11: Send Order Confirmation Email Number M9: Create Order createOrder in item, in quantity, in totalPrice, M10 Order Confirmation emailConfirmation( in CustEmail) entity Delivery Order system interface Email aBank AuthorizationNo, out OrderConfirmation)
