CONTACTS 

SUBJECTS
Doc Log Fields Create for Linking Called, 04408 by 01211
Doc Log Primary Format, F1 F5, 04408
Other Files Doc Log System F1 F5 Receiving Documents into SDS
Other Files Format Fails to Support Using F5 for Posting Document Dir
F5 Fails Post Document Directory Structure from Control Field to Othe
F5 Doc Log Subjects, Directory Path, Descriptions, 04101

0908 -
0908 -    ..
0909 - Summary/Objective
0910 -
091001 - Follow up ref SDS 6 0000, ref SDS 2 0000.
091002 -
091003 - Encountered problem with doc log fields for Other Files when a record
091004 - has no existing Other Fields format, nor other SDS and Doc Log
091005 - content.  This turned out to be an SDS problem that is corrected
091006 - today. ref SDS 0 FQ4K  Gary later reported another problem that turned
091007 - out to be caused by lack of uniform alignment of outline structure.
091008 - The correction was to shift a few lines one column to the left to
091009 - create a uniform right margin. ref SDS 0 5Z3O   Provided ideas for
091010 - constructing effective Knowledge Space by assignment directory and
091011 - filenames based on subjects of Other Files. ref SDS 0 5D6L  Created a
091012 - format for the document Gary submitted, which may illustrate how to
091013 - create an effective format rather than perfectly match the original
091014 - source. ref SDS 0 F34H  The substance of the file Gary submitted
091015 - provides a good criteria for setting up subjects on the Aerospace company
091016 - project. ref SDS 0 WE7N  Sent updated SDS code with corrections,
091017 - ref SDS 0 NE6M, and updated SDS records that include this record with
091018 - the sample file that may provide a template to guide future work.
091019 -
091020 -
091021 -
091022 -
091024 -  ..
0911 -
0912 -
0913 - Problem
0914 -
091401 - Other Files Format and Operation Problems Posting Subjects with F5
091402 -
091403 - Follow up ref SDS 11 7J7I.
091404 -
091405 - Gary called and explained a new problem that occurs when creating an
091406 - "Other File" format to receive a document into an SDS record, per
091407 - discussion yesterday on building comprehensive Knowledge Space.
091408 - ref SDS 13 R383
091410 -  ..
091411 - For some reason, the command sequence using F1 F5 F6 and then using F5
091412 - to assign the first part of the address from the subject code in the
091413 - control field is not working properly.
091415 -  ..
091416 - I was able to replicate the problem following along with Gary on the
091417 - phone doing the same steps in a new record, so will investigate to fix
091418 - it.  Subsequently, a correction to SDS was accomplished. ref SDS 0
091419 - FQ4K
091421 -  ..
091422 - After our call, received ref DRT 1 0001 from Gary explaining a second
091423 - problem
091424 -
091425 -        When I import it with 'g x.txt' it looks fin. Using F2 to save
091426 -        it kills SDS reliably. ref DRT 1 SU5N
091428 -  ..
091429 - Actually, the bigger problem is Gary's explanation that...
091430 -
091431 -        Still fighting the OF problem.
091433 -         ..
091434 -        I have a file that I have been trying to get referenced all
091435 -        morning.
091437 -  ..
091438 - Why is the problem persisting.  Sending and receiving documents takes
091439 - only seconds for email, as I have just done with Gary's letter today,
091440 - and with his letters yesterday. ref SDS 13 TN9J and ref SDS 13 L36J
091442 -  ..
091443 - This seems to be coming down to a situation where understanding the
091444 - underlying processes and objectives from having created the system
091445 - imparts ways and means to work around problems that makes them
091446 - invisible, and so they are never fixed.  But, for people who lack that
091447 - background, they are problems that paralyze productivity.  We cannot
091448 - sustain this condition.  Even apart from lost time, it is emotionally
091449 - debilitating.
091451 -  ..
091452 - What seems curious is that Gary and I had similar problems using
091453 - Microsoft stuff this morning.  Took an hour or so to figure out how to
091454 - transmit attached files.  So SDS is not alone in having problems, but
091455 - it lacks the weight of cultural acceptance that encourages people to
091456 - invest any amount of time to solve the latter, but with SDS people are
091457 - more inclined to give up because it is possible to get by without
091458 - improving.
091460 -  ..
091461 - Only solution is to keep finding the problems and improving SDS to
091462 - avoid them in the future.
091464 -  ..
091465 - After getting Gary's letter I called and asked him to send the SDS
091466 - record and the file he is capturing as an Other File that is causing
091467 - the SDS "save" function to crash, so I can replicate the problem.
091468 -
091469 -
091470 -
091471 -
091473 -  ..
0915 -
0916 -
0917 - Background
0918 -
091801 - On 010311 major improvement were made in Doc Log system. ref SDS 2
091802 - TO65
091803 -
091804 -
091805 -
091807 -  ..
0919 -
0920 -
0921 - Progress
0922 -
092201 - 04408  Doc Log Other Files Format
092202 -
092203 - Line 230, ref OF 1 WG5N, -label m113 in 04408
092204 -
092205 -    Debug tried here to investigate problem.  This is where the code
092206 -    starts in normal mode.
092207 -
092208 -
092210 -  ..
092211 - Line 810, ref OF 1 KQ5O, -label exit1 in 04408 about 40 lines below
092212 -
092213 -    The code is not executing properly at this location.  It should
092214 -    pass control to -label over, but this is failing, possibly because
092215 -    the conditional string is too long.  When a conditional that
092216 -    branches gets close to column 80, this presents problems for the
092217 -    design of the macro compression op in macro file 011.
092219 -     ..
092220 -    Just trying to split up the conditional into two strings.
092222 -     ..
092223 -    This solved the problem.
092225 -     ..
092226 -    What was occurring, is that the code branched to the wrong
092227 -    location, which was sufficient to end the routine, rather than get
092228 -    stuck in a loop, but it did not assign the flag that identified the
092229 -    condition as pending assignment of a directory string and subject.
092230 -    I have not noticed this previously, because I never use this
092231 -    feature in my own work.  I just key in the directory string for
092232 -    Other Files.  But in Gary's case, he expects this work the same as
092233 -    for issued and received formal correspondence, and in fact the code
092234 -    was intended to do this, I just never used it, so the error in the
092235 -    code never materialized.
092237 -     ..
092238 -    How many more problems of this type are out there????
092239 -
092241 -  ..
092242 - The second problem Gary reports occurs in his record for today, and
092243 - per his letter today, per above, ref SDS 0 F44G, which says...
092244 -
092245 -        When I import it with 'g x.txt' it looks fin. Using F2 to save
092246 -        it kills SDS reliably. ref DRT 1 SU5N
092248 -  ..
092249 - Not clear if save is called in the file or in SDS?
092251 -  ..
092252 - One issue that is immediately suspicious is that there is not a blank
092253 - line below the OF entry in Gary's record.  I thought this was
092254 - addressed previously, so it does not matter, but that stands our as a
092255 - candidate for a format "problem."
092256 -
092257 -
092258 -
092259 -
0923 -

