Sie sind auf Seite 1von 23

Hotel Management System

ANALYSIS AND DESIGN MODELS


prepared by Team 1
Sandra Busik
Susan Le
Peter Lockwood
Pradeep Miglani
Reita Sikka
Kai Zhang

TABLE OF CONTENTS
1

ANALYSIS MODEL.......................................................................................................................................................................................................................................................3
1.1
1.2
1.3
1.4

STATIC MODEL.......................................................................................................................................................................................................................................................3
ATTRIBUTES OF THE CLASSES ON THE STATIC MODEL.............................................................................................................................................................................4
STATE CHARTS.......................................................................................................................................................................................................................................................5
COLLABORATION DIAGRAMS (ONE FOR EACH USE CASE) & MESSAGE SEQUENCE DESCRIPTIONS.....................................................................................................8

DESIGN MODEL............................................................................................................................................................................................................................................................8
2.1
CONSOLIDATED COLLABORATION DIAGRAMS & MESSAGE SEQUENCE DESCRIPTIONS.................................................................................................................8
2.1.1 CONSOLIDATED COLLABORATION DIAGRAMS............................................................................................................................................................................................9
2.1.2 MESSAGE SEQUENCE DESCRIPTIONS FOR CONSOLIDATED COLABORATION DIAGRAMS...............................................................................................................11
2.2
DISTRIBUTED SOFTWARE ARCHITECTURE DOCUMENT..........................................................................................................................................................................13
2.2.1 DESCRIPTION OF HOW THE SYSTEM IS DECOMPOSED INTO COMPONENT-BASED SUBSYSTEMS & CONCURRENT COLLABORATION DIAGRAM...............13
2.2.2 DESIGN OF RELATIONAL DESIGN DATABASE.............................................................................................................................................................................................15
2.3
SUBSYSTEM SOFTWARE ARCHITECTURE....................................................................................................................................................................................................16
2.3.1 OVERVIEW DESCRIPTION OF SUBSYSTEM SOFTWARE ARCHITECTURE...............................................................................................................................................16
2.3.2 TASK ARCHITECTURE......................................................................................................................................................................................................................................17
2.4
INFORMATION HIDING CLASSES....................................................................................................................................................................................................................19

1 ANALYSIS MODEL
1.1 STATIC MODEL

Static Diagram
Payment
Bill

Reservation
has

makes

processes

HMS

authenticates

Customer

has

Discount

User
has

authenticates

Login

uses
Room

Room
Availability

1.2

ATTRIBUTES OF THE CLASSES ON THE STATIC MODEL

Static Diagram Attributes


<<entity>>
Customer
customerID : int = 0
fName : string = ""
lName : string = ""
mName : string = ""
Street : string = ""
city : string = ""
state : string = ""
zip : string = ""
zip4 : int = 0
Country : type = initval
homePhone
WorkPhone
Email
Preferences
LastVisited
CCNum
CCExp
CCExpYr
CCHolder

<<entity>>
Payment
paymentID : Integer
paymentType : String
paymentTypeDesc : String
CCNumber : String
CCExp : String
CCOwner : String
paymentAmount : String
paymentDate : Date
<<entity>>
Room
roomID : Integer
roomNumber : Integer
roomType : String
roomStatus : String
roomDesc : String
roomRate : String
numBeds : String
isAvailable : Boolean

<<entity>>
Report
reportType : string = ""

<<entity>>
Reservation
reservationID : int = 0
customerID : int = 0
reservationDate : Date = 0
ExpCheckinDt : Date
expCheckoutDt : Date
AnticipatedArrTime
NumGuests
ToomTypeID
RoomRate
Smoking
Preferences
Guaranteed
Comments
PaymentType
BedType
Discount

<<entity>>
User
userID : Integer
loginName : String
password : String
roleID : Integer
userFirstName : String
userMName : String
userLastName : String
userContactInfo : String

<<<<entity>>>>
RoomAvailability
roomAvailabilityID : Integer
roomTypeID : Integer
Date : Date
NumAvailable : Integer

<<entity>>
Discount
discountID : Integer
discountName : String
discountPercent : String
discountExp : Date
discountAmount : Integer
description : String

1.3 STATE CHARTS

Room Statechart

Customer makes a reservation


Available

Not Available
Five hrs. past check in

Customer checks in
Customer checks in

