Skip to main content Accessibility help
×
Hostname: page-component-5c6d5d7d68-tdptf Total loading time: 0 Render date: 2024-08-15T14:40:19.357Z Has data issue: false hasContentIssue false

3 - Reservations Online: Case Study 1

Published online by Cambridge University Press:  05 June 2012

Ghinwa Jalloul
Affiliation:
American University of Beirut
Get access

Summary

Work on this case study was motivated by an anticipated need of travel agencies to improve their sales by making their products, namely, tours, directly accessible to their client base. Although this application focuses on travel agencies, it could be viewed as one instantiation of a general application framework that handles reservations in general, such as hotel and car reservations.

INCEPTION

USER REQUIREMENTS

User requirements are a summary of information that is collected by customers asking travel agencies about tours that the travel agencies offer. From that information we deduced the user requirements, shown in Description 3-1.

Constraints

For simplicity, we made two assumptions. The first one is that the customer can only reserve a single tour. Consequently, he is assigned a login ID and a password. The second assumption is that the customer can optionally reserve as many trips as he wants in his tour reservation. For example, suppose that the travel agency company provides a tour to Athens. Then the customer who chooses this tour can optionally choose one or more trips related to the Athens tour such as a trip to the temples or a tour to Olympus.

A software for a travel agency provides reservation facilities for the people who wish to travel on tours by accessing a built-in network at the agency bureau. The application software keeps information on tours. Users can access the system to make a reservation on a tour and to view information about the tours available without having to go through the trouble of asking the employees at the agency. The third option is to cancel a reservation that he/she made. […]

Type
Chapter
Information
UML by Example , pp. 83 - 129
Publisher: Cambridge University Press
Print publication year: 2004

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×