Project- OO Analysis

8/12/2019 Project- OO Analysis

1/27

Project- OO Analysis of the Ophelias Oasis product.

Scenarios for the 14 use cases of Ophelias Oasis appear in Figures 12.9 to 12.1!9.

"For #re$ity% only one scenario for each use case is sho&n here.'

A manager wishes to enter a room base rate.

1. The manager enters the date for which the base rate is to be entered.

2. The manager enters the base rate.

3. The system displays a message that the base rate has been successfully entered.

Figure 12.96. A scenario of the Enter Room Base Rateuse case of Ophelias Oasis.

A manager wishes to update a room base rate.

1. The manager enters the date for which the base rate is to be updated.

2. The manager enters the new base rate.

3. The system displays a message that the base rate has been successfully updated.

Figure 12.9!. A scenario of the Update Room Base Rateuse case of Ophelias Oasis.

A guest wishes to ma"e an incenti#e reser#ation.

1. The employee enters reser#ation information pro#ided by the guest$

%umber of days of reser#ation

&ates of reser#ation

'uest name

'uest address

'uest phone number

'uest e(mail address )if applicable*

'uest credit card number+ e,piration date+ and type )if applicable*

-omments )if applicable*

The employee informs the guest that a room is a#ailable and what the incenti#e rates will

be. The guest accepts the reser#ation.

2. The system displays a message that the reser#ation has been successfully entered.

Figure 12.9. A scenario of the Make an incentive Reservationuse case of Ophelias Oasis.


2/27

A guest wishes chec" if accommodation is a#ailable for specific date)s*.

1. The employee enters the date)s* pro#ided by the guest.

2. The system displays a message regarding room a#ailability for the date)s* specified.

The employee informs the guest as to room a#ailability for the gi#en dates.

Figure 12.99. A scenario of the Check Room Availabilityof the use case of Ophelias Oasis.

A guest wishes to change the dates of a prepaid reser#ation. The guest pro#ides thereser#ation /&.

1. The employee enters the reser#ation /&.

2. The employee enters the new reser#ation information pro#ided by the guest$

%umber of days of reser#ation&ates of reser#ation

The employee confirms room a#ailability and additional charges. The guest replies that theadditional charges are acceptable.

3. The system displays a message that the reser#ation has been successfully changed.

Figure 12.100. A scenario of the Change Reservationuse case of Ophelias Oasis.

A guest wishes to cancel a reser#ation.

1. The employee enters the reser#ation /& pro#ided by the guest.

The employee confirms the reser#ation that the guest is canceling and informs the guest ofany charges that he or she will incur due to the cancellation.

2. The system displays a message that the reser#ation has been successfully cancelled.

Figure 12.101. A scenario of the Cancel Reservationuse case of Ophelias Oasis.

A guest wishes to chec"(in.

1. The employee enters the reser#ation /& pro#ided by the guest.

2. The system displays the number of the room assigned to the guest.

The employee informs the guest as to his or her room number+ and gi#es him or her theroom "ey.

Figure 12.102. A scenario of the Check-in Guestuse case of Ophelias Oasis.


3/27


4/27

An employee wishes to print a daily occupancy report.

1. The employee re4uests that the daily occupancy report be printed.

