Professional Documents
Culture Documents
Lab 3
Lab 3
DOMAIN MODELLING
Interest I_descrip
I_intensity
Traveller T_name
T_address
T_telephone
T_email
Comment C_timeDate
C_narrative
C_ratings
TravelerInRoom T_checkInDateTime
T_checkOutDateTime
Accommodation A_roomNum
A_telephone
Resort R_name
R_addr
R_telephone
R_emailId
Facility F_name
F_description
F_capacity
F_loc
Activity A_beginDateTime
A_finishDateTime
A_description
2.
3.Relationship(Multiplicity)
Payment to Customer Account
0...* to 1
Customer Account to Customer
1 to 1
Customer to PickupRequest
1 to 1...*
Customer to Package
1 to 0...*
IndividualCustomer to Customer
Subclass
BusinessCustomer to Customer
Subclass
PickupRequest to Package
1 to 1...*
Package to Route Trip
1...* to 0...*
Package to MovementEvent
1 to 1...*
Route Trip to Employee
0...* to 1
Employee to MovementEvent
1 to 0...*
4. Finalize the class diagram, including all your classes, attributes, primary keys,
relationships, and multiplicity constraints.
Sandia Medical Devices
1.
2 Yes, to distinguish between the variations of cell phones, the user requires a general abstract class
with attributes that are common to every cell phone.