You may do this project in teams of 2 or 3. Projects will be evaluated the same, no matter how many people in your group, so it is recommended that you find a partner if you can. (You need special permission from the instructor to do this project by yourself.)
For the final project, you will present a tutorial on a database-related subject that we do not cover in class. Some suggestions:
The tutorial should lay out a story - for instance, don't just say what a stored procedure is (if you choose that option). One way to do this (using stored procedures as an example) is to start with a sample user and explain what they need to accomplish, then walk us through how that person uses stored procedures with some examples. You will likely need to bring a laptop to class - if no one on your team has one, we may be able to provide one, but let us know ASAP. If that also fails, screenshots may be sufficient.
The written component of the project is a write-up of your tutorial. Think of it as a walk-through that you might find on a website or other help site. To follow the stored procedure example, here's what you might provide in your write-up:
· A brief summary of the sample user and what they are trying to accomplish
· A brief description of what a stored procedure is, how it works, and why they are important
· How to create one
· How to alter/delete one
· How to grant/revoke privileges on one
Deadlines:
February 3, 2009: Send Lois Delcambre and Tom Raney a list of who is on your team, and the topic you have chosen. Send this as soon as you can - if more than one team wants the same topic, and combining teams would put you over the 3 person limit, whoever sends their team and topic in first will get preference.
March 3, 2009 (Week 9): Send Lois Delcambre your writeup and a copy of your slides.
March 10, 2009 (Week 10): Deliver your tutorial presentation - maximum length to be determined by the number of groups. You will probably have 15 minutes to present your tutorial.
Rubric:
20%: Intermediate deliverables (team listing and project document)
20%: Presentation does not go over time (10% off for going over by a couple of minutes, 20% off for going way, way over time)
20%: Technology is well-motivated. The presentation includes a sample user or some other scenario that illustrates why the technology is needed (does not need to take more than a minute). The presentation also includes a simple, to-the-point description of what the technology does.
40%: Demonstration is clear and to the point. Demo illustrates the technology in a simple way that shows the basic features without being overwhelming or confusing.