Customer checks out

Occupied

Bill/Payment Statechart

Recieve & add item

Open

Adjust Bill

Generate Bill

Generated

Record Payment

Scheduler Statechart
Retrieve Time
System Started
Time is 1:00 p.m.

Scheduler Running

Billing Additional Day

Billing Complete
System Stopped
Time is 6:30 p.m.
Reservations Canceled

Billing Complete
Time is 6:00 p.m.

Billing Guaranteed Reservations

Cancelling Non-guaranteed Reservations

1.4

COLLABORATION DIAGRAMS (one for each use case) & MESSAGE SEQUENCE DESCRIPTIONS
We have done individual collaboration diagrams (one for each use case). Per Dr. Wu, they are not required to be turned in. Please see
Consolidated Collaboration Diagrams and Message Descriptions for Consolidated Collaboration Diagrams in section 2.1.1 and 2.1.2,
respectively.

2 DESIGN MODEL
2.1

CONSOLIDATED COLLABORATION DIAGRAMS & MESSAGE SEQUENCE DESCRIPTIONS

2.1.1 CONSOLIDATED COLLABORATION DIAGRAMS


CONSOLIDATED COLLABORATION DIAGRAM FOR RESERVATION & BOOKING SYSTEM
<<entity>>

<<entity>>

: Customer

: Report

Retriev e/Add/Update Cust Record

Customer data

Report

<<control>>
: CustRecord

CSR Input

Report request

<<control>>
: GenerateReport

: Customer
ServiceRep
'Customer Record' selected

Display Inf o

'Generate Report' selected

<<user interface>> CSR/Manager Ev ents (Transaction Details) <<control>>


: HMSControl
: HMSInterface

<<periodic timer>>
: Scheduler

Inf ormation display ed

Manager
Input

Cancel non-guaranteed
Bill no-show
Bill additional day

Reserv ation display ed


Display Inf o

'Checkin' selected

<<control>>
: Checkin

<<control>>
: ReservationControl
Apply /Remov e discount

Set Room
Status

Set Room
Status

<<control>> Update Pay ment <<entity>>


: Checkout
: Payment

<<entity>>

Generate Bill

: Room

Av ailability
inf o

Update
Reserv ation

Reserv ation
Inf o

<<entity>>

Apply /Remov e
discount

Check av ailability
Update av ailability
Av ailability
inf o

: Scheduler
(Timer)

'Checkout' selected

'Reserv ation' selected

: Manager

Scheduler Ev ents

Bill data

<<entity>>
Apply /Remov e Discount
Check Av ailability
Update Av ailability

:RoomAvailability

<<control>
:Discount

: Bill

Room Serv ices /Food Bill data

: Reservation

<<subsystem>>
:Room Services/Food
Subsystem

CONSOLIDATED COLLABORATION DIAGRAM FOR MANAGEMENT SERVICES SYSTEM


<<entity>>
: Report

Report

Report Request

<<control>>
: GenerateReport

'Generate Report' selected

Manager Input

Display Info

<<user interface>>
: HMSInterface

Manager Events (Transaction Details)

<<control>>
: HMSControl

Information Displayed

: Manager

'User Administration' selected


'Room Administration' selected
<<control>>
: RoomAdmin

Room Info

Add/Update Room Info

<<entity>>
: Room

<<control>>
: UserAdmin

User Profile Info

Add/Update/Delete User Profile

<<entity>>
: User

10

2.1.2 MESSAGE SEQUENCE DESCRIPTIONS FOR CONSOLIDATED COLABORATION DIAGRAMS


