[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Europe-Swas-Artificial-Intelligence |
|
Moderator: | HERON::BUCHANAN |
|
Created: | Fri Jun 03 1988 |
Last Modified: | Thu Aug 04 1994 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 442 |
Total number of notes: | 1429 |
244.0. "DPM - Knowledge Base Development." by CHEVIE::FITZGIBBON (Joe Fitzgibbon VB/EIC) Mon Nov 05 1990 15:12
At the wrap-up of last weeks AI Forum, Stephane Ripoll, Caroline Stutz
and Leopold Ngamby were kind enough to volunteer their spare time to ensuring
that Expert System project methologies are correctly represented in the DPM
documentation set. I agreed to co-ordinate the activity and interface with
George Ristich. This note is to start the ball rolling on how we go about
performing this task.
I have not yet read any DPM documentation on Software Engineering
techniques, but I am making the assumption that a subject for definition by
this community is the techniques and management issues which relate specifically
to the development of the Knowledge Base contents of any expert system
application - and any issues around integration.
In order to minimise any effort on our part I suggest we take the
opportunity to "re-use" existing documentation on the subject and restrict
ourselves to a "cut and patch" operation.
I would therefore suggest that the goals of this topic be to identify
any diversity of opinion from the guidelines offered in the Grey Book (Guide to
Expert System Program Management), any suggestion for aspects not included in
the Grey Book, or any opinions on which elements of the Grey Book are not
necessary - i.e. they are general enough to be covered by conventional software
project methodologies.
If anybody has their favourite "reference work" on the subject, which
they would like to include as potential source material, then please make it
known since we (I) do not have any strong theological preferences.
We may consider dividing our efforts into two fields -
1. Management process items which are essential to the
successful development of the Knowledge Base contents and integration
considerations. This will include issues of Why, Who, roles,
Resourcing, awareness, education, communication, planning for change, prototyping, evaluation and
evolution, etc...
2. Techniques specific to the definition and development of a Knowledge
Base; issues of Elicitation, formalisation, representation,
inference, evaluation and verification of KB, distribution,
maintenance, etc....
Does anybody consider the question of integration to be significant
enough to merit separate treatment?
Regards,
Joe.
T.R | Title | User | Personal Name | Date | Lines
|
---|