2. The e(ployee recei#es confirmation that report has been printed successfully.

Figure 12.10. A scenario of the Print Daily Occupancy Reportuse case of Ophelias Oasis.

An employee wishes to print a guests accommodation bill and chec"(out the guest.

1. The employee enters the room number pro#ided by the guest.

2. The system prints the accommodation bill.

The employee hands the bill to the guest.

3. The employee recei#es confirmation that the guest has been chec"ed out successfully.

Figure 12.109. A scenario of the Print Accommodation Bill use case of Ophelias Oasis.

)andidate entity classes are deter(ined using noun e*traction.

Description of information system in a single paragraph:A soft&are product is to #e

de$eloped to handle reser$ations% roo( rates% and guests #ills% and (ust print $arious

infor(ational reports regarding occupancy% arri$als% and inco(e.

Identify the nouns:A soft&are productis to #e de$eloped to handle reser#ations% room

rates% and guests bills% and (ust print $arious infor(ational reports regarding

occupancy% arri#als% departures% and income.

+ith regard to the nouns in the pre$ious paragraph% productand roomdo not change

&hile the syste( is operating, in o#ject-oriented ter(inology% they do not ha$e an

internal state. Also% occupancy+ arri#al+ departure+and incomeare a#stract nouns. ouns

bill and report (ight turn out to #e report classes. Finally% guest is a property of

reser#ation. hus% the candidate entity classes appear to #e Reservation andRate.

he initial class diagra( is sho&n in Figure 12.11!.


5/27

Figure 12.110. The initial class diagram of Ophelias Oasis.

he initial statechart is sho&n in Figure 12.111.

he initial #oundary classes are

Employee Screen Class% Manager Screen Class,Print Expected Occupancy Report Class+Print Expected Room Income report Class+

Print Incentive Report Class+Print Daily Arrivals Report Class +Print Daily OccupancyReport Class+Print Accommodation Bill Class.

he initial control class are Maintain Reservation Class%Maintain Rates Class% Daily

Reports Class+andManager Reports Class.

Rates ClassReservation Class

date

ratereser#ation%umber

typestatus

comment

reser#ation&aysdatesOf7eser#ationguest%ameguest8hone%umber

guestAddressguest5ailAddress

ratesOf7eser#ationcredit-ard%umbercredit-ard5,pirationcredit-ardType

date7eser#ationadedate:il8aid

amount:ill8aide,tra-harges

room%umber


6/27

Figure 12.111. The initial statechart of Ophelias Oasis.

Figure 12.112. -lass diagram showing the classes that reali;e the use cases Enter Base Room

Rateand Update Base Room Rateof Ophelias Oasis.

ManagerScreenClass

MaintainRatesClass

RatesClassManager

Op!elia"s Oasis Product Selector

reser#ation

charges

selected

chec"(in

selected

reser#ations

selected

rates

selected

C!argingReservations

8rocess no(shows

%o(payments.

MaintainingRates

5nter


7/27

Figure 12.113. A collaboration diagram of the reali;ation of the scenarios of Figures 12.96 and 12.9!of theEnter Base Room Rate and Update Base Room Rateuse cases of Ophelias Oasis.

The manager gi#es the date and the )new* rate )1*. The rates are enteredend ac"nowledgment

1$ 'i#e date+ rate

2$ Transfer date+ rate

3$ 5nter


8/27

Figure 12.11 A se4uence diagram e4ui#alent to the collaboration diagram of Figure 12.113. The flowof e#ents is therefore as shown in Figure 12.11.

/se case Make Reservation

he class diagra( for the Make Reservationuse case is sho&n in Figure 12.11.

)onsider the scenario of Figure 12.9. he colla#oration diagra( is sho&n in Figure

12.110% the flo& of e$ents in Figure 12.11% and the eui$alent seuence diagra( in

Figure 12.119.


9/27

Figure 12.116. -lass diagram showing the classes that reali;e the use cases Make Reservation

and Make Reservationof Ophelias Oasis.

Figure 12.11!. A collaboration diagram of the reali;ation of the scenario of Figure 12.9 of theMake

Reservationuse case of Ophelias Oasis.

EmployeeScreenClass

MaintainReservation

Class

ReservationClassEmployee

%uest

Rates

Class

Employee

ScreenClass

MaintainReservation

Class

Reservation

ClassEmployee

%uest

7eser#ation data pro#ided

by the guest

1$ 5nter

reser#ation

data

10$ -onfirm

reser#ation

2$ Transfer

reser#ation

data

11$ Transfer

confirmation

$ &etermine

a#ailability

12$ Transfer

confirmation

9$ &isplay

reser#ation

status1$ &isplay

ac"nowledgment

$ Transfer

reser#ation

information1$ Transfer

ac"nowledgment

6$ 7eturn

a#ailability

status13$ 7eturn

ac"nowledgment

RatesClass

$ 7eturn

base rates

3$ 7e4uest

base rates

!$ Apply

discount


10/27

The employee enters reser#ation data supplied by the guest )1*. The data are used to determinethe rate )2=* and a#ailability )=6*. The incenti#e rate discount is now applied )!*. Theprospecti#e guest is informed that a room is a#ailable and what the rates will be )=9*? the guestaccepts the reser#ation. The reser#ation is confirmed )10=12*+ and the employee is informed thatthis has been done )13=1*.

Figure 12.11. The flow of e#ents of the reali;ation of the scenario of Figure 12.9 of theMakeReservationuse case of Ophelias Oasis.

Figure 12.119 A se4uence diagram e4ui#alent to the collaboration diagram of Figure 12.11!. The flowof e#ents is therefore as shown in Figure 12.11.

2$ Transfer reser#ation

data

3$ 7e4uest rates

9$ &isplay

reser#ation status

$ Transfer reser#ation

information

$ 7eturn rates

$ &etermine a#ailability

6$ 7eturn a#ailability status

%uest Employee

ScreenClass

MaintainReservation

Class

RatesClassEmployee

ReservationClass

7eser#ation

data pro#ided by

the guest

10$ -onfirm reser#ation

11$ Transfer confirmation

12$Transfer confirmation

1$ 5nter reser#ation

data

1$ Transfer

ac"nowledgment

13$ 7eturn ac"nowledgment

1$ &isplay

ac"nowledgment

!$ Apply discount


11/27

Figure 12.120. -lass diagram showing the classes that reali;e the use cases Check Room

Availability+Cancel Reservation+ and Check-in Guestof Ophelias Oasis.

.

Figure 12.121. A collaboration diagram of the reali;ation of the scenario of Figure 12.99 of theCheck

Room Availabilityuse case of Ophelias Oasis.

/se case Check Room Availability

he class diagra( for the Check Room Availabilityuse cases is sho&n in

Figure 12.12!.

)onsider the scenarios of Figure 12.99. he colla#oration diagra( is sho&n in Figure


Figure 12.12.

The employee enters a#ailability data supplied by the guest )1*. The data are entered )2=3*.A#ailability status is sent to the employee )=6* who informs the guest.

Figure 12.122. The flow of e#ents of the reali;ation of the scenario of Figure 12.99 of theCheck

Room Availabilityuse case of Ophelias Oasis.

EmployeeScreenClass

MaintainReservation

Class


%uest

EmployeeScreenClass

MaintainReservation

Class


%uest

A#ailability data pro#ided

by the guest

1$ 5nter

a#ailability

data

2$ Transfer

a#ailability

data

3$ &etermine

a#ailability

6$ &isplay

a#ailabilitystatus

$ Transfer

a#ailabilitystatus

$ 7eturn

a#ailability

status


12/27


%uest Employee

Screen

Class

Maintain

Reservation

Class

Reservation

ClassEmployee

A#ailability

data pro#ided

by the guest

1$ 5nter a#ailability

data

2$ Transfer a#ailability

data

3$ &etermine a#ailability

6$ &isplay a#ailability

status

$ Transfer a#ailabilitystatus

$ 7eturn a#ailability

status


13/27

Figure 12.12. A collaboration diagram of the reali;ation of the scenario of Figure 12.100 of theChange Reservationuse case of Ophelias Oasis.

The employee enters changed reser#ation data supplied by the guest )1*. The data are used todetermine the rate )2=* and a#ailability )=6*. The additional charges for changing a prepaidreser#ation are no computed )!*. The prospecti#e guest is informed that a room is a#ailable andwhat the additional charges will be )=9*? the guest accepts the additional charges. Thereser#ation is confirmed )10=12*+ and the employee is informed that this has been done )13=1*.

Figure 12.12. The flow of e#ents of the reali;ation of the scenario of Figure 12.100 of theChange


/se case Change Reservation

he class diagra( for the Change Reservationuse case is sho&n in Figure

12.11.

)onsider the scenario of Figure 12.1!!. he colla#oration diagra( is sho&n in Figure


Figure 12.12.

EmployeeScreenClass

MaintainReservation

Class


%uest

-hanged reser#ationdata pro#ided by the

guest

1$ 5nter changed

reser#ation

data

10$ -onfirm

reser#ation

2$ Transfer changed

reser#ation

data

11$ Transfer

confirmation

$ &etermine

a#ailability

12$ Transfer

confirmation

9$ &isplayreser#ation

information

1$ &isplay

ac"nowledgment

$ Transferreser#ation

information

1$ Transfer

ac"nowledgment

6$ 7eturna#ailability

status

13$ 7eturn

ac"nowledgment

Rates

Class

$ 7eturn

base rates

3$ 7e4uest

base rates

!$ -ompute

charges


14/27

Figure 12.126. A se4uence diagram e4ui#alent to the collaboration diagram of Figure 12.12. The

flow of e#ents is therefore as shown in Figure 12.12.

2$ Transfer changed

reser#ation data

3$ 7e4uest rates

9$ &isplay reser#ation

information

$ Transfer reser#ation

information

$ 7eturn rates

$ &etermine a#ailability

6$ 7eturn a#ailability status

%uest Employee

ScreenClass

MaintainReservation

Class

RatesClassEmployee

ReservationClass

-hanged

reser#ation data

pro#ided by the

guest

10$ -onfirm reser#ation

11$ Transfer confirmation

12$Transfer confirmation

1$ 5nter changed

reser#ation data

1$ Transfer

ac"nowledgment

13$ 7eturn ac"nowledgment

1$ &isplay

ac"nowledgment

!$ -ompute charges


15/27

Figure 12.12!. A collaboration diagram of the reali;ation of the scenario of Figure 12.101 of the

Cancel Reservationuse case of Ophelias Oasis.

The employee enters the reser#ation /& supplied by the guest )1*. The reser#ation /& is used tocancel the reser#ation )2=3*. -onfirmation is sent to the employee )=6*+ who informs the guest.

Figure 12.12. The flow of e#ents of the reali;ation of the scenario of Figure 12.101 of theCancel


/se case Cancel Reservation

he class diagra( for the Cancel Reservationuse cases is sho&n in Figure 12.12!.

)onsider the scenario of Figure 12.1!1. he colla#oration diagra( is sho&n in Figure


Figure 12.129.

EmployeeScreenClass

MaintainReservation

Class


%uest

7eser#ation /& pro#ided

by the guest

1$ 5nter

reser#ation /&

2$ Transfer

reser#ation /& 3$ -ancel

reser#ation

6$ &isplay

reser#ation

status

$ Transfer

reser#ation

status

$ 7eturn

reser#ation

status


16/27

Figure 12.129 A se4uence diagram e4ui#alent to the collaboration diagram of Figure 12.12!. The flowof e#ents is therefore as shown in Figure 12.12.

%uest Employee

Screen

Class

Maintain

Reservation

Class

Reservation

ClassEmployee

7eser#ation /&

pro#ided by the

guest

1$ 5nterreser#ation /&

2$ Transfer

reser#ation /&

3$ -ancel reser#ation

6$ &isplay reser#ation

status

$ Transfer reser#ationstatus

$ 7eturn reser#ation

status


17/27

Figure 12.130. A collaboration diagram of the reali;ation of the scenario of Figure 12.101 of theCheck-in Guestuse case of Ophelias Oasis.

The employee enters the reser#ation /& supplied by the guest )1*. The reser#ation /& is used toobtain chec"(in information+ including the room number )2=3*. This information is sent to theemployee )=6*+ who informs the guest.

Figure 12.131. The flow of e#ents of the reali;ation of the scenario of Figure 12.102 of theCheck-in

Guestuse case of Ophelias Oasis.

/se case Check-in Guest

he class diagra( for the Cancel Reservationuse cases is sho&n in Figure 12.12!.


12.1!% the flo& of e$ents in Figure 12.11% and the eui$alent seuence diagra( in

Figure 12.12.

EmployeeScreenClass

MaintainReservation

Class


%uest


by the guest

1$ 5nter

reser#ation /&

2$ Transfer

reser#ation /& 3$ 7e4uest chec"(in

information

6$ &isplay

chec"(in

information

$ Transfer

chec"(in

information

$ 7eturn

chec"(in

information


18/27


%uest Employee

Screen

Class

Maintain

Reservation

Class

Reservation

ClassEmployee

7eser#ation /&

pro#ided by the

guest

1$ 5nter

reser#ation /&

2$ Transfer

reser#ation /&

3$ 7e4uest chec"(ininformation

6$ &isplay chec"(in

information

$ Transfer chec"(ininformation

$ 7eturn chec"(in

information


19/27

Figure 12.133. -lass diagram showing the classes that reali;e the use case Reservation

Chargesof Ophelias Oasis.

Figure 12.13. A collaboration diagram of the reali;ation of the scenario of Figure 12.103 of theReservation Chargesuse case of Ophelias Oasis.

The employee enters the date for which reser#ation charges are to be computed )1=3*. Thecharges are made+ and information is sent to the employee )=6*.

Figure 12.13. The flow of e#ents of the reali;ation of the scenario of Figure 12.103 of theReservation Chargesuse case of Ophelias Oasis.

/se case Reservation Charges

he class diagra( for the Reservation Chargesuse cases is sho&n in Figure 12.1.

)onsider the scenario of Figure 12.1!. he colla#oration diagra( is sho&n in Figure


Figure 12.1.

EmployeeScreenClass

MaintainReservation

Class


1$ 5nter date 2$ Transfer date 3$ 7e4uest charges

6$ &isplay charges $ Transfer charges $ 7eturn charges

EmployeeScreenClass

MaintainReservation

Class



20/27


EmployeeScreenClass

MaintainReservation

Class

Reservation

ClassEmployee

1$ 5nter date

2$ Transfer date

3$ 7e4uest charges

6$ &isplay charges

$ Transfer charges

$ 7eturn charges


21/27

Figure 12.13!. -lass diagram showing the classes that reali;e the use casePrint Expected

Occupancy Reportof Ophelias Oasis.

/se case Print Expected Occupancy Report

he class diagra( for thePrint Expected Occupancy Report use case is sho&n in

Figure 12.10.



Figure 12.14!.

ManagerScreen

Class

Manager Manager

Reports

Class

Print ExpectedOccupancy Report

Class

Reservation

Class

Manager

ScreenClass

Manager

1$ 5nter re4uest 2$ Transfer re4uest $ 7e4uest report

6$ >endac"now(

ledgment

!$ Transferac"now(

ledgment

.$ &isplayac"now(

ledgment ManagerReports

Class


Class

ReservationClass

3$ 7e4uestreport data

$ 7eturnreport data


22/27

Figure 12.13. A collaboration diagram of the reali;ation of the scenario of Figure 12.10 of thePrint Expected Occupancy Reportuse case of Ophelias Oasis.

The manager re4uests the report )1=2*. The information is obtained )3=*. The report is printed)*+ and an ac"nowledgment is sent to the manager )6=*.

Figure 12.139. The flow of e#ents of the reali;ation of the scenario of Figure 12.10 of thePrint

Expected Occupancy Reportuse case of Ophelias Oasis.

.


/se case Print Expected Room Income Report

/se case Print Incentive Report

he reali5ations of these t&o use cases are si(ilar to that of use case Print Expected

Occupancy Report "Figures 12.10 through 12.14!'.

ManagerScreen

Class

ManagerReports

Class

ReservationClassManager

1$ 5nter re4uest

2$ Transfer re4uest

3$ 7e4uest report data

$ >end report data

!$ Transferac"nowledgment

.$ &isplay

ac"nowledgment


Class

$ 7e4uest report

6$ >end ac"nowledgment


23/27

Figure 12.11. -lass diagram showing the classes that reali;e the use case Print Daily

Arrivals Reportof Ophelias Oasis.

/se case Print Daily Arrivals Report

he class diagra( for thePrint Daily Arrivals Report use cases is sho&n in

Figure 12.141.


12.142% the flo& of e$ents in Figure 12.14% and the eui$alent seuence diagra( inFigure 12.144.

EmployeeScreenClass

Employe DailyReportsClass

Print DailyArrivals

Class

ReservationClass


24/27

Figure 12.12. A collaboration diagram of the reali;ation of the scenario of Figure 12.10! of thePrint Expected Occupancy Reportuse case of Ophelias Oasis.

The employee re4uests the report )1=2*. The information is obtained )3=*. The report is printed)*+ and an ac"nowledgment is sent to the manager )6=*.

Figure 12.13. The flow of e#ents of the reali;ation of the scenario of Figure 12.10! of thePrint

Daily Arrivals Reportuse case of Ophelias Oasis.


EmployeeScreen

Class

Employee

1$ 5nter re4uest 2$ Transfer re4uest $ 7e4uest report

6$ >end

ac"now(

ledgment

!$ Transfer

ac"now(

ledgment

$ &isplay

ac"now(

ledgment Daily

ReportsClass

Print Daily

ArrivalsClass

ReservationClass

3$ 7e4uest

report data

$ 7eturn

report data

EmployeeScreenClass

DailyReportsClass


1$ 5nter re4uest

2$ Transfer re4uest

3$ 7e4uest report data

$ >end report data

!$ Transfer

ac"nowledgment $ &isplay

ac"nowledgment

Print DailyArrivals

Class

$ 7e4uest report

6$ >end ac"nowledgment


25/27

/se case Print Daily Occupancy Report

his use case is si(ilar to use case Print Daily Arrivals Report "Figures 12.141

through 12.144'.

/se case Print Accommodation Bill

he class diagra( for the Print Accommodation use cases is sho&n in Figure

12.143.



Figure 12.14.


26/27

Figure 12.1. -lass diagram showing the classes that reali;e the use case Print

Accommodation Billof Ophelias Oasis.

Figure 12.16. A collaboration diagram of the reali;ation of the scenario of Figure 12.109 of thePrint Accommodation Billuse case of Ophelias Oasis.

The guest+ wishing to chec"(out+ supplies his or her reser#ation /& to the employee+ who enters itinto the system )1*. The reser#ation /& is used to compute the bill )2=*+ which is then printed )*.An ac"nowledgment is sent to the employee )6=* that the bill has been printed and the guestchec"ed(out.

Figure 12.1!. The flow of e#ents of the reali;ation of the scenario of Figure 12.109 of thePrint

Accommodation Billuse case of Ophelias Oasis.

Employee

Screen

Class

Maintain

Reservation

Class

Print

Accommodation Bill

Class

Employee

%uest

1$ 5nter

reser#ation /&

2$ Transfer

reser#ation /&

$ 7e4uest bill

be printed

.$ &isplayac"nowledgment

!$ Transferac"nowledgment

6$ 7eturnac"nowledgment

Reservation

Class

$ 7eturn bil l

information

3$ 7e4uest bill

information


by the guest

EmployeeScreen

Class

MaintainReservation

Class

PrintAccommodation Bill

Class

Employee

%uest

ReservationClass


27/27

Documents

Project- OO Analysis