Article directory
Modeling with UMLet
Question 1
- Using class diagrams, model the domains for the Make Reservation use case and the Payment use case in the Asg_RH document, respectively. Then, based on the above model, give the suggested data table along with the main fields, especially the primary and foreign keys
- Precautions:
- Objects must be nouns, especially the processing of technical nouns, reports, and description classes;
- Association must have multiplicity, part noun and navigation direction
- Attributes should pay attention to calculated fields
- For data modeling, only a list of tables needs to be given to simplify the description, for example:
- Hotel（ID/Key, Name, LocationID/Fkey, Address…）
1. Make Reservation
Domain modeling looks like this:
The data modeling looks like this:
- Hotel(HotelID/Key, Name, LocationID/Fkey, ReservationID/Fkey, Address, star-rating, info)
- Reservation(ReservationID/Key, HotelID/FKey, ShoppingBasketID/FKey, PaymentID/FKey, RoomItemsID/Fkey, CustomerID/FKey, checkInDate, checkOutDate, numOfNights, customerFullName, customerSmoking, contactEmail)
- Location(LocationID/Key)
- Customer(CustomerID/Key,)
- ShoppingBasket(ShoppingBasketID/Key)
- Payment(PaymentID/Key)
- RoomItems(RoomItemsID/Key, type, adults, children, ageFrom, ageTo)
- Room(RoomID/Key, RoomDescriptionID/FKey type, date, price, isAvailabel, reservedNum)
- RoomDescription(RoomDescriptionID/Key, type, listPrice, Info)
- RoomType(RoomTypeID)
2. Payment
Domain modeling looks like this:
The data modeling looks like this:
- Customer(CustomerID/Key, ShoppingBasketID/FKey, Name)
- Payment(PaymentID/Key, CarditCardID/Key, TotalPrice)
- CreditCard(CredotCardID/Key, CHADID/FKey, type, isAvailabel, CardNumber, CardSecurityCode, ExpityDate)
- CardHolderAddressDetail(CHADID/Key, FirstName, LastName, Address1, Address2, City, County/State, Country, Postcode, DaytimeTelephone, EveningTelephone)
- ShoppingBasket(ShoppingBasketID/Key, BookingDetailID/FKey)
- BookingDetail(BookingDetailID/Key, BookingDetailDescription/FKey, TotalPrice, check-in-date, numberOfDate, check-out-date)
- BookingDescription(BookingDescriptionID/Key, Name, Number, Price)
Question 2
- Use UML State Model to model the life cycle of each order object
- Modeling Objects: Model Reservation/Order objects with reference to the Asg_RH documentation
- Modeling requirements: The reference exercise does not provide enough information to help you model the order object. Please refer to the travel website of the hotel booking now, and analyze the various situations surrounding the order as much as possible until the order ends the order through a sales event (counter sales).