SUBJECTS
Flexible Structure Harder to Learn Easier to Make Mistakes than Tradi
Multiple Views KM Dilemma Frustrating Difficult to Learn Organic Stru
Define Subject Multiple Ways Multiple Views Empower People to Find Im
Categories Subject Index Assignments Reflect Organic Structure of Wor
Multiple Views Context Subjects Organization Management Pandora's Box
Knowledge Space Filename Directory Assignments Based on Subject Index

1508 -
150901 -  ..
150902 - Directory Structures for External Other Files
150903 -
150904 - Another issue that does not affect this problem in the least, but is
150905 - worth noting.   The directory structure Gary developed needs further
150906 - work as follows...
150907 -
150908 -    1.  The directory in Gary's SDS record shows....
150909 -
150910 -            F: 04 00001 03 04 0801            CMM for Standards
150912 -         ..
150913 -        The intent appears to be to construct a directory using the
150914 -        date, which is the format that is created automatically for DIT
150915 -        and DRT, and is, also, used for formal publications.
150916 -
150918 -         ..
150919 -    2.  Received directory "60" is needed as follows....
150920 -
150921 -            F: 04 00001 60 03 04 0801            CMM for Standards
150923 -         ..
150924 -        This revised format shows that typically, where a date
150925 -        structure is used, there should be "received" directory added
150926 -        for "60" between the primary structure and the date component,
150927 -        at least that is the format for formal correspondence issued
150928 -        and received.
150930 -         ..
150931 -        Alternatively, if Gary wants to make this a formal publication,
150932 -        say for example this is a military manual or something similar
150933 -        that has been published, then the following would work...
150934 -
150935 -            F: 02 14 01 60 03 04 0801            CMM for Standards
150937 -         ..
150938 -        Actually, I am thinking of eliminating the 02 account because
150939 -        it was originally developed to reflect the idea of one's own
150940 -        organization.  In Gary's case it would be the Aerospace company company
150941 -        accounts.  Further work developing the 05 account for contacts
150942 -        seems to indicate that 02 does not hold up over the long run.
150943 -        One's own organization changes over time.  The 05 account
150944 -        enables applying a stable structure for any organization, and
150945 -        so they can all be treated the same.  This makes training and
150946 -        learning easier by using a uniform procedure for all
150947 -        organizations.
150949 -         ..
150950 -        Making this change merely requires changing the Doc Log report
150951 -        code to process 05 and 02 to continue handling legacy files
150952 -        that I have.
150953 -
150954 -            This is an action item for changing SDS and not for Gary on
150955 -            issues today.
150956 -
150957 -
150959 -         ..
150960 -        How to organize files that are not formal correspondence?
150961 -
150962 -        Gary might note the procedure I used to figure out a directory
150963 -        and filename for the file he submitted today.
150965 -         ..
150966 -        In this case, I am using the file as a training example for
150967 -        using SDS.  This sets the beginning level as a project and
150968 -        SDS, so that means....
150969 -
150970 -                  03 00050
150972 -         ..
150973 -        Next, look at assigned subjects.
150974 -
150975 -           03 00050 01 10 03 14
150976 -
150977 -                 Marketing Training Procedures
150978 -
150979 -           03 00050 01 10 CK 021109a 030408aa
150980 -
150981 -                 Marketing Training Learning Flexible Structure
150983 -            ..
150984 -           03 00050 01 10 CK 021109a 030408ab
150985 -
150986 -                 Marketing Training Learning Format Outline
150988 -         ..
150989 -        Decided to create a directory at the following level...
150990 -
150991 -           03 00050 01 10........... SDS, Marketing, Training/Learning
150993 -         ..
150994 -        The filename needs to be flexible to enable adding more files
150995 -        later that may have some order.
150996 -
150997 -           One of the default methods is to start with the filename...
150998 -
150999 -                       00101
151001 -            ..
151002 -           We can have 100 files ahead of this, and a lot of below it.
151004 -            ..
151005 -           In Gary's case for the project at Aerospace company, recommend setting
151006 -           up the standard organization accounts shown in the template
151007 -           for Contacts.  This has two good candidates....
151008 -
151009 -                 FI.......... Procedures
151010 -
151011 -                     The substance of the file is software development
151012 -                     procedures. (see discussion below. ref SDS 0 WE7N
151014 -                  ..
151015 -                 JF.......... Projects
151016 -
151017 -                     The substance of the file concerns procedures that
151018 -                     govern a particular project, and that project in
151019 -                     turn will have elements that include procedures,
151020 -                     and/or software development, and that subject can
151021 -                     have a procedures element.  This means a wide
151022 -                     range of possible subjects exist.  They can all be
151023 -                     assigned in SDS, so it does not make a lot of
151024 -                     difference which is used to create the actual
151025 -                     file, because it can always be located through the
151026 -                     SI using record segments.
151027 -
151028 -
151029 -
151030 -
151031 -
151032 -
1511 -

SUBJECTS
F2 Save Fails When File Outline Format Does Not Conform to SDS Requir
Outline Format Does Not Conform to SDS Requirements Causes F2 Save to
Outline Nums and Letters Update Macro 207 Part of F2 Save Function
F02 Save Macro 207 Update Outline Structures and Lists
207 Macro Outline Numbers Letters for Lists Called by Macro 1421 Unde
Filename Directory Structure F5 Fails to Post from Control Field to D
Other Files Save F2 Fails When File Outline Format Does Not Conform t
Save F2 Fails When File Outline Format Does Not Conform to SDS Requir
People Good Way to Start Assigning Subjects to Avoid Frustrating Diff
Save F2 Fails When File Outline Format Does Not Conform to SDS Requir
Flexible Structure Learn New Way Working Difficult Augment Intelligne
Johnson, Gary F2 Save Fails When File Outline Format Does Not Conform

3014 -
3015 - 2019
301601 -  ..
301602 - CMM KPAs and Activities Outline Alignment Problem Causes Save to Fail
301603 - F2 Save Fails External Files When Right Margin Outlining Not Uniform
301604 - Outline Problem Requires Uniform Right Margin, Not Uniform Left Margin
301605 -
301606 - Replicated the problem that Gary reports. ref SDS 0 0P50  It occurs by
301607 - pressing F2 in the file, ref OF 2 0001, rather than in SDS.  I don't
301608 - think the lack of a blank line below the entry in the SDS record is
301609 - the problem.
301610 -
301611 -     It is good practice to leave a blank line below every list of
301612 -     entries in the Reference field, even though this does not cause a
301613 -     problem in this case.
301614 -
301615 -         [On 030505 difficulty reported maintaining consistent format
301616 -         in flexible structure of SDS. ref SDS 18 T85N
301618 -          ..
301619 -         [On 030505 improved SDS to verify and correct the format to
301620 -         put a blank line at the end of each Reference field.
301621 -         ref SDS 18 6U9S
301623 -  ..
301624 - Since I have never encountered this problem it will be interesting to
301625 - see what is occurring.
301627 -  ..
301628 - I am now guessing the problem is with the outline code, because that
301629 - is the only thing that F2 does in an external file, other than write
301630 - the file to the disk.
301632 -  ..
301633 - Work arounds to "save" a file....
301634 -
301635 -    Gary needs to be aware that when something like this occurs, there
301636 -    are other ways to write the file to disk other than by using F2
301637 -    which is causing a crash.  Since we process outline code, this has
301638 -    potential for problems, because of variability in the way folks
301639 -    might designate an outline structure, and some of it might cause
301640 -    SDS to choke.  So, one of the things we want to be able to do is
301641 -    at least to save the file, so we don't have to do this over and
301642 -    over again.
301643 -
301644 -          "save"
301645 -
301646 -    ...can be accomplished with F2, which processes outlining, as
301647 -    related in the record on 021107. ref SDS 7 AG5S  Other ways to
301648 -    save the file are to....
301649 -
301650 -           a.  Press Home to put the cursor on the Command Line.
301652 -                ..
301653 -           b.  Enter "save" and press Home
301655 -                ..
301656 -           c.  Enter "file" and press Home
301657 -
301658 -               This has the effect of closing the file after writing
301659 -               it to the disk.
301661 -     ..
301662 -    These work arounds, let you save a lot of work so it does not have
301663 -    to be done again to test out the F2 op.
301665 -     ..
301666 -    Now that we are in the hunt, a couple of candidates for problems
301667 -    are...
301668 -
301669 -        1.  At about line 64 there is the following....
301670 -
301671 -            Activities:
301672 -               1) The software engineering group reviews the allocated
301673 -                  requirements before they are incorporated into the
301674 -                  software project. ref OF 2 1D8K
301676 -                   ..
301677 -                  [Note - the reference used here is to corrected
301678 -                  alignment, so the actual problem is not shown at this
301679 -                  link.]
301681 -             ..
301682 -            It might be that not having a blank line between
301683 -            "Activities" and the next line beginning with 1), creates a
301684 -            fly in the ointment.
301685 -
301687 -             ..
301688 -        2.  Outline format right margin uneven cause of problem.
301689 -
301690 -            This seems more likely to be the problem, although both may
301691 -            be problems, i.e., we have a compound problem.  Subsequent
301692 -            analysis and testing showed that only the uneven right
301693 -            margin of the outline structure is the problem.
301695 -             ..
301696 -            Line 112 shows.....
301697 -
301698 -               9) Estimates for the size of the software work products
301699 -                  (or changes to the size of software work products)
301700 -                  are derived according to a documented procedure.
301701 -                  ref OF 2 4Y4U
301703 -                ..
301704 -               10) Estimates for the software project's effort and costs are derived
301705 -                  according to a documented procedure.
301707 -                ..
301708 -               11) Estimates for the project's critical computer resources are derived
301709 -                  according to a documented procedure.
301711 -             ..
301712 -            The file received from Gary shows an outline structure
301713 -            aligned with a uniform left margin, but should be aligned
301714 -            with a uniform right margin, and the line below the first
301715 -            line is offset from the line above.  These are minor
301716 -            misalignments, but are likely the cause of the problem.
301718 -             ..
301719 -            Without using debug to investigate further, will try to
301720 -            clear the problem by moving the lines to look like the
301721 -            following....
301722 -
301723 -               9) Estimates for the size of the software work products
301724 -                  (or changes to the size of software work products)
301725 -                  are derived according to a documented procedure.
301727 -                   ..
301728 -              10) Estimates for the software project's effort and costs
301729 -                  are derived according to a documented procedure.
301731 -                   ..
301732 -              11) Estimates for the project's critical computer
301733 -                  resources are derived according to a documented
301734 -                  procedure.
301736 -             ..
301737 -            Correction requires shifting all lines for every outline
301738 -            structure that exceeds 9), so in the above case lines 10)
301739 -            and 11), and then doing the same to other instances where
301740 -            the right margin of the outline structure is not aligned on
301741 -            the same column.
301743 -             ..
301744 -            Curiously, when F2 is used in SDS, the same outline
301745 -            structure does not cause a problem, so why does it crash
301746 -            in external files?
301748 -             ..
301749 -            In any case, after making these changes in the file Gary
301750 -            submitted for "CMM KPAs and Activities," F2 functioned
301751 -            normally.  Since I did not change the line spacing noted
301752 -            under issue 1, per above, ref SDS 0 NR6L, this indicates
301753 -            that the only problem is lack of a uniform right margin for
301754 -            outline structures, per above. ref SDS 0 2L5N
301755 -
301756 -
301757 -
301758 -
301759 -
301760 -
3018 -