Message Sequence Description for Consolidated Collaboration Diagram of Reservation and Booking System
The message sequence description below addresses the messages on the Consolidated Collaboration Diagram for Reservation and Booking System.
CSR or Manager actor inputs screen selection and information to HMS Interface.
HMS Interface sends the CSR's or Manager's reservation & booking transaction inputs to Reservation.
Reservation sends a Retrieve Customer Info request along with customer's name to Customer to search for the customer record.
If the customer record is already in the system, Customer sends Customer Info to Reservation. Reservation sends Update Customer Info
request along with updated info to Customer.
If the customer record is not yet in the system, Reservation sends Create Customer Info request along with customer info to Customer to
create a customer record.
Customer sends Add/Update/Retrieve Customer Info message to HotelDatabase.
Reservation sends a Check Room Availability request along with information on room type, check-in date, check-out date to Room to search for a
vacant room.
Room sends a Retrieve Room Availability request to HotelDatabase to get room availability information.
HotelDatabase sends a Room Availability Info response to Room.
Room sends Availability Status to Reservation.
Reservation sends an Apply Discount request to Discount.
Discount sends Get Discount message to HotelDatabase to obtain discount data.
Reservation sends an Update/Retrieve Data request to HotelDatabase to update/retrieve reservation&booking data, and HotelDatabase sends
reservation&booking data to Reservation.
Reservation sends a Generate Bill, Charge Bill (or Credit Bill) request along with balance due information to Bill/Payment.
Bill/Payment sends Get Room/FoodService Bill Data message to Room/Food Services System, and Room/Food Services System sends
Room/FoodService Bill Data to Bill/Payment.

Timer sends Scheduler Events to Scheduler.


Scheduler sends a Get Reservation Data request to HotelDatabase. HotelDatabase returns Reservation Data to Scheduler.
Scheduler sends a Cancel Non-Guaranteed Reservation request to Reservation.
Scheduler sends Bill No-Show, Bill Additional Day, Bill GuaranteedReservation request to Bill/Payment.
11

HMS Interface sends Make Payment (or Credit Payment) message along with customer's payment information to Bill/Payment.
Bill/Payment sends a Payment Made (or Payment Credited) acknowledgment message to HMSInterface.
Bill/Payment sends an Update Bill/Payment request to HotelDatabase.

HMS Interface sends GenerateReport request along with ReportType, ReportParameters to Report.
Report sends Get Pending Checkout Data message to HotelDatabase.
HotelDatabase sends Pending Checkout Data to Report.
Report sends Report generated to HMSInterface.

HMSInterface sends DisplayInfo message to display information to CSR or Manager actor.

Message Sequence Description for Consolidated Collaboration Diagram of Management Services System
The message sequence description below addresses the messages on the Consolidated Collaboration Diagram for Management Services System.

Manager actor inputs screen selection and information to HMS Interface.


HMS Interface sends Administer User Profile (or Administer Info on Room & Rate) message along with the information inputs to Administration.
Administration sends a Add/Modify/Delete Employee Profile request along with employee information inputted to Employee.
Employee sends an Update/Get Employee Info request to HotelDatabase.
HotelDatabase sends an Employee Info response to Employee.

Administration sends a Add/Modify/Delete Info on Room & Rate request along with room information inputted to Room.
Room sends an Update/Get info on Room & Rate request to HotelDatabase.
HotelDatabase sends an Info on Room & Rate response to Room.

HMS Interface sends GenerateReport request along with ReportType, ReportParameters to Report.
Report sends Get Report Data message to HotelDatabase.
HotelDatabase sends Report Data to Report.
Report sends Report generated to HMSInterface.

HMSInterface sends DisplayInfo message to display information to Manager actor.

12

2.2 DISTRIBUTED SOFTWARE ARCHITECTURE DOCUMENT


2.2.1 DESCRIPTION OF HOW THE SYSTEM IS DECOMPOSED INTO COMPONENT-BASED SUBSYSTEMS &
CONCURRENT COLLABORATION DIAGRAM
As shown on the Concurrent Collaboration Diagram below, the subsystems consist of a Reservation and Booking subsystem, a Room and Food
Services subsystem, and a Management Services subsystem. These subsystems were determined through the use-case-based collaboration diagrams.
The objects in the use-case-based collaboration diagrams that communicate frequently with each other, are related to each other, and have high coupling
were placed in the same subsystem. Each of these subsystems also performs a major function, which is relatively independent of the functionality
provided by the other subsystems. These subsystems can be allocated to a separate node in the distributed environment or can be executed on the same
node as other subsystems. These three subsystems are composite subsystems because they all reside at the same location. They all have localized
autonomy. Each subsystem controls a given aspect of the system. They encapsulate the objects they contain. The communication between the three
subsystems is loosely coupled asynchronous message communication. The Hotel Management System component encompasses the three subsystems.
The Hotel Management System is also a composite system. It also encapsulates the objects it contains. All of these components are logical and physical
containers.
Concurrent Collaboration Diagram Documentation
The Hotel Management System contains three subsystems. These are Reservation and Booking, Room and Food Services, and Management
Services. The Reservation and Booking subsystem encompasses customer check in, check out, room reservation, billing for the customers' stay, and
room availability. The Room and Food Services subsystem allows the customer service representative to create the customers' food order and will
generate a bill for the order. The Management Services subsystem deals with the maintenance of the hotel services. This subsystem allows management
to add, modify, and delete information on rooms and rates and food menu items and prices. Management Services also may administer new employee
user profiles for the HMS. The managers may delete, modify, and add employee profiles. This subsystem will also generate reports on these uses.
The Hotel Management System Interface will allow the users; Managers and customer service representatives to interact with the system. The
users will be able to administer Reservation & Booking services, Room & Food services, and Management services (for management only).
The external output device, the printer, is not part of the software to be created. The computers in the hotel will have printers available. The
report on pending checkouts and the bill data generated from the Reservation & Booking subsystem will be able to be printed. The reports of all
subsystem data from the Management Services subsystem will be able to be printed. The bill generated from the Room & Food Services subsystem will
be able to be printed.
Concurrent Collaboration Diagram below

