Table of Contents:

1.0 Introduction

Moki Mac River Expeditions, a small family-owned company in Salt Lake City, inspired RivX. Moki Mac uses a system called Breeze to schedule their river expeditions. Breeze runs on their three Windows95 machines and uses an old Microsoft database called FoxPro. They would like to upgrade, but the company that developed Breeze has gone out of business. After discussing Moki Mac's situation with the team, we immediately saw a project possibility that could include development in several areas of interest: desktop application development, database design, and web application development. We also recognized that other companies like Moki Mac that schedule outdoor recreation tours and expeditions will need a replacement for Breeze. The proposed project is a system for scheduling outdoor recreational expeditions. This system will use some of the Breeze functionality as a starting point. The core system task is maintaining customer and scheduling information in a database. The system also provides functionality for billing invoices, printing out general business reports, tracking leads, and printing labels for mailings. We see great potential in exceeding the Breeze system's functionality by integrating scheduling with a web site as well as web based forms for customers to schedule expeditions. By adding a web application piece to the over all system, outdoor recreation companies have fewer barriers between them and their customers. Currently Moki Mac receives the largest number of inquiries and leads through their web site via email. Though Moki Mac provided the inspiration for this project, Professor Henderson will serve as the customer. Our project goal will be to provide a general solution not specific to any one recreational sport, type, or company.

back to table of contents

2.0 Historical Overview

2.1 User-interface prototyping and requirements gathering 

As we created and wrote a project plan and Software Design Specifiction, User-interface Prototyping and Requirements Gathering has been initiated.

2.2 Architectural design

Architectural design was created as we wrote Software Design Specification. Basic DB layout were discussed during this phase, and how we are going to implement those were also discussed. Also Server and Client API were discussed.

2.3 Quality assurance planning

2.4 General stage planning

2.5 Activities from detailed design through release

• Stage 1
  Basic DB layout has been established. Also each page were derived from generic template we created initially. Each page consider *.jsp, *_list.jsp, *_view.jsp, and *_proc.jsp. It includes requesting info from DB, inserting Data to DB, and updating DB info.
  
• Stage 2
  Added more feature to our existing product layout.
  Reservation Page: User can make a reservation within customers and party.
  Report Page: User can view and print various of reports that can be created using DB informations.
  Links: Links are added to Party and Scheduled Trip page where user can click customer name, trip name, or employee name to view more detail version of itself.
  Invoice Line Items: Our first step toward billing, the user can now create a library of line items to build invoices from.
  
• Stage 3
  More features were added.
  Added form validation to each page where user gets error message if form is invalid.
  New report can be viewd - Roster report
  Line items and Payment pages are added.
  Redesigned main page for more intuitive navigation.
  Modified Party and Reservation pages which are related to each other.
  Added more fields to Customer and link from Roster to show info.
  Order function to view table which will sort table by its field.
  Separated Pages with links on top of page to view table within some amount of info.

2.6 Final software release

back to table of contents

3.0 Project Data

Moki Mac is our executive sponsor. Even though they do not support any material physically, we gain information from their exisiting system and try to improve system.
Each member took a role in our project. Gib and John  took a role to create and layout DB tables on DB server. Shawn and Kyungseog took a role to create each pages that will be displayed on client application. We are trying to create user interface for more easier and intuitive usage. Gib and John also have a role to test each page and create them. Shawn and Kyungseog are also in charge of creating documents and to keep our website updated.

back to table of contents

4.0 Lesson Learned

4.1 Planning

We learned planning is one of most important fact in developing project. Since we are working whole semester without planning, we won't be able to meet our goal in time. Because we had specific timeline and deadline for our project we could finish each stage release in time.

4.2 Reqruiements

It is easy set too many requirements in the beginning that might not be finished at the end that it is hard to come up with requirements at the beginning. but as we had many requirements, we could be more ambitious and work hard to achieve those goals and requirements. And with requirements it is easy to separte stage releases and deadline for specific features.

4.3 Developement

As we started to developement, we learned that it is important to set up CVS which will project and easy to share resources as we worked apart from each other. And also establish good communication between members helps to improve developement situation. Once one of memeber finishes one part of project, then he should notify others that they don't work same area again.

4.4 Testing

Mostly we tested as we implemented our project by each individual. And testing is also one of important feature that we learned. Since our product is going to be used by real company, we have to make sure our project is free of bug. And as we implemented, we found several serious bugs that must be fixed.

Change Log