Semester: Spring 2004 Room: 2145 NH Time: 3:30 - 4:45 PM, TR
Students will work in teams on a major database development project.
Database development principles, tools, and techniques are stressed.
Prerequisite: CS 4722 with a grade of "C" or better..
Students will develop and demonstrate their abilities to work in a team
on a substantial software project. There are three conceptual parts to
the project efforts expected of each team:
1. Define the problem
2. Design and implement a solution
3. Deliver the system to the customer and/or the instructor.
Intensive team-based project experience in the specification, design, and implementation of database systems. Projects will be done by teams of four or five students (if class size permits). The faculty advisor (the instructor) will meet with the team on a regular basis to monitor progress, make sure the team is following a coherent process, and assist with team organizational problems. Each team will present a midterm report and a final demo and report to their advisor, their customer (if applicable), and the rest of the class.
Requirements Document
Details: TBA
Project Plan
Details: TBA
Design Document
Details: TBA
Weekly Progress Reports
Each team is required to submit a weekly progress report stating the tasks worked
on, tasks accomplished, problems faced, team members contribution and time spent.
Weekly progress reports can be submitted in person or electronically.
Midterm Presentation
These presentations are meant to provide a progress report and to make sure that
the team has a clear view of the current status and plans for the project.
Each presentation should include at least the following components:
1.A concise statement of the goal or vision for the project and a brief
description of the requirements derived from the goal.
2.What has been accomplished so far.
3.What the schedule looks like for the rest of the term.
It is strongly suggested that your schedule should be for an iterative
development approach, so this presentation should include you plans for
development iterations. Remember also that a good test plan should be
executed on anything that is implemented, so your schedule should include
a realistic amount of time for testing.
4.A discussion of any problems or risks the team is facing.
Everyone on the team must have a part either in this presentation and/or the
one at the end of the term.
Final Presentation
Each presentation should include at least the following components:
1.A concise statement of the goal or vision for the project and a brief description
of the requirements derived from the goal.
2.A description of what you accomplished during the semester and a demonstration,
if feasible.
3.A discussion of how well the results matched your initial plan, including the
reasons for any significant deviations from the plan.
4.A few words about what you learned from this experience.
Since everyone on each team is supposed to do a part of one of the two presentations,
be sure that the team members who didn't present at mid-term do the major part of this one.
It's ok for someone to be part of both, but not as the primary presenter.
Delivering the Project to your Customer
The final requirement for the semester includes scheduling a meeting of the whole project
team with the customer. Attendance by the faculty advisor at this meeting is strongly
encouraged, but not required. The agenda for this meeting should include:
1.A brief presentation of what you have accomplished relative to the requirements,
probably taken from your final presentation to the class. This presentation need
not be a formal, stand-up one unless your customer is actually a group.
2.A demonstration of the operation of your software to the customer.
3.An opportunity for the customer to try out the software.
4.Discussion with the customer of the strengths, weaknesses and opportunities
for extension of the software.
5.Hand over of the source code and documentation of the software. Remember that
documentation can include such things as test results, in addition to a user
manual that describes the features of your system.
Evaluations
Each team member will complete a set of self and peer evaluations for each team member.
You will be asked to evaluate the effort and performance of the individuals in your group.
This feedback will be a significant factor in determining an individual's grade.
Oracle9 MS SQL Server E-mail Internet Browser
You may need to have a number of books to implement your appication.
Fundamentals of DATABASE SYSTEMS, Elmasri/Navathe. Database Stystems - The Complete Book, Garcia, Ullman, and Widom Oracle Documentation
The grades for the course will be assigned based on the following
percentages:
. Project (Team grade) 40 %
. Project (individual grade) 20 %
. Documentation, progress reports, etc. 20 %
. Presentation, attendance, and class participation 20 %
Said C. Fares Office: 2132 Nevins Hall Traditional Office Hours: 10:45 AM - 11:45 TR or by appointment Electronic Office Hours: Any day, any time E-mail: sfares@valdosta.edu Phone: (912) 333-5780
January 12: First Class Day January 19: MLK March 5: Mid-term April 5-9: Spring Break May 3: Last Class Day May 4: Exam Preparation Day May 5: Demonstration (Thursday, 5:0 pm - 7:00 pm)
Last update January 12, 2004