CSCI 6838 Capstone Projects
Guidelines For Project Web Page

by K. Yue, August 2001

I. General

Each technical team must maintain an active Web page for the capstone project. The URL of Web page should be:

http://dcm.uhcl.edu/cap<#semester_Year>gp<#n>

where <#n> is the team number. For example, the URL of team #3 of the Fall 2001 semester is:

http://dcm.uhcl.edu/capf01gp3

User accounts and passwords will be assigned in the first week of the semester. The project Website should be set up within the first two weeks of the semester.

Actively maintaining a project Website is beneficial:

• It facilitates communications and feedback between team members and the advisor.
• It provides a structural support for managing the project.
• It strongly benefits the writing of the final report and presentation.

The Web site should be professional. The team accounts will be kept as long as possible and can be used by the individual and UHCL beneficially:

• As showcases for external companies interested in sponsoring capstone projects.
• As examples for students taking capstone projects in the future.
• As links from individual resumes to showcase their projects.

The team must select a Webmaster to maintain the Web page. The Webmaster is also responsible to ensure that other team members are able to update the Web page actively.

II. Contents

All information about the project should be accessible through the Web page, if possible.

The following sections are the minimum requirements.

General Project Information

This section contains general information about the project:

• Project title.
• Project abstract.
• Customer/Mentor Information.
• Faculty advisor contact.
• Team member information: name, email, Web page, major, etc.
• Technologies used.

Deliverables

This section contains project deliverables and their descriptions:

• Design and Modeling document, including UML diagrams, relational schema, software model, etc.
• Source code: including a well described collection of source code of the project, coding standard guideline, etc.
• Project prototype documentation: startup, FAQ, tutorial, guideline, reference manual, etc.
• Presentations: power point files of all presentations.
• Reports: the final report, any technical reports, project weekly status reports and individual member progress reports.
• Logbooks: daily logbooks of team members.

Project Management

This section contains artifacts for managing the project.

• Roles and their responsibilities: for example, team leader, Webmaster, dba, etc.
• Role assignments.
• Tasks and their descriptions.
• Schedule and timeline: use a Gnatt chart (a table listing all tasks, task assignments and planned and actual start date, end date and duration.)
• Project weekly status reports (or links to them, if they are displayed under the deliverables section.)
• Meeting minutes: minutes of team and mentor meetings.
• Feedback from faculty advisers and customers.
• Configuration management, if applicable.
• Budgeting information, if needed.

Starting from Spring 2002, team member logbooks will become optional.

Resources

This section maintains resources beneficial to the projects. Each team member may come across useful resources, such as related articles, pages, examples, tutorials, how-to, etc. They are collected here in a structural way for sharing.

III. Layout

There are not too many specific requirements for page layout except that it must be consistent. Use CSS. Navigation should be simple and functional. Use left-side menu, if possible. HTML editors are ok.