13

CONCURRENT COLLABORATION DIAGRAM


Concurrent Collaboration Diagram

<<system>>
:Hotel Management System

<<subsystem>>
:Reservation &
Booking

<<subsystem>>
:Room & Food
Services

items added to cost


room & customer info

<<subsystem>>
:Management
Services

menu item, price

reports of all subsystems' data


report pending checkout
bill data generated
HMS request
HMS data requested

bill generated

<<external output device>>


:Printer

<<user interface>>
:Hotel Management
System Interface

14

2.2.2 DESIGN OF RELATIONAL DESIGN DATABASE

HMS Data Relationship Model

15

2.3 SUBSYSTEM SOFTWARE ARCHITECTURE


2.3.1 OVERVIEW DESCRIPTION OF SUBSYSTEM SOFTWARE ARCHITECTURE
The Hotel Management System is functionally decomposed into the Reservations and Management subsystems. This section describes the
criteria used to determine which objects are active and which are information-hiding classes. Active objects execute concurrently and run in their
own thread. The active objects are modeled as tasks and the other objects are modeled as information hiding classes. A collaboration diagram is
given for each subsystem. The objects having the thicker, bolded borders are tasks. In the Information Hiding Classes Diagram, each class has
been given a <<stereotype>> to reflect the type of class being shown. Here are the criteria used to determine which objects in each subsystem are
active.

Keep design simple by not having too many tasks


Objects that execute concurrently can be made into tasks
Identify user interface objects
o HMS Interface
Identify device interfaces
o None, other than standard i/o (keyboard, mouse, monitor, and printer)
Identify system interfaces
o Room and Food Service System
o Reservation and Management subsystems
Identify entity objects
o See Information Hiding Classes Diagram
Identify timer objects
o Scheduler
Identify state dependent control objects
o No state dependent control objects that need to run in their own thread
Identify coordinator objects
o HotelDatabase object coordinates access to the database
Identify business logic objects
o The only business logic object in this stand-alone system is the Reservation object. This object will not be accessed concurrently, so it
does not need to run in its own thread. Each client will have its own instance of the Reservation object.
Identify algorithm objects
o No substantial algorithms used in the problem domain
16

2.3.2 TASK ARCHITECTURE

ODBC

TASK ARCHITECTURE DIAGRAM FOR RESERVATION & BOOKING SYSTEM

ODBC

Get Pending CheckOut Data

: Report

Pending CheckOutData

: Discount

<<Coordinator>> : <<Access
HotelDatabase
DB>>

: HotelDatabase

Get Discount

Update / Retrieve Room Availability


Room Availability Info

: Room

Data returned
Apply
Discount

Availability
Status

Update/Retrieve data

CheckRoomAvailability (Type, Dates)


Set Room Availability

Update/Retrieve Customer Info

Update Bill/Payment
Customer Info

: Reservation

Create/Update/Retrieve Customer Info

: Customer

Get Reservation Data


Reservation Data returned

Customer Info

GenerateReport (PendingCheckOutRpt,
Report Generated
ReportParameters)

Cancel Non-Guaranteed
Reservation
Generate Bill
Charge Bill
CreditBill

Reservation Info

Create/Retrieve/Update Reservation, CheckIn, CheckOut (Trans Data)

