Minimal Project Requirements:

In general, two types of projects are acceptable:  1) a project that does an extensive analysis of a novel application domain resulting in a comprehensive object and functional model specification but no implementation or 2) a project that has a relatively simple object model specification (textbook type class diagram) but has a relatively comprehensive functional model, system design and implementation.  Alternatives are permissible but require a detailed proposal submitted as soon as possible.

Students who are interested in implementation and have an interest in evolving tools and techniques are strongly encouraged to explore implementation using OWL and an accompanying query language (Prolog, Java, C/C++).  Those having an implementation interest but wishing to gain some experience with "nuts and bolts" tools may use MicroSoft Access, SQL, and some host language (Java, C/C++) for implementation.  Alternative implementation platforms are OK.

All UML class diagrams must be developed using Rational Rose (available in ET 312).

Grading:

70% of the grade will be based on the document preparation including conformation to requirements, clarity, organization, grammar, attention to detail, and incorporation of recommendations as discussed in class.  30% of the grade will be based on the originality of your work and the suitability for expanding it for future efforts.

Report Format:

Final report must be double spaced using at least 11-12 pont font and include a title and abstract.   A suggested outline of the final report is shown below:

I. Conceptualization

II. Analysis

    a) Problem Statement

    b) Object Model Construction

    c) Data Dictionary

    d) Functional Model including Use Cases and ONN  for Operations

III. System Design

IV. Detailed Design

V.  Implementation

VI. Appendix [optional contents]

         Instructions for running application

         Source Code