Group Project

 

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

- Who you would like to team up with

- Some candidate topics that you would like to work on

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

 

Project Phases

 

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

 

Project Phase

% Of total class grade

1

Proposal

2%

2

Logical Model

6%

3

DDL

4%

4

Team Grade

2%

5

PowerPoint Presentation

4%

6

Final Report

6%

7

Demo

6%

 

Each of these phases is described below.

Project Phase 1: Proposal

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

 

Team #

Team Members

Captain

Group Project Description

Team Name

1

Prasad Natarajan

Rajalingam Alagesan

Dinesh Natarajan Mohan

Sriram Ramamurthy

Prasad Natarajan

The project will serve to meet the database requirements of the UT Child Care Center (UTCCC). The objective of this project is to automate the processes and make them web-based wherever required.

MEDICARE (Mechanical Engineers’ Database for Infants’ CARE)

2

Xiao Zhang

Brian Kowalski

Michael Wright

Cameron Aderhold

Michael Wright

Develop a web interface for online registration where the database would be used to keep track of all aspects of MBU such as scouts’ info, teachers’ info, class times and places, scout registrations, etc.

The Leftovers

3

Hector Oropeza-Salas

Allan Arditti

Hector Oropeza-Salas

This project will handle all the information regarding the residents of Castillian Dorm, such as Personal information, parents information, financial status, assigned room, discipline, bike/car parking, meal plans, leasing, mailboxes and maintenance orders.

Castillian ITS

4

Will Arthur

Will Berger

Jeremy Sulak

Jody Urbanovsky

Will Berger

Design a database to help in the overall business operation of a local skating rink.

WJG Database Enterprises

5

Daniel Chin

Brian Zavala

Janice Liu

Ross Perkins

Tom Hurley

Tom Hurley

Design a library system.

Thriller

6

Fred Forster

David Pfahler

Jimmy Tran

Fred Forster

David Pfahler

Jimmy Tran

Our group will be writing a database that can easily be adopted by the UT Intramural Sports department. This tool will help easily organize the Intramural Leagues.

DatabaseBall

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

 

The instructor 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 One-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

1

2003-10-17

08.00am-08.30am

Thriller

2

2003-10-17

08.30am-09.00am

The Leftovers

3

2003-10-17

09.00am-09.30am

Cinematix

4

2003-10-17

09.30am-10.00am

MEDICARE

5

2003-10-17

10.30am-11.00am

WJG Database Enterprises

6

2003-10-28

06.00pm-06.30pm

DatabaseBall

7

2003-10-28

06.30pm-07.00pm

Castillian ITS

NOTE: All meetings will take place in the instructor’s office.

 

Project Phase 2: Logical Model

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

 

The Project Report must include

a)      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.

 

b)      All functional dependencies. The schema must be in at least 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.

 

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

 

d)      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. “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). “Buy a book on www.amazon.com” is another example of a use case.

 

The ER diagram must include

a)      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. Use IDEF1X notation if possible, otherwise Extended ER notation.

 

No programming language code is required to be submitted; neither is any SQL code required.

 

Next Steps:

 

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

Stored Procedures and Triggers are required to implement business rules, constraints, and assumptions.

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

Application Logic.

Distributing above work/Implementation Strategy among team members.

 

Project Phase 3: DDL

This step consists of submitting all the SQL statements required to

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

 

From the above, the required DDL are

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.

 

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, any VIEWS and INDEXES will be considered for bonus points.

Project Phase 4: Team Grade

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

 

 

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

Each member will submit a cumulative score (out of 100) for their respective team members and mail them to me confidentially.

Project Phase 5: PowerPoint Presentation

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

 

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

 

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

 

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

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

 

Attendance is required/mandatory during ALL presentations. If you miss these classes, your whole team will be penalized for some portion of the project.

 

Each team captain needs to email the instructor as to when his or her team would like to present.

 

Presentation time slots:

Slot #

Date

Time

Team Name

1

2003-12-01

8.45am

Thriller

2

2003-12-01

9.00am

MEDICARE

3

2003-12-01

9.15am

The Leftovers

4

2003-12-01

9.30am

WJG Database Enterprises

5

2003-12-05

8.45am

DatabaseBall

6

2003-12-05

9.00am

Castillian ITS

 

Project Phase 6: Final Report

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

 

Bound copy of project report must be brought and submitted in class on the due date. In addition, an electronic copy needs to be emailed to the instructor.

Project Phase 7: Demo

In addition to the presentation, the team will provide a live demo in 10 minutes, followed by 5 minutes of Q&A. All demos will take place in the lab.

The instructor and/or the TA at the end of the course will test the project LIVE. During the team demo, all team members of the team giving the demo are required to attend. If you miss this class, your whole team will be penalized for some portion of the project. The attendance of the rest is optional. If you have your demo on laptops, make sure you get it to the lab.

 

Each team captain needs to email the instructor as to when his or her team would like to give the demo.

 

Demo time slots:

Slot #

Date

Time

Team Name

1

2003-12-05

9.30am

Thriller

2

2003-12-05

9.45am

MEDICARE

3

2003-12-05

10.00am

The Leftovers

4

2003-12-05

10.15am

WJG Database Enterprises

5

2003-12-05

10.30am

DatabaseBall

6

2003-12-05

10.45am

Castillian ITS

 

Project Grade Calculation

The grade on the project will be determined by

§         Submitted Project Report

§         Team members grading each other

§         Scope/Depth/Features of DBMS etc. of project

§         Design of the project

§         Implementation of the project

§         End of class presentation and LIVE demo

§         Electronic copy of the project

§         Comments in Source+SQL+Modelling code+GUI code

§         Submitted Project Proposal

§         Submitted Logical Model

§         Submitted DDL

 

 

Finally,

You must read the following sections from Dr. Debra Richardson’s URL:

http://www.ics.uci.edu/~djr/classes/ics125/project.html#coordination

Most of what is said in these sections is also applicable for this course.

 

Sample cs327e Group Project Reports from Previous Semesters

 

 

Last Updated: 11/3/2003 10:06:08 PM