BIS 2040 Resit Course Work

Resit students may either do the normal coursework or the project described below. NB: the normal coursework starts in the lab in the second week of the course.

The assignment for the module is as follows:
You are to build a Knowledge Based System using Clips, or Caspian. It will contain knowledge from a domain of your choosing, and will include rule-based reasoning (either forward chaining, backward chaining or mixed), or case-based reasoning. Approval for your chosen knowledge domain must be obtained from the module tutor, to ensure that the domain is suitable. Your coursework, when handed in, should include a floppy disk containing the finished system.

In past semesters we have made it mandatory that you select your own domains. This was to force you to explore the knowledge engineering issues. While we would prefer you to choose your own domain, we have provided several example domains below; it is unlikely that you will recieve a first class mark if you use these domains, but they should give you an idea of a minimal system.

Marking scheme:

1. The Program Runs (up to 20).
2. Sophistication and Extent of Knowledge Base (up to 25 marks)
3. Extent to which the system performs a useful function (up to 15 marks)
4. Discussion of why this particularly domain is appropriate for the type of expert system you used. (up to 10 marks)
5. Description of the knowledge acquisition process. A sample taken from a published source of the knowledge or an interview transcript are useful. (up to 10 marks)
6. Description of rules or cases and data items (up to 10 marks)
7. Descriptions of "successful" and "unsuccessful" program runs, including sample output. (up to 10 marks)

Some notes on the above marking scheme:

• "Extent to which the system performs a useful function" - a trivial application will get less marks than an application that someone (in the real world) might actually get some benefit from. Also, marks may be deducted for lack of validity in the knowledgebase: in other words, if relevant features of the domain knowledge have been ignored, or distorted, or invented, in the process of turning them into components of the knowledgebase, this may result in loss of marks.
• "The extent of the knowledgebase" - a knowledgebase containing, say 8 rules, will get rather poor marks in this category (10 marks). One containing, say, 24 rules will get rather high marks (18), assuming the rules are useful. Beyond a certain point, however, no more marks will be awarded, so it is not worth devoting time to producing an enormous rule base. Also note that one rule can do the work of several other rules. This is reflected in the sophistication of the rule base.
• "The sophistication of the knowledgebase". Partly, this is the extent to which the features of the package are employed to produce an effective reasoning system. But it is also true that a more ingenious or original system will obtain more marks than a less ingenious or original system.
• "Description of rule or cases and data items" - I want a chart describing the knowledge, and the reasoning that it supports. For example an and-or chart for a backward chaining system, but you may choose another form of representation if you feel it to be more appropriate. There is no need to include a listing of the rules or the case base as you'll submit that on a floppy.
• "Description of successful and unsuccessful runs" - this describes runs of the system you submit. There is no need to describe problems you had while developing the system. Moreover, you should describe the system so that the run can be replicated.

Deadlines

Project handed in to Student Office (end week 11)

Where to submit

• Clips Projects
  1. Tic-Tac-Toe
  2. Plant Identification
  3. Bag Packing
  4. MS Word Ruler Help Desk
  5. Engine Diagnosis
  6. Dormitory Assignment
• Caspian Projects
  1. Gift Selection
  2. University Program Selection
  3. Bag Packing

There's a sample cover sheet on the next page - feel free to copy it and use it on your assignment, inserting your details. Your assignment, including cover sheet, write-up and program on floppy disk, must be submitted to the student office where it will be dated and receipted. You should keep your receipt - it is for your own protection. Do not hand written assessed coursework direct to your tutor. Your assignment should normally be handed in on the campus at which the module is being taught (e.g. Hendon); if for any reason you have to hand it in at another campus, please point this out to the student office so that it can be sent to the correct campus. If, in an emergency, you have to send in written assessed work by post you must send it by recorded delivery to the appropriate student office and keep the Post Office receipt. It will be deemed to have been submitted on the date of the postmark.

Receipts for work submitted outside opening hours can be collected from the student office.