<<Periodic>> : Scheduler

<<External Timer>>

Timer Events

Bill No-Show
Bill Additional Day
Bill GuaranteedReservation

Make Payment, Credit Payment

<<User Interface>>

: Bill/Payment

: HMSInterface

: DigitalClock

<<Subsystem>> : FoodService

Payment made, Payment credited

Manager Input

Display Info
CSR Input

Generate Bill

Display Info
Bill Data returned

: Customer
ServiceRep

: Manager

17

ODBC

TASK ARCHITECTURE DIAGRAM FOR MANAGEMENT SERVICES SYSTEM


Get Report Data

ODBC

<<Coordinator>> : HotelDatabase <<Access DB>>

: Report

: HotelDatabase

Report Data
Update/Get Info on Room & Rate

: Room

Info on Room & Rate


Employee
Info

Update/Get
Employee Info

Add/Modify/Delete Info on Room & Rate


Report
Generated

GenerateReport (ReportType,
ReportParameters)

: Administration
Add/Modify/Delete Employee Profile

Administer User Profile


Administer Menu Item & Price
Administer Info on Room & Rate

<<User Interface>>

Manager Input

: Employee

: HMSInterface

Display Info

: Manager

18

2.4 INFORMATION HIDING CLASSES

<<entity>>
Customer
customerID : int = 0
fName : string = ""
lName : string = ""
mName : string = ""
Street : string = ""
city : string = ""
state : string = ""
zip : string = ""
zip4 : int = 0
Country : type = initval
homePhone
WorkPhone
Email
Preferences
LastVisited
CCNum
CCExp
CCExpYr
CCHolder
getFName()
getCustomerID()
getLastDateVisited()
getEmail()
getPreferences()
getMName()
getLName()
getStreet()
getState()
getZip()
getZip4()
getCountry()
getHomePhone()
getWorkPhone()
getCCNum()
getCCExp()
getCCxpYr()
getCCholder()()
setFName()
setCustomerID()
setLastDateVisited()
setEmail()
setPreferences()
setMName()
setLName()
setStreet()
setState()
setZip()
setZip4()
setCountry()
setHomePhone()
setWorkPhone()
setCCNum()
setCCExp()
setCCxpYr()
setCCholder()

<<<<control>>>>
Checkin
sReservation : String = ""
sReservationDate : String = ""
sFirstName : String = ""
sMI : String = ""
sLastName : String = ""
sStreet : String = ""
sCity : String = ""
sState : String = ""
sZip : String = ""
sHomePhone : String = ""
sWorkPhone : String = ""
sEmail : String = ""
sCheckinDt : String = ""
sComments : String = ""
sPreferences : String = ""
sArrivalTime : String = ""
sGuests : String = ""
sCheckinDate : String = ""
sCheckoutDate : String = ""
sRoomRate : String = ""
sCCHolder : String = ""
sPayment : String = ""
sCCNumber : String = ""
sExpMonth : String = ""
sCheckinID : String = ""
sRoomID : String = ""
sAmtPaid : String = ""
sRoomNumber : String = ""
sCheckinID : String = ""
sRoomID : String = ""
sRoomType : String = ""
sRoomTypeID : int = ""
sPaymentID : String = ""
sPaymentTypeID : Stirng = ""
sReservationID : String = ""
customerID : int
sDiscount : String = ""
clearAll()
populateCombos()
CheckOut()
jbInit()
btnDiscount_actionPerformed()
btnClear_actionPerformed()
btnClose_actionPerformed()
btnRetrieve_actionPerformed()
insertReservation()
checkFrontEndValidations()
btnCheckIn_actionPerformed()
btnRoomNbr_actionPerformed()
insertCustomer()
updateReservation()
getData()
PopulateRecord()

