Back-end Class Diagram Description

The following describes the concept used in the class diagram

• Relationship

  The class “Bank” is made up of one or more Transactions, Accounts, Administrators, Customers, and Traces. It uses the aggregation connector to show this relationship, which means they can exist independently of the Bank class and they are not strongly dependent on the lifecycle of the Bank class. even when the library is dissolved.

• Referential bidirectional integrity

  In the class diagram, the User class and Account class are interrelated. The User takes on the association with the multiplicity value of 1..1 which means that when the instance of Account exists, it can either have one instance of User associated with it or no User associated with it as a result Both User and Account classes are aware of each other and their relationship with each other

• Inheritance

  In the above class, the diagram describes the classes for the bank app project. The Administrator and the customer class inherits the User class. Other classes like Account are a separate class connected to user Class. The Administrator and the customer class acquires the properties of the User class and can use them in their class.

• cardinality of relationships

  In the class diagram, one transaction may include multiple Trace and one User may include multiple trace, while one user may have one account, This is denoted using the notation 1...1.