B$.$ Use case diagram $(10$ Points$)$

Consider the following use case diagram:

According to the diagram, Transaction is an abstract superclass for Withdrawal, Inquiry, Deposit, Transfer and Invalid PIN.

The relation between Invalid PIN and Transaction does not conform to the UML standard.

The use case should clarify in what direction data is transferred to and from the Central Database.

The Central Database should be moved outside the ATM System box, but the connections should be kept.

The relation between the Customer and the GUI is not permitted in UML use case diagram syntax.

The relations connecting the Operator, GUI and Bank to the ATM System are missing the arrows.