SUBJECTS
CMM KPAs Aerospace company HTML Example Format Template Publish Other F  es to I
Procedures HTML Format Other Files
Examples Format Guidelines Use Cases Samples HTML Other Files
Demand for SDS Records Working Intelligently Based on Stuart Harrow's

4106 -
410701 -  ..
410702 - CMM KPAs and Activities Example Format HTML Other Files
410703 - Format Suggestions to Expedite Constructing Knowledge Space
410704 -
410705 - While thinking about formatting "received" and "Other File" documents
410706 - and since this is a big headache that takes a lot of time per telecon
410707 - with Gary yesterday, ref SDS 13 NF7H, a few suggestions are offered
410708 - here on using the sample file received from Gary. ref OF 2 0001
410709 -
410710 -      Cite this analysis in the letter to Gary. ref DIT 1 118I
410711 -
410712 -         [On 030410 this sample template file was not noticed; Gary
410713 -         will review. ref SDS 14 QB3H
410715 -  ..
410716 - The idea is to create a file that can be used by SDS for a connected
410717 - record of organizational memory, and, also, enables other people to
410718 - readily use the work product outside of SDS, within the meaing of a
410719 - 3-layer architecture developed on 020820. ref SDS 5 0001  HTML
410720 - formatting accomplishes this because most people these days have
410721 - access to a Microsoft web browser.
410722 -
410723 -      1.  Would like to see the original file in order to ensure there
410724 -          is nothing that needs attention that is not apparent from
410725 -          what is received from Gary today.
410727 -           ..
410728 -          If it came from the Internet, then there should be a link to
410729 -          the original source.  Actually, there is an address to
410730 -          Aerospace company, which is incorporated into the sample file, but it
410731 -          does not seem to be on the Internet.
410733 -           ..
410734 -          Otherwise, there should be a note or something that
410735 -          identifies the original source, author, publisher, date, etc.
410737 -           ..
410738 -          Using the original source as an outline, added some HTML to
410739 -          accomplish "close" to what the original thing looks like.
410741 -           ..
410742 -      2.  Not everything needs to be exactly the same.
410743 -
410744 -          Some formatting can be omitted, if the structure can be
410745 -          otherwise conveyed without adding HTML code.  To illustrate
410746 -          will bring this file into my own records for training.
410747 -          ref OF 2 0001
410749 -           ..
410750 -          An example are subheadings.
410752 -           ..
410753 -          The format shown is....
410754 -
410755 -             LEVEL 2 KEY PRACTICES, ref OF 2 WV8K,
410756 -
410757 -               Requirements Management (RM)
410758 -
410759 -                 Goals:
410760 -
410761 -                   1. System requirements allocated to software are
410762 -                      controlled to establish a baseline for software
410763 -                      engineering and management use.
410764 -                      ..
410765 -                   2. Software plans, products, and activities
410766 -                      are kept consistent with the system requirements
410767 -                      allocated to software.
410769 -           ..
410770 -          Suggested revision is....
410771 -
410772 -             LEVEL 2 KEY PRACTICES, ref OF 2 WV8K,
410773 -
410774 -                 The next two levels of outline are accomplished by
410775 -                 changing the size and adding bold to intermediate
410776 -                 headings in order to avoid using dir or other commands
410777 -                 that clutter up the file.  Another option is to add a
410778 -                 and b for Goals and Activities, but since this is a
410779 -                 consistent format, and there is never a subsequent
410780 -                 item in the list, it seems unnecessary to have either
410781 -                 further indentation or an ordered outline
410782 -                 identification to accomplish the objective.
410784 -              ..
410785 -             Requirements Management (RM)
410787 -              ..
410788 -             Goals:
410789 -
410790 -                   1. System requirements allocated to software are
410791 -                      controlled to establish a baseline for software
410792 -                      engineering and management use.
410793 -                      ..
410794 -                   2. Software plans, products, and activities
410795 -                      are kept consistent with the system requirements
410796 -                      allocated to software.
410797 -
410799 -           ..
410800 -      3.  Outline format changed from n) to n.
410801 -
410802 -          In the fomrat example file I created, ref OF 2 WV8K, changed
410803 -          the outline format to use n. because n) does not seem to
410804 -          support the feature that creates anchors.  For outline
410805 -          material, we want the anchor inline or on the same line,
410806 -          since all external (Other) files are formatted for processing
410807 -          by a web browser that automatically wraps the text within
410808 -          margins; whereas SDS records use the pre command, and so the
410809 -          anchors are all above the line.  SDS code that creates
410810 -          anchors puts them on the text line for outlining that uses a.
410811 -          or n., but not a) or n). Additionally, the n) format seems to
410812 -          fail when the number gets above 10.  Changing to n. fixes all
410813 -          of this.
410814 -
410815 -              [...later corrected SDS to handle outline structures
410816 -              using n) above 10, and so switched the format from n.
410817 -              back to n), which was Gary's original choice.  This
410818 -              change, however, resulted in HTML not wrapping text at
410819 -              the outline level.  Evidently HTML does not support n) as
410820 -              an outline format.  So changed it back to n. because this
410821 -              gives a cleaner outline structure with the text wrapped
410822 -              at the outline level.
410823 -
410824 -
410825 -
410826 -
410827 -
410828 -
410829 -
4109 -

