Guideline For Students
of Independent Study, Thesis and
Capstone Project
under Dr. K. Yue's supervision
by K. Yue
January 11, 2001
General Information
-
Taking a project course is not a good route
for an easy grade. Be prepared to work harder than a regular course.
-
Benefit of a project course:
-
More realistic environment allows you to gain useful practical experience.
-
Direct supervision from me.
-
Potentially allow you to submit a paper or article externally.
-
Add to your resume.
-
If you are interested, you should schedule an appointment with me for an
interview as soon as possible. I will only supervise good student
swith the right background, skill and altitude for the selected projects.
Topics
-
Currently, my research interest is mainly in Internet
Application Development, database and computer science education.
-
For applied projects, I am especially interested
in the following areas:
-
XML/XSL development.
-
Java, J2EE, Servlet and JSP.
-
Wireless Internet development using WML, WMLScript,
VoXML, etc.
-
Server-side Web development
-
Web security
-
Web performance
-
For more theoretical topics, I am interested in concurrent
programming, real-time systems and artificial intelligence.
-
However, Drs. Davari and Leibfried are better choice
for projects in real-time systems.
General Requirements
-
Collect all information (technical papers, articles, program listing, etc.)
in a binder to submit with your final report at the end of the semester.
This binder will not be returned.
-
Set up a Web page for easy access to all resources you collected and created
for the project.
-
Email to me your contact information: name, email address, phone, address,
SS#, semester, computer ticket number, topic title, work information (if
working), etc.
-
Reasonable documentation standard should strictly be followed for programming.
For examples, use javadoc for Java program and POD for Perl.
-
Usually, you will be expected to write a technical article to be submitted
externally. This may be used to replace the final report.
Technical Meeting
-
You are responsible for scheduling a weekly meeting with me.
-
The technical meeting is for you to discuss your project with me.
You can raise technical questions during the meeting.
-
The meeting will usually last 15 to 60 minutes.
-
You will need to report the progress you have made in the week.
-
I will raise technical questions in the meeting. Be prepared to answer
them. If you cannot answer the questions, that will be fine.
Just prepare to answer them in the next meeting.
Tips
-
Make sure you understand the objective of the project at the beginning
of the semester.
-
Make sure you have the necessary resource for your project as soon as possible.
-
Make sure that you are in full speed at the beginning of the semester.
-
Perform a thorough literature search.
-
Use software engineering concepts and tools through out the entire project.
-
Target your publication source as early as possible.
-
In case of doubt, ask as soon as possible.