CONTACTS 

SUBJECTS
OHS Program Code Architecture Under Production
OHS Architecture Eric Armstrong Creating Code for OHS to be Released So  , 001017
Architecture Snag OHS Eric Armstrong, 001018
Architecture Makes Sense Contemporaneous Engineering Record with Code
Architecture Problems KM Linking Versioning, Eric Armstrong, 001018
Linking Architectural Snag KM, Eric Armstrong
Ease of Use More Important than Usefulness
High Tech Tourism Cannot Solve Complexity Issues in KM
Complexity Knowledge KM Dilemma, Paul Fernhout

2411 -
2411 -    ..
2412 - Summary/Objective
2413 -
241301 - Follow up ref SDS 6 M4W7, ref SDS 5 M4W7.
241302 -
241303 - Over the past severl days, a lot of people including Eric have
241304 - analysed design challenges he reported on 001018. ref SDS 5 M4W7
241306 -  ..
241307 - Today, Paul Fernhout submits another thoughtful letter, ref DRT 1
241308 - 0001, that underscores the difficulty of discoverying an architecture
241309 - for Knowledge Management which accomodates the complexity of human
241310 - knowledge, ref DRT 1 RY8F, set out, as well, in POIMS. ref OF 1 0561
241312 -  ..
241313 - Validation and error recovery are discussed, along with versioning,
241314 - which was treated in some depth on 000305 by Xanadu, including
241315 - versioning methods it calls transclusions. ref SDS 1 4725
241317 -  ..
241318 - Paul supports using an analyst to patch over the occassional really
241319 - unexpected glitch. ref DRT 1 P48O
241320 -
241321 -     Need example from Paul of a "really unexpected glitch" that
241322 -     requires a data base analyst.
241323 -
241324 -     On 000327 Doug calls for special expertise to help people through
241325 -     the learning curve, ref SDS 2 5256, which seems to be reflected
241326 -     in recent plans announced on 001017 under the leadership of Carla
241327 -     Woodworth and Reg Ford. ref SDS 4 01DP
241329 -      ..
241330 -     Communication Metrics calls for special expertise to use special
241331 -     technology for adding intelligence to daily management, in order
241332 -     to save time, reduce cost, avoid conflict and solve problems,
241333 -     large and small. ref OF 2 6369
241334 -
241336 -  ..
241337 - Paul delves into the usefulness v. ease of use battle, with a quote
241338 - from somewhere...
241339 -
241340 -      "Design a system that even a fool can use, and only a fool will
241341 -      want to use it." ref DRT 1 R64L
241343 -  ..
241344 - On 000921 Eric commented. ref SDS 3 0FU3
241345 - ..
241346 - Paul further says...
241347 -
241348 -      Another way to think of this is as "classes of validation" or
241349 -      "classes of error recovery". So, some errors one expects the
241350 -      system to handle routinely and other errors one expects a human
241351 -      to have to detect or deal with (ranging from a minor automated
241352 -      error recovery confirmation to a day long debugging session).
241353 -      ref DRT 1 XG5J
241354 -  ..
241355 -      Need example of errors that require "recovery" capability by the
241356 -      system.  What is the "system" doing that can make an error?
241357 -
241358 -        [On 001027 Paul submitted conmprehensive explanation.
241359 -        ref SDS 7 0001
241360 -
241361 -
241362 -
241363 -
241364 -
241365 -
241366 -
241367 -
241368 -
241369 -
241370 -
2414 -