Department of Computer Engineering
(Assoc. Prof. Dr. Atilla Elçi)
(Revised on 25 April 2008)
This guide states the term project (TP) in terms of its requirements, process of its evolution, grading, and reminder of important due dates.
1. Each student is expected to work out, report and present a term project in partial fulfillment of the requirements of this course. Term project is worth 35 points out of 100 for the course.
2.
Term project concerns the implementation of a semantic Web technology
information system commensurate with this course’s content and in agreement with
the contract to be enacted between the instructor and a student.
Specifically, a student is expected to:
a. Locate a best practice method and/or toolset for implementation of an ontology-based information system. Alternatively, a student may actually prepare a method / toolset usable in developing an ontology-based application.
b. Port it to run locally on our systems here in EMU/CMPE.
c. Pick a topic and evolve own ontology-based information system;
d. Devise and execute exemplary tasks of the topic. Display outcome to show that the implementation runs properly.
e. Compare results against that of “non-semantic web” implementations,
f. Prepare a term paper report,
g. Do an oral presentation and live demo of the term project.
3. The subject of the term project must relate to this course’s content. Specifically, the following subjects are to be included in any case:
a. Ontology: OWL or an extension
b. Semantic annotation
c. Semantic info access
d. Web front end
e. Backend support: a reasoner-based system (imported or used remotely) or at least an editor
f. ?
Contact the instructor if in doubt.
4. Student is free to choose the term project topic or its application area. See below for consultation needs.
5. In terms of effort required to bring about, a term project should be worth about 6-8 weekly homework assignments. In exceptional conditions such as taking considerably longer to prepare and expected to be highly difficult, a term project may be done by two students. If so, each student’s part will be clearly identified; parts must be mutually exclusive of each other; and, students shall prepare, report, and present their parts individually. However, there will be a single integrated report and presentation nevertheless.
6.
Term project of CmpE 588 is an individual responsibility requiring
essentially original work. Concept of the term project, overall design and
execution MUST be uniquely done by the student. Naturally, the backend system
and/or the toolset are to be borrowed complete with its implementation platform.
Selection of the application area of the TP, implementation platform, and tools
are up to the student.
It is alright to benefit from others creation in enhancing the functionality,
sophistication, and look-and-feel of the term project as long as proper credit
is given. These may be small code pieces such as scripts; graphical elements
such as icons, images, art work, sound pieces, or other enhancements to enliven
your term project, report, demo and presentation.
The process of contracting a TP will be as follows:
1. Student proposes a term project in writing. Proposal is a one-page paper format report identifying the following as clearly as feasible:
a. Term project title: as descriptive as possible
b. Name of student (or of the team members),
c. Summary of the case,
d. Summary of the proposed term project,
e. Summary of the expected findings,
f. Platform, tools and technologies to use,
g. Completion and Success criteria.
2. Instructor evaluates a proposal individually. The outcome could be “Approved”, “Rejected”, “Needs Rework”.
a. “Approved” means that the proposal has received clearance to carry out. An approved proposal is countersigned by the instructor and returned to student.
b. “Rejected” means that the proposal was judged totally unsuitable. Student then can propose another term project. Carrying out and submitting a rejected term project involve major risk of getting considerably lower grade.
c. “Needs Rework” means that the term project was judged suitable but the proposal is found deficient; reason and source(s) of deficiency will have been indicated. Such a proposal may be reworked to get rid of its deficiency and then resubmitted. There is no limit to the number of times a term project proposal may be resubmitted. Carrying out and submitting a proposal that is not approved by the instructor involves risk of getting lower grade.
3. Student carries out the term project and prepares a term project report.
4. Term project report content will be similar to that of the graduation project but probably much shorter. Check CmpE 401 Course Website for guidance on reporting requirements. A term project report would normally be not more than 15 pages excluding cover, references and appendices. Soft copy of the report is to be provided together with the report. Additional guidance may be provided on this aspect later.
5. Student will present the completed term project. Presentation will involve an oral explanation of issues such as the case, term project configuration, technologies used, etc., demonstration of findings, and a live demo. Total duration of presentation including demo and Q&A may not exceed 30 minutes.
6. Presentations will be open to all concerned faculty and students alike from all departments. To help schedule individual talks, an “Ontology-Based Information Systems Day” seminar event is being organized. Schedule will be announced separately. Venue will be the departmental amphitheater. Demo of the term project and presentation slides as well will be made available.
TP will be judged and graded in the following:
1. Technical content vis-à-vis the contract.
2. Project report itself
3. Presentation.
1. Submitting proposals: any time from now on, but earlier the better.
2. Final date for clearance of proposals: May 15th, 2008. No proposal clearance will be given after this date.
3. A draft report may be turned in any time until May 30th, 2008. Draft reports will be reviewed, commented on and returned. No grade point is granted for draft reports.
4. Final report is due by June 4th, 2008. Final reports will be reviewed, graded and kept. A final report may be accepted after due date without grade.
5. Presentations are on June 6th, 2008. Mode and place of the presentation are mentioned above.
6. The above dates may be readjusted depending on the class’ preference.