<<<<control>>>>
Checkout
sReservation : String = ""
sReservationDate : String = ""
sFirstName : String = ""
sMI : String = ""
sLastName : String = ""
sStreet : String = ""
sCity : String = ""
sState : String = ""
sZip : String = ""
sHomePhone : String = ""
sWorkPhone : String = ""
sEmail : String = ""
sCheckinDt : String = ""
sComments : String = ""
sPreferences : String = ""
sArrivalTime : String = ""
sGuests : String = ""
sCheckinDate : String = ""
sCheckoutDate : String = ""
sRoomRate : String = ""
sCCHolder : String = ""
sPayment : String = ""
sCCNumber : String = ""
sExpMonth : String = ""
sCheckinID : String = ""
sRoomID : String = ""
sAmtPaid : String = ""
sRoomNumber : String = ""
sCheckoutID : String = ""
sDiscount : String = ""
nBillID : int
nBillSum : int
sHtlBal : int
nBillItemAmt : int
clearAll()
populateCombos()
CheckOut()
jbInit()
btnDiscount_actionPerformed()
btnClear_actionPerformed()
btnClose_actionPerformed()
btnRetrieve_actionPerformed()
checkFrontEndValidations()
btnPayment_actionPerformed()
btnCheckout_actionPerformed()
checkFrontEndValidation()
getData()
PopulateRecord()

19

Information Hiding Classes (continued)


<<Utilities>>
CLIENT
HMSControl ParentFrame : static
showMessage()
Debug()
Confirm()
sqlEncode()
getStatus()
validateAlphaNumeric()
getRoomTypeID()
getRoomType()
VerifyDate()
getDate()
replaceString()
convertSQLQuotesToNull()
populateStateCombo()
getINIParam()
SetParent()
SetStatus()
SetStatusReady()
OpenDialog()
executeQuery()
executeupdate()
SetMouseCursor()

<<<<control>>>> <<User Interface>>


<<Database>>
HMS Interface
HMSControl
jdbcConnection
ParentFrame
userName : String
openFrame()
MenuBar
password : String
doLogin()
ToolBar
databaseName : String
Init()
getData()
setData()
commit()
rollback()
<<control>>
Scheduler
customerID : int = 0
reservationID : int = 0
roomRate : int = 0
chargeRoom : boolean = False
timeChargeForNoShow : string = ""
timeChargeForAdditionalDay : string = ""
timeChargeForGuaranteedRoom : string = ""
cancelNonGuarRes()
billGuarRoom()
billAddtlDay()
billNoShows()

20

Information Hiding Classes (continued)


<<entity>>
Room
roomID : Integer
roomNumber : Integer
roomType : String
roomStatus : String
roomDesc : String
roomRate : String
numBeds : String
isAvailable : Boolean

<<entity>>
Payment
paymentID : Integer
paymentType : String
paymentTypeDesc : String
CCNumber : String
CCExp : String
CCOwner : String
paymentAmount : String
paymentDate : Date

getRoomNumber()
getRoomType()
getRoomStatus()
getRoomDesc()
getNumBeds()
isAvailable()
setRoomNumber()
setRoomStatus()
setRoomRate()
setRoomDesc()
setNumBeds()
makeAvailable()

getPaymentType()
getPaymentTypeDesc()
getCCNumber()
getCCExp()
getCCOwner()
getPaymentAmount()
getPaymentDate()
setPaymentType()
setPaymentTypeDesc()
setCCNumber()
setCCExp()
setCCOwner()
setPaymentAmount()
setPaymentDate()

<<entity>>
Report
reportType : string = ""
generateReport()

<<entity>>
Reservation
reservationID : int = 0
customerID : int = 0
reservationDate : Date = 0
ExpCheckinDt : Date
expCheckoutDt : Date
AnticipatedArrTime
NumGuests
ToomTypeID
RoomRate
Smoking
Preferences
Guaranteed
Comments
PaymentType
BedType
Discount
getReservationID()
getCustomerID()
getReservationDt()
getExpCheckinDt()
getExpCheckoutDt()
getAnticipatedArrTime()
getNumGuests()
getRoomTypeID()
getRoomRate()
getSmoking()
getPreferences()
getComments()
getPaymentType()
getBedType()
getDiscount()
setReservationID()
setCustomerID()
setReservationDt()
setExpCheckinDt()
setExpCheckoutDt()
setAnticipatedArrTime()
setNumGuests()
setRoomTypeID()
setRoomRate()
setSmoking()
setPreferences()
setComments()
setPaymentType()
setBedType()
setDiscount()

<<entity>>
User
userID : Integer
loginName : String
password : String
roleID : Integer
userFirstName : String
userMName : String
userLastName : String
userContactInfo : String
getUserID()
getLoginName()
getPassword()
getRoleID()
getUserFirstName()
getUserMName()
getUserLastName()
getUserContactInfo()
setUserID()
setLoginName()
setPassword()
setRoleID()
setUserFirstName()
setUserMName()
setUserLastName()
setUserContactInfo()

