Group Project

As you can see, the group project is a very important aspect in determining your grade. Typically, teams consisting of 3 to 4 students will be formed, and suggested topics for the group project will be handed out as the semester progresses. You are free to choose your own topics, as long as the instructor approves each project topic and its scope. I encourage you to start thinking about

a) Who you would like to team up with

b) Some candidate topics that you would like to work on

as soon as possible. Feel free to discuss any ideas with the instructor at any time.

In the last week of the course, there will be PowerPoint presentations by each team. Each team will prepare no more than 5 slides, and present the topic to the rest of the class in a 10-minute presentation, followed by 5 minutes of Q&A. In addition to the presentation, the team will provide a live demo in 10 minutes, followed by 5 minutes of Q&A.

The instructor and/or the TA at the end of the course will test the project LIVE.

As the semester progresses, each team will need to fill up the following table:

Team #	Team Members	Captain	Group Project Title	Team Name	Comments
1	Anh Le, Tram Le, Patricia Kehoe	Patricia Kehoe	Air-conditioning shop system	Keep U Cool
2	Ayati Ghosh, Clint Newsom, Christy Ho	Ayati Ghosh	TA-Class Assignment system	The Golden Retrievers
3	Sheryl Anderson, Michael Beam, Casey Bump, Hui Liu	Michael Beam	Personal Media Catalogue System
4	Austin Newton, Amin Ghazi, Nam Nguyen	Austin Newton	Portfolio Tracker System	DATASAPS D elivering A lternative T echniques for A nalyzing S tandard A and P oors S tocks
5	Nicholas Derrett, Sanghamitra Sahu, Trent Smith, Digvijay Choudhari	Nicholas Derrett	Textbooks Auction System	The Java Beans
6	Aditya Soman, Do Kim, Dhiraj Gadia	Aditya Soman	Wholesale store Inventory Management System	WHIMS WH - Wholesale I - Inventory M - Management S - Systems
7	Michael West, William Donohoe, Graciella Phillips	Michael West	Student Course Scheduler System

Each group member will be required to grade his or her respective team members (including themselves) on the following criteria:

a) Participation

b) Completion of tasks on time

c) Attitude

d) Any other comments/mutually agreed upon criteria

These criteria (and any more) will be discussed in the first day of class.

Also, on the due date, each team will submit a project report (in electronic, preferably MS-Word for Windows format, and print format) outlining:

a) The purpose of the project, the audience

b) The team members and their roles

c) Assumptions/Constraints/Requirements going into the design phase (see chapters 6, 7, & 8 for guidance)

d) Different phases of the database design

e) Hardware & Software used to implement the project

f) PowerPoint presentation, if any

g) Source+SQL+Modelling code

h) Table/View/Procedures/Triggers definitions

i) Any other information relevant to running/executing the project on a system

The grade on the project will be determined by

a) Submitted Project Report

b) Team members grading each other

c) Scope/Depth/Features of DBMS etc. of project

d) Design of the project

e) Implementation of the project

f) End of class presentation and LIVE demo

g) Electronic copy of the project

h) Comments in Source+SQL+Modelling code

i) Submitted Project Proposal

j) Submitted Logical Model

Project Proposal Submission

The Project Proposal is a 1-page MS-Word document that highlights:

a) Name of team members (along with team captain)

b) Team Name

c) Project Topic

d) Need/Purpose for doing this project

e) The audience (i.e. users) of the project who will benefit the most

f) At least 5 salient features of this project/system to be built

g) Optionally, requirements (as gathered from the users)

h) Optionally, assumptions, constraints, and functional dependencies

The instructor to more concretely define the scope of the project will then review this project proposal. This proposal is also the starting point for the Project Report to be submitted at the end of the course.

Sample Proposals

Project Proposal 0ne-on-One review with the instructor

Each team will get an opportunity to meet with the instructor for ~ 30 minutes. Along with the project proposal, all constraints, assumptions, functional dependencies will be reviewed in order to attempt defining what part of the “real world” this project is going to model. Be prepared to ask as many questions as you can. Also, write down, as many requirements from your users that you think would be pertinent for the project.

Time Slots:

Each team captain needs to send an email to the instructor, signing up for the appropriate timings (on a first come first serve basis)

Slot #	Date	Time	Team Name	Team Captain
1	2001-10-11 thu	18.00-18.30	The Golden Retrievers	Ayati Ghosh
2	2001-10-11 thu	18.30-19.00		Michael Beam
3	2001-10-11 thu	19.00-19.30		Aditya Soman
4	2001-10-11 thu	19.30-20.00		Michael West
5	2001-10-12 fri	10.00-10.30	The Java Beans	Nicholas Derrett
6	2001-10-12 fri	10.30-11.00	Keep U Cool	Patricia Kehoe
7	2001-10-12 fri	11.00-11.30		Austin Newton
NOTE: All meetings will take place in the instructor’s office.

Project Logical Model Submission

This phase of the project will account for 6% of the course. As part of the deliverables, I expect

a) Project Report (in MS-Word format)

b) ER diagram

The Project Report must include

1) The project proposal that you submitted earlier, with any modifications

2) All functional dependencies, cardinalities of relationships, entities, constraints on these entities, along with appropriate naming conventions

3) Things that you are going to deliver as part of this project

