Group Project

As you can see, the group project is a very important aspect in determining your grade. Typically, teams consisting of 4 to 5 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

c) Team captain (chosen on a volunteer basis with full team consensus)

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
1	Simeen Zubairy Sudeep Potharaju Shobana Sankaran Pavithra Prasad Cyrus Murphy Prabhjot Kaur	Simeen Zubairy	A database for Philip Tucker’s Lab located in ESB 532.	DNA Packers
2	Clare Riviello Brandon Zinn Nick Leger Michael Larson Marcia Hoelting	Clare Riviello	A database for “Foundation For the Homeless”, a private non-profit corporation that specializes in working with homeless families.	Group 2
3	Angela Crosby Mark Hallbauer Anuj Timblo Sahil Kamdar Sahir Sait	Sahir Sait	A dynamic database that will enable the user to efficiently maintain and organize all music/sound related files so that queries and searches can be made on the basis of attributes that are relevant to the particular file (e.g. file extension, artist name, music genre etc.)	Shadow Platypus
4	Sri Hartati Stephen Sclater Gordana Westmoreland Mary Kay Barber	Sri Hartati Stephen Sclater Gordana Westmoreland Mary Kay Barber (On rotating basis)	A database for the Study Abroad Office to use to collect and track application materials for UT Students applying to participate in study abroad programs.	UTSAS
5	Saahil Malik Traci Thibodeaux Li Ma Sabina Malik Tabassum Khan	Tabassum Khan	On-line database management system for Quality Management Consortium (QMC), UT	The Union
6	Eric Lyons Lisa Gahagan Binh Vu Louisa Grecieca Yan Xia	Eric Lyons	To put online a collection of references on the topic of shear-wave seismic studies, allowing the user to search various attributes.	Geradeaus
7	Jide Osifekun Brandon Albano Brian Sprawka Jason Anderson	Jason Anderson	A database for tracking the instructional resource materials of the Learning Technology Center on the fifth floor of the Sanchez building.	ACQUIRE (ACcess QUick Information Resources Efficiently)
8	Indhumathi Setlurraghunathan Balaji Vijayan Venkatesh Tanuku Sanjeevkumar Uruvandavida	Indhumathi Setlurraghunathan Balaji Vijayan Venkatesh Tanuku Sanjeevkumar Uruvandavida (On rotating basis)	We are planning to work on a database for a library (PCL).	Noolagam
9	Richard Cherico Erinc Albey Stephen Jordan Ahmed Asheq Mahmud Medha Joshi	Richard Cherico	Design a database system for a dermatologist office that can track patient data including visits, diagnoses, treatments product sales and service billing.	Scabies
10	Nick Gallardo Emily Starnes Derek Burgess Matt Greenfield	Nick Gallardo	The focus of this project is to build a database and interface that will facilitate management of events for non-profit organizations.	Events Tracker 1.0
11	Amir Thapa Dhruv Gajaria Vinu Kuriakose	Vinu Kuriakose	To provide a database for buying and selling tickets for a wide range of recreational and art events.	BevoTickets
12	Olin Bjork John Ward David Fisk Jimmy Rice	John Ward	A database to track the fields of study, areas of expertise, and contact information of faculty at UT and graduate degree holders from UT.	Connect2UT

Each group member will be required to grade his or her respective team members (excluding 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, including all the DDL

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

k) Submitted DDL

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.

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	Group Name	Team Name
1	2002-02-22 Fri	10.15 am	Group 2
2	2002-02-22 Fri	10.45 am	Group 1
3	2002-02-24 Sun	12.30 pm	Group 4
4	2002-02-24 Sun	1.00 pm	Group 11
5	2002-02-24 Sun	1.30 pm	Group 7	ACQUIRE
6	2002-02-24 Sun	2.00 pm	Group 10
7	2002-02-24 Sun	2.30 pm	Group 9	Scabies
8	2002-02-24 Sun	3.00 pm	Group 8
9	2002-02-25 Mon	6.00 pm	Group 3	Shadow Platypus
10	2002-02-25 Mon	6.30 pm	Group 6	Geradeaus
11	2002-02-25 Mon	7.00 pm	Group 5	The Union
12	2002-02-25 Mon	7.30 pm	Group 12	Connect2UT
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. This must include things that you are going to deliver as part of this project as well as, things that you are NOT going to deliver as part of this project, and maybe flag them as future enhancements. I.e. Phase II etc. You do want to show that you have thought through some of the issues beyond the project, but in interest of time, you may not be able to achieve those.

2) All functional dependencies. The schema must be in atleast 3NF, otherwise, explicit reasons need to be stated as to why your schema is not in 3NF. Preferably, submit functional dependency diagrams similar to lab2.

3) Some description of application interfaces (UI screens etc.)-Not necessarily complete.

4) Some description of Work Flow for the intended audience. (Use cases)-not necessarily complete. Work Flow includes the UI screens, including the order in which a user will navigate through the screens to achieve a certain task. Each such “navigation path” is deemed a use case. E.g.

