- - -
- TerraUser
CSE 476/486 Senior Design Website
-
-
- -
- - Schedule: Status | Reviews
-
Introduction

Team Info

Team Management

Sponsor Info

Project Overview

Solution/Plan

Schedule/Status

Documents

Links


Link to NAU.
Link to USGS.

The timeline is a significant process for a top-quality product to be created in a given time. Our timeline must follow the college capstone curriculum. An overall timeline for the project is shown in Table 10.3.

We will use Visio software to create Gantt charts to keep track of our tasks for this project. The chart will be updated weekly. Here are jpegs of the gantt charts for the project for Fall 2001 and Spring 2002.

Timeline

Objective

Document / presentation

1st week of November

Initial sponsor contact

Team forming stage

Team Inventory

Team Bylaws

Team Website

2nd week of November

Problem definitions / statements

 

Mid. November

Initial requirements/specification acquisition, requirements document

Requirement document

Introduction presentation

 

Project analysis

Feasibility study document

Risk assessment document

End of November

Draft proposal

 

Early December

Complete specification

Proposal document

Proposal presentation

During winter break

Learn and master technology that need on the project

N/A

Mid. January

Development detailed architecture

Functional Specification document

End of January

Functional Specification accepted by the sponsor

 

Feb., 2002

Implementation

 

March, 2002

Testing / Integration

Usability Document

April 26, 2002

Capstone Project Conference

As-built report / presentation

Table 10.3: Project Timelines

The first phase contains the team forming an initial sponsor contact. There the team members discussed their skills for the project. Team standards were discussed and documented. The first meeting with the sponsor was held to introduce the team members to the client and to discuss the project in more detail.

Requirements capture and documentation, feasibility study, risk analysis, and proposal documentation were in phase two. The project was analyzed from different angles to produce the best solutions. High-level software architecture has been created. Hardware/software setup is also an ongoing process in phase 2.

Over the winter break, the team members will learn the skills needed for the project before phase 3. Spring semester starts with phase 3, and the functional specification will be completed. After the functional specification is accepted by the client, detailed design and implementation take place. A detailed list of milestones for this phase is in Table 8.1 in the design page.

In phase 4, the product will be tested and integrated. The requirements and specification will be reviewed to examine if the product satisfies the clients’ needs. Usability will be also checked. As the last stage, the Capstone Project Conference will be held on April 26, 2002. An as-built report and presentation will be given.

We are confident that our timelines are sufficient for our project to develop a useful, high-quality product. We allowed time between the semesters to gain knowledge of technology that we will need on the project. Implementation should start as soon as the spring semester starts to allow enough time for testing and integration. Our timeline also follows the college capstone curriculum. The project will be completed for the Capstone Project Conference.

-
-