Implement Check-out Customer use case using an object-oriented programming language (such as Java) as specified in the communication diagrams (Fig. 1 and Fig. 2). The classes and their operations are given below and a sample data for entity objects are also given. The logic (pseudocode) for operations provided by Check-out Manager class is specified. When your program requests authorizing a credit card from Bank, you need to enter an authorization number (4-digit number) through a screen provided by Bank Interface object. Also a credit card number will be entered by you via a screen provided by Card Reader Interface object. A receipt and a bill will be printed out on screens in Receipt Printer Interface and Bill Printer Interface objects respectively. State your assumptions if necessary.

Verizon 5:32 PM a ttu.blackboard.com k-out Customer use case using an object-oriented programming langua C4) as specified in the communication diagrams (Fig. 1 and Fig. 2). Th a, 1 of 3 and uneir operations are given below and a sample data for entity objects are also gi logic (pseudocode) for operations provided by Check-out Manager class is specified. W program requests authorizing a credit card from Bank, you need to enter an authorizatior (4-digit number) through a screen provided by Bank Interface object. Also a credit caro will be entered by you via a screen provided by Card Reader Interface object. A receipt a will be printed out on screens in Receipt Printer Interface and B Printer Interface respectively. State your assumptions if necessary Fig. 1 Communication Diagram for Check-out Customer use case - Approved Credit Card Case checkOut in Rooa, out Bill updateReferenccin Room", in Reference#) Al: Room Number readBilI(in Rooml, out Bill read Totalin Room, out Total Bit Al2, A3.& Read Bill A1.5 A312: A2.2: Read Total A3.3: Update Reference Printed BillPrinted) Al4: Bill A3.11: Bill printed Display Bill display Desk Cle A1.3, A3.9: Bil A2.3: Total Al.I: Request Bil request Bill in Roome, out Bill in Total, i A3.5: Room Released printBillin Bill A3.6: Custom Customer readCard in Cardi) Credis Card A2 [crediCard: Number Dekted I Delete reditcardi in Card#. in Total, out Result) Number Charge CardReader intertia? Customsr Appoved Bank delcteCustomer(in Roon, out CustomerDelcted) Verizon 5:32 PM a ttu.blackboard.com k-out Customer use case using an object-oriented programming langua C4) as specified in the communication diagrams (Fig. 1 and Fig. 2). Th a, 1 of 3 and uneir operations are given below and a sample data for entity objects are also gi logic (pseudocode) for operations provided by Check-out Manager class is specified. W program requests authorizing a credit card from Bank, you need to enter an authorizatior (4-digit number) through a screen provided by Bank Interface object. Also a credit caro will be entered by you via a screen provided by Card Reader Interface object. A receipt a will be printed out on screens in Receipt Printer Interface and B Printer Interface respectively. State your assumptions if necessary Fig. 1 Communication Diagram for Check-out Customer use case - Approved Credit Card Case checkOut in Rooa, out Bill updateReferenccin Room", in Reference#) Al: Room Number readBilI(in Rooml, out Bill read Totalin Room, out Total Bit Al2, A3.& Read Bill A1.5 A312: A2.2: Read Total A3.3: Update Reference Printed BillPrinted) Al4: Bill A3.11: Bill printed Display Bill display Desk Cle A1.3, A3.9: Bil A2.3: Total Al.I: Request Bil request Bill in Roome, out Bill in Total, i A3.5: Room Released printBillin Bill A3.6: Custom Customer readCard in Cardi) Credis Card A2 [crediCard: Number Dekted I Delete reditcardi in Card#. in Total, out Result) Number Charge CardReader intertia? Customsr Appoved Bank delcteCustomer(in Roon, out CustomerDelcted)