THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: March 27, 2002 02:51 PM Wednesday; Rod Welch

Gary asked to work on requirements for SDS.

1...Summary/Objective
........Software Requirements Specifications (SRS) Needed for SDS
........SDS Secret Design Advantage for Creating SRS to Explain KM


..............
Click here to comment!

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

SUBJECTS
Specification Interoperability Between Collaborative Knowledge Applic
Software Development Plan SDP
Software Requirements Specifications SRS
SDS Software Requirements Specifications SRS
SDS Proof of Existence for KM Not Technical Problem
Design Requirements SDS Gary Prepare Software Requirements Sp
SDS Design Requirements Prepare Software Requirements Specification S
SDS Secret KM Design Counterintuitive, 000425
Architecture Counterintuitive SDS Design Aided by Synergy from Daily
Difficult to Understand Knowledge Management SDS Core Capability
Requirements Documents Specification (SRS) Needed to Define Scope SDS

2713 -
2713 -    ..
2714 - Summary/Objective
2715 -
271501 - Follow up ref SDS 36 0000, ref SDS 34 0000.
271502 -
271503 - Submitted ref DIT 1 0001 to Gary submitting a letter received today
271504 - (in another record) from Michael Poremba, ref SDS 37 0001, who
271505 - contacted us some weeks ago expressing interest in contributing to SDS
271506 - development, as shown by the record on 020301. ref SDS 31 0001
271507 - ..
271508 - This follows up the letter to Gary on 020325, ref DIP 3 0001
271509 - linked to the record and explaining potential improvement scenarios.
271510 - ref SDS 36 2N4F
271511 - ..
271512 - Today, explain...
271513 -
271514 -    1.  Michale recently left a dotcom company in San Francisco. His
271515 -        background and age are good factors for possibly contributing
271516 -        to an SDS project, as shown on 020301. ref SDS 31 P64K
271517 -
271518 -        Michale's interest in contributing to SDS, discussed in the
271519 -        record on 020301, ref SDS 31 DY3N, alerts Gary that he is not
271520 -        alone in wanting to do something to advance SDS. ref DIT 1 EY6F
271521 -
271523 -         ..
271524 -        Software Requirements Specifications (SRS) Needed for SDS
271525 -        SDS Secret Design Advantage for Creating SRS to Explain KM
271526 -
271527 -
271528 -    2.  One thing that struck me from your recent letter on
271529 -        020315 explaining work at Aerospace company, ref SDS 33 4E4J, is that a
271530 -        first step toward formalizing SDS in a next generation
271531 -        commercial product might be to write up a set of specs using
271532 -        the current product as a prototype for functionality,
271533 -        ref DIT 1 4F6M, as Gary is doing the ISS software project.
271534 -        ref SDS 33 01VV and ref SDS 33 01X2
271536 -  ..
271537 -        This is a big job, as discussed previously with Morris on...
271538 -
271539 -             Asked Morris for Requirements... 000531, ref SDS 9 0001
271540 -             Morris advises Gary need data
271541 -             flow and structure for SDS...... 020108, ref SDS 28 C53H
271542 -             Morris considering this task.... 020110, ref SDS 28 C53H
271543 -
271544 -        But, apart from fixing the memory issue and ensuring continued
271545 -        viability of SDS on Windows for next 10 years, as we discussed
271546 -        the other day, writing up a set of specs to formally explain
271547 -        SDS is likely the next most important task.
271548 -
271549 -           [On 020521 sent follow up asking about this. ref SDS 39 0001
271550 -
271551 -           [On 020522 Gary is thinking about an SRS for SDS program,
271552 -           mentions needing code from Morris; letter to Gary explains
271553 -           this code is with SDS program on Welch computer. ref SDS 40
271554 -           0001
271555 -        ..
271556 -        A lot of people have been trying to develop requirements
271557 -        (e.g., OHS/DKR, LANL, I suspect some group in Microsoft and in
271558 -        Oracle, etc.) and we know that IBM crashed with Raven, as
271559 -        reported on 001130, ref SDS 16 F26K, because the underlying
271560 -        design seems to be a secret of SDS for reasons discussed with
271561 -        Morris on 010924. ref SDS 21 JS6G
271562 -        ..
271563 -        So we know the secret, as shown on 000425, ref SDS 7
271564 -        0480, and this should provide an advantage on creating
271565 -        something useful.  Just a thought.
271566 -
271567 -
271568 -
271569 -
271570 -
271571 -
271572 -
271573 -
271574 -
271575 -
271576 -
271577 -
271578 -
271579 -
271580 -
271581 -
271582 -
271583 -
271584 -
271585 -
271586 -
2716 -
Distribution. . . . See "CONTACTS"