Software Manual

The Burn Project

by Kyle Gossman


Table of Contents


Documentation, Standards and Conventions

Internal Documentation

Each file has a comment with the filename, author name, creation date, and a short description of the file at the top.  For example, the comment for the file add_course.php would look like this:

/*
** add_course.php
** by Andy Cooper
**
** Created: May 05, 2003
**
** This script displays the form to add a course
** to a student plan.
*/

Each function also has a comment with the function name and a description of the function, for example:

 /*
** get_student_plan
**
** Returns the student plan given a username.
*/
 

Coding Standards

The coding standards followed included having opening semicolons on the same line as a function header or control statement.

function get_student_plan() {

/* .... */

}

Variable names were to be clear and indicate what they were used for.  They should be longer than 2 characters, with the exception of counter variables, which were usually named $i and $j.  In general we would put the <? and ?>s that signified blocks of php code instead of html on their own lines to clearly separate the two.  The only exception is when this new line caused an error in the software.  For example, if we had an html tag like the following:

<option name="

<?

    /* ... */

?>

">

The new lines would be included in the name parameter.

File Naming Conventions

All files have either the extension php or txt depending on whether they are web content or data files.  Each file is named clearly and suggests what its function is, and files are placed in directories based on what module they belong in as described in the design document.


Source Code Files

1.1 authentication_utils.php

1.2 index.php

1.3 admin/add_course.php

1.4 admin/admin_main.php

1.5 admin/catalog.php

1.6 admin/change_course.php

1.7 admin/change_course2.php

1.8 admin/remove_course.php

1.9 admin/statistics.php

1.10 admin/view_catalog.php

1.11 datamod/admin_config.php

1.12 datamod/advisee_list.php

1.13 datamod/course_cat.php

1.14 datamod/data_module.php

1.15 datamod/skeleton.php

1.16 datamod/stud_sched.php

1.17 faculty/faculty_main.php

1.18 student/add_course.php

1.19 student/confirm_delete.php

1.20 student/move_course.php

1.21 student/show_plan.php

1.22 student/student_main.php

 


Software Installation

2.1 Development Platform

2.2 Client Delivery Platform


Design Issues List

Items
 


Cross-Reference Table
 

Table Key:

RE – Requirements Document, Requirements section.
UI – Design Document, User Interface section.
IP – Design Document, Implementation Platform section.
DD – Design Document, Detailed Design section.
DS – Design Document, Data Storage section.

Design ID and Heading Name Software ID and Heading Name
UI / 2.1 1.1
UI / 2.2 1.22
UI / 2.2.3 1.18
UI / 2.3 1.17
DS / 1.1 1.13
DS / 1.2 1.16
DS / 2.1 1.11
DS / 2.2 1.12
DS / 2.3 1.13
DS / 2.4 1.16
DS / 2.5 1.15
IP / 1 2.1
IP / 2 2.2


To Do List
 

Items
 
 
 


Revision History

Date Name Revision
05/08/2003 Kyle Gossman Created Software Manual
05/09/2003 Kyle Gossman Finished Source Code Files documentation