SUBJECTS
Context Management Multiple Views Subject Index Assignments  eflect O
Dilemma KM Organizing Context into Useful Subjects Pandora's Box of C
CMM KPAs and Activities Contracts Manuals Policy Procedures Published
Contracts Manuals Policy Procedures Published Criteria Objectives Re
Productivity IT Declined Last 10 Years Info Highway Requires Ergonomi
Setup Project Accounts Transfer from Initial Learning Accounts in 04
Aerospace company  combat Setup Major Project Subject Accounts Transfer  nitial Lear

4909 -
491001 -  ..
491002 - Subject Index Use CMM KPAs and Activities
491003 - CMM KPAs and Activities Good Source for Subjects
491004 -
491005 - Follow up ref SDS 9 TK8F.
491006 -
491007 - Two related issues present challenges using a new way of working...
491008 -
491009 -     1.  Figuring out a directory and filename to store an external
491010 -         file like a specification, spreadsheet, letter, book, etc.
491012 -          ..
491013 -     2.  Figuring out subjects, making subject assignments and
491014 -         selecting a subject for locating information.
491016 -  ..
491017 - Since these are related issues; making progress on one helps the
491018 - other.
491020 -  ..
491021 - The first issue is to set up  combat under the 03 major projects account.
491022 - Gary got started using SDS by assigning everything under the 04 00001
491023 - account because I moved all of the initial accounts he created to 04
491024 - 00001 to correct initial problems, reported on
491025 -
491026 -     [On 030420 follow up on setting up major account for combat.
491027 -     ref SDS 17 KS9H
491029 -  ..
491030 - On 030111 the idea of using "people" and "organizations" for primary
491031 - subject management, was discussed. ref SDS 9 TK8F
491033 -  ..
491034 - Today, the file Gary submitted, ref OF 2 0001, illustrates another
491035 - approach that makes context management with the subject index fast and
491036 - easy.
491038 -  ..
491039 - We have previously discussed the need to get the Aerospace company contract to
491040 - use as a primary control criteria.  This is helpful for a lot of
491041 - reasons, but a special reason concerning the use of SDS is that it
491042 - provides a template for creating a subject structure, along with WBS,
491043 - CPM and budgets, that require minimal time, since the planning has
491044 - already been done by others.  Similarly, using a policy and procedure
491045 - manual to set up subjects is extremely helpful. Without these
491046 - criteria, subjects can be constructed using the history of
491047 - communications, as was done on the OHS/DKR effort, but this takes a
491048 - lot more time and expertise.
491049 -
491050 -     [On 030414 letter to Gary discusses this issue. ref SDS 16 N236
491052 -      ..
491053 -     [On 030420 follow up on setting up major account for combat.
491054 -     ref SDS 17 KS9H
491056 -  ..
491057 - The file on...
491058 -
491059 -                  CMM KPAs and Activities
491060 -
491061 - ...demonstrates this benefit. ref OF 2 0001  This file has a lot of
491062 - requirements, much like the Federal Acquisition Regulations (FAR),
491063 - that are excellent guidelines for good management, but are hard to
491064 - implement by people on the job, as related in the record on 020504.
491065 - ref SDS 4 NS6F  In the case of FAR, there is authority of law, a cadre
491066 - of professionals to inspect for compliance, and the government can
491067 - issue payments to encourage performance, yet the complexity of the
491068 - task to align work with requirements results in requirements largely
491069 - being ignored until catastrophe strikes, as with loss of the Columbia
491070 - Space Shuttle, reviewed on 030304. ref SDS 10 KV6K
491072 -  ..
491073 - None-the-less, this particular document provides important guidance
491074 - that makes identifying subjects fast and easy, including an acronym
491075 - structure that can be applied directly to create organic structure
491076 - with minimal analysis, since somone has already done this work.
491078 -  ..
491079 - Once the subjects are set up, daily work can be routinely aligned with
491080 - requirements, and progress can be assembled quickly and easily.  The
491081 - procedures in CMM KPAs and Activities, like FAR, represent a lot of
491082 - hard won experience over many centuries.  While software development
491083 - is a new field, these procedures simply restate methods developed for
491084 - other fields.  Studies showing software engineering typically ignores
491085 - good management, related on 950428, ref SDS 1 3921, suggests that
491086 - using SDS to expand span of attention can enable engineers to comply
491087 - with procedures in CMM KPAs and Activities which are otherwise ignored
491088 - in the "fog of war."  Using good management can save time and money by
491089 - solving problems on past projects, reported on 011006. ref SDS 3 O99K
491091 -  ..
491092 - These guidelines supplement criteria from contracts, regulations,
491093 - industry standards like ISO, to help Aerospace company and the government succeed
491094 - by expanding span of attention by continually reminding everyone about
491095 - alignment between the work and requirements.  If this is done daily,
491096 - then issues will arise when they are small and so within the ability
491097 - of people to make adjustment at minimal time and expense.  If this is
491098 - not done, then people only will be reminded that the work has drifted
491099 - off course when disaster strikes, and that time, the time and expense
491100 - will be so great as to cause people to cover up and deny, rather than
491101 - fix anything.  It is another KM dilemma.
491102 -
491103 -
491104 -
491105 -
491106 -
4912 -

SUBJECTS
Zip Update SDS Program and My SDS Records for Training Purposes on Ga

5003 -
500401 -  ..
500402 - SDS Program Code and Work Records Updated
500403 -
500404 - Follow up ref SDS 12 0245.
500405 -
500406 - Submitted ref DIT 1 0001 notifying Gary by email that an SDS update is
500407 - on the web covering the period from last transfer on 030318.
500408 - ref SDS 12 0245
500410 -  ..
500411 - Used procedures reported on 021201. ref SDS 8 CL9N
500413 -  ..
500414 - This update does not report any improvements nor corrections, although
500415 - a few small things have been fixed, including the problem that Gary
500416 - reported this morning, per above. ref SDS 0 NH7O
500418 -  ..
500419 - Updated files can be downloaded at....
500420 -
500421 -
500422 -        http://www.welchco.com/09/
500423 -
500424 -     [On 030411 submitted another update to correct code for conacts.
500425 -     ref SDS 15 0001
500426 -
500427 -
500428 -
500429 -
500430 -
500431 -
500432 -
500433 -
5005 -