CONTACTS 
0201 - Dynamic Alternatives                                                                                                                                               O-00000793 0101
020101 - Mr. Garold L. Johnson; 714 896 3311 ext 71223                                                                                                                    O-00000793 0101

SUBJECTS
Software Requirements Specifications SRS
SDS Software Requirements Specifications SRS
Design Requirements SDS Gary Prepare Software Requirements Sp
Architecture Counterintuitive SDS Design Aided by Synergy from Daily
Difficult to Understand Knowledge Management SDS Core Capability
Johnson, Gary Considering Developing SRS for SDS Needs Code from Morr
Medit C Version Update to Run SDS on Windows Solve Memory Problem
Medit C Version Update to Run SDS on Windows Solve Memory Problem
Johnson, Gary Needs Code from Morris to Work on Solving SDS Memory Pr

3111 -
3111 -    ..
3112 - Summary/Objective
3113 -
311301 - Follow up ref SDS 62 0000, ref SDS 61 0000.
311302 -
311303 - Received ref DRT 1 0001 from Gary commenting on the letter submitted
311304 - on 020522, ref DIP 6 0001, thanking Gary for consideration of doing an
311305 - SRS for the SDS program, ref SDS 62 OY7K, and explain that code Morris
311306 - has created to support SDS is on Welch computers. ref DIP 6 5R5O
311308 -     ..
311309 -    Memory Problem in SDS Needs Morris' Original Code
311310 -
311311 -
311312 - Gary says in response....
311313 -
311314 -    My discussions with Morris focused on what is needed to get SDS
311315 -    moved to a Windows program that doesn't have the memory constraints
311316 -    of the current program.  That requires working from the assembly
311317 -    code since the C editor was not intended to be a functional clone
311318 -    of Medit, and the only real documentation is the code. ref DRT 1
311319 -    438G
311320 -
311321 -        This was raised with Gary on 020108. ref SDS 46 EH6J and
311322 -        ref SDS 46 229G
311324 -         ..
311325 -        Any chance Morris and Gary could work together in some way on
311326 -        this so the entire burden does not fall on a single person?
311328 -         ..
311329 -        On 010426 Morris asked if people are "ready" for a Windows
311330 -        version of SDS. ref SDS 31 0001
311331 -        ..
311332 -        I called Morris about Gary's point, and understood Morris
311333 -        to explain that the C version of Medit is one path for solving
311334 -        the memory problem by adding support for macro commands that
311335 -        were added to the original version for SDS, discussed
311336 -        previously on....
311337 -
311338 -            010205................................. ref SDS 30 6Q8H
311339 -            980722................................. ref SDS 12 3280
311340 -
311342 -     ..
311343 -    SRS for SDS Can Begin Based on POIMS, SDS Program and Record
311344 -
311345 -
311346 - Gary quotes from my letter on 020522 that says....
311347 -
311348 -    Why is assembly code for Medit needed to get started on
311349 -    requirements (SRS) for SDS? ref DIP 6 VX6M
311350 -
311351 -    (Omitted analysis in the letter on this pointg, also shown in the
311352 -    record on 020522. ref SDS 62 VX6M
311353 - ..
311354 - ...and then he comments...
311355 -
311356 -    You are correct that developing requirements for SDS uses different
311357 -    information. To tackle it for real would require bringing up SDS so
311358 -    that all of its features are visible and can be investigated. The
311359 -    macro code would likely be helpful as well as the only sure way of
311360 -    finding all the features would be to make sure that all of the
311361 -    macros have been covered. At the same time, this would complete the
311362 -    documentation of the macros, much of which I know is in the record
311363 -    so that it might not be necessary to go through the code for them.
311364 -    ref DRT 1 X28N
311366 -  ..
311367 -
311368 -        Notify Gary to let me know if there is anything I can do
311369 -        to expedite work on SRS, per his letter today.
311370 -
311371 -        One scenario might be for Gary to initially produce a first
311372 -        order statement of capability based on POIMS, his interaction
311373 -        with SDS records on the Internet, and his experience using
311374 -        other methods to see if plausible case can be made for
311375 -        identifying unique SDS capabilities that justify a broader
311376 -        effort.
311378 -         ..
311379 -        With a professional statement of capability needs for improving
311380 -        the work at places like Aerospace company, Microsoft, IBM, the FBI and so
311381 -        on, together with an explanation that SDS meets these needs, it
311382 -        might then be possible to develop funding for a project to
311383 -        create an SDS version for Windows that would finance a full SRS
311384 -        for SDS.
311385 -        ..
311386 -        Morris' point is that there is no market for better
311387 -        management, and Gary has largely agreed, so this suggests not
311388 -        taking any action.  On the other hand, there is a sense that
311389 -        Gary wants to take some action, so a first step is to develop a
311390 -        case for what is needed to improve current practice, which Gary
311391 -        has considered, based on his letter issued 011006, ref SDS 41
311392 -        G46I, so that knowledge can be applied to explain how SDS meets
311393 -        the need to improve current practice.
311394 -
311395 -
311396 -
311397 -
311398 -
3114 -

SUBJECTS
Aerospace company Projects Get Fouled Up Due to Changing Personnel
ISS International Space Station Gary Contractor on Requiremen
Aerospace company Fouled Up Project Capable Unwilling to Use Good Manag  ent Per
Work Should be Traceable to Original Requirements SRS STD PID and ICD
Requirements Failure Perform Huge Holes Between Requirements and Desi

3607 -
360801 -     ..
360802 -    Design and Implementation ISS Software Fails Requirements
360803 -    Huge Holes Between Requirements and Design and Implementation
360804 -    Requirements Not Met by Design Implementation ISS Software
360805 -
360806 -    Follow up ref SDS 62 T29G.
360807 -
360808 - Gary points out....
360809 -
360810 -    This continues to amaze me. The deeper I dig in terms of analyzing
360811 -    the mismatch between the documents that are supposed to describe
360812 -    what is to be built and what they actually built (before writing
360813 -    the requirements), the worse the situation looks. There are so many
360814 -    broken connections in the small portion that I am able to analyze,
360815 -    that I shudder to think what the code must be like. ref DRT 1 VM6G
360816 - ..
360817 - Gary says in closing...
360818 -
360819 -    I don't think it is possible to overstate the magnitude of the mess
360820 -    that the ISS requirements are in. I think that the requirements and
360821 -    then the code need to be redone from the beginning; that this is
360822 -    the prototype that should be thrown away. I realize that this is
360823 -    unacceptable for a product that has cost the millions of dollars
360824 -    that this one has, but that doesn't alter my opinion. ref DRT 1
360825 -    5Y9G
360826 -
360827 -
360828 -
360829 -
360830 -
3609 -

SUBJECTS
Aerospace company Case Study Bad Management Developing Requirements
Private Gary's Analysis of Aerospace company Management Developing Requ  ements to
FAR Legal Exposure ISS Software Project being Performed by Aerospace co  any
ISO Traceability to Original Sources Audit Trail Alignment Accountabi
Cover-up Ignore Small Problems Not Enough Time Ignored Resists Proact
FAR Legal Exposure ISS Software Project being Performed by Aerospace co  any
Quality Compliance Failed Tests Rigged to Pass Rather than Demonstrat

8409 -
841001 -  ..
841002 - Risk Management Avoids Accountability for Failure to Perform
841003 - ISO 9000 Audit Passed by Aerospace company without Actual Compliance
841004 - Legal Exposure Arises from Failure to Perform FAR Requirements
841005 - Aerospace company ISS Software Project Requires Compliance with FAR
841006 -
841007 - Follow up ref SDS 62 RJ4K, ref SDS 61 0000.
841008 -
841009 - Gary responds to the idea in the letter to him on 020522 about using
841010 - the record on the ISS Software project, ref DIP 6 Z59K, as a case
841011 - study, i.e., an "example," he developed on 020315, ref DRP 5 QM6K, for
841012 - lessons learned to strengthen DOD management under FAR, ref SDS 62
841013 - UL4J
841014 - ..
841015 - Gary says today...
841016 -
841017 -      I have to agree with Stuart that technology alone cannot produce
841018 -      good management. Given a desire to produce good management,
841019 -      however, technology can most certainly help. ref DRT 1 TI5I
841020 -
841021 - ...referring to Stuart's comments in the record on 010608 concerning
841022 - benefits of SDS, ref SDS 32 RS4J, and later on 010730 on need for
841023 - intellectual bridges to build new attituges, ref SDS 34 LC5O, cited in
841024 - the letter to him on 020522. ref SDS 62 UL4J
841026 -  ..
841027 - Gary does not comment on concept that technology that makes good
841028 - management faster and easier, so that it is within reach of people,
841029 - can foster attitutes about using good management, as discussed in the
841030 - record on 020522. ref SDS 62 8Y6K
841031 - ..
841032 - In other words, it is not necessary to hold "attitude adjustment
841033 - and ideological training" classes.  Empower people to work better and
841034 - enable people to experience benefits of good mangement and the cost of
841035 - bad management, and attitudes change for a large segment of the
841036 - population.  But so long as people get rewarded for bad management
841037 - people will continue to press the Reply button in email noted on
841038 - 010908, ref SDS 35 UV4H, rather than invest intellictual capital
841039 - required by FAR.
841040 - ..
841041 - Gary continues...
841042 -
841043 -      I am currently reading some work of Stafford Beer who developed a
841044 -      cybernetic model of Viable Systems, and what sorts of effort are
841045 -      required by management actually to manage the enterprise
841046 -
841047 -          http://www.staffordbeer.com/
841049 -       ..
841050 -      I don't recommend you dig into it as it is hairy stuff. I am just
841051 -      starting, but it looks as though it may shed some light on how we
841052 -      are able to manage so poorly from a perspective of the way
841053 -      systems actually work.
841054 -
841055 -
841056 -
841057 -
8411 -

SUBJECTS
Case Study Aerospace company ISS Developing Requirements to Fit Work Ac  ally Pe
Case Study Lessons Learned Gary Agrees to Release Case Study on Boein

9204 -
920501 -  ..
920502 - Release Case Study to Improve FAR Contract Management
920503 - Case Study Lessons Learned Released to Improve FAR Contract Management
920504 -
920505 - Gary comments on request to release his analysis for a case study of
920506 - lessons learned to improve FAR and DOD management as set out in the
920507 - letter, ref DIP 6 GT4F, submitted on 020522. ref SDS 62 UL4J
920508 -
920509 -      I don't have any problem wit[h] the facts of what I have said
920510 -      being made available, particularly to someone who might be
920511 -      interested and able to do something about improving the
920512 -      situation, but there are cases where the wording may be more
920513 -      harsh than I would have allowed myself in a public report. The
920514 -      facts, however, are as I have stated them. ref DRT 1 318K
920516 -  ..
920517 - This modifies Gary's request on 020315. ref SDS 52 8Z8J
920518 -
920519 -     [On 020530 Stuart Harrow at DCMA reviewing case study for lessons
920520 -     learned to strengthen FAR and DOD management. ref SDS 63 QR9G
920521 -
920522 -     [On 020531 sent follow up letter to Gary. ref SDS 64 0001
920523 -
920524 -
920525 -
920526 -
920527 -
9206 -

SUBJECTS
Changing Personnel Causes Communication to Fail on Projects  or Softw
Aerospace company Assignment Ends in Few Months Then Needs Another Assi  ment Ti
Communication Fails Personnel Changes Productivity Falls Until New St
Change Personnel Productivity Falls Communication Fails Until New Sta
Get By Bad Management Memory 5% Gist Skills Good Enough Feel Good Man
Giving Up on Communication
Improve Management Resisted Change New Way Working Takes Faith Commit

AR09 -
AR1001 -  ..
AR1002 - Attitude and Intent Follow the Money
AR1003 - Good Management Must be Specified Overwhelming Tendency Bad Management
AR1004 -
AR1005 - Follow up ref SDS 62 FL5H, ref SDS 52 GHSQ.
AR1006 -
AR1007 - Gary observes...
AR1008 -
AR1009 -      Bridges are certainly necessary. I think that an organization has
AR1010 -      to be in pretty good shape to be able to make good use of tools.
AR1011 -      The more comprehensive the tool, the more difficulty an
AR1012 -      organization in trouble has with it. As I have said, until the
AR1013 -      management and the culture achieve the determination to deliver
AR1014 -      the best product possible and to continue to align with its own
AR1015 -      stated goals, a tool such as SDS which could help them do that is
AR1016 -      simply not anything they can deal with. ref DRT 1 MF4H
AR1017 - ..
AR1018 - Gary does not address the fact that a combination strategy is
AR1019 - needed that makes payment based on compliance with FAR requirements
AR1020 - for good management, and SDS technology that makes good management a
AR1021 - realistic possibility, explained in the record on 020522. ref SDS 62
AR1022 - 0351
AR1024 -  ..
AR1025 - Attitudes come from experience.  If there is experience that good
AR1026 - management is not required, people will form an "attitude" of doing
AR1027 - just enough to get by for getting paid.  However, if requirements are
AR1028 - enforced by withholding payment, then people will form an attitude of
AR1029 - looking for economical ways to use good management. ref SDS 62 7G5H
AR1030 -
AR1031 -
AR1032 -
AR1033 -
AR1034 -
AR1035 -
AR1036 -
AR1037 -
AR1038 -
AR1039 -
AR11 -