1. “search for a book by title on www.amazon.com” is a use case that probably comprises of 3 or 4 UI screens (in some particular order).

2. “buy a book on www.amazon.com” is another example of a use case.

The Logical Model ER diagram must include

1) Entities, Relationships (along with appropriate cardinalities), Optional / Mandatory, Weak / Strong entities, Attributes, RI (Referential Integrity) definitions i.e. PK (Primary Key) and FK (Foreign Key) attributes need to be clearly labeled.

No Programming language 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.

Project DDL Submission (Physical Model definition)

This step consists of submitting all the SQL statements required to

a) Create tables

b) Create views

c) Create referential integrity

d) Create indexes

e) Create users

f) Create privileges

g) Create stored procedures

h) Create triggers

i) Any other settings required for transforming the logical model into the physical.

From the above, the required DDL are

a) Create tables

b) Create referential integrity

c) Create stored procedures (only the header, and not the SQL statements contained in it).

For example, if your stored procedure looks like

CREATE PROCEDURE titles_sum @TITLE varchar(40) = '%', @SUM money OUTPUT

AS

SELECT 'Title Name' = title

FROM titles

WHERE title LIKE @TITLE

SELECT @SUM = SUM(price)

FROM titles

WHERE title LIKE @TITLE

Then, what you need to submit is

CREATE PROCEDURE titles_sum @TITLE varchar(40) = '%', @SUM money OUTPUT

With some English description of what this procedure is supposed to do (similar to the description of Q4 on Test 2).

d) Create triggers (only the header, and not the SQL statements contained in it).

The rest of the DDL is optional, but dependent on your project i.e. if your project requires creating users, and privileges, then submit the DDL for doing so.

For the project, VIEWS and INDEXES will be considered for bonus points.

The following is due in the last 2 weeks of the final project

3. 2002-04-19 5.00 pm (Friday)

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.

4. 2002-04-22 8.30 am – 10.00 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 3 classes for all students, when presentations are going on. If you miss these 4 classes, your whole team will be penalized for some portion of the project.

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

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.

5. 2002-04-26 8.30 am – 11.30 am (Friday)

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

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

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

6. 2002-04-29 8.30 am – 10.00 am (Monday)

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

2. 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.

7. 2002-05-03 8.30 am – 11:00 am (Friday)

1. We will meet in PAI 5.38 (instead of the class room) 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 lab.

NOTE: The class time meetings during the last 2 weeks are mandatory for everyone ONLY for presentations. In other words, when the presentations are going on, everyone must be present in class irrespective of whether your team is presenting or not.

For the DEMO, ONLY the team members who are giving the demo at a given time slot need to be present for the demo. The rest are most welcome to attend, but optional.

The team captains need to send me the slot #s for their team for demo and presentation.

Presentation time slots:

Slot #	Date	Time	Team Name
1	2002-04-22	8.45 am	Geradeaus
2	2002-04-22	9.00 am	ACQUIRE
3	2002-04-22	9.15 am	Events Tracker 1.0
4	2002-04-22	9.30 am	Shadow platypus
5	2002-04-26	8.45 am	Group 2
6	2002-04-26	9.00 am	UTSAS
7	2002-04-26	9.15 am	BevoTickets
8	2002-04-26	9.30 am	Scabies
9	2002-04-29	8.45 am	DNA Packers
10	2002-04-29	9.00 am	Noolagam
11	2002-04-29	9.15 am	The Union
12	2002-04-29	9.30 am	Connect2UT

Demo time slots:

Slot #	Date	Time	Team Name
1	2002-04-26	10.15 am	Group 2
2	2002-04-26	10.30 am	Shadow platypus
3	2002-04-26	10.45 am	ACQUIRE
4	2002-04-26	11.00 am	Events Tracker 1.0
5	2002-05-03	8.45 am	Geradeaus
6	2002-05-03	9.00 am	UTSAS
7	2002-05-03	9.15 am	Scabies
8	2002-05-03	9.30 am	Connect2UT
9	2002-05-03	9.45 am	Noolagam
10	2002-05-03	10.00 am	The Union
11	2002-05-03	10.15 am	BevoTickets
12	2002-05-03	10.30 am
13	2002-05-03	10.45 am
14	2002-05-03	11.00 am	DNA Packers

The project grade (for all teams) is broken up as follows, with percentages and due dates:

Project Phase	% of total grade	Due Date
Proposal	2%	2002-03-01
Logical Model	6%	2002-03-08
DDL	4%	2002-04-01
Team Grade	2%	2002-04-19
PowerPoint Presentation	4%	2002-04-19
Final Report	6%	2002-04-22
Demo	6%	2002-04-26

Software to be used on this project

Java compiler, Oracle, Microsoft Office, JDBC, ODBC, JSP, ASP, ADO, SQL Server, PHP, mySQL, IIS, Apache etc.