Top Level Module Uses View

Primary Presentation

Visio file

Element Catalog

Consumer Website

The web-based user interface of the Adventure Builder is implemented in this module. The user interface lets the user browse the catalog of travel packages, place a new purchase order, and track the status of existing orders. This module creates the purchase orders based on user input and passes them to OpcApp for processing. It uses an implementation of the Model View Controller pattern called the Web Application Framework (waf). The model is implemented using Entity beans, the controller is implemented using servlets, and the view is a collection of JSPs and static HTML pages. Part of the client-facing code is implemented using the GWT framework.

A module decomposition refined view and a module uses refined view of OpcApp are available.

utils

This module contains utilities used by the Adventure Builder system.

dao

This module contains Data Access Object (DAO) utilities, such as a DAO factory. It does not contain the actual DAO classes that access the database--these classes are inside the ConsumerWebsite module.

logger

This module contains tracing and debugging utilities. The original name was tracer.

servicelocator

This module is an implementation of the ServiceLocator design pattern.

gwt

Google Web Toolkit (gwt) is an open source framework for development of rich internet applications based on Ajax.

waf

Waf stands for Web Application Framework. It is a Model View Controller framework similar to Struts. It allows you to specify in configuration files the web screens and action that are associated to user clicks on specific elements of the screen. The configuration file has the mapping of screens and actions to Java classes. The framework provides the engine to display the proper screens and invoke the proper actions.

Bank credit card service

This module represents an external service provided by a partner bank to validate credit card transactions.

Airline booking service

This module represents an external service provided by an airline partner company to book air travel.

Lodging booking service

This module represents an external service provided by a lodging partner company to book hotel rooms.

Activity booking service

This module represents an external service provided by an activity supplier company to book different activities.

Context Diagram

N/A

Variability Guide

See OPC Module Uses View - Variability Guide.
See Top Level SOA View - Variability Guide.
See Consumer Website Multi-tier View - Variability Guide.

Rationale

GWT

The GWT framework was chosen for the following reasons:

• It is open source, which allows us to go under the hood and fix things when needed.
• It provides a rich development environment with powerful trace/debug, IDE integration and build management.
• It integrates well with any other frontend technologies since it does not use proprietary standards.
• It offers powerful widget construction features.
• There are several extension libraries of widget components available.
• Code is written in Java (and translated to JavaScript during build), which is an OO language that is familiar to the majority of the team.
• Code is compiled into Javascript, which is available on a very high percentage of browsers.
• It has a reasonably large support community and is backed by a major player in the industry (Google).

The table below shows the comparative analysis of GWT and competing technologies based on the specific needs of our project.

*All performance tests were executed on the same hardware: Pentium M 1.7GHz, 2GB RAM, Win XP Pro SP2

Related Views

• Refinement of OpcApp showing decomposition: OPC Module Decomposition View
• Refinement of OpcApp showing use dependencies: OPC Module Uses View