4) Things that you are NOT going to deliver as part of this project, and maybe flag them as future enhancements.

5) Some description of application interfaces (UI screens etc.)-not necessarily complete.

6) Some description of Work Flow for the intended audience. (Use cases)-not necessarily complete.

The Logical Model ER diagram must include

1) Entities, Relationships (along with appropriate cardinalities), Attributes, RI definitions

2) The schema must be in atleast 3NF

No Java code is required to be submitted neither is any SQL code required.

Next Steps:

1) Start thinking of “actions” required on each entity. These actions will dictate your stored procedure and trigger definitions.

2) Stored Procedures and Triggers to implement business rules, constraints, assumptions.

3) For the “Physical”, start thinking about data types.

4) Application Logic.

5) Distributing above work/Implementation Strategy among team members.

Software to be used on this project

Java compiler, Microsoft Access, Oracle, Microsoft Office, JDBC, JSP etc.

Suggested Topics for Group Project

(Most of these topics are taken from Reference c))

1. Design and implement a web-based system to keep track of the exploits of your favorite sports teams in a league. You should store the matches played, the scores in each match, the players in each match and individual player statistics for each match. Summary statistics should be modeled as derived attributes. E.g. UT football team in College football, Dallas Cowboys in NFL. LA Lakers in NBA etc. The web-based system should facilitate enter, update, and viewing of data.

2. Design and implement a web-based publications listing service. The service should permit entering of information about publications, such as title, authors, year, where the publications appeared, pages, and so forth. Authors should be a separate entity with attributes such as name, institution, department, e-mail, address, and home page. Your application should support multiple views on the same data. For instance, you should provide all publications by a given author (sorted by year, for example), or all publications by authors from a given institution or department. You should also support search by keywords, on the overall database as well as within each of the views. E.g. Go to your respective department and see if they would like to do this project for all publications of this department.

3. Design and implement a simple electronic marketplace where items can be listed for sale or for purchase under various categories (which should form a hierarchy). You may also wish to support alerting services, whereby a user can register interest in items in a particular category, perhaps with other constraints as well, without publicly advertising his/her interest, and is notified when such an item is listed for sale.

4. Design and implement a web-based system that permits recording of course performance information-specifically, the marks given to each student in each assignment or exam of a course, and computation of a (weighted) sum of marks to get the total course marks. The number of assignment/exams should not be predefined; that is, more assignments/exams can be added at any time. The system should also support grading, permitting cutoffs to be specified for various grades.

5. Design and implement a web-based system for managing online multiple-choice tests. You should support distributed contribution of questions (by teaching assistants, for example), editing of questions by whoever is in charge of the course, and creation of tests from the available set of questions. You should also be able to administer tests online, either at a fixed time for all students, or at any time but with a time limit from start to finish (support one or both), and give students feedback on their scores at the end of the allotted time.

The following is due for the final project

1. 2001-11-25 8.00 pm (Sunday)

1. Email to the instructor, the electronic copy of the PowerPoint presentation with the following 5/6 slides:

a. Title of Project, Team members

b. Introduction/Purpose/Need/Functionality (Not all of these need to be included)

c. ER Diagram (Logical)

d. UI screen shots

e. Conclusions/Problems encountered in implementation/Team roles/task distributions (Not all of these need to be included)

f. Future Suggestions/Lessons Learned

NOTE: You are free to do more slides, as long as you can do the presentation in 15 minutes.

2. 2001-11-26 8.30 am (Monday)

1. Bound copy of project report brought and submitted in class

a. Must have all electronic material from beginning of project

b. This should include all SQL/Java code, screen shots, diagrams etc.

2. Attendance is mandatory and required in this and next class for all students. If you miss these 2 classes, your whole team will be penalized for some portion of the project.

3. There will be 4 presentations in this class (15 minutes each), with question/answers. Each team captain must decide who is going to present. Which team presents on what day, will be decided in class on 2001-11-19.

4. The class will start at 8.30 a.m. promptly.

5. Email the electronic version of the class project by 8.30 a.m. to the instructor.

3. 2001-11-30 8.30 am (Friday)

1. There will be 3 presentations in this class (15 minutes each), with question/answers. Each team captain must decide who is going to present.

2. After class, we will go to Painter 5.38 Lab for live demo of the project, in the order of team presentations. If you have your demo on laptops, make sure you get it to the class.

3. Attendance is mandatory and required in this class for all students. If you miss this class, your whole team will be penalized for some portion of the project.

The project grade is broken up as follows:

Proposal	4%
Logical Model	6%
Team Grade	2%
Report	6%
PowerPoint Presentation	2%
Demo	10%

Slot #	Date	Time	Team Name	Team Captain
1	2001-11-26 mon	8.45-9.00	The Golden Retrievers	Ayati Ghosh
2	2001-11-26 mon	9.00-9.15	Personal Media Catalog System	Michael Beam
3	2001-11-26 mon	9.15-9.30	WHIMS	Aditya Soman
4	2001-11-26 mon	9.30-9.45	Student Course Scheduler	Michael West
5	2001-11-30 fri	8.45-9.00	The Java Beans	Nicholas Derrett
6	2001-11-30 fri	9.00-9.15	Datasaps	Austin Newton
7	2001-11-30 fri	9.15-9.30	Keep U Cool	Patricia Kehoe

Home Page