Configuration Management Plan

E-COACH

Clint Miller, Fall 2001


Special Instructions

Procedure Name Steps
FTP procedures (via Windows Explorer) The ftp server can be reached through this URL: ftp://edwork.cs.ttu.edu.  The username is cs2365 and the password is SoftWeb1492  
  • 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.

FTP procedures (via DOS/command line) Go to:
  • Start | Run...
  • Enter ftp in the text input area and click "OK"
  • Type: open edwork.cs.ttu.edu
  • The username is cs2365
  • The password is SoftWeb1492
  • 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
To submit documents such as requirements, design, software, team requests, etc..
  • Use an ftp procedure given above
  • Submit into the appropriate folder beneath readftp
Weekly Review submission
  • 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, if necessary).
  • 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.  It also serves a purpose in my backup plan.
To submit a modified version of a document
  • 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): CS2365DoeJohnWR_MMDDYYYY.html
  • New document (version 2, submitted into the "change_request" folder): CS2365DoeJohnWR_MMDDYYYY.html.v2
  • After submitting the updated document into the change request folder, send an email to the configuration manager (john.c.miller@ttu.edu) and report the need for a document update.
When problems occur...
  • 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 (john.c.miller@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.

Version Control

Artifacts will be made available through the Historical Archives page.  When archived, they will be given an appropriate extension, such as .A1, .A2, etc...


Directory/File Organization

Directory Description
/projects/read
  • Main project directory, holds all subdirectories and top level files
  • index.html
  • HistoricalArchives.html
  • ReviewReportsPage.html
  • WeeklyReviewPage.html
  • The Configuration Management Plan
  • The Short Term Plan
  • The Long Term Plan
/projects/read/weekly_reviews Contains weekly reviews in subdirectories according to week
/projects/read/weekly_reviews/WR_MMDDYYYY Contains sub directories for all the weekly reviews, according to team role.
/projects/read/requirements Contains the requirements documents
/projects/read/requirements/archives Contains the requirements documents archives
/projects/read/design Contains the design documents
/projects/read/design/archives Contains the design documents archives
/projects/read/software Contains the software manual and other documents
/projects/read/software/archives Contains the software manual and other documents archives
/projects/read/team_requests Contains completed team requests
/projects/read/team_requests/archives Contains completed team requests archives
/projects/read/submit (/readftp) Root ftp directory, don't deposit files here!
  • Most of the ftp directories contain a "posted_archives" sub-directory for backup use.  Don't post here!
/projects/read/submit/weekly_reviews (/readftp/weekly_reviews) Contains team weekly reviews, submit as instructed.
  • Subdirectories:
  • brent
  • brian_crowell
  • clint
  • design_team
  • lindsey
  • programming_team
  • requirements_team
  • ryan
/projects/read/submit/requirements (/readftp/requirements) Submission directory for the requirements documents
/projects/read/submit/design (/readftp/design) Submission directory for the design documents
/projects/read/submit/design (/readftp/software) Submission directory for the software documents
/projects/read/submit/team_requests (/readftp/team_requests) Submission directory for completed Team Request forms
/projects/read/submit/change_requests (/readftp/change_requests) Submission directory for additional versions of files submitted previously that the configuration manager should update.  Follow instructions...

Backup Log

Document/Artifact Media Location Date
       
       
       

Change Control Log

Not applicable since this is the first team working on the E-Coach project; drastic client requested changes to the project requirements are unlikely.


Team Request Forms


Revision History

Date Name Revision
11/07/2001 Clint original document creation