Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!network!ucsd!orion.cf.uci.edu!uci-ics!zardoz!ccicpg!cci632!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!rochester!rutgers!cs.utexas.edu!uunet!mcvax!unido!uklirb!shell From: peterson_s@apollo.com (Steve Peterson) Newsgroups: comp.ai.shells Subject: Knowledge Engineering References Message-ID: <5353@uklirb.UUCP> Date: 22 Jul 89 22:36:00 GMT Sender: news@uklirb.UUCP Organization: Apollo Computer, Chelmsford, Mass. Lines: 21 Approved: shell@uklirb.uucp Posted-Date: Fri Jun 16 14:23:47 GMT 1989 Hello, Recently I've been searching for some references on the knowledge engineering process. I'd appreciate receiving any information on methodologies for structuring the knowledge acquisition process (manual or automated) and then transforming that knowledge into an appropriate knowledge representation. Information on using a top-down/structured approach with hueristics like "Define your object classes before writing the rules", "Start with defining declarative knowledge, then define procedural knowledge", "Group rules into knowledge-islands", or "Only have one condition in the IF part of your rules" would be especially interesting. Comparisons of methodologies(top-down vs. bottom-up) would also be very interesting. Thanks in advance and I'll post a summary to net if there is sufficient interest. Stephen Peterson ARPA: peterson_s@apollo.com UUCP: {decwrl!decvax, mit-eddie, attunix}!apollo!peterson_s USPS: Apollo Computer, 220 Mill Rd.,MS: CHM 01 SS, Chelmsford MA. 01824