Fall 2002 Programming Language Seminar:
Aspect-Oriented Programming with AspectJ
Back to main course page

Final Project Schedule

Wednesday, 20 November 2002

1:00pm - 1:20pm

Bicycling Simulation

Sharath Cholleti

1:20pm - 1:40pm

Blackjack

Jonathan Hseu

1:40pm - 2:00pm

Aircraft design & analysis tool

Tim Gatzke

2:00pm - 2:30pm

Filesharing & messaging application

Ben Oberkfell and Dylan Lingelbach

Wednesday, 4 December 2002

1:00pm - 1:20pm

Proxy server

Adam Mitz

1:20pm - 1:40pm

Web browser

Delvin Defoe

1:40pm - 2:10pm

PCESGraph/Clazzer enhancements

Marty Linenweber, Anand Krishnan, and Guoliang Xing

2:10pm - 2:15pm

Demo: Bicycling Simulation

Sharath Cholleti

2:15pm - 2:20pm

Demo: Blackjack

Jonathan Hseu

2:20pm - 2:30pm

Wrap-up, course evaluation, etc.

The presentation times above are intended to be approximate. I plan to supply a networked Windows laptop and projector on both presentation days. You will probably want to prepare a few slides to show the structure of the classes and aspects in your program, demonstrate your program, and show some interesting pieces of code (e.g., aspects in your program that can be reused), although the content of your presentation is up to you. For a 20-minute presentation above, try to shoot for 14-16 minutes (not including setup time) to give time for questions and any unforeseen technical difficulties.

Some suggestions for the presentation (these are only suggestions, and please don't limit yourself to these if you have something else that you'd like to talk about!):

Build a few different configurations (by weaving in different configurational aspects) and show their difference (e.g., network vs. non-network, GUI vs. non-GUI, applying different policies or rules, etc).
Talk about your experience with AspectJ (or AOP in general); what features would have been helpful that AspectJ didn't provide?
If you have modified your aspect design while coding, talk about your initial designs and why you switched.
What intertype dependencies are there? Do aspects "know too much" about classes? Do classes "know too much" about aspects? How reusable are different parts of the system? How do aspects help in this regard?
Were the development tools (ajbrowser, IDE support, etc.) useful? What pointcuts (if any) did you have to rewrite because they were applying to too many join points, causing an efficiency problem? (Or weren't applying where you thought they were, causing problems?)

Since there are two weeks between the two sessions scheduled, it is understood that projects presented the first week have had less time for design, coding, debugging, testing, and enchancement.

Please let me know if you have any questions or if I've goofed on the ordering of presentations (as decided last week in class by lottery).

Morgan Deters / About me / OpenPGP Public Key / 02 Jan 2006