Getting started :

DISK$GSC2:[CASB.CMTOOLS.DOC]SOFTWARE_GUIDE_JULY96.TXT

This is a fairly large document that describes the [casb] software tree; software guidelines; and build and delivery guidelines. It is slightly out of date, but it's the best we have at the moment.

DISK$GSC2:[CASB.CMTOOLS.DOC]DIDFILE.CONVENTIONS

Describes the rules for applications which use the DID file. All plate processing pipeline tasks must use the DID file.

DISK$GSC2:[CASB.CMTOOLS.DOC]DEVELOPMENT_ACTIVITIES.TXT

A list of the development, test, and delivery stages which we've developed. Not every application will go through every one of these stages, and not every item will occur in the order given, but this is a useful planning reference for software projects.

Development tools:

@disk$gsc2:[casb]internal_users.com

You must execute this com file before beginning to work. It defines the necessary logicals for the environment you're in. It takes one of five parameters: DEV, TEST, BASE, QUICK, or OPS

@disk$gsc2:[casb.cmtools]apptree.com

Creates a standard directory tree structure in the [casb.develop.apps] area. Use this to begin working on a new application.

Development documents:

DISK$GSC2:[CASB.CMTOOLS.DOC]HEADER.FOR, HEADER.COM, HEADER.IDL

This is a template for the standard software header which all new CASB software must use. It's set up so that you can fill in the blanks. The idea is that printing out the standard header for a module would produce all the documentation that a person would need in order to use the module, eg, calling sequence, data types, etc.

DISK$GSC2:[CASB.CMTOOLS.DOC]MOVE_TO_TEST_CHECKLIST.TXT

Under CASB software rules, pretty much "anything goes" in develop, but things need to be cleaned up before they are migrated to TEST and subsequently BASE. Additionally, there are procedures which it is the developer's responsibility to follow, to facilitate the testing and development. These items are also included on the checklist.

DISK$GSC2:[CASB.CMTOOLS.DOC]DOC_TEMPLATE.HTML

This is a template for the standard HTML software for CASB software. It is set up so that you can fill in the blanks. Please doublecheck the "availability" section, and be sure to put your name and email address in the contact section.

DISK$GSC2:[CASB.CMTOOLS]LIBLIST.DAT

This is the hierarchy of common libraries in the CASB tree. They are described in more detail in the software guide, but this is a quick reference list. The order in which they are listed is important. You can and should omit libraries you do not use from this list, but those which are used, must be listed in this order.

Migrating existing software into CASB tree

DISK$GSC2:[CASB.CMTOOLS.DOC]CONVERSION_CHECKLIST.TXT

If you are migrating existing software into the [casb] environment, this checklist walks you through the procedures to follow.

DISK$GSC2:[CASB.CMTOOLS]FIX_INCLUDE_STATEMENTS.COM

This is a moderately well tested tool to operate on .C and .FOR files looking for include statements with paths, and replacing them by include statements without paths. It produces a file called paths.dat containing all the paths. It does not purge or delete any files.

Test and delivery documents:

DISK$GSC2:[CASB.CMTOOLS.WORK]DELIVERERS_GUIDE.TXT

Describes the role of the software deliverer.

DISK$GSC2:[CASB.CMTOOLS.WORK]DELIVERY_CHECKLIST.TXT

A checklist which is used to facilitate the delivery process. (Needs updating) All developers are strongly encouraged to read this as well, since it contains the standards that the software must conform to.

Vicki Laidler ---- laidler@stsci.edu