The 2 links below open MS/Word documents. If/when your Browser asks, direct it to MS/Word on your computer or network.
| Instructor | Michael Gordon |
| Office | B3208 |
| Phone | 313-763-9779 |
| mdgordon@umich.edu | |
| Home Page | http://www-personal.umich.edu/~mdgordon/ |
| Fax | 313-936-0279 |
As this goes to press, there is no TA yet (this page will change when
the situation does).
The Lab Consultants are not familiar with Mahogany or the concepts
in this course. Don't ask them about those kinds of things. They should
be familiar with printing issues, network issues, etc.
Expert systems make human expertise available through software. This expertise can be obtained from the world's foremost authority in a given field or can be that of a very experienced clerk whose job performance is the result of years of accumulated experience. Building expert systems involves a new kind of programming (i.e. very different from Pascal, Fortran, Basic, etc.) and expert systems projects require careful management, since businesses do not have a lot of experience to draw on to guide them.
I do not assume you have any familiarity with expert systems. Nor do I assume that you have had previous programming experience. What I do expect is that:
We will be working on Macintosh computers in the Business School Computing Lab. I have arranged that, if you have a Mac (or access to one), you may copy Mahogany and use it on that computer. Of course, this is only for course Ñ not commercial Ñ purposes. If you do not know how to use a Macintosh, please talk to me. Or, if you prefer a DOS environment, I can supply you with a DOS (not Windows) version of Mahogany to use on any machine you choose. The DOS and Mac versions of Mahogany are similar; but the program was written for a Mac, is better on a Mac, and you have the responsibility of adjusting for differences between versions if you choose the DOS route. You will receive Tutorials (that IÕve written) that are Mac-based.
Since this course is dependent on computers (and their ability to be up and running), some adjustments may be made to the course syllabus and contents throughout the term. This may affect the timing of homeworks and other course activities. At various points in the term, a revised syllabus may be issued.
Also, although the UMBS supports the software and network being used for this course, and even though we are using sophisticated computers, nothing that involves computers ever goes as smoothly as planned. Please understand that this may result in certain inconveniences to you. Your responsibility in these matters is to report serious disturbances to the professor as soon as possible. Do not simply tell the lab consultants.
James Ignizio. Introduction to Expert Systems. Available at Ulrichs and other campus book stores. Another attempt for the perfect book. You know what? There isnÕt one. This book is clear regarding most introductory material, thought it will not cover everything we do in the course. Mostly, this book will support what we cover in class, but it also will provide amplification and contrast.
None. A few articles will be passed out throughout the term.
David S. Prerau,Developing and Managing Expert Systems. (In Business
School Library.). This book provides a start to finish examination of a
real-life expert system built by GTE for maintaining telephone switching
equipment. It is especially strong at letting you know how to mange a project
(theirs was one of the largest ESs built, but their experiences apply to
you!). The book has wonderful checklists at the end of chapters to ensure
youÕre on the right track. Use this book as a resource, or for another
point of view. Some chapters assigned.
John Durkin, Expert Systems: Catalog of Applications. (In Business
School Library.). This book contains many examples of both research and
commercially deployed expert systems. It should be especially helpful to
you as you begin to learn about what expert systems can be used for, and
as you choose a topic for the term project. Mahogany Software Manual. (In
Business School Computing Lab). ItÕs there if you like manual-ese.
I donÕt recommend it, but itÕs a source of information
Under ordinary circumstances, the culmination of the course will be your completed, term-long project. To provide you with the skills necessary to complete the project, you will do computer-based and paper and pencil homeworks.
My experience has been that, for a variety of reasons, some groups would prefer to forego the final project. To accommodate these students, an alternative plan of completion is to a) complete 4 graded computer homeworks and substitute a paper for the Final Project. (Details of the paper later in the term.) .
Your group will have the option to do the project or not; your group will either all do the project, or all do the Final Paper. The Final Paper will be group written.
| Final Project | Final Paper | |
| Computer assmts
(2 or 4, resp.) |
10 | 20 |
|---|---|---|
| Paper and pencil
assmts |
5 | 5 |
| Proposal | 10 | 10 |
| Prototype | 20 | 20 |
| Final Exam | 20 | 20 |
| Fianl
Project / Paper |
40 | 25 |
| Total | 105 | 100 |
Please Note: There are some important skills youÕve got
to pick up along the way if you are to produce a Final Project that reflects
your best work. The paper and pencil and computer assignments will ensure
you have some of these important skills. Generally speaking, the assignments
should be fairly easy to complete (especially the non-computer assignments)
and, they can let us both know youÕre having some difficulty so
we can correct it before itÕs too late.
Teams vs. individual work: You will be working on your project (all
phases) on a team of 3 people. I will let you choose your team. Each
team member will each receive the same grade on all team submissions, and
I will ask for peer evaluations at the term's end, which can adjust
points earned.
On homework assignments, you may discuss, collaborate, and even
turn in one assignment representing a group of (2-3) students (not necessarily
the same group as your project). My feelings are that a) you learn a lot
from each other, so discussing and collaborating is not cheating; b) you
should all get (close to) 100% on these homework assignments.
Final exam: This you do by yourself.
Latework: On-time work: 100% * points earned. 2 1 class late: 80%
* points earned. Later than that, no credit. Extenuating circumstances
may apply.
Grade Distribution: This is not a core course. No grade distribution
is prescribed. This means that this class is not about competition-it
is about learning, enjoying, experimenting, and exploring. You'll get out
of the course what you put in!
You are expected to do much out-of-class work and exploration in order to get up to speed on the required computer applications and concepts. If this were a class teaching you how to play jazz piano, you'd have to explore like crazy to until you truly absorbed what was being taught and "made it your own." Approach this class with the same spirit of creativity and exploration.
You are expected to come to all lectures and all labs. In each class, time for questions and answers will be provided. If you are uncomfortable asking questions in the class, you are encouraged to e-mail the question to the professor (through UMCE) any time before the class. I will attempt to answer such questions (without identifying the questioner) in front of the class (if warranted), or one-on-one after class, during office hours, or by e-mail. Of course, this is not to discourage a high degree of in-class participation.
I use e-mail to communicate with the class. You should check it every day during the semester.