• For Windows Explorer: link or navigate to this URL, pull down the file menu and click "Login As...".  Enter the username and password and click "Login".
• Navigate to the appropriate folder.
• Use familiar "drag and drop" techniques to upload the file or document in question.  Make sure your file is named appropriately!

Linking to this site through mail messages or through an html link (as the one above) has been problematic.  DOS/command line ftp may have to be used.

• Start | Run...
• Enter ftp in the text input area and click "OK"
• Type: open edtool.coe.ttu.edu
• The username is cs2365
• The password has been given to you in class.
• Change to our project directory--type cd readftp
• If and only if submitting zip files, type binary
• Else type put <path to local file>\file_name.extension <remote file destination>\file_name.extension
• Make sure your file is named appropriately!
• Repeat until all desired files are uploaded
• Type bye to logoff and exit

• Use an ftp procedure given above
• Submit into the appropriate folder beneath readftp
• Put pictures and separate document files in separate directory.

• There is a folder called "weekly_reviews" under our ftp directory.  All the different teams (requirements, design and programming) have subfolders for their members' weekly reviews.  The team leaders and managers have their own folders, named according to the person's first name and last name.
• All of the folders mentioned have a "posted_archive" folder at the lowest level in the directory tree.  Do not post documents of any kind to this folder!  It helps the configuration manager keep track of what has been moved to the web server and linked and what has not.

• Use the folder called "change_request" under our ftp directory.
• Append a version number in the following fashion (considering a weekly review as an example):

• Original document (version 1, submitted, according to above instructions, somewhere within the "weekly_reviews" folder): 2365DoeJohnWR_MMDDYYYY.html
• New document (version 2, submitted into the "change_request" folder): 2365DoeJohnWR_MMDDYYYY.v2.html

• After submitting the updated document into the change request folder, send an email to the configuration manager (jpharis@ttu.edu) and report the need for a document update.

• Pay special attention to the nature of the problem so you can accurately describe it.
• Let the configuration manager know about the problem, via email (jpharis@ttu.edu).  Feel free to carbon copy the software manager or Dr. Mengel, if necessary.
• But most importantly, don't email your documents to the configuration manager without approval.  There's already a huge volume of email flowing, that is relatively hard to keep track of, even with filters, folders and rules.

• Main project directory, holds all subdirectories and top level "current" files

• index.html
• HistoricalArchives.html
• WeeklyReviewPage.html
• outline.js
• The Configuration Management Plan
• The Short Term Plan
• The Long Term Plan

• Most of the ftp directories contain a "posted_archives" sub-directory for backup use.  Don't post here!

• Subdirectories:

• adam_thomas
• bj_barton
• design_team
• fall2002_archive
• jason_pharis
• jeremy_stanley
• matt_mason
• programming_team
• requirements_team
• robin_d'souza
• SQA_team
• trainer_team
• vu_le