You are to design and model a bank database pertaining to customers and banking transactions Information internal to banks and irrelevant to customers and transactions will be omitted, like information about internal office structures and employees. The objective of Project 1 is to model the following basic objects accounts (e.g., savings accounts, checking accounts, credit card accounts, loan accounts) account holders branches terminals: objects used to initiate and conduct transactions (e.g., bank websites, ATMs, credit/debit card scanners, mobile devices, user interfaces within bank intranets) . paper checks and credit/debit cards issued to account holders These objects must be modeled by a UML class diagram. Use generalization-specialization (inheritance) hierarchies effectively. For example, different types of accounts should be organized by an inheritance hierarchy, with the most general account class at the root. Use weak/strong composition whole-part hierarchies effectively. For example, branches have terminals like ATMs, card scanners at the counter, and intranet user interfaces used by clerks Your task is to design a well-structured database model on which necessary algorithms and functions can be implemented and added ere is a summary of key points All the classes, inheritance hierarchies, whole-part hierarchies must be modeled in a UML class diagram. The multiplicity ranges of each whole-part relation must be specifie Include basic, essential attributes in classes. Attribute data types may be specified or omitted in this project Make classes abstract if you are certain they will not have any direct objects Key attributes, if any, should be specified by appending (key) to the attribute names. For example, if an account class has a key attribute accouutNuu, designate it by ej If attribute/relation names are not self-explanatory, concisely describe their intended semantics by English comments in the text documentation area. Your UML tool should provide text documentation areas/boxes for this purpose Use the following identifier convention consistently: Class names should begin with uppercase letters; if a class name is a noun, it should be in singular form. Attribute and relation names should generally begin with lowercase letters You are to design and model a bank database pertaining to customers and banking transactions Information internal to banks and irrelevant to customers and transactions will be omitted, like information about internal office structures and employees. The objective of Project 1 is to model the following basic objects accounts (e.g., savings accounts, checking accounts, credit card accounts, loan accounts) account holders branches terminals: objects used to initiate and conduct transactions (e.g., bank websites, ATMs, credit/debit card scanners, mobile devices, user interfaces within bank intranets) . paper checks and credit/debit cards issued to account holders These objects must be modeled by a UML class diagram. Use generalization-specialization (inheritance) hierarchies effectively. For example, different types of accounts should be organized by an inheritance hierarchy, with the most general account class at the root. Use weak/strong composition whole-part hierarchies effectively. For example, branches have terminals like ATMs, card scanners at the counter, and intranet user interfaces used by clerks Your task is to design a well-structured database model on which necessary algorithms and functions can be implemented and added ere is a summary of key points All the classes, inheritance hierarchies, whole-part hierarchies must be modeled in a UML class diagram. The multiplicity ranges of each whole-part relation must be specifie Include basic, essential attributes in classes. Attribute data types may be specified or omitted in this project Make classes abstract if you are certain they will not have any direct objects Key attributes, if any, should be specified by appending (key) to the attribute names. For example, if an account class has a key attribute accouutNuu, designate it by ej If attribute/relation names are not self-explanatory, concisely describe their intended semantics by English comments in the text documentation area. Your UML tool should provide text documentation areas/boxes for this purpose Use the following identifier convention consistently: Class names should begin with uppercase letters; if a class name is a noun, it should be in singular form. Attribute and relation names should generally begin with lowercase letters