21

Information Hiding Classes (continued)


<<<<control>>>>
SearchResults
aReservationControl : ReservationControl
aCheckin : Checkin
aCustRecord : CustRecord
aPayment : Payment
SearchResults()
SearchResults()
SearchResults()
SearchResults()
SearchResults()
jbInit()
btnCancel_actionPerformed()
btnSelect_actionPerformed()
<<<<control>>>>
Discount
customerID : int = 0
reservationID : int = 0
discountType : string = ""
discountAmount : int = 0
discountID : Integer
discountPercent : String
discountExp : Date
discountAmount : Integer
description : String

<<<<control>>>>
RoomAvailability
myCheckin : Checkin
roomAvailabilityID : Integer
roomTypeID : Integer
Date : Date
NumAvailable : Integer
RoomAvailability()
RoomAvailability()
jbInit()
populateRoomType()
btnClose_actionPerformed()
btnSearch_actionPerformed()
doSearch()
validateInput()
btnClear_actionPerformed()
checkAvailability()
showAvailability()
decrementRoom()
IncrementRoom()
makeOccupied()
makeAvailable()
btnOK_actionPerformed()

<<<<control>>>>
UserAdmin
userID : Integer
loginName : String
password : String
roleID : Integer
userFirstName : String
userMName : String
userLastName : String
userContactInfo : String
aUser : User

<<<<control>>>>
RoomAdmin
roomID : Integer
roomNumber : Integer
roomTypeID : Integer
roomStatusID : Integer
description : String
smoking : String
roomRate : Double
numberOfBeds : Integer

findUser()
updateUserInfo()
addUser()
deleteUser()

findRoom()
updateRoomInfo()
addRoom()
deleteRoom()
updateRoomTypeInfo()

applyDiscount()
removeDiscount()

22

Information Hiding Classes (continued)


<<<<control>>>>
CustRecord
sReservation : String = ""
sReservationDate : String = ""
sFirstName : String = ""
sMI : String = ""
sLastName : String = ""
sStreet : String = ""
sCity : String = ""
sState : String = ""
sZip : String = ""
sHomePhone : String = ""
sWorkPhone : String = ""
sEmail : String = ""
sCheckinDt : String = ""
sPreferences : String = ""
sDiscount : String = ""
clearAll()
populateCombos()
CheckOut()
jbInit()
insertCustomer()
checkFrontEndValidations()
btnSave_actionPerformed()
btnClear_actionPerformed()
btnClose_actionPerformed()
btnRetrieve_actionPerformed()

<<<<control>>>>
GenerateReport
btnCancel : JButton
btnClear : JButton
btnExceptions : JButton
btnOccupancy : JButton
btnPending : JButton
btnPendingCO : JButton
btnRevenue : JButton
txtBeginDate : String
txtEndDate : String
btnCancel_actionPerformed()
btnClear_actionPerformed()
btnExceptions_actionPerformed()
btnOccupancy_actionPerformed()
btnPendingCO_actionPerformed()
btnRevenue_actionPerformed()
verifyBeginEndDate()
verifyDate()

<<<<control>>>>
ReservationControl
sReservationDate : String
sFName : String
sMI : String
sLName : String
sStreet : String
sCity : String
sState : String
sZip : type
sZip4 : String
sHomePhone : String
sWorkPhone : String
sEmail : String
sCheckinDt : String
sCheckoutDt : String
nRoomType : int
sArrivalTime : String
sGuests : String
sRoomRate : String
sPaymentType : String
sBedType : String
sCCHolderName : String
sSmoking : String
sCCNumber : String
sCCExpMo : String
sCCExpYr : String
sComments : String
sPreferences : String
sGuaranteed : String
sDiscount : String
isNewCust : boolean
jbInit()
populateCombos()
btnClose_actionPerformed()
getDate()
btnSave_actionPerformed()
btnRetrieve_actionPerformed()
insertCustomer()
updateCustomer()
insertReservation()
updateReservation()
populateRecord()
btnClear_actionPerformed()
btnDiscount_actionPerformed()
btnCancel_actionPerformed()
cmbRoomType_actionPerformed()
opname()

23

Das könnte Ihnen auch gefallen