Adaptive Knowledge Base Development
April 06, 2004
At the day job we are finally beginning to make plans for developing the next iteration of IndianaUniversity's KnowledgeBase. To gather my thoughts I wrote a little document that brings together some of the thoughts about situated software and software development that have been bouncing around over the last several days. (3UZ)
Here's the beginning: (3V0)
This comes at an interesting time in systems development: an awareness of the desirability of unintended uses of systems and reuse of code is growing alongside a growing understanding of the importance of systems that are well suited to the many dimensions of the environment in which they are situated. T (3V1)
and the end: (3V2)
A small pieces Knowledge Base will not and cannot foresee all eventualities but it can be more prepared for them by being adaptable. That adaptability can be achieved by breaking the monolithic service of the existing KB into smaller pieces that act independently but also interoperate. Additional small pieces of situated software acting as front ends to the KB system can meet the needs of emerging groups in an ad-hoc fashion. T (3V3)
Update: Thanks to Seb for catching my misattribution of the preface of ''Small Pieces Loosely Joined". (41G)
Comments
Interesting piece. Minor nit: you attribute the preface of SPLJ to Shirky. (41F)