Adventure Builder Data Model

From SAD

Jump to: navigation, search

Contents

Primary Presentation

Image:DataModel_PP.png

Visio file


Element Catalog

PurchaseOrder
OrderStatusHistory
Document
UserAccount

An end user of the AdventureBuilder application. We store email id, password, and contact info.

AirlineOrder
Transportation

Each transportation entry is a flight available for booking in our travel packages. For each one, we record: name, departure and arrival airports, days and times, airline name, flight number, rate, cabin class.

LodgingOrder
Lodging

A hotel, guesthouse or B&B that can be used for lodging in our travel packages. For each type of lodging, we store name, description, location info, room description, rates.

Package

A travel package available in our catalog. A package specifies lodging and a list of activities. Attributes of a package include name, description, rate per person, category and a representative image to show to the user.

Category

A category of adventure travel packages. Examples: island packages, mountain adventures. This categorization helps the user to browse through our catalog of packages. Category data consists of a name, description and a representative image to show on the user screen.

Activity

An adventure activity available. Examples: snorkeling, fishing, bird watching, rafting, surfing. Activities are available in selected packages. Information stored for each activity include: name, description, rate, and a representative image to show to the user.

ActivityInPackage

This entity represents the many-to-many relationship between activity and package. It simply lists the activities in each package.

ActivityPurchaseOrder


Context Diagram

TODO: Add here a context diagram that graphically shows the scope of the part of the system represented by this view. A context diagram typically shows the part of the system as a single, distinguished box in the middle surrounded by other boxes that are the external entities. Lines show the relations between the part of the system and the external entities.


Variability Guide

N/A


Rationale

TODO: Describe here the rationale for any significant design decisions whose scope is limited to this view. Also describe any significant rejected alternatives. This section may also indicate assumptions, constraints, results of analysis and experiments, and architecturally significant requirements that affect the view.


Related Views

N/A

Personal tools
TOOLBOX
LANGUAGES