- Person National Int Unique Name String Phone Int Personname String National In Updatename Updateemail Updatephone Cu 1 (107.55 KiB) Viewed 22 times
What is the correct visibility of person attributes?
What is the correct relationship that must be done between Payment and Insurance classes? what is the direction of this relationship?
hint: the customer can pay for insurance partially, but each payment relies on the updated data of the insurance
Solution:
The correct visibility of person attributes is __________________The relationship between Payment and Insurance classes is_______________________ relationship, from ___________________
Person National int(unique) name: String Phone:int Personname: String national in UpdateName UpdateEmail UpdatePhone) Customer Username: In National D password in update Userliame(userName: int updatePassword pw.int) 0.1 Admin - Userhiamerint id, readOnly, unique} password: int updatePasswordipw.int) 1 InsuranceSystemController -insuranceList: Insurance10.11 -admin Admin|1.1 customers. Customer(0.1) addNewAdmin -addNewCustomer addNewinsurance customer Customer) edit Insurance insurance in delete_insurance insuranceln) editAdmin(adminiDint) editCustomer(customer
managePayment paymenti) -checkforExpiredinsurance expiredinsuranceList Insurance|0D checkor Unpaidinsurance(unpaidinsuranceList Insurance. 1 Insurance insurance ind unique) InsuranceType InsuranceType insuranceStartDate: Date insurance Expiry Date -insurance Description: String insurance Price: double customerlin -insurance Status Status Insurance customer Dint) updateDescription updateExpiry Date updatePrice updateStatus 0. 1 cenumerations Status unpaid paid expired Payment paymenti in funique) -paymentDate: Date insurance Insurance updateinsuranceStatus 1 enumeration Vehicle carinsurance bicycleinsurance motorbikeinsurance InsuranceType price: double -updatePrice TransferPayment another attribute CashPayment updase Payment deletePayment updatePayment deletePayment