CONTACTS 

SUBJECTS
SDS, Business Development, Product Support,
MS Windows Development Tools, Windows Compiler
SDS Records, Design, Schedule
Core of Knowledge Management
Using SDS Essential to Understand How to Create Next Generation Versi
SDS Secret of KM Others Don't Have It
Experience Using SDS Needed in Order to Understand How to Develop Des
Architecture Morris Starting Design for SDS Windows Program
Software Category None Apply to SDS
Architecture Human Thought Predicate Architecture KM, 000531
Breakthrough SDS Design Yields Breakthrough Productivity
Spreadsheet for Knowledge Integrates All Information Streams from Dif
Executives Want to Expedite Save Time Money Need to Know Who What Whe

3515 -
3515 -    ..
3516 - Summary/Objective
3517 -
351701 - Follow up ref SDS 12 0000.
351702 -
351703 - Considered plan for program development based on SDS prototype.
351704 -
351705 -    [On 950816 Morris does not have time to continue work on the SDS
351706 -    Windows app. ref SDS 13 0599]
351707 -
351708 -
351710 -  ..
3518 -
3519 -
3520 - Progress
3521 -
352101 - Role of SDS Records Integrates All Information Streams
352102 -
352103 - I guess my question from our work last night ref SDS 12 3088, is
352104 - whether SDS is a tool to "incorporate" graphics, spreadsheets, CPM
352105 - schedule elements internally, or is it a place primarily for analysis
352106 - about the larger world of knowledge that, then, merely POINTS to those
352107 - other things (e.g., graphics and spreadsheets), and if the User wants
352108 - to see them he can access them by clicking on pointers within a
352109 - record.
352111 -  ..
352112 - If we incorporate graphics, spreadsheets and so on, directly into the
352113 - SDS record, then it could take a much longer time to open such
352114 - records, as is the case with IBM's Web program.  In that case SDS
352115 - records may not jump onto the screen as they do now.  Could this slow
352116 - daily work, and especially reports that show what was done and why,
352117 - and thereby incrementally reduce reliance on the record, and increase
352118 - use of personal recall, i.e., cursory, spontaneous, impulsive "seat
352119 - of the pants" management?
352121 -       ..
352122 -      [On 000423 listed features to compliment SDS. ref SDS 21 8000
352124 -       ..
352125 -      [On 000503 reviewed ideas for development of KM using SDS as core
352126 -      technology. ref SDS 23 6903
352127 -
352129 -  ..
352130 - Executives want to expedite!
352132 -  ..
352133 - They want to work quickly.  They want to go with what they "know."
352135 -  ..
352136 - They want to "know" the "bottom line" and the "big picture," again, so
352137 - they can expedite, and feel good about telling others to expedite
352138 - while insisting on getting the "truth," reported on 950412.
352139 - ref SDS 6 3920
352140 -
352141 -      [On 000706 Morris discussed what SDS does that customers care
352142 -      about. ref SDS 24 RX3K
352144 -  ..
352145 - This is an endemic drive of most humans that technology must support,
352146 - or at least strike a new, more powerful, balance between accuracy and
352147 - speed.
352149 -  ..
352150 - This requires technology that enables people to quickly discover and
352151 - create what they "know," otherwise they will rely on false knowledge
352152 - in their head that is obtained and transferred to others through
352153 - conversation, because it seems fast and easy.  They will fail as they
352154 - are doing now because they are ignoring the true state of affairs.
352155 -
352156 -      [On 990625 Fortune article reports executives fail for precisely
352157 -      this reason. ref SDS 16 7344]
352159 -       ..
352160 -      [On 000227 explained SDS as core capability for knowledge
352161 -      management. ref SDS 18 8960]
352162 -
352164 -  ..
352165 - Executives mainly want to know what was done, what was seen, what was
352166 - said, and what they "think" about it, for the reasons set out in the
352167 - NWO... ref OF 1 2536
352169 -  ..
352170 - When we go to a meeting or have a telephone call, these are verbal
352171 - exchanges that consider the larger world of images, calculations,
352172 - documents, contracts, and so on.  When a decision is made it is
352173 - typically a narrative that may refer to a document, graph, picture or
352174 - calculation.  Similarly, when a question is asked, very few people
352175 - draw a picture.  They "explain" the answer and cite a picture, graph
352176 - or calculation for support.  This is how SDS works now, but it cannot
352177 - use the pointers to graphical and spreadsheet data to access the
352178 - actual data in those files, as it can with correspondence done in
352179 - ASCII.  What we want to give executives this capability so it can be
352180 - used when needed, but we don't want it to clutter up or slow down the
352181 - core capability which is to manage knowledge through langauge.
352183 -  ..
352184 - My sense is then that we want to achieve a way to link into other data
352185 - forms to integrate them with the language in SDS, so in effect we are
352186 - aiming to create a:
352188 -                    ..
352189 -                   Spreadsheet for Language/Knowledge
352190 -
352191 -
352192 - I think it could be very helpful to incorporate pictures directly into
352193 - the SDS record, and it could occassionally be helpful to incorporate
352194 - graphs, and to extract portions of spreadsheets for inclusion into an
352195 - SDS record.  However, the main emphasis should be on using the special
352196 - tools that have been created for special work such as graphics,
352197 - spreadsheets and CPM, and use SDS as the tool that synthesizes
352198 - everything through language that says what we want, what we did, what
352199 - influenced what was done, why, and what we expect will occur and when.
352200 -
352201 -
352202 -
352203 -
3523 -

SUBJECTS
SDS Design Takes Time Using SDS Current Version Prototype for 5 Years
5 Year Development Schedule Need to Continue Enhancing Current Versio

3704 -
370501 -  ..
370502 - Options and Ideas - Enhance Current SDS Program
370503 -
370504 - We might begin the Windows version of SDS by maintaining the current
370505 - SDS directory sturcture, since experience shows that it works, it is
370506 - simple, reliable and very fast.  See if we can achive this in Windows,
370507 - and concentrate on other aspects of SDS to apply Windows advantages,
370508 - such as menus scroll bars, and links to other applications.
370509 -
370510 -     Of course it may turn out that it is just as much work trying to
370511 -     get Medit to support SDS under Windows as it is to craft a
370512 -     dedicated program.
370514 -  ..
370515 - This may save a lot of time in creating and debugging a new data base
370516 - structure, complete with report writing and error recovery tools,
370517 - before we can use the system at all.
370518 -
370519 -      [On 950816 discussed with Morris. ref SDS 13 0599]
370521 -  ..
370522 - We need to ensure that SDS will continue to run on computers in the
370523 - market place through the period required to develop a Windows version
370524 - of SDS, which may take 5 to 10 years.  During this time evolution may
370525 - obsolete ability of Medit to run SDS,
370527 -  ..
370528 - An intermediate step can be achieved with limited coding resources
370529 - available by writing a version of Medit that is backward compatible,
370530 - so it can use all of the existing macros.  Morris said he began such a
370531 - program several years ago.  This might provide fairly quickly a new
370532 - tool that Morris can use to evaluate his ideas, based on the current
370533 - level of capability.  So the first step is to create a way to grow and
370534 - test our knowledge of what this tool is and what it should be.
370535 -
370536 -
370538 -  ..
370539 - Plan & Schedule Giving Developers Experience with SDS
370540 -
370541 - Experience on 910523 shows that people need to work with SDS in order
370542 - to understand counterintuitive processes that integrate time and
370543 - information, ref SDS 2 2736,, per planning on 910520 when SDS was
370544 - installed for Morris to use. ref SDS 1 XR5H
370546 -  ..
370547 - Discussions on 911121, ref SDS 3 7420, and later on 920215 support
370548 - this conclusion. ref SDS 4 5820,
370549 -
370550 -      [On 000406 Doug Engelbart proposes similar scenario for creating
370551 -      KM capability, i.e., train software engineers first so they learn
370552 -      what to program. ref SDS 20 5078
370554 -  ..
370555 - Discussion with Morris last night is an example of the disconnect from
370556 - cultural barriers that block understanding of SDS. ref SDS 12 BF4A
370557 - Morris demonstrated good command of SDS scope and value added in the
370558 - product development plan he prepared on 950221. ref SDS 5 JC7O
370559 - Today, for some reason understanding seems to have completely slipped
370560 - away, evidently from lack of use, and lack of exposure to language
370561 - describing capabilities.
370563 -  ..
370564 - This record suggests there is something about SDS that is hard for
370565 - people to grasp without experience using it, so we need to start by
370566 - giving engineers experience using SDS, as attempted on 910520.
370567 - ref SDS 1 0001
370568 -
370569 -      [On 000106 Morris advised SDS is a unique design. ref SDS 17 1316
370571 -       ..
370572 -      [On 000324 research at SRI indicates all of the projects to
370573 -      create Knowledge Management have failed. ref SDS 19 4877
370575 -       ..
370576 -      [On 000425 KM seems to be a secret of SDS. ref SDS 22 0480
370578 -       ..
370579 -      [On 000503 proposed 2 phase plan for new project. ref SDS 23 0760
370581 -       ..
370582 -      [On 000716 professor Ransdell comments SDS enables a theory of
370583 -      management based on a communication "process" which has eluded
370584 -      discovery since the 17th century, so it should be expected that
370585 -      understanding SDS will take time. ref SDS 25 7838
370587 -       ..
370588 -      [On 010924 Morris explains SDS is only KM capability, because
370589 -      need synergy between use and application. ref SDS 26 NK4J
370591 -  ..
370592 - To accomplish this objective, here is what an SDS development schedule
370593 - might look like....
370594 -
370595 -
370596 -     Create Intermediate SDS runs in Windows, Update Medit C Version
370597 -     ---------->----|
370598 -         6 Mos      |
370599 -            |       v
370600 -            |       |
370601 -            v  Use Intermediate version gain experience
370602 -            ------------------//---------------------->------|
370603 -                     |  5 years                              |
370604 -                     |                                       |
370605 -                     |                                       |
370606 -                     v    Create New Windows SDS version     v
370607 -                     --------------------------//-------------------->
370608 -                               8 years
370609 -
370611 -  ..
370612 - Actually, it would not be unreasonable to set a goal of introducing
370613 - the version of SDS Morris has in mind in 5 years as a new tool for a
370614 - new age in the year 2000.  Would have to figure out how to accelerate
370615 - the coding operation.
370616 -
370617 -     [On 030803 discussed with Morris and Gary Johnson need interim
370618 -     improvements to memory for current version. ref SDS 27 QE40
370620 -  ..
370621 - It probably is not a good idea however to assume we can jump over the
370622 - step of gaining experience in the hands of software engineers, who
370623 - will design and code the program, about what needs to be designed and
370624 - coded.  Publications emphasize the importance of giving software
370625 - engineers experience with the problems they are trying to solve, see
370626 - for example on 951221. ref SDS 15 FJ6J
370627 -
370628 -    [On 951012 discussion with Morri. ref SDS 14 0001
370629 -
370630 -
370631 -
370632 -
370633 -
370634 -
370635 -
370636 -
370637 -
370638 -
370639 -
370640 -
3707 -