CONTACTS 

SUBJECTS
Directory for TEM Meetings Listed Under Other Files Switched from 60
SDS Direcotry for Other Files OF Incorrectly Used 60 Which is Reserve
Other Files OF Directory Incorrectly Used 60 Which is Reserved for Do
Directory for Other Files OF Incorrectly Used 60 Which is Reserved fo
SDS Directory for Other Files OF Incorrectly Used 60 Which is Reserve
Directory for Other Files OF Incorrectly Used 60 Which is Reserved fo

1108 -
1108 -    ..
1109 - Summary/Objective
1110 -
111001 - Follow up ref SDS 1 0000.
111002 -
111003 - The problem yesterday that required changes to SDS that maintain the
111004 - structure of entries in the Reference field, also showed that Gary
111005 - used directory 60 for Other Files.
111007 -  ..
111008 - Directory 60 is reserved for Documents Received in formal
111009 - correspondence to facilitate reports and other doc log ops, including
111010 - figuring out where to put a file when it is linked.
111012 -  ..
111013 - Since this is not obvious, Gary assigned the Powerpoint files for the
111014 - TEMs to directory 60, yet put them in Other files.  When he did a link
111015 - from another record they were put in DRP, rather than OF.  He manually
111016 - moved them and moved on.
111018 -  ..
111019 - Today, we discussed ideas for changing the location of these files
111020 - from OF to DRP.
111022 -  ..
111023 - Received ref DRT 1 0001 from Gary saying....
111024 -
111025 -    1.  I created a F:\03\00101\TM\03\04 directory and moved the TEM
111026 -        presentation files from the F:\03\00101\60\03\04 directory.
111027 -
111028 -        There were some DRx files there so I moved only the TEM
111029 -        records:
111030 -
111032 -         ..
111033 -        I edited the TEM SDS records to change the 60 to TM, and that
111034 -        fixed the problem, as well as conforming the record per your
111035 -        fix. ref DRT 1 847M
111036 -
111037 -
111038 -
111039 -
111040 -
1111 -

SUBJECTS
Requirements File to Explain SDS Functionality Start One File
File Accumulate Requirements to Explain SDS Functionality Start One F
SDS Design Takes Time Using SDS in Order to Understand Architecture
Requirements File to Explain SDS Functionality Start One File

280601 -         ..
280602 -        Requirements Define Record Types and Format Constraints
280603 -
280604 -    2.  The Save function is accumulating a series of fixes for getting
280605 -        the records to conform to required formats. ref DRT 1 2F8G  I
280606 -        think it would be a good idea to start a file that defines:
280607 -
280608 -           •  All of the SDS record types
280610 -               ..
280611 -           •  All format constraints and variations for each record
280612 -              type. ref DRT 1 CF8N
280614 -         ..
280615 -    3.  My objectives are:
280616 -
280617 -           •  continue documenting the functioning of SDS as a basis
280618 -              for current knowledge and fro creating a new version of
280619 -              SDS. ref DRT 1 OF9F
280620 -
280621 -           •  Continue looking at more robust structures to accomplish
280622 -              the necessary functions, ref DRT 1 ZF9L
280624 -               ..
280625 -           •  Force records to conform on save; build script to conform
280626 -              records in bulk as a "database repair" function.
280627 -              ref DRT 1 TF9O
280629 -         ..
280630 -    4.  I realize that all of this information is in the record, but I
280631 -        would like a reference to tie them all together. (Evolving
280632 -        documents actually *can* be useful!), ref DRT 1 2G4H
280634 -  ..
280635 - This is all good for go.  Aligns with objectives to get a system
280636 - requirements specification (SRS), based initially on broad objectives,
280637 - and then on experience using SDS.
280638 -
280639 -
280640 -
280641 -
280642 -
280643 -
280644 -
280645 -
280646 -
280647 -
2807 -