Object Oriented Analysis Systems Creating a complete class diagram for the "Housekeeper service system" if given you an overview of the classes, attributes, and associations you would need: 1. *User* - Attributes: name, password, mobile phone, email - Methods: updatePassword(), updateMobilePhone() 2. *System Administrator* - Inherits from User - Attributes: level Of Access - Methods: registerWorker(), registerCustomer(), updateServices(), addOffers() 3. *Worker* - Attributes: age, nationality, specialty, evaluation degree - Methods: displayAssignedVisits(), submitLeaveOfAbsence() 4. *Customer* - Inherits from User - Attributes: nationality ID, addresses - Methods: selectServices(), chooseVisitTime(), confirmServiceInformation(), makePayment(), getTransactionInformation() 5. *Address* - Attributes: street name, building number, zip code, city - Methods: addAddress(), deleteAddress(), updateAddress(), setDefaultAddress() 6. *Payment* - Attributes: transaction ID, date, time, type (Apple Pay, Credit card, bank transfer) 7. *Service* - Attributes: contract ID, service type, frequency, start date, end date, period time, number of visits, location, cost in SR - Methods: bookService(), selectService(), cancelService(), getServiceInformation() 8. *Visit* - Attributes: visit ID, date, address - Methods: rescheduleVisit(), changeVisitAddress(), evaluateWorker(), cancelVisit() 9. *VisitWorker* - Attributes: worker ID - Association with Visit: Many-to-One (Many VisitWorkers to One Visit) 10. *CustomerService* - Attributes: services - Association with Customer: Many-to-Many (Many Customers to Many CustomerServices) 11. *ServiceVisit* - Attributes: visits - Association with Service: One-to-Many (One Service to Many ServiceVisits) 12. *ServiceAddress* - Attributes: address - Association with Service: One-to-Many (One Service to Many ServiceAddresses) Please note that you would need to add multiplicities and association names to the diagram, specifying whether associations are one-to-one, one-to-many, or many-to-many as per your system's requirements. Additionally, the diagram should show inheritance relationships between classes as mentioned in the problem statement. This is a simplified representation, and you can further refine it based on your specific needs and constraints.
Object Oriented Analysis Systems
Creating a complete class diagram for the "Housekeeper service system" if given you an overview of the classes, attributes, and associations you would need:
1. *User*
- Attributes: name, password, mobile phone, email
- Methods: updatePassword(), updateMobilePhone()
2. *System Administrator*
- Inherits from User
- Attributes: level Of Access
- Methods: registerWorker(), registerCustomer(), updateServices(), addOffers()
3. *Worker*
- Attributes: age, nationality, specialty, evaluation degree
- Methods: displayAssignedVisits(), submitLeaveOfAbsence()
4. *Customer*
- Inherits from User
- Attributes: nationality ID, addresses
- Methods: selectServices(), chooseVisitTime(), confirmServiceInformation(), makePayment(), getTransactionInformation()
5. *Address*
- Attributes: street name, building number, zip code, city
- Methods: addAddress(), deleteAddress(), updateAddress(), setDefaultAddress()
6. *Payment*
- Attributes: transaction ID, date, time, type (Apple Pay, Credit card, bank transfer)
7. *Service*
- Attributes: contract ID, service type, frequency, start date, end date, period time, number of visits, location, cost in SR
- Methods: bookService(), selectService(), cancelService(), getServiceInformation()
8. *Visit*
- Attributes: visit ID, date, address
- Methods: rescheduleVisit(), changeVisitAddress(), evaluateWorker(), cancelVisit()
9. *VisitWorker*
- Attributes: worker ID
- Association with Visit: Many-to-One (Many VisitWorkers to One Visit)
10. *CustomerService*
- Attributes: services
- Association with Customer: Many-to-Many (Many Customers to Many CustomerServices)
11. *ServiceVisit*
- Attributes: visits
- Association with Service: One-to-Many (One Service to Many ServiceVisits)
12. *ServiceAddress*
- Attributes: address
- Association with Service: One-to-Many (One Service to Many ServiceAddresses)
Please note that you would need to add multiplicities and association names to the diagram, specifying whether associations are one-to-one, one-to-many, or many-to-many as per your system's requirements. Additionally, the diagram should show inheritance relationships between classes as mentioned in the problem statement. This is a simplified representation, and you can further refine it based on your specific needs and constraints.
Step by step
Solved in 3 steps with 1 images
