Methodology
Well, great then. The next task then would be for Urwumpe to tell me the basics of using the SVN. I've read how one can reference several separate .tex files then have them combined into one PDF when it is created, which is I think what Urwumpe was talking about.
Long term, I think the docs should be broken in to sections like:
STS:
basicly used to go over anything that can't be directly referenced from the SCOM like keystrokes (if there are any), dialog boxes, ect. (Otherwise we simply point the user to the nessesary SCOM section.
Ground OPS:
With the pads nearly finnished and with the potental for stacking operations, this section/doc would be used for things from Wheels Stop to the Terminal Countdown (whatever is actualy simulated in this area). For now it would mainly be how to control things like the crawler, MLP, OWP, RSS, ect.
Terminal Countdown:
a section/doc that describes what needs to be done to complete the countdown (say T-1 day to T-0 including RSLS abort and scubs) once (if ever) implimented (at the very least, it can be a small section the describes the current, mostly auto, countdown)
Mission specific Documentation:
This is were it can get tricky. For historical missions (even "simple" ones like STS-1, 2, and 3) how much material do we include in the base install? Do we include mission specific checklists (are these created "in house" or are they NASA copies)? Do we include mission timelines and Flight Plans or do we just tell the user the Launch date and the Landing date and let them figure the rest out on their own? Also this section may include explanation of items included in the Mission File for the specific mission. EXAMPLE, the Doc for STS-1 would give an overview of what one would find in the mission file for STS-1. (The Documentation of the MISSION FILES themselves would be covered in its own section).
Scenario Files, Mission Files, and Payload Handeling:
This section would be used by people who want to create there own missions or to developers looking to create or adapt payloads to be used with SSU. It can range from simply describing and documenting all the required perameters that need to be present as well as describing all available entries.
External Programs Doc:
Urwumpe has mentioned that there may be small external programs that are used with SSU (his example was a program that creates mass memory tape images). Any of these would either be together in a grouped Doc or in seprate docs for each.
Now, don't think I've gone off the deep end.
For the short term (ie before the next public release) I'm thinking of continuing with the setup we already have. One manual that contains the descriptions and some checklists.
The first goal is to update the current manual with all the stuff that has been added (or not even covered) since the v1.25 doc. Once I get cought up, maintaining the manual and spliting it into the aformentioned sections will be much easier.
What do ya'll